News | November 11, 2017
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.
Lunch & Learn: Learnings from Writing My Own Operating System from Scratch
In this Lunch & Learn session, Peter Vegh advises on ‘Learnings from Writing my Own Operating System from Scratch’When Your Product Teams Should Aim to be Inefficient – Part 2
Many businesses advocate for efficiency, but this is not always the right goal. In part one of this article, we explored how product teams can…PlatformCon 2022 – People, Process, and Platform – a community-focused approach (Recording)
Watch the recording of our CEO/CTO, Nicki Watt from the PlatformCon Conference 2022 on her talk “People, Process, and Platform – a community-focused approach.”