InfoQ Homepage Programming Content on InfoQ
-
/articles/building-ai-agent-gateway-mcp/en/smallimage/building-ai-agent-gateway-mcp-thumbnail-1771417896950.jpg)
Building a Least-Privilege AI Agent Gateway for Infrastructure Automation with MCP, OPA, and Ephemeral Runners
This article presents a least-privilege AI Agent Gateway that places clear controls between AI agents and infrastructure. Agents do not access infrastructure APIs directly. Instead, every request is validated, authorized using policy as code with Open Policy Agent (OPA), and executed in short-lived, isolated environments, with built-in observability using OpenTelemetry.
-
/articles/architecting-agentic-mlops-a2a-mcp/en/smallimage/architecting-agentic-mlops-a2a-mcp-1770303550343.jpg)
Architecting Agentic MLOps: a Layered Protocol Strategy with A2A and MCP
In this article, the authors outline protocols for building extensible multi-agent MLOps systems. The core architecture deliberately decouples orchestration from execution, allowing teams to incrementally add capabilities via discovery and evolve operations from static pipelines toward intelligent, adaptive coordination.
-
/articles/ai-generated-mvp/en/smallimage/thumbnail-ai-generated-mvp-1770282822570.jpg)
You’ve Generated Your MVP Using AI. What Does That Mean for Your Software Architecture?
AI‑generated code creates implicit architectural decisions, forcing teams to rely on experimentation to validate quality attributes. To get useful results from AI, teams must clearly express trade‑offs and reasoning so the model can generate solutions aligned with desired QARs.
-
/articles/prompts-to-production-playbook-for-agentic-development/en/smallimage/prompts-to-production-playbook-thumbnail-1770374539263.jpg)
From Prompts to Production: a Playbook for Agentic Development
In this article, author Abhishek Goswami shares a practitioner's playbook with development practices, that describes building agentic AI applications and scaling them in production. He also presents core architecture patterns for agentic application development.
-
/articles/jakartaee-12-milestone-2/en/smallimage/jakartaee-12-milestone-2-thumbnail-1770367607817.jpg)
Jakarta EE 12 Milestone 2: Advent of the Data Age along with Consistency and Configuration
Jakarta EE 12 Milestone 2 marks the beginning of the next generation of enterprise Java. It introduces Jakarta Query, a unified query language across Persistence, Data, and NoSQL, while aligning the platform with Java 21. This milestone focuses on integration, modernization, and improving developer productivity for cloud-native enterprise applications.
-
/articles/building-llms-resource-constrained-environments/en/smallimage/building-llms-resource-constrained-environments-thumbnail-1770217548603.jpg)
Building LLMs in Resource-Constrained Environments: a Hands-On Perspective
In this article, the author argues that infrastructure and compute limitations can drive innovation. It demonstrates how smaller, efficient models, synthetic data generation, and disciplined engineering enable the creation of impactful LLM-based AI systems despite severe resource constraints.
-
/articles/agent-assisted-intelligent-observability/en/smallimage/agent-assisted-intelligent-thumbnail-1769595476571.jpg)
From Alert Fatigue to Agent-Assisted Intelligent Observability
As systems grow, observability becomes harder to maintain and incidents harder to diagnose. Agentic observability layers AI on existing tools, starting in read-only mode to detect anomalies and summarize issues. Over time, agents add context, correlate signals, and automate low-risk tasks. This approach frees engineers to focus on analysis and judgment.
-
/articles/skeleton-architecture/en/smallimage/skeleton-architecture-thumbnail-1769508521191.jpg)
Working with Code Assistants: the Skeleton Architecture
Prevent AI-generated tech debt with Skeleton Architecture. This approach separates human-governed infrastructure (Skeleton) from AI-generated logic (Tissue) using Vertical Slices and Dependency Inversion. By enforcing security and flow control in rigid base classes, you constrain the AI to safe boundaries, enabling high velocity without compromising system integrity.
-
/articles/why-ml-projects-fail-production/en/smallimage/why-ml-projects-fail-production-thumbnail-1769072877092.jpg)
Why Most Machine Learning Projects Fail to Reach Production
In this article, the author diagnoses common failures in ML initiatives, including weak problem framing and the persistent prototype-to-production gap. The piece provides practical, experience-based guidance on setting clear business goals, treating data as a product, and aligning cross-functional teams for reliable, production-ready ML delivery.
-
/articles/ai-developers-rewriting-software-process/en/smallimage/ai-developers-rewriting-software-process-thumbnail-1768398859653.jpg)
Virtual Panel - AI in the Trenches: How Developers Are Rewriting the Software Process
This virtual panel brings together engineers, architects, and technical leaders to explore how AI is changing the landscape of software development. Practitioners share their insights on successes and failures when AI is incorporated into daily workflows, emphasizing the significance of context, validation, and cultural adaptation in making AI a sustainable element of modern engineering practices.
-
/articles/ai-assisted-development-series/en/smallimage/ai-assisted-development-thumb-image-1768388299998.jpg)
Article Series: AI-Assisted Development: Real World Patterns, Pitfalls, and Production Readiness
In this series, we examine what happens after the proof of concept and how AI becomes part of the software delivery pipeline. As AI transitions from proof of concept to production, teams are discovering that the challenge extends beyond model performance to include architecture, process, and accountability. This transition is redefining what constitutes good software engineering.
-
/articles/spec-driven-development/en/smallimage/spec-driven-development-thumbnail-1767777707872.jpg)
Spec Driven Development: When Architecture Becomes Executable
Spec-Driven Development inverts traditional architecture by making specifications executable and authoritative. It transforms declared intent into validated code through AI generation and provides architectural determinism. It eliminates drift through continuous enforcement, but demands new engineering discipline in schema design and contract-first reasoning.