Let it be said: «Chaos is the new order».
I have been working with microservices for the past few years and it’s been quite a ride. By breaking down the monolith into more focused independent entities, questions have presented new challenges. Obviously, from a software architecture perspective, but also operational and organizational.
Indeed, in a monolith, developers make a lot of the calls that can impact even operations but leave the ops side with little knobs to tweak. One of the first consequence of the breakdown is that operations should be much more involved in the design choices of the application. A sane DevOps culture might even emerge.
With that said, running a healthy system made of unpredictable parts is challenging, there is no way around it. All teams that have transitioned to microservices architecture have had to learn, adapt and become creative to face those challenges: service discovery, faulty services, stateless services, network latency, authentication across the system and many more.
The ecosystem is now ripe for running those systems with confidence and speed. I will now be working full steam on providing content towards running microservices hands on.
Running is one thing, as my friend Russ Miles often says, we must stress the system as it’s a living thing. Software do not live in a vacuum. Things go bad and we need to learn how to cope and respond fast with confidence. Russ and I will therefore talk more about how chaos experiments will make your teams stronger and faster at delivering great software.
Stay tuned because this is going to be fun as I will speak about Kubernetes, service mesh, logging, monitoring, storage and more! Embrace chaos as it is going the new order.