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.
Cisco is currently working on an open source ‘microservice-infrastructure’ project, which will support the continuous deployment of microservice-based applications, and is built upon technologies such as Mesos, Consul and Docker. Development is occurring primarily in the open, via the CiscoCloud Github account.
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 CraftConf 2015, Mitchell Hashimoto argued that current provisioning and configuration tooling is not adequate for orchestrating the ‘modern datacenter’. The modern datacenter is agile and elastic, and ‘services’ may be spread across potentially disparate vendor platforms. Hashimoto introduced Terraform and Consul, which may be used to provide automation in these challenging environments
CoreOS has released Tectonic, a new product created from the aggregation of the CoreOS stack and the Google Kubernetes platform. Tectonic packages up different container technology and puts an UI on top of containers which includes a management console, an integrated registry and other tools to automate deployment.
PowerShell Tools for Visual Studio is a Visual Studio extension that brings the power of Visual Studio to PowerShell developers. Adam Driscoll, the original creator of this extension, got help from Microsoft over the past couple of months. The result is a new release, v3.0.108, offering 64-bit and remote session support, among other improvements.
Docker, Inc. has announced the release of Docker Engine 1.6, Registry 2.0, Compose 1.2, Swarm 0.2, and Machine 0.2. This release targets improved developer experience and performance.
Microsoft continues its push to adapt to the new realities brought about by the containers tsunami, having recently announced the Nano Server, a "minimal footprint" Windows Server, and Hyper-V containers, which provide virtual machine isolation capabilities to containers. The Nano Server has 92 percent fewer critical bulletins and requires 80 percent fewer reboots than a typical Windows Server.
Recently Adrian Cockcroft gave an interview to ActiveState's John Wetherill about microservices. In it he talks about how polyglot fits into microservices and the impact on him when he head that companies such as Target and Macy's, as well as Homeland Security had adopted that architectural approach.
DevOps promises to break down the barriers between the developers and the systems operators, but success with DevOps hinges on the company's culture and flexibility.
Avishai Ish-Shalom talked about the importance of moving from agile cargo cult to agile organizations at DevOps Days Ljubljana 2015. He gives some practical examples and guidance for taking full advantage of Conway's Law.
DevOps Days Ljubljana 2015 took place on the 3rd and 4th April and talks covered the full CAMS spectrum: Culture, Automation, Measurement and Sharing.
Oliver Hankeln shares the anti-patterns he found for handling failure in organizations: hiding mistakes, engaging in blame game, the arc of escalation and cowardice. He then suggests corrective actions for each of them.