Blog

Not too long ago, it was unheard of to put persistent data on Kubernetes. The wise operator would almost certainly have reached for a comparable cloud service and sacrificed functionality for the sake of simplicity and peace of mind.But over the past few years, Kubernetes has matured and grown into areas that would not previously have been considered suitable for container orchestration. This is largely due to the increased stability and feature set of Kubernetes and its growing sophistication as a platform. One of the more powerful features to have emerged in recent releases is the combination of [Custom Resource Definitions] (CRDs) and the [Operator Pattern].

The more distributed a software system is designed, the more you should think about resilience. Because of the distribution, calling the involved communication partners can and will often lead to errors. In order to keep the effects of these errors as small as possible, or to avoid them completely, it has become the norm to work with the necessary resilience patterns. But what is the right approach for dealing with resilience? A service mesh tool or a framework? Both approaches have their pros and cons.

Did you attend DevOpsCon Munich 2019? Perhaps you were there but couldn’t physically attend all of the talks. Well we’ve got you covered. We collected some of the key takeaways from the conference and want to share them with our readers. We learned about the changing role of Ops, how soft skills are so important they’re now called core skills, what books we should read, and much more. See what went down at DevOpsCon Munich 2019.

Today we pay close attention to scaling our systems, testing for chaos, and reducing MTTR in production. Yet our delivery pipelines don’t get nearly as much love. In his talk from the DevOpsCon 2019 in Berlin, Manuel Pais presents tried and tested patterns for increasing accelerating delivery of changes in a safe manner. Manuel Pais will also try to solve the mystery of what is sustainable Continuous Delivery.