From the course: Microservices: Asynchronous Messaging

Unlock the full course today

Join today to access over 24,900 courses taught by industry experts.

The trade-offs

The trade-offs

From the course: Microservices: Asynchronous Messaging

Start my 1-month free trial Buy for my team

The trade-offs

“

- [Instructor] As with every technical decision, there are trade-offs when making decisions on how to develop software. Asynchronous communications is no exception to this rule. One of the single biggest trade-offs with a microservices implementation that includes asynchronous messaging is the overall complexity of the system. Some of the complexity comes from artifact sprawl. Usually consumers of messages are individual artifacts that have their own repositories, build pipelines, deployment pipelines, and configuration management. You now have to account for all of this in your system. Another complexity issue comes from disconnected code paths. This adds complexity to many areas of your system, as we will discuss, but for now, considering the debugging pathway alone, having disconnected paths makes debugging, troubleshooting, and evaluating outcomes significantly more complex than in a standard synchronous system. Multiple…

Contents