Elevator Pitch
Service Oriented Architecture has been around for awhile, now Microservices is the new black, that’s cool, but can we learn from when we failed and succeeded implementing SOA? There are some really useful lessons we can take and avoid the pitfalls.
Description
In our industry, we keep on re-inventing or as someone coined re-factoring the wheel… now the new buzzword is Microservices, and we all are on the bandwagon :-). Some call it “SOA 2.0” or “SOA Done Right” or just “Microservices”, but wait, we did SOA for the last 15 years or more, and yes it has its challenges, but I’m sure there is a lot to learn from years of doing, failing and succeeding. Yes, the world has changed, decomposing the monolith is now mainstream, we have DevOps and Netflix, Docker and Kubernetes, polygons and NoSQL and the list goes on and on… BUT distributing ALL the things is not a silver bullet, It introduces a lot of complexity we need to think about. It is a huge paradigm shift from the classic monolith architecture, where the monolith was complicated, distributed architectures introduce a new level of complexity, there are a lot of pitfalls ready for us to walk straight into. Let me share what I and others learnt in the last while doing SOA/Distributed systems. I’ll talk about why we suck in building distributed systems, how we can do that better, what we need to avoid when building/migrating a monolith to a distributed Microservices architecture. At least you will be able to walk into a Microservices transformation with a better chance to succeed.
Notes
Build stuff Nov 2017: SOA lessons learnt (OR Microservices done better)
Vox Vienna June 2017: SOA lessons learnt (OR Microservices done better)