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

You probably don’t need microservices

thrownewexception.com · 1,626 words · saved by 1 readers

Dear fellow developers, we need to talk. We need to talk about microservices and some situations that are not OK. It won't be easy, but we need to do it. Or we are not gonna to make it. Microservices are very popular nowadays. It's a great architectural style that helps to scale the system and the organization. Many successful companies use microservices (e.g. Netflix, Spotify, etc). Therefore, it's normal that most companies are using or planning to use it. But some miss the added costs it brings. Before diving in, let me talk about my experience with microservices. In 2012, in the company I was working at, we were presented with a challenge: how to grow the company to thousands of engineers and 1000x more transactions. This post isn’t focused on the hiring, onboarding, etc, but on the architecture. I was reading Scalability Rules: 50 Principles for Scaling Web Sites at the time, and the book introduced the AKF Scale Cube. I found it incredibly easy to understand. So I used it to expl

This blog post was fun to write. It'll most likely be hated by many, but… Dear fellow developers, we need to talk. We need to talk about microservices and some situations that are not OK. It won't be easy, but we need to do it. Or we are not gonna to make it. Microservices are very popular nowadays. It's a great architectural style that helps to scale the system and the organization. Many successful companies use microservices (e.g. Netflix, Spotify, etc). Therefore, it's normal that most companies are using or planning to use it. But some miss the added costs it brings. Before diving in, let

Explore this link on the map →

related reading