InfoQ Homepage Architecture & Design Content on InfoQ
-
The MVP Dilemma: Scale Now or Scale Later?
Scaling a system is a hard problem to solve. Underinvesting in scalability leads to a shortened lifespan for the system, but overinvesting can kill the MVP business case because of cost.
-
Designing Resilient Event-Driven Systems at Scale
Learn how to design resilient event-driven systems that scale. Explore key patterns like shuffle sharding and decoupling queues to handle load spikes and failures. Understand common pitfalls like over-relying on retries and neglecting observability for robust, scalable architectures.
-
Best Practices for Managing Shared Libraries in .NET Applications at Scale
This article discusses real-world cases of using shared libraries, their consequences, and possible solutions to blockers caused by using them in many dependent projects.
-
Legacy Modernization: Architecting Real-Time Systems around a Mainframe
At its heart, our transformation journey is about breaking dependencies at multiple levels. Many enterprises face similar challenges with legacy systems: tightly coupled architectures that are difficult to scale, change, or maintain. For us at National Grid, the solution came through four complementary paradigms that worked together to enable different forms of decoupling.
-
InfoQ Software Architecture and Design Trends Report - 2025
The InfoQ Trends Reports offer InfoQ readers a comprehensive overview of key topics worthy of attention. The reports also guide the InfoQ editorial team towards cutting-edge technologies in our reporting. In conjunction with the report and trends graph, our accompanying podcast features insightful discussions among the editors digging deeper into some of the trends.
-
Distributed Cloud Computing: Enhancing Privacy with AI-Driven Solutions
Distributed cloud, PETs, and AI enable secure, private data processing. This integration enhances collaboration, security, and compliance across marketing, finance, and healthcare, addressing the growing need for data protection.
-
Renovate to Innovate: Fundamentals of Transforming Legacy Architecture
Rashmi Venugopal explores the inevitability of legacy systems in successful companies and the importance of transforming legacy systems to accelerate innovation. Rashmi discusses various strategies to tackle such technical renovation initiatives, like evolutionary architecture, deprecation-driven development, and intentional organization design.
-
Fitness Functions for Your Architecture
Software, its size, its requirements, and its infrastructure environment evolve over time. Software architecture should evolve accordingly, to meet current and future operational and developmental requirements. Fitness functions are guardrails that enable the continuous evolution of your system's architecture, within a range and a direction, that you desire and define.
-
Shadow Table Strategy for Seamless Service Extractions and Data Migrations
The shadow table strategy creates a synchronized duplicate of the data that keeps the production system fully operational during changes, enabling zero-downtime migrations. The approach supports diverse scenarios - including database migrations, microservices extractions, and incremental schema refactoring - that update live systems safely and progressively.
-
Architectural Experimentation in Practice: Frequently Asked Questions
This third article in a series answers some frequently asked questions about architectural experiments. Architectural experiments test critical decisions to reduce risks and costs, using well-defined hypotheses and results for clarity. They are structured, not unfocused, exploratory learning.
-
DiRMA: Measuring How Your Organization Manages Chaos
Elevate your disaster recovery strategy with DiRMA—an innovative framework for assessing and enhancing Disaster Recovery Testing (DiRT) maturity across people, processes, and tools. As chaos engineering becomes essential for resilience, DiRMA guides organizations through structured improvement, addressing cultural hurdles and ensuring robust recovery readiness in the face of modern challenges.
-
Applying Flow Metrics to Design Resilient Microservices
Software design with resilience is an acknowledgement to the reality that everything fails. We put metrics in place to help us detect and resolve such problems and failures. Flow metrics, commonly used to measure how well teams deliver software, can be used to measure and improve system resilience.