Training for technical diving prepares you for situations in a high pressure environment where failures are unavoidable but also highly dangerous. It means surviving in a hostile environment with limited resources where the failure of individual components can trigger deadly failure cascades. A diver who can’t understand how to do proper post-accident analysis and who hasn’t learned to repeatedly survive through failure is a liability to themselves and to others. This talk uses the framework of technical SCUBA and rebreather diving to talk about patterns for failure management and how they can be applied in an engineering context.
Go packages don't have versions or dependencies. At least, not yet. With Go 1.11 and its experimental support for versioned Go modules, this is changing. Go 1.11 brings native support for versions and modules in Go as a fixed component to the Go toolchain. The modules are meant to replace community solutions such as dep or glide and create a new uniform solution. But does that really work? We take closer look in this article by Jan Stamer.
"Public Cloud: yes or no?" - a question radically outpaced by the train of technology. More and more companies are looking into the advantages and disadvantages of a public cloud infrastructure. There is no doubt that the public cloud has its advantages. Its elasticity, high vertical integration, and global distribution are ideal for certain applications. However, very few applications really need this, and it's worth taking a closer look.
Amazon Web Services (AWS) provides a huge portfolio of services and products that can be combined to work with one another. Bruns Michael explains how it is possible for developers to just click through this infrastructure using a colorful web UI and the possibility of automation, versioning and replication.
DevOps has become a part of good business etiquette for modern companies. Still, companies can achieve an optimal performance, if they integrate these methods with a maximum quality. What we need now isn’t just DevOps but “DevQOps”.
The full advantage of DevOps can only be achieved if development and operations work together with the specialist departments and management on a value adding product. Or to put more radical: The topic is no longer called DevOps, but BizDevOps. The integration of business and DevOps changes the cooperation, organization, and processes of companies. All involved must set impulses for the digital transformation of the company and can generate economic benefits faster.
Data-driven decision-making is a goal of most leaders today. Unfortunately, between the overwhelming amounts of data available to us and the ease of falling prey to misleading vanity metrics, how to begin this journey can feel extremely elusive. In this talk from DevOpsCon 2018 Julia Wester, co-founder and Principal Consultant at Lagom Solutions, discusses ways to map your metrics back to your desired goals and a better understanding of metrics safety. This is the first step for setting the stage for smart, data-driven decision-making.
In the DevOps environment, Docker can no longer be reduced only to a container runtime. An application that is divided into several microservices has greater orchestration requirements instead of simple scripts. For this, Docker has introduced the service abstraction Docker Swarm to help orchestrate containers across multiple hosts.