An interview with Alexander Heusingfeld and Tammo van Lessen about getting operations involved in architecture and dealing with "us vs. them" behavior when applying DevOps, how to use the Self-Contained Systems approach to modernize software systems, similarities and differences between Self-Contained Systems and microservices, improving deployment pipelines and using measurements in deployment.
Boyan Mihaylov covers his experience when working with both traditional waterfall software architectures and agile ones. He depicts the similarities and differences between these with a focus on three areas: the specifics of the software architect role, the timespan of the software architecture, and the output of the software architecture.
Len Bass on the motivation for "DevOps: A Software Architect's Perspective", what does looking at DevOps from an architectural perspective mean, DevOps education, microservices and more. 1
At the recent Dynatrace Perform conference, a panel of technology companies discussed the topic of cloud migration and uncovered some key findings.
InfoQ ran a series of interviews during the DevOps Enterprise Summit 2015, focusing on the DevOps transformations that many corporations are currently undertaking.
This article focuses on why DevOps is needed, what concepts and values should support it, as well as how we implemented it at Seamless, what results we obtained and the challenges we faced.
InfoQ asked Matthias Marshall what's new in the 2nd edition of his book and his view on the evolution of the configuration management tool space.
In this article, author discusses a bio-informatic software as a service (SaaS) product which was built as a public data warehousing and analytical platform for mass spectrometry data. 3
Agendashift is a values-based Kanban approach to organizational transformation, covering delivery, change and leadership. An interview with Mike Burrows.
Find out what's new in Kubernetes V1 with a Jenkins example in Google Container Engine. V1 brings enterprise-level capabilities such as self healing, service discovery, dynamic DNS, resource quotas.
This article explains the goals of proper application delivery using immutable infrastructure: automated, flexible, scalable, secure and transparent; and how to take gradual steps toward those goals.