The Puppet Labs: State of DevOps Report 2015 shows the current DevOps trends in IT, comparing the high and low performers in terms of deployment success and stability, and observing the link between architecture and developer productivity.
Adrian Cockcroft's devopsdays Amsterdam 2015 keynote addressed how CIOs' key goals - align IT with business, develop products faster, avoid security breaches - are attained through the adoption of DevOps practices and Continuous Delivery with containerized microservices. But managing microservices poses new challenges. Cockcroft proposes simulation as a solution to some of those challenges.
Steve Smith presented at Devoxx UK 2015 how Continuous Delivery is performed within Atlassian. After the talk, we had the chance to discuss further details of his presentation and ask him a few questions.
At QCon New York 2015, Paul Payne discussed a project at Nordstrom that required modifying and re-deploying a live application service within twenty minutes, which was made possible due to the use of Go-based microservices, Docker container technology, and a continuous delivery methodology.
Google have created a Kubernetes-based open source reference implementation that automates the building of custom Google Compute Engine VM images with Jenkins and Packer. The primary goal of this work is to demonstrate how to add image creation into a build pipeline for continuous delivery, and produce artifacts that may provide increased reliability and reduced speed of VM initialisation.
Lindsay Holmwood, Flapjack's creator, offers advice to enable fast, with quality, feedback loops and to support small, discrete changes. Holmwood asserts that to get quality feedback there are five main issues to think about: the CAP theorem; SLA definition; SLA validation; interfaces between services; data and infrastructure immutability.
Teams rarely consider success as a mode of failure, but not preparing for exceeding their goals can be just as dangerous as ignoring basic software and infrastructure needs. Mark Simms and Mark Souza discuss anti-patterns they've seen and some of the best ways to architect to win in spite of your own success.
An interview with Yaniv Yehuda, Co-Founder and CTO of DBmaestro, about how they are doing agile development and using DevOps, how they implemented continuous delivery, on agile practices that turned out to be difficult to implement, and the benefits that they are getting for using agile and DevOps practices.
At QCon London 2015 Phil Calcado shared lessons learnt from SoundCloud’s move from a monolithic to microservices architecture, and stated that the core requirements for building a microservice platform include developing capabilities for rapid provisioning, basic monitoring and rapid application deployment.
Microservices are conceptually too big; they conflate optimizing for organisational and technical factors, but solutions to problems of each type may not fit together very well, Phil Wills, senior architect at The Guardian, explained in a presentation at the QCon London conference promoting thinking about independent services and single responsibility applications, rather than microservices.
At the last QCon London, Michael Brunton-Spall, Technical Architect at the UK's Government Digital Service, expressed his views on how DevOps patterns are crucial to successfully operate microservices. Brunton-Spall identified the key ingredients to identify a microservice, explained how to build your first microservice and the necessary tools and practices to manage an ecosystem of microservices.
At QCon London 2015, Dave Farley proposed that although the state of software development has been suboptimal in the past, studies are revealing that the implementation of continuous delivery leads to considerable improvement. Farley stated that continuous delivery changes the economies of software development, and provides more rapid business idea validation and reduced defect rates.
Jez Humble has stated that current software delivery practices are not optimised to create valuable software, and three issues must be addressed in order to enable innovation. First, the traditional project model is unsuitable. Second, the entire organisational value stream must be addressed. Third, the problems are rooted in process and culture, not organisational structure or tooling.
Fastlane is a suite of tools that aim at automating the iOS app release process and provide "a fully working Continuous Deployment process" that can be triggered by running a single command. Interview with fast lane's creator, Felix Krause.
In a blog post on bad code and technical debt Steve Freeman described how Chris Matts came up with the metaphor of an unhedged call option for bad code. This post is being intensively discussed on Reddit and on Hacker News recently. InfoQ interviewed Steve and Chris about using metaphors for bad code and code smells, trade-offs and costs of low quality code, and responsibilities for code quality.