Microservices

We Mapped 115 Microservices for Our Coding Agents — Kamalakannan Nandagopal, Postman

We Mapped 115 Microservices for Our Coding Agents — Kamalakannan Nandagopal, Postman

Kamalakannan Nandagopal from Postman explains why coding agents struggle beyond a single repo and how an API context graph, grounded in code and production telemetry, gives agents system-wide awareness. The talk covers evals built from real PRs, wins on API discovery, redesign and impact assessment, a stale-graph failure, and a 21-page architecture review generated by the agent.

Operating Distributed Inference Systems at Scale — Nishant Gupta & Naman Ahuja, Meta

Operating Distributed Inference Systems at Scale — Nishant Gupta & Naman Ahuja, Meta

Meta's Nishant Gupta and Naman Ahuja explain how AI inference, the company's fastest-growing workload, requires a dedicated orchestration layer akin to Kubernetes for virtual machines. They detail the unique challenges of LLM serving compared to traditional microservices, emphasizing the intricate coupling of infrastructure layers, the distributed transaction nature of requests, and a seven-axis framework for scheduling. The talk concludes with the imperative to optimize for "cost per successful task" and the necessity of an inference-specific control plane to manage the complex interplay of latency, cost, and throughput.

AI-Native Organisations Run on Skills: How to Structure and Scale Them — Imad Touil, QuantumBlack

AI-Native Organisations Run on Skills: How to Structure and Scale Them — Imad Touil, QuantumBlack

Imad Touil explores the critical need for governing AI skills within organizations, asserting that skills represent the true repository of enterprise know-how. He contrasts simplified coding agent loops with complex, real-world product lifecycles, demonstrating how ungoverned skills lead to technical debt—including duplication, quality degradation, security risks, and lack of discoverability. Proposing a microservices-inspired approach, Touil outlines a centralized skills platform and human-led governance model essential for achieving deterministic workflows, boosting productivity, and mitigating risks in AI-native enterprises.

Platform Engineering for Developers, Architects & the Rest of Us • Daniel Bryant • GOTO 2025

Platform Engineering for Developers, Architects & the Rest of Us • Daniel Bryant • GOTO 2025

Daniel Bryant discusses platform engineering for software developers and architects, emphasizing treating platforms as internal products with developers as customers. He outlines a three-layered architecture, the evolution from monolithic systems to microservices, and the importance of 'golden bricks' over 'golden paths' for composability. Key takeaways include API-first design, minimizing cognitive load, avoiding leaky abstractions, and measuring success through frameworks like DORA and DevEx to achieve speed, safety, and scale.

The Last Human Code Review: Building Trust in AI-Generated Code — Itamar Friedman, Qodo

The Last Human Code Review: Building Trust in AI-Generated Code — Itamar Friedman, Qodo

Itamar Friedman discusses how the bottleneck in AI-driven development has shifted from code generation to code review. He argues that current AI models are not the constraint; rather, it's the lack of codified, accessible context for AI agents. The solution involves building context engines that cater to both human and AI needs, integrating deep architectural knowledge and historical data to transition from reviewing individual pull requests to analyzing a comprehensive software graph, ultimately leading to automated code governance and "AI wisdom."

MCP Tasks (async): Why Aren't Any Agents Supporting Them? — Cornelia Davis, Temporal

MCP Tasks (async): Why Aren't Any Agents Supporting Them? — Cornelia Davis, Temporal

Cornelia Davis explains why the MCP tasks specification, designed for durable, long-running, and interactive operations, hasn't seen widespread adoption. She details V1's architectural flaws, particularly concerning scalability and stateful human-in-the-loop interactions, and introduces V2's shift to a stateless core, client-initiated updates, and a clearer path for client-side durability, while outlining future work on scaling and adoption.