InfoQ Homepage Architecture Content on InfoQ
-
/articles/rightsizing-platform-engineering/en/smallimage/rightsizing-platform-engineering-thumbnail-1787296955801.jpg)
Rightsizing Platform Engineering: Building the Platform Your Organization Actually Needs
Shift-left and DevOps have impacted how we flow changes from inception to production, but at the cost of increased cognitive load and duplication of effort across testing, security, and maintenance. This article explores the real-world challenges of rightsizing developer platforms and finding a cultural match for engineering teams who use them to reduce cognitive load and deliver change faster.
-
/articles/agentic-fitness-functions-evolutionary-architecture/en/smallimage/thumbnail-1786428822427.jpg)
Agentic Fitness Functions: Extending Evolutionary Architecture Beyond Deterministic Rules
Deterministic rules safeguard hard metrics, but what about architectural intent? Discover how agentic fitness functions combine AI agents and versioned rubrics to evaluate complex, judgment-heavy concerns—such as boundary fidelity, semantic contract drift, and stale ADR assumptions. Elevate evolutionary architecture governance with continuous, calibrated feedback loops.
-
/articles/cloud-devops-trends-2026/en/smallimage/infoq-trends-report-small-logo-1785421405039.jpeg)
InfoQ Cloud and DevOps Trends Report - 2026
InfoQ editorial staff and friends of InfoQ are discussing the current trends in the domain of Cloud and DevOps as part of the process of creating our annual 2026 trends report.
-
/articles/system-comprehension-evolutionary-architecture/en/smallimage/thumbnail-1786087830832.jpg)
Comprehension as an Architectural Characteristic: A System That Is Not Understood Cannot Evolve Safely
As AI commoditizes code output, system comprehension silently decays, creating cognitive debt that threatens safe architectural evolution. This article explores why human understanding must be treated as an essential architectural characteristic, offering actionable strategies, socio-technical metrics, and design checkpoints to preserve intent across modern engineering teams.
-
/articles/evolutionary-architecture-change-locality/en/smallimage/evolutionary-architecture-change-locality-thumbnail-1785239081753.jpg)
Enabling Evolutionary Architecture through the Preservation of Change Locality
Why do simple features suddenly require cross-team negotiations? In this article, explore how boundary drift quietly destroys change locality and increases cognitive load across teams. Learn practical sociotechnical strategies - redistributing mechanics, exposing essential policy, and rehearsing exception paths - to restore domain boundaries and enable a truly evolutionary software architecture.
-
/articles/virtual-threads-after-jdk24/en/smallimage/virtual-threads-after-jdk24-thumbnail-1785232507934.jpg)
Virtual Threads after JDK 24: What Changed for Production Java
JDK 24 removed the monitor-related carrier-thread pinning that stalled Netflix and similar teams on Java 21. What has replaced it on JDK 25 LTS is downstream-resource saturation: the bottleneck moved and now demands explicit bounding in application code. This article maps the failure modes that surface after virtual-thread adoption and gives a practical sequence backed by a public benchmark.
-
/articles/pull-based-migration/en/smallimage/pull-based-migration-thumbnail-1784812950594.jpg)
The Hard-Stop Rule: from 3 HCM Monoliths to 120 Domain Microservices
A payroll and HR software team rebuilt three monoliths into over 120 smaller services over five years, with no dedicated migration budget. Every new feature was built as its own service instead of changing the old ones. The article covers the pull-based migration, the tools that made this possible, how costs were kept down, and the problems the team ran into along the way.
-
/articles/evolutionary-architecture-pattern/en/smallimage/evolutionary-architecture-pattern-thumbnail-1784798616611.jpg)
An Evolutionary Architecture Pattern for Managing AI’s Pace of Change
Traditional API gateways assume deterministic services and simple schemas - assumptions agentic AI breaks. Discover why enterprise engineering leaders are adopting AI Gateways as an evolutionary architecture seam. Centralize guardrails, model routing, agent identity, action policy, and semantic audit within a single control plane to prevent costly incidents while keeping core platforms stable.
-
/articles/multi-agent-security-operations/en/smallimage/Multi-Agent-AI-for-Production-Security-Operations-thumb-1784628007582.jpg)
Multi-Agent AI for Production Security Operations: an A2A and MCP Architecture in a 5G Core
The bottleneck in a mature SOC is rarely analyst triage; rather, it is the detection-engineering team's ability to keep the rule base aligned with a threat landscape that evolves faster than rules can be written. Learn how multi-agent system for production security operations has reduced mean times to detect and to respond by 40% and compressed the human work required by 12x.
-
/articles/ai-speed-context-store-architecture/en/smallimage/ai-speed-context-store-architecture-thumbnail-1783673492911.jpg)
Comprehension at AI Speed: Building a Context Store for Evolutionary Architecture
AI makes the first 80% of development feel fast, but hides architectural complexity until it's too late. To prevent system instability, engineering leaders must shift from raw throughput to systemic comprehension. By unifying spec-anchored SDD, TDD, and automated fitness functions into a repo-bound "Context Store," teams can ensure AI agents and human reviewers evolve code safely.
-
/articles/aws-multi-region-signing/en/smallimage/aws-multi-region-signing-thumbnail-1783602485181.jpg)
Removing a Hidden Round Trip from a Multi-Region AWS API
When a series of regional outages forced a rethink of a multi-region AWS API, the team discovered that an obstacle to global failover was hiding in plain sight: a pre-flight discovery call baked into every client session years earlier as the only available option. This article describes what it took to remove it, and what the rollout actually cost.
-
/articles/multi-region-latency-cost-tradeoffs/en/smallimage/multi-region-latency-cost-tradeoffs-thumbnail-1783416229477.jpg)
Trade-Offs in Multi-Region Architectures: Latency vs. Cost
Adding cloud regions changes latency and cost in ways simple math can't capture. This article presents a framework from multiple launches: decompose your latency budget before committing to infrastructure, choose deployment patterns by consistency and traffic profile, and optimize before expanding. A phased approach cut latency 35% through routing alone, before a new region brought it under 60ms.