These days, you can’t swing a dry erase marker without hitting someone talking about microservices. Developers are studying Eric Evan’s prescient book Domain Driven Design. Teams are refactoring monolithic apps, looking for bounded contexts and defining a ubiquitous language. And while there have been countless articles, videos, and talks to help you convert to microservices, few have spent any appreciable time asking if a given application should be a microservice.
In this hands-on 3.5 hrs workshop, I will show you a set of factors you can apply to help you decide if something deserves to be a microservice or not. We’ll also look at what we need to do to maintain a healthy micro(services)biome.
There are many good reasons to use a microservices architecture. But there are no free lunches. The positives of microservices come with added complexity. Teams should happily take on that complexity, provided the application in question benefits from the upside of microservices. This workshop will cut through the hype to help you make the right choice for your unique situation.
You may also be interested in
Stateful Functions is an open source framework that reduces the complexity of building and orchestrating distributed stateful applications at scale....