AI : Learned Execution Graphs for Real-Time Anomaly Detection & Drift Classification in APIs
Ritvik Pandya
- When
- Thursday, July 21:30 PM – 1:50 PM · 20 min
- Where
- Track 5San Francisco, CA · imported from ai.engineer's public schedule feed
About this session
API ingress controllers process requests through ordered sequences of middleware steps — authentication, authorization, validation, rate limiting, routing, service invocation, caching. We model this pipeline as a directed acyclic graph (DAG) learned from structured telemetry events, then apply graph-based anomaly detection and drift classification in real time at 1,600+ TPS. The system emits one structured event per processing step, constructs per-endpoint execution graphs using sequence mining with statistical confidence thresholds, and learns per-node baselines (latency, dependency, execution frequency). Three graph intelligence capabilities emerge: (1) Graph-based anomaly attribution — compute per-node deviation ratios against learned baselines to identify the exact bottleneck node and its dependency. In production, this pinpointed a 41x deviation at a single graph node that was invisible to service-level monitoring, reducing root cause identification from 2-3 hours to under 30 seconds. (2) Graph structural drift detection — compare observed node sequences against the learned graph topology to detect missing nodes (mandatory processing step silently skipped), reordered nodes (middleware misconfiguration), and unexpected new nodes (unauthorized middleware injection). Traditional monitoring reported "system healthy" when a mandatory node was removed — latency dropped, errors at zero — only the learned graph comparison detected the structural change. (3) Per-client graph fingerprinting — learn client-specific execution graph profiles using exponential moving averages. Detect when a client's graph traversal pattern changes, classify the cause (client behavior change vs. configuration drift vs. infrastructure failover) using KL divergence on node-visit distributions, and apply graph-aware adaptive control scoped to specific nodes rather than entire endpoints. The execution graph model also enables a novel approach to retry storm detection: analyzing idempotency key entropy at graph nodes to classify traffic as legitimate growth vs. retry amplification, and returning cached responses at the specific graph node rather than rejecting requests — breaking the retry amplification loop. Production system processing high TPS. Attendees will learn the graph construction methodology, the anomaly attribution algorithm, and concrete patterns for adding learned graph intelligence to any middleware pipeline.
Speaker
Engineering Manager, JP Morgan Chase
Ritvik Pandya is an engineering leader with over seventeen years building distributed systems and large-scale payment infrastructure, currently at JPMorgan Chase, with prior experience at other leading technology companies. He works at the intersection of platform engineering, observability, and reliability — designing high-throughput systems that stay dependable under real-world load. He writes and speaks on building dependable systems at scale, and is a member of the IEEE Consumer Technology Society.
More in Graphs
- Thinner Agents on a Smarter Substrate: The Ontology-based Semantic LayerThursday, July 2 · 10:20 AM – 10:30 AM · Main Stage
- CrabRAG: Why Automated Assistants Need Graph Memory, Not More TokensThursday, July 2 · 10:45 AM – 11:05 AM · Track 5
- Active Graph Agent Runtime (BabyAGI 4)Thursday, July 2 · 11:10 AM – 11:30 AM · Track 5
- Your Moat Is Your Data ModelThursday, July 2 · 11:40 AM – 12:00 PM · Track 5
- From Systems of Record to Systems of ContextThursday, July 2 · 12:05 PM – 12:25 PM · Track 5
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.