A Hot Topic
The interesting thing is that I've been harking on about using simple, single-purpose components in order to enable the properties of antifragility in software now for a couple of years. I'm just about to launch a course on the subject, and what excited me was that in fact what was being branded as microservices at that point was what I was simply referring to 'adaptable components'. So, for me, microservices works.
After just about every conversation I had after QCon being dominated by the subject I felt, and so did Skills Matter, that it was time to take things to the next level and so µCon (pronounced, and hash tagged, as 'muCon') was born.
But why do we need this conference? Here are my reasons.
Pebbles and Boulders
Netflix, and other innovative companies, is not just down to processes and practices, it's down to philosophy. Netflix designed and architected for unpredictability from the word go, both in terms of requirements and runtime conditions. They coined the term 'cloud native' for this style of architecture, and it is made up of another term they adopted 'microservices'. I think these terms are a little too implementation specific, what they are in fact achieving is antifragility in that they have designed and architected to thrive on change in requirements as well as to thrive in the face of runtime instability.
Netflix have designed microservices so that their system is antifragile, while accepting that some services can be fragile, some may be robust. Antifragility is a property of the system itself, and microservices have as an underlying implementation choice been the natural destination to achieve this valuable antifragile property.
Antifragile Software Systems and Competitiveness
We've spent over 10 years now becoming agile in our processes and practices, even our organisations, but our software architecture and design has had difficulty keeping up.
It's not just about comprehension and clean code, the software itself needs to be designed with change in mind. This is where simple, single-purpose services that do one thing well and are able to live and failover and deal with transient environmental conditions successfully are so important. It's no surprise that these are the natural properties of a system that is labelled as following a micro service architecture.
Back to the Conference
You can see this confusion in ongoing discussions around "What is a microservice?", or even "Isn't a microservice architecture just SOA?". These are important discussions, but they tend to cloud the real underlying properties that are being sought, those that I'm characterising as innovation enabled by antifragility.
So this conference intends to set the record straight. To share real-world experiences of building microservices architected systems and how they enabled the benefits, such as antifragility, that they were aiming for. We're going to discuss values, principles, architecture, design and real implementation techniques. This won't be for the faint-hearted, but it will be a heck of a lot of fun!
So if you're interested in building software that can adapt as fast as you and your business can, then this could well be the one conference you need to be at this year. If that hasn't sold you on the conference, then the forthcoming speaker announcements surely will do, and let's not forget the obligatory evening-keynote and launch party on the first night.
Sign-up for Earlybird Discount Today
It's going to be an amazing learning experience and a lot of seriously technical fun, and right now it only costs £200 for two-days as well, so get in early while the earlybird discount is still available!