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.
Agile is not meant only for software development. People implement Agile practices in their personal lives too. This post talks about implementation of Agile at home.
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.
Last week, RedHat hosted a "Microservices Architecture Developer Day" in London, and presented a set of technologies and patterns that can be used to create microservice-based applications using open-source solutions like Kubernetes, Docker, Fabric8 and Maven. Read on for more details about the day, including links to the presentations and demo videos.
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.
The Agile Australia 2015 conference is running in Sydney on 17 - 18 June with its theme around the art of simplicty. The conference has been running since 2009 and is set to attract over 1,000 delgates representing over 250 of Australia's leading organisations.
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.
Continuous Integration can help to find integration issues earlier and to visualize the status of the build to all involved. Integration problems can be detected at build-time in stead of run-time during testing and teams can get immediate feedback on changes that they made and on the impact on components that are developed by other teams.
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.
Oftentimes, complex software projects span across multiple repositories on account of external dependencies. This can be a challenge in itself, explains Google WebRTC engineer Patrik Höglund, who also described Google's approach to developing software that uses dozens of third-party libraries such as Chrome.
InfoQ interviewed Hans Aerts, vice president software development and agile coach at TomTom, about why they decided to adopt SAFe and how it was introduced and used to simplify the organizational structure and stop doing projects, why they focus on throughput rather than output, how they modified SAFe for Custom Systems, and what using SAFe has brought TomTom.
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.
InfoQ did an interview with Gil Zilberfeld about better ways to do product planning and tracking, his thoughts about #noestimates, including value in product planning discussions, and how to improve decision making in product development.
At Unruly teams have been applying eXtreme Programming (XP) since being founded in 2006. Teams take a test-first approach to developing code and invest in automated checks that can be run in live environments. InfoQ interviewed Rachel Davies about the importance of a continuous approach to testing, how this has evolved over the years and the business advantage that it delivers to Unruly.
CONTENT IN THIS BOX PROVIDED BY OUR SPONSOR
Blog Series: A skeptic's guide to Continuous Delivery