InfoQ Homepage Architecture & Design Content on InfoQ
-
/articles/identity-as-architecture/en/smallimage/identity-as-architecture-thumbnail-1793629959196.jpg)
Identity as an Architectural Concern: Enterprise IAM Beyond Authentication
The way you design your identities will drive your data models, your service scope, and your revocation policies; enterprise identity management is thus an architectural problem, not an afterthought. Based on our experience in service account governance, this article touches upon graph vs. RBAC, integrating a vault you don't own, and bounding revocation latency for an event stream.
-
/articles/agentic-ai-context-memory-knowledge/en/smallimage/agentic-ai-context-memory-knowledge-thumbnail-1793173492489.jpg)
Systemic Approach to Memory, Knowledge, and Context in Agentic AI Architectures
The article argues that reliable agentic AI architecture depends on a context engine that selects, injects, compresses, and expires information before it reaches the model. It separates context, memory, and knowledge, and recommends tiered memory, curated knowledge, and token budgeting. It also covers common anti-patterns, such as context stuffing and stale data loops, with mitigations.
-
/articles/agentic-ai-architecture-harness-evolution/en/smallimage/agentic-ai-architecture-harness-evolution-thumbnail-1792744961862.jpg)
The Evolution of Agentic Harnesses: from Chains to Graph to Code
Agentic LLM systems have moved from linear prompt chains to graph-based workflows and, more recently, code-executing harnesses. Chains are simple but fragile, graphs add branching, retries, and validation, and code harnesses verify outputs through execution. The article advises validating model outputs and choosing the least complex design that meets reliability, speed, and cost needs.
-
/articles/multi-cloud-finops-cost-optimization/en/smallimage/multi-cloud-finops-cost-optimization-thumbnail-1792499448017.jpg)
Multi-Cloud FinOps: an Engineering Framework for Cross-Cloud Cost Optimization
Multi-cloud flexibility comes with hidden egress costs driven by service placement and communication patterns. This article applies Backend FinOps to cross-cloud architecture, covering cost visibility through FOCUS, workload placement, synchronization models, and CI/CD-integrated cost governance. A controlled experiment shows architecture changes saved far more than rate negotiation alone.
-
/articles/ai-changes-data-interface/en/smallimage/thumbnail-1792487239242.jpg)
AI Changes the Data Interface, Not the Query Engine
This article presents a disaster-recovery analytics workflow in which an AI agent generates constrained SQL or Python, DuckDB computes reproducible facts from Parquet, and the agent interprets the results. It explains the determinism split, replayable analysis, and four signals for deciding when an embedded engine is sufficient or a managed lakehouse is justified.
-
/articles/agentic-ai-architecture-article-series/en/smallimage/agentic-ai-architecture-thumb-image-1792485862285.jpg)
Article Series: Agentic AI Architecture
In this article series, we try to establish agentic AI architecture as a new type of software architecture that will likely dominate the industry for years to come. The articles, written by industry experts, cover various elements and aspects of agentic AI architecture. We aim to present the latest trends and developments shaping the new type of architecture as it enters the mainstream.
-
/articles/spring-batch-without-broker/en/smallimage/Distributed-Spring-Batch-Without-a-Message-Broker-thumb-1792419294298.jpg)
Distributed Spring Batch without a Message Broker
Distributed Spring Batch partitioning already needs a shared, persistent job repository. This article makes that database the whole coordination plane and drops the message broker, sizing work to the live node count, a per-job master with no standing coordinator, compare-and-set claiming that prevents double-execution, two-phase heartbeat failover, and where a broker is still the right choice.
-
/articles/distributed-systems-microservices-agentic-ai/en/smallimage/thumbnail-1792138504151.jpg)
From Microservices to Agents: the Next Evolution of Distributed Systems
The article examines the transition from microservices to agentic AI architecture in distributed systems. Microservices allow for functional decomposition, while agentic systems focus on decision decomposition. This shift introduces new complexities in observability, reliability, and system design, highlighting the need for updated architectural patterns and practices.
-
/articles/enterprise-mobile-id-mdl-blueprint/en/smallimage/thumbnail-1791967143918.jpg)
Cryptographic Foundation of Mobile ID Systems: an ISO/IEC 18013-5 Enterprise Architecture Blueprint
This article provides a framework for asking the right architectural questions before an enterprise commits to an mDL provider or library. It shows which components can be abstracted safely, which trust boundaries must remain visible to the enterprise, what cryptographic and interoperability properties should be verified, and how requirements change across real-world use cases.
-
/articles/spring-security-7-server-side-dpop-token-exchange/en/smallimage/spring-security-7-server-side-dpop-token-exchange-thumbnail-1791884636157.jpg)
Server-Side DPoP and Token Exchange in Spring Security 7
Spring Authorization Server now lives inside Spring Security 7 under the same Maven coordinates, so the upgrade is a version bump. This server-side guide covers enabling DPoP and RFC 8693 Token Exchange, explains why 7.1 apps can silently stop enforcing DPoP until they call .dPoP(), and shows how to combine both into narrowed, sender-constrained tokens for service-to-service and agentic calls.
-
/articles/shipt-composable-commerce-design-ddd/en/smallimage/shipt-composable-commerce-design-ddd-thumbnail-1791812515573.jpg)
Composable Commerce: inside Shipt’s Kit Platform
Shipt launched its Kits feature, enabling quick assembly of themed grocery bundles for events. The platform architecture lets merchandisers easily create store-aware kits, streamlining previously labor-intensive workflows. It utilizes a flexible model of items, shopping lists, and kits to ensure kits display accurately based on local inventory and customer needs.
-
/articles/liquid-clustering-lakehouse-layout/en/smallimage/liquid-clustering-lakehouse-layout-thumbnail-1791465984987.jpg)
When Should You Use Liquid Clustering? Benchmarking Lakehouse Layout Strategies
Physical data layout is one of the most consequential decisions in lakehouse engineering. The author compares Liquid Clustering, ZOrdering, and partitioning across four workload types on Delta Lake, uncovering two undocumented failure modes that likely affect production systems today and offering a decision framework for choosing the right layout strategy.