InfoQ Homepage Architecture Content on InfoQ
-
Q&A with Tyler Treat on Microservice Observability
Tyler Treat attempts to disambiguate the concepts of Observability and Monitoring. He discusses how the complexity of elastic systems produces more unknowns that require a discovery-based approach. InfoQ recently sat down with Treat to discuss the topics of observability and monitoring, and he shares some challenges and best practices when introducing observability concepts.
-
The Unicorn Project and the Five Ideals: Interview with Gene Kim
The Unicorn Project is a fictionalized story about a DevOps transformation. Gene Kim introduces the five ideals of Locality and Simplicity; Focus, Flow and Joy; Improvement of Daily Work; Psychological Safety; and Customer Focus. The book confirms the importance of the DevOps movement as a better way of working and addresses the importance of architecture and developers’ productivity.
-
Q&A on the Book Team Topologies
The book Team Topologies by Matthew Skelton and Manuel Pais shows how to arrange teams within an organization to enable effective software delivery. It describes four fundamental team types and three team interaction patterns, and dives into the responsibility boundaries of teams and how teams can communicate or interact with other teams.
-
Testing Microservices: Six Case Studies with a Combination of Testing Techniques - Part 3
This article presents six real world use cases of testing microservice-based applications, and demonstrates how a combination of testing techniques can be evaluated, chosen, and implemented.
-
Categorise Unsolved Problems in Agile Development: Premature & Foreseeable
Productivity decline and technical debt, as often seen in agile development, can be prevented by separating unsolved problems into premature and foreseeable. It shifts the discussion about unsolved problems from importance to likelihood. With small but essential adjustments, agile can be kept sustainable. With this insight, developer-architect differences and team psychology gaps can be bridged.
-
Q&A on the Book: The Technology Takers – Leading Change in the Digital Era
The Technology Takers – Leading Change in the Digital Era by Jens P. Flanding, Genevieve M. Grabman, and Sheila Q. Cox explains how organizations can achieve competitive advantage through their speed and flexibility in adopting technology. It prescribes a change management approach for adapting workplace behaviors to market-dominating technology to maximize its benefits.
-
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.