InfoQ Homepage Patterns Content on InfoQ
-
Facilitating Feedback That's Psychologically Safe
This article focuses on feedback with regards to a plan or proposal - ways to make it easier to give and receive feedback, so the psychological safety of the team can increase. The aim is to give you insights, models, structures and practical things to try, in order to facilitate feedback that boosts psychological safety in your team(s).
-
Paving the Road to Production
Coinbase has gotten much from its deploy pipelines. We deploy thousands of servers across hundreds of projects per day, to serve our millions of customers and their billions in assets. This article explores the journey Coinbase took to get where it is now, it describes their paved roads and how they've had to change over time in response to their company growing.
-
Building Stronger Human Teams by Managing the Inner Lizards
Each of us has an inner lizard that frets constantly about our safety. People come with brains that are pre-configured to scan everything you say for threats to their safety. Learning to recognize when you're operating under reptilian influence is a great start. This article introduces some techniques to help you manage the lizard within you along with those around you.
-
Danske Bank’s 360° DevSecOps Evolution at a Glance
This article provides an overview of the ongoing DevSecOps evolution at Danske Bank, positioned within the broader transformation that the firm is performing. The main enablers and motivating factors of the evolution are outlined, with challenges discovered. The high level overview of the DevSecOps operating model, together with anti-patterns discovered and main lessons learned concludes it.
-
DevOps is Not Enough for Scaling and Evolving Tech-Driven Organizations: a Q&A with Eduardo da Silva
Eduardo Silva from bol.com on the need for sociotechnical systems thinking. DevOps is a good starting point but a wider view of the organization as a sociotechnical system is key for sustained growth.
-
Saga Orchestration for Microservices Using the Outbox Pattern
The outbox pattern, implemented via change data capture, is a proven approach for addressing the concern of data exchange between microservices. The saga pattern, as demonstrated in this article, is useful for data updates that span multiple microservices.
-
Q&A on the Book Retrospectives Antipatterns
Using the familiar “patterns” approach, the book Retrospectives Antipatterns by Aino Vonge Corry describes unfortunate situations that can sometimes happen in retrospectives. For each situation, described as an antipattern, it also provides solutions for dealing with the situation; this can be a way to solve the problem directly or avoid similar problems in future retrospectives.
-
Q&A on the Book Reinventing the Organization
The book Reinventing the Organization provides a framework of principles of practices that can help companies to deliver greater value in fast-moving markets. The authors explored some of today’s nimblest and fastest-growing large companies, looking at what goes on inside these companies and what's outside: networks, partners, and the marketplace they want to dominate.
-
Sooner, Safer, Happier: a Q&A with Jon Smart from DevOps Enterprise Summit Las Vegas 2020
At DevOps Enterprise Summit Las Vegas, Jonathan Smart gave a keynote talk titled ‘Leading for Better Value Sooner Safer Happier’. Smart is the only person who has spoken at every DevOps Enterprise Summit London conference and each time in Las Vegas since 2017, previously from his role as head of ways of working at Barclays.
-
Adoption of Cloud Native Architecture, Part 2: Stabilization Gaps and Anti-Patterns
In this second part of cloud native adoption article series, the authors discuss the anti-patterns to watch out for when using microservices architecture in your applications. They also discuss how to balance between architecture and technology stability by not reinventing the wheel in every new application and at the same time, avoiding arbitrary reuse of technologies.
-
Multi-Runtime Microservices Architecture
Best practices have emerged around “microservice” architecture and “12-factor app” design. As cloud, containers, and container orchestrators (.g. Kubernetes) have become popular, new solutions to address common integration principles have emerged. This article discusses the approach of using "mecha" components to provide enterprise integration pattern functionality for microservices.
-
How to Avoid Cascading Failures in Distributed Systems
Cascading failures are failures that involve some kind of feedback mechanism. In distributed software systems they generally involve a feedback loop where some event causes either a reduction in capacity, an increase in latency, or a spike of errors. Laura Nolan explores them using public accounts of real production incidents.