Wednesday, November 11, 2020
As in life, so in software: boundaries are critical. Without setting the correct boundaries we can get stuck maintaining a logically broken system potentially for years.
You may be designing a greenfield application using microservices architecture with goals of speed, scale, and flexibility or you may be attempting drastic new features to an existing system with a more monolithic design. But without doing the work upfront to define the true business boundaries of each service in your system, you end up with a brittle, tightly-coupled system that negates all these longed-for benefits or doubles down on a coupled monstrosity.
So how do you know you’re setting the right boundaries? In this session, we’ll explore some tactical tools for identifying those boundaries and show you how to evaluate them via a change scenario to an existing system. The exercise focuses attention on considerations for data, reliability, and the human factor of ownership and customer experience. We will also discuss some pitfalls to avoid coupling in your system.
You’ll leave empowered to set boundaries that enable true autonomy and help you get the most value out of your distributed architecture.
Download these images to your phone and post using the Instagram app.