V. VINOD LOGANATHAN RAMESH KUMAR
← Selected work

Intuit · Platform engineering

Shared AgentOps operations layer

Shared service context, policy, and audit across a large microservices estate.

Platform scope 1,000+ microservices in the supported estate.

What this scale represents

Supported estate
The figure describes the size of the developer microservices estate supported by shared cloud operations at Intuit.
Adoption
Active workflow usage and adoption rates are not quantified in this case study. Estate size alone does not establish how many services or teams actively use each workflow.
AGENTOPS PLATFORM
Developer services Supported estate: 1,000+ microservices
Shared operations layer Routing · service context · policy · audit
GCP & GKE Telemetry Runbooks Verified actions
Conceptual overview of my engineering work

Problem

A large microservices estate needs consistent support workflows while keeping service ownership and operational context clear to individual teams.

My contribution

Architected shared AgentOps infrastructure for routing, service context, policy, telemetry, and auditable operational actions.

Scope and ownership

The shared workflows support a service estate of 1,000+ developer microservices. I focused on common context, guardrails, and audit while service teams retained their operational decisions.

Architecture decision

I built a shared control plane for common context and policy instead of a centralized remediation service. Centralizing every action promised tighter consistency, but would have obscured team ownership and created a bottleneck. The control plane standardizes discovery, guardrails, and audit while each service retains its operational decisions.

ADR 03 · Shared context, distributed ownership

Portfolio decision summary

Alternative considered

A centralized remediation service promises consistency, but risks becoming a bottleneck and obscuring service ownership.

Trade-offs & consequences

Share discovery, policy, and audit infrastructure while keeping operational decisions with service teams.

Operating constraints

The platform must scale across independent services, preserve team context, and provide a common operational path without centralizing every decision.

This case study summarizes my professional work. The diagram is a conceptual overview, and architecture decisions are portfolio summaries.