Please log in to watch this conference skillscast.
It has been said that “Microservices is SOA done right”. But really, what’s the difference between SOA and microservices and why is this question fundamental and has implications that could go beyond a potentially amusing twitter debate?
Microservices have been around for a few years now. Many organisations with large and complicated systems that would truly benefit from introducing microservices can not do so in a vacuum; they are often operating in a context that has been heavily influenced by the SOA movement - for better or worse. This influence can often be easily discerned by existing technical choices, but what is less obvious but more important is the conceptual and architectural influence that the SOA approach is still exerting on how microservices systems even when technical legacy is not an issue.
This talk is based on 4 years and a few microservices project that Tareq has been directly involved in at different stages of maturity. Tareq will share with you some fundamental differences between SOA and microservices, and following that you will learn a number of pragmatic lessons and simple design recommendations that hopefully help bridge the gap between the reality of organisations trying to adopt microservices today and the bleeding edge of theory and technology. Many of these lessons can help you design and build better microservices architectures today.
YOU MAY ALSO LIKE:
A Not SO(A) Trivial Question!
Tareq Abedrabbo
Tareq is Chief Technical Officer at OpenCredo. He is continually involved in the delivery of innovative projects, frequently incorporating NoSQL/Big Data and Cloud platforms, to a wide range of organisations. His approach is highly pragmatic and hands-on, and focuses on problem solving and delivering value to his clients.