Building a multi-region or multi-cloud environment for your applications requires a lot of attention.
In a typical deployment, you would have an API gateway running close to the several application runtimes. You should enhance your deployment to support different regions in a given cloud, or in an even more distributed and hybrid scenario, multiple services running across other public clouds and on-premise environments.
The task gets even more challenging when we consider service mesh-based applications implementing canary releases, A/B testings, blue-green deployments, etc. Moreover, a zero-trust network requirement for distributed environments should be considered mandatory.
From the networking perspective, the multi-cloud environment should address critical requirements. For example, it should:
In summary, we recommend pursuing three key attributes:
Aviatrix provides complete and easy-to-manage connectivity solutions to support all typical networking requirements for single cloud and multi-cloud application development.
From the distributed application perspective, you should consider and address all topics listed above. Furthermore, all the necessary networking connectivity requirements should be in place already so you can implement all diverse topologies on top of the multi-region/multi-cloud platform.
Among these topologies and architecture, we could mention:
Kong provides technologies to implement both layers in enterprise architecture:
The following picture describes a reference architecture:
Notice the reference architecture focuses on the communication between the service mesh components from the application perspective only.
With the extensible list of networking requirements listed above, we recommend implementing a multi-cloud deployment with a combination of both companies' technologies. The picture below describes an example of a hybrid application platform:
While Kong and Kuma are implementing an application platform composed of both an API gateway and service mesh, Aviatrix solves all networking connectivity idiosyncrasies across multiple clouds.
A multi-region/multi-cloud application platform implementation must deal with multiple abstraction layers, including different network infrastructure and services running across multiple runtimes.
The synergistic use of network support technologies provided by Aviatrix, combined with products designed for cloud environments provided by Kong, allows architects to create topologies for their applications to address their technical and business requirements. In other words, customers conduct the technological decision-making process for the application architecture design. The products used must support the process and not the other way around.
Ever feel like you're fighting an uphill battle with your API strategy? You're building APIs faster than ever, but somehow everything feels harder. Wasn’t API-first supposed to make all this easier? Well, you're not alone. And now industry analys
It’s been almost a year since we released our Konnect Terraform provider . In that time we’ve seen over 300,000 installs, have 1.7 times as many resources available, and have expanded the provider to include data sources to enable federated managem
In the last two parts of this series, we discussed How to Strengthen a ReAct AI Agent with Kong AI Gateway and How to Build a Single-LLM AI Agent with Kong AI Gateway and LangGraph . In this third and final part, we're going to evolve the AI Agen
Survey Says: Google LLMs See Usage Surge, Most OK with DeepSeek in the Workplace Enterprise adoption of large language models (LLMs) is surging. According to Gartner , more than 80% of enterprises will have deployed generative AI (GenAI) applicatio
Kafka delivers massive value for real-time businesses — but that value comes at a cost. As usage grows, so does complexity: more clusters, more topics, more partitions, more ACLs, more custom tooling. But it doesn’t have to be that way. If your tea
A Practical Look at When (and When Not) to Use Ambient Mesh The word on the street is that ambient mesh is the obvious evolution of service mesh technology — leaner, simpler, and less resource-intensive. But while ambient mesh is an exciting develop
I'm commonly asked by customers for advice on how they can build a good platform cross-charging model for their organization. And my gut reaction is nearly always "don't." We'll come back to why I think that later, but first let's look at what cross