Underestimated Costs Of Microservice Architectures
July 25, 2018
With many business success stories, our beautiful software systems can degrade into monolithic Big Balls of Mud. And to fix these kinds of monstrosities, we as developers and architects have begun to reach for microservices as our solution. Beautifully-designed architecture diagrams and org charts clearly show the benefits in terms of coordination, batch size, and codebase understandability, but is it really all unicorns and rainbows?
As folks who have been down this road can tell you, microservice architectures don’t solve all our problems. Tradeoffs abound, and in this talk, we’ll see the costs we need to be prepared to pay when we introduce microservices, including team dynamics as well as technical tradeoffs around consistency, failure handling, and observability.
Learning Outcomes:
- Deeper familiarity with microservice architectures
- Ability to make more informed decisions about microservices based on tradeoffs in the form of costs and benefits.
On demand recording
Meet our panelists
Colin Jones, CTO at 8th Light in Chicago
Colin Jones is the CTO at 8th Light in Chicago. He is a passionate software developer and technical leader, with an eye for detail and a drive to learn, solve problems, and teach. Colin is a frequent public speaker and open-source contributor, crafting high-quality, reliable, and maintainable software.
