Continuous delivery should be treated as an agile project as it is about automating your deployment. You have to speed up in small steps and gain trust by doing small deliveries and solve problems fast. The story about how Klaverblad insurance has implemented Agile, DevOps, continuous delivery, and microservices.
At the sixth ‘Agile on the Beach’ conference, held in Cornwall, UK, several leading practitioners of agile software delivery presented the state-of-the-art and emerging trends within this domain. Key takeaways included the value of the scientific method to drive change; the use of Continuous Delivery (CD) for improving safety and speed; and the power of cognitive bias during the user testing.
Moving towards microservices means moving towards distributed systems where you have to deal with latency, authorization and authentication, and messages that do not arrive, argues Sander Hoogendoorn. With microservices you can break down large systems into smaller components to regain control over the architecture.
Continuous deployment results in a higher sense of responsibility and better quality of deployments, argues Paul de Raaij, technical pathfinder at Coolblue. Coding standards prevent your code base from becoming a mess, automated inspections are great for tedious and boring checks, and manual checks are great for checking if the logic or use of code actually makes sense.
Test Butler is an open-source testing tool for Android that aims to allow developers to reliably run UI tests, writes LinkedIn engineer Drew Hannay and creator of Test Butler, by allowing developers to programmatically control a number of testing environment settings.
WireMock v2, an API mocking and service virtualisation tool, has been released. Core enhancements include improved request verification failure reporting, the ability to create custom request matching logic (including the use of Java 8 lambdas), randomly distributed delays (currently with uniform and lognormal distributions), and matching on cookies and basic auth headers.
Robert Scherrer, head of application engineering at SIX, on how the company leveraged DevOps principles and benefits in the highly regulated Swiss financial industry. Engaging with compliance auditors to collaboratively agree on solutions early before it's too costly to change and avoiding legacy internal directives (not actually required by external regulations) are the main takeaways.
DevOps transformation projects are increasingly appealing to established enterprises. InfoQ spoke to three businesses focused on DevOps consulting to understand how they are helping businesses make the change.
At QCon New York, Eric Brewer described how advancing from continuous delivery to fast and stable continuous evolution requires a discrete construction step to define an immutable model of the system. Brewer’s compute infrastructure design team uses Helm to construct and safely validate new deployment models, prior to attempting real deployment, although the concepts are technology agnostic.
RightScale published the results of its survey report highlighting the devops trends in the industry. Docker, Puppet and Chef dominate the tools market, with Docker adoption rising in the enterprise.
On April 27, 2016 Microsoft announced a new personal workflow tool called Flow. The platform is an “IFTTT like” tool that focuses on the automation of personal tasks by orchestrating work across popular SaaS based services.
In order to implement DevOps, individuals and organizations must prepare for the culture shift, new tools, and automation. This consensus has evolved during years of debate concerning what exactly DevOps means and how to use it. There are many voices in the discussion, and even with some areas of consensus, many points are far from agreement.
Android Studio 2.0 comes with several new features and improvements: Instant Run, integration with a Google service for testing on real devices, faster emulator, faster builds, GPU profiler and debugger, support for deep linking and others.
At QCon London 2016 Peter Alvaro and Kolton Andrus shared lessons learned from a fruitful collaboration between academia and industry, which ultimately resulted in the creation of a novel method for automating failure injection testing at Netflix. Core learnings included: work backwards from what you know; meet in the middle; and adapt the theory to the reality.
The world is naturally chaotic, and we should both plan for and test that our systems can handle this chaos, Rachel Reese claimed at the recent QCon London conference describing how Jet, an e-commerce company launched in July 2015, work with microservices and chaos engineering.