Over the past year, service mesh has come to the fore as a crucial component of the cloud native stack. Giants like Ticketmaster and PayPal have all added a service mesh to their production applications. But what is a service mesh, exactly? Is it even relevant? And why?
Some DevOps transformations flourish, but many others are stalling. Why is that? In his Keynote at the DevOpsCon 2019 in Berlin, Damon Edwards makes the case that Operations is the most predictable differentiator.
The digitalisation of business processes is increasingly bringing applications to the centre of the company’s activities. At the sametime, customers expect utmost ease of use and up-to-date functions. Applications must therefore always be updated as soon as possible. This leads to several release cycles per day. This speed, however, can also cause security policies to be violated. To prevent this, application security must be integrated via infrastructure as code in the CI/CD system.
There are many ways to run an agile project. Backlog, Scrum and Kanban are the most common. However, they only work if tasks already exist and are entered in the backlog. But how is a project organized agilely and how can an agile project be measured before the first sprint starts?
10 years ago, DevOps introduced the idea that IT could be more effective without silos between development and operations. Since then, “cloud native” has entered the scene, along with practices and technologies such as Platform-as-a-Service (PaaS), Site Reliability Engineering (SRE), and Serverless.
Ansible, by Red Hat, provides automated configurations as well as orchestrations of machine landscapes. The lightweight and flexible tool is increasingly used in DevOps toolchains and cloud computing. This article shows how to get a complex multi-tier setup on the server with it.
In the past 10 years and since its initial conception, DevOps has become a cornerstone aspect for company culture and the developer community. While DevOps is celebrating its 10th anniversary this year, our experts are taking a step back and looking at its evolution so far and what awaits it in the future, as well the biggest obstacles to overcome when implementing DevOps.
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.