InfoQ Homepage Architecture Content on InfoQ
-
Using Docker Application Packages to Deliver Apps across Teams
In this article, we will look at how the CNAB packaging format provides application providers and developers with a way of installing a multi-component application into a distributed computing environment, supporting many executable units, and makes it easy to deliver apps across teams, organizations and marketplaces.
-
SLOs Are the API for Your Engineering Team
SLOs provide a simple common language for evaluating risk in terms of error budgets. SLOs save everyone involved both time and energy, which you can redirect toward more important things, like keeping your customers happy.
-
Q&A on the Book Impact: 21st Century Change Management, Behavioral Science, and the Future of Work
The book Impact by Paul Gibbons explores how to lead and manage change in the 21st century to support digital transformations while taking the needs of millennials and Gen Z into account. It describes how we can humanize change and use pull models and dialogs to support behavior change.
-
Liberating Structures - an Antidote to Zombie Scrum
Although many organizations use Scrum, the majority struggle to grasp both the purpose of Scrum as well as its benefits. They do Zombie Scrum; it looks like Scrum from a distance, but you see that things are amiss when moving closer. This article describes what Zombie Scrum is about and gives you tangible examples of how to recognize, treat and prevent Zombie Scrum by using Liberating Structures.
-
Scrum: The Art of Changing the Possible
The Scrum Fieldbook aims at introducing Scrum within organizations outside of the software industry, where Scrum can help leaders achieve a culture of high performance. The author shares patterns, practices and practical steps that leaders can take to incorporate these successfully in their organization.
-
Q&A on the Book Managing Technical Debt
The book Managing Technical Debt by Philippe Kruchten, Robert Nord, and Ipek Ozkaya provides principles and practices that help you gain control of technical debt throughout the software development process and life of the software product.
-
Q&A on the Book Engineering the Digital Transformation
The book Engineering the Digital Transformation by Gary Gruver provides a systematic approach for doing continuous improvement in organizations. He explores how we can leverage and modify engineering and manufacturing practices to address the unique characteristics and capabilities of software development.
-
Testing Microservices: Examining the Tradeoffs of Twelve Techniques - Part 2
A successful microservice testing strategy must effectively manage the interdependent components involved. This article presents the tradeoffs for twelve testing techniques. Each approach has advantages and disadvantages. Which technique, or blend of techniques, should be used for your application, depends on your context.
-
Q&A with Cyrille Martraire on the Book Living Documentation
Cyrille Martraire argues that we should rethink how we work with documentation when building software systems — we should embrace documentation that evolves at the same pace as the code. In the book, he describes the concepts and ideas that are the base for living documentation and uses practical examples on how documentation that is always up-to-date can be created.
-
Implementing Policies in Kubernetes
The author explains what Kubernetes policies are, and how they can help you manage and secure the Kubernetes cluster. We will also look at why we need a policy engine to author and manage policies.
-
The Magic of Organizing around Customer Journeys - and How to do it
Organizing around the value delivered to the customer requires maturity in the organization that needs to be built up over time. This article describes eight typical steps that companies are taking in order to mature towards the end goal of becoming a true enterprise agile organization, and explains how to move up the ladder.
-
Rethinking Flink’s APIs for a Unified Data Processing Framework
Since its very early days, Apache Flink has followed the philosophy of taking a unified approach to batch and streaming. The core building block is the “continuous processing of unbounded data streams, with batch as a special, bounded set of those streams.” Recent updates to the Flink APIs include architectural designs by the community to support batch and streaming unification in Apache Flink.