✳flâneur — a map of the web's best reading

From Monolith to Microservices to Reasonably-sized Services

perandrestromhaug.com · 1,335 words · saved by 1 readers

There's a saying that software engineers know the benefits of everything and the drawbacks of nothing. When the microservices hype took off circa 2015, everyone was talking about the benefits: At Managed by Q, we went from monolith to microservices and then back to a happy medium. We realized that while some of the benefits of microservices are real, there are also very real downsides and risks. In 2017 I joined the engineering team at Managed by Q, a company that ran a services marketplace for office managers. The team size was about 20 engineers at the time, and our monolith was a Django application deployed on ECS. We were doing a lot of greenfield development, so we mostly built new services to house the new development work. Here is an incomplete list of some of the services we created over the course of about two years: We felt pretty good watching the number of services grow. After all, we were catching up to modern development practices! Plus, doing work in these smaller servic

From Monolith to Microservices to Reasonably-sized Services Per-Andre's technical blog From Monolith to Microservices and Back Again There's a saying that software engineers know the benefits of everything and the drawbacks of nothing. When the microservices hype took off circa 2015, everyone was talking about the benefits: Resilience Scaling Ease of deployment Clear ownership boundaries and team alignment At Managed by Q, we went from monolith to microservices and then back to a happy medium. We realized that while some of the benefits of microservices are real, there are also very real downs

Explore this link on the map →

saved by

related reading