Decommission Notice: msg-mongod

What is msg-mongod?

It is a shared legacy database infrastructure, intended to be used for any activities related to message-passing, including but not limited to, task scheduler and queue.

What do I need to do?

You need to migrate out from this database because of the following reasons.

It is shared between multiple services from different tiers and different usage patterns. You wouldn't want, for example, to have your payment system disrupted when a bulk message sending job is being run.
It is making it difficult to, if not blocking, the multi-account migration. You wouldn't want to setup a special connectivity just to be able to connect to this legacy database.
It will be decommissioned latest by March, 31 2019.

How can I migrate?

Please take a look at the decoupling guide. Check whether your teams are listed there or using any methods mentioned in the page, and plan your migration activity accordingly. Should you have any questions, feel free to leave a comment or start a discussion.

Special note for MessageService users: The consumers will no longer consume scheduled jobs after ~~February, 28 2019~~ March, 18 2019.

Thank you!