November 22, 2026

From Manual Ticketing to Programmatic APIs: Manoj Kagitha on the Architectural Evolution of Modern Cloud Infrastructure

In the rapidly evolving landscape of enterprise technology, the transition from legacy operational models to modern, automated frameworks is often cited as a primary goal for digital transformation. However, the practical reality of this shift involves a complex dismantling of decades-old habits and the careful construction of programmatic interfaces. Manoj Kagitha, a Senior Cloud Engineer at Digital Realty, recently joined hosts Ned Bellavance and Kyler Middleton on the Packet Pushers podcast, sponsored by Meter, to provide a deep dive into the architectural challenges and triumphs of replacing manual workflows with a robust API-driven platform.

Digital Realty, a global leader in data center, colocation, and interconnection solutions, sits at the heart of the world’s digital infrastructure. For a company of such scale, the efficiency of internal and external operations is not merely a matter of convenience but a critical component of service delivery. Kagitha’s insights shed light on the sophisticated engineering required to move away from the traditional "email and ticket" culture toward a future defined by microservices, automated service buses, and rigorous API management.

The Architectural Shift: Moving Beyond the Inbox

For many years, the standard operating procedure for requesting infrastructure changes—whether provisioning a new virtual machine, adjusting network configurations, or updating security policies—revolved around manual communication. This often took the form of sprawling email chains or static ticketing systems where requests were logged, assigned to a human operator, and eventually fulfilled manually.

As Kagitha explained during the discussion, this legacy approach is fraught with bottlenecks. Email chains lack a single source of truth, making it difficult to audit changes or track the status of a request in real-time. Manual ticketing, while more structured, still relies on human intervention at every step, which introduces the risk of human error and significantly slows down the pace of deployment.

The alternative presented by Kagitha is the development of a programmatic API platform. In this model, infrastructure is treated as code, and operational tasks are exposed as API endpoints. This allows for self-service capabilities where developers or automated systems can trigger infrastructure changes without ever having to send an email or wait for a ticket to be picked up by a technician. This shift represents a fundamental change in the "architectural reality" of the enterprise, moving from a reactive stance to a proactive, automated one.

Translating Human Knowledge into Automated Logic

One of the most profound challenges Kagitha highlighted is the difficulty of translating human operational knowledge into machine-executable rules. In a legacy environment, experienced engineers often possess "tribal knowledge"—an intuitive understanding of the nuances, edge cases, and safety margins required to keep a system running. When a human processes a ticket, they apply this context naturally.

Automating this process requires codifying that intuition into logic. Kagitha discussed the necessity of defining strict rules, rate limits, and service bus workflows to ensure that automation does not inadvertently cause system instability. For instance, while an API can provision resources in seconds, the underlying physical and virtual infrastructure must be protected from sudden surges in demand.

Rate limiting, therefore, becomes a critical architectural component. It ensures that no single user or process can overwhelm the system, maintaining the quality of service across the entire platform. Furthermore, the use of service buses allows for asynchronous processing. Instead of a request blocking the system while it waits for a long-running task to complete, the request is placed on a bus, processed by the relevant microservices, and the state is updated once the task is finished. This decoupled architecture is essential for building scalable, resilient platforms that can handle the complexity of a global data center provider.

Managing Microservices with Apigee X

Central to Digital Realty’s programmatic evolution is the use of Apigee X, Google Cloud’s API management platform. Kagitha provided technical details on how Apigee X serves as the gateway for the company’s microservices architecture. By placing Apigee X in front of their services, the engineering team can centralize security, monitoring, and traffic management.

Apigee X allows for the creation of a consistent interface for developers, regardless of the complexity of the backend services. It provides a layer where authentication and authorization can be enforced uniformly, ensuring that only authorized users can access sensitive infrastructure APIs. Moreover, it offers deep visibility into how APIs are being used, allowing Kagitha and his team to identify performance bottlenecks or unusual usage patterns before they escalate into outages.

The discussion also touched upon the coordination required to manage these microservices. Unlike a monolithic application, where all components are tightly coupled, a microservices architecture involves many independent services communicating over a network. While this offers greater flexibility and allows teams to deploy updates independently, it also introduces challenges in terms of service discovery and inter-service communication. Kagitha emphasized that the success of such a system depends on a well-defined contract between services, often mediated by the API gateway.

Navigating Cloud Infrastructure Migrations

Beyond the internal software architecture, Kagitha discussed the broader challenge of managing cloud infrastructure in a state of constant flux. Cloud providers frequently retire older generations of hardware and software, forcing enterprises to migrate their workloads to newer, more efficient platforms.

Migrating away from retiring cloud infrastructure is a high-stakes endeavor. It requires meticulous planning to ensure that there is no disruption to live services. Kagitha noted that this process involves not just moving data, but also updating the automation logic and API endpoints that interact with that infrastructure. The goal is to make these migrations as transparent as possible to the end-user. By abstracting the underlying infrastructure behind a programmatic API, the team can swap out the backend components—moving from an old cloud region to a new one, for example—without changing the way the user interacts with the service.

This "infrastructure agility" is a primary motivator for the work Kagitha is doing at Digital Realty. In an era where hardware cycles are shortening and cloud offerings are constantly expanding, the ability to pivot quickly is a significant competitive advantage.

The Role of the Modern Cloud Engineer

The conversation with Kagitha also highlighted the changing role of the cloud engineer. In the legacy world, an engineer’s value was often tied to their ability to troubleshoot specific, manual problems. In the programmatic world, the engineer’s role is to build the systems that prevent those problems from occurring in the first place.

As seen through Kagitha’s work and his contributions to the technical community—including his writing on Dev.to and his projects on GitHub—the modern cloud engineer is as much a software developer as they are a systems administrator. They must be proficient in API design, microservices orchestration, and the use of advanced tools like Apigee X.

The transition Kagitha describes is not just a technical upgrade; it is a cultural shift. It requires moving away from the comfort of manual control and embracing the discipline of automation. While the hurdles are significant—ranging from the technical debt of legacy systems to the difficulty of codifying human logic—the rewards are a more scalable, resilient, and responsive infrastructure.

Episode Links:

Watch this episode on YouTube

Manoj Kagitha’s Website

Manoj Kagitha on GitHub

Manoj Kagitha on X

Manoj Kagitha’s Writing