Microservices, “SOA done right”, are the cool kids of the moment. Everyone wants to know them and sit next to them in the classroom. Everytime I see a customer just trying to copy the Netflix architecture or the Facebook architecture, it makes me cringe. Every architecture should be problem space first and technology/architecture second. Too many times people just start with a cool new architecture and then try to fit it inside their codebase, project and IT landscape. The new golden hammer makes everything look a nail…
So reading the blog posts of Christian Posta about Microservices was a relief for me. Finally some sanity in this crazy world. If you think that microservices fit your problem domain and you want to get some real insights, I recommend reading his blog series:
- The real success story of microservices architectures.
- Why Microservices should be event-driven: autonomy vs authority?
- Carving the Java-ee monolith into microservices. Prefer verticals not layers.
- 3 easy things to do to make your microservices more resilient.
- The hardest part about microservices: data.
I hope that more posts will follow!
Although I’m not a Java developer, I even ordered his book, Microservices for Java developers