Microservices
Two articles to help you judge whether splitting a system is worth it. The first goes through technical reasons and keeps the ones that hold up, such as parts of the system with very different load, or customers and regions that must not affect each other. The second looks at the human side: choosing microservices because they look good on a CV, help hiring or give a team its own territory. The Monolith vs Microservices guide goes further.
2 articles
![Sociological aspects of Microservices]()
Sociological aspects of Microservices
Last week, I started writing about the topic of cutting systems into microservices (read more here). I was sceptical about the frequent…
![How (not) to cut microservices]()
How (not) to cut microservices
Today, I’m holding a keyboard in one hand and scissors in the other. What do I need these scissors for? According to the post title, I would…
