Join us for µCon London 2017!
We are excited to announce that Tareq Abedrabbo, Matt Long and Fahran Wallace are speaking at µCon London 2017!
Join µCon 2017 to learn how other teams have adopted microservices and what they learned along the way. Help shape the conversation in discussions with some of the worlds leading architects and microservices experts. Share the challenges you are facing, the technologies you are exploring and the skills you have gained with 400 other engineers passionate about creating highly flexible systems that rock. Follow us at #mucon for all the latest updates on the conference!
A Not SO(A) Trivial Question! By Tareq Abedrabbo
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.
Testing Programmable Infrastructure By Matt Long
With the rise of DevOps, programmable infrastructure is reaching widespread adoption. However, although automated testing of software is becoming more common, the same cannot be said of testing the automated deployment of cloud infrastructure.
With microservices making our deployments more and more complex, you can no longer afford to ignore this type of testing. During this talk you will learn some approaches to programmable infrastructure testing that we have created, from the perspective of a project that required functional testing of infrastructure.
Cognitive Bias, Software Projects, and the Microservice Mindset by Fahran Wallace
The human brain is a powerful piece of hardware, and the software… certainly gets the job done. However, it has plenty of quirks and legacy code from back when not getting eaten by lions was a primary concern.
The unfortunate result is a set of cognitive biases that make you feel like you’re making great, logical decisions about the things you build, whereas in reality, you’ve overlaid your own experiences and desires on the problem, and wind up building something that reflects those biases. Whether it’s favouring the first solution you think of (Anchoring effect), being suspicious of things that were “Not Invented Here”, or wildly under or overestimating the ability of ourselves or others (often all simultaneously!), your mental quirks can leave their mark on software that has developers cursing years into the future.
Whilst the move to a Microservices architecture has helped you to technically circumvent some of these biases and problems, it can also encourage us to run merrily towards others. Life gets even more interesting when considering how groups of people interact and organise. Starting with Conway’s law, Fahran will share with you how Microservice architectures are shaped by this, as well as other unseen cognitive forces at play.
Cognitive Bias, Software Projects and the Microservice Mindset is a whimsical talk that explores the intersection of Programming, Architecture and Psychology, through the medium of funny-in-retrospect memories, borrowed war stories, and attempts to avoid people swearing at Fahran’s design choices 5 years later.