InfoQ Homepage Development Content on InfoQ
-
/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/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/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/regeneratable-ui-component-library/en/smallimage/regeneratable-ui-component-library-thumbnail-1790758478325.jpg)
From Reusable to Regeneratable: Rethinking the Shared UI Component Library
Regeneration has changed reuse economics. A model pointed at a solid design system can produce most standard UI on demand, so paying to keep a canonical component package alive is much harder to justify than it used to be. Keep the design system, tokens, guidelines and tests central. They are what actually buy you consistency.
-
/articles/high-availability-not-resilience-cloud/en/smallimage/high-availability-not-resilience-cloud-thumbnail-1790670587417.jpg)
High Availability is Not Resilience: Why Cloud Systems Fail When it Matters Most
A routine TLS 1.3 upgrade silently broke Route 53 health checks, causing a CDN to stop routing traffic to a healthy region while internal dashboards showed nothing wrong. This article examines why HA and resilience are different problems, how control-plane dependencies create invisible failure modes, and why recovery capability erodes without explicit ownership.
-
/articles/ai-agents-improve-software-architecture/en/smallimage/ai-agents-improve-software-architecture-thumbnail-1790153650841.jpg)
Five Ways to Use AI Coding Agents to Improve Your Software Architecture
Modern architectures often use legacy services for specific tasks, but these services may lack accurate documentation and using them can be risky if you don't understand them well. AI coding agents can help close that knowledge gap.
-
/articles/agent-harness-build-one/en/smallimage/The-Agent-Harness-What-It-Is-and-Two-Ways-to-Build-One-thumb-1789997776393.jpg)
The Agent Harness: What it is and Two Ways to Build One
This article explains the development and operational layers of an agent harness through two implementations of a finance assistant: AWS AgentCore Harness and LangChain with Envoy AI Gateway. It compares how each handles tools, memory, model access, cost control, and observability, and examines the trade-offs in operational ownership, portability, and engineering effort.
-
/articles/modular-edge-computing/en/smallimage/modular-edge-computing-thumbnail-1790163631197.jpg)
Modular Edge Computing at Multi-Tenant SaaS Scale on Cloudflare Workers
At multi-tenant SaaS scale, a monolithic edge worker creates deployment coupling and broad blast radius. The article presents a modular Cloudflare Workers architecture using service bindings, with image optimization as a worked example of per-tenant format negotiation and device-aware sizing. It covers multi-CDN differences, staged releases, configuration, and testing.
-
/articles/secure-scalable-facial-verification/en/smallimage/secure-scalable-facial-verification-thumbnail-1789468796366.jpg)
Architecting Secure and Scalable Facial Verification Systems
When three thousand employees verify at once, synchronous API calls collapse. This article presents a four-layer architecture for high-volume face verification: client-side filtering that cut cloud costs 30%, decoupled detection and verification enabling 10x scaling, risk-based dynamic thresholds, and zero-trust privacy with consent gates and automated data purging for GDPR and HIPAA.
-
/articles/next-dsl-author-language-model/en/smallimage/Your-Next-DSL-Author-Is-a-Language-Model-thumb-1789048983233.jpg)
Your Next DSL Author is a Language Model
In this article, the author introduces Typed Domain Grounding, an approach to reducing LLM hallucinations in domain-specific languages by embedding them in mainstream typed languages. Using kUML benchmarks and an infrastructure-as-code example, he explores how compiler validation and generate-compile-repair loops can make model-generated DSL output more reliable.
-
/articles/chaos-engineering-ecs-payments/en/smallimage/chaos-engineering-ecs-payments-thumbnail-1788254676411.jpg)
Implementing Chaos Engineering in Financial Payment Systems: Lessons from Enterprise ECS Deployments
Standard chaos engineering assumes experiments stop cleanly, blast radius is knowable in advance, and production is fair game. Payment systems violate all three. Salim Adedeji describes ECS-specific failure modes from enterprise deployments: a 60-second DNS TTL that produced 93-second failover, retry logic amplifying database load 2.4x, and AZ rebalancing loops that generic tooling misses.