Agents Are Where Microservices Were in 2015. We're Making All the Same Mistakes.
Roberto Milev, Uday Kanagala
- When
- Wednesday, July 12:50 PM – 3:10 PM · 20 min
- Where
- Leadership 1San Francisco, CA · imported from ai.engineer's public schedule feed
About this session
Remember when everyone was shipping microservices without service discovery, circuit breakers, or distributed tracing? Agents are in that exact phase right now. Everyone's building them. Almost nobody is thinking about the infrastructure underneath. We've been deploying production agents across 120+ microservices. Here's the stack that's emerging: Runtime — containerized execution, session persistence, workspace snapshots. Solved-ish, mostly duct tape. Memory — RAG had a good run. It's not enough. Tiered memory — short-term, long-term with semantic/episodic strategies, agents deciding what to remember and forget. Observability — you can't tail -f an agent. Execution traces, reasoning chains, confidence signals — agents need their own observability stack. Testing — the biggest gap. Unit testing non-deterministic behavior, regression testing prompt changes, knowing your agent got worse before users do. Skills and tools — MCP and skill definitions as the standard interface layer — the REST APIs of the agent era. Context engineering — what the agent knows at decision time. The new performance tuning. Guardrails and auth — scoped credentials, budget limits, knowing when to stop. Least-privilege for agents. Orchestration — single vs. multi-agent, choreography vs. orchestration. Same tradeoffs as microservices, new failure modes. This talk maps the stack, draws the parallels to how we eventually got microservices right, and calls out what's still painfully missing.
Speakers (2)
Chief Architect, Navan
Roberto Milev is Chief Architect at Navan, where he leads AI architecture across 120+ microservices and 20 engineering teams. His work on autonomous agent systems has been published at ACM CAIS 2026, and he has presented at OpenAI and the UnLock conference on AI architecture topics.
Software Architect, Navan
Uday Kanagala is a Software Architect at Navan with experience in cloud-native distributed systems, microservices, DevOps, and autonomous-agent workflows for production issue resolution and architectural governance.
More in AI-Native Enterprises
- Building the engine while flying the plane — launching the Figma MCP serverTuesday, June 30 · 11:10 AM – 11:30 AM · Leadership 1
- Agentic SDLC at Uber: Building Blocks for Uber's Software FactoryTuesday, June 30 · 11:40 AM – 12:00 PM · Leadership 1
- Scaling Code Quality: Building uReview, Uber’s Multi-Agent Code Review EngineTuesday, June 30 · 12:05 PM – 12:25 PM · Leadership 1
- AI Evals Platform for Cross-Functional Teams at ScaleTuesday, June 30 · 1:55 PM – 2:15 PM · Leadership 1
- Productionizing LLM Gateways: Architecture, Tradeoffs, and Hard Lessons from the TrenchesTuesday, June 30 · 2:25 PM – 2:45 PM · Leadership 1
For developers: this programme is open data — JSON, iCal, schedule XML and an MCP endpoint.Show endpointsHide
- JSONEvery published session and speaker, in one request./aie-worldsfair-2026-import/feed.json
- iCalSubscribe in Google, Apple or Outlook Calendar./aie-worldsfair-2026-import/feed.ics
- Schedule XMLfrab / pentabarf — the format conference apps import./aie-worldsfair-2026-import/feed.xml
- MCP + RESTPoint Claude at the programme. OpenAPI 3.1 included./agents
No key, no signup, CORS open. Everything here is generated from the same data the organisers edit.