Reading Time: 4 minutes

We’re excited to announce the general availability of Managed Flex Gateway – the newest addition to our suite of API gateway solutions. Managed Flex Gateway is a fully managed API gateway for APIs running anywhere – built both with and without MuleSoft.

What is Managed Flex Gateway?

Managed Flex Gateway solves the challenges posed by self-managed gateway solutions. These place the burden of maintenance and operations fully on an IT team – managing scaling, patching, and troubleshooting on a 24/7 basis. Additionally, teams have to provision and configure the underlying infrastructure, like a Kubernetes cluster, and deploy the gateway runtime, along with related dependencies. 

Managed Flex Gateway eliminates all of this complexity. With a simple single-click deployment to CloudHub 2.0, it’s dramatically faster to get started. Managed Flex Gateway has high availability and scaling automatically enabled. The scaling of CPU, memory, and runtimes is all managed for you. Underlying software upgrades are all one-click and automated. Managed Flex Gateway can handle high volumes of requests – up to 500 requests/second. It’s fully integrated with Anypoint Monitoring so you’ll have near real-time oversight over all of your gateways. 

Managed Flex Gateway ensures your security through use of a Private Space – ensuring logical isolation from other Cloudhub 2.0 deployments. You can use transit gateways in a private space to connect the gateway instance to VPCs within your own infrastructure.  

Alongside this launch, we’re pleased to announce the launch of outbound policies for Flex Gateway. Previously, the scope of policies has been limited to the ingress path. Our initial policies include basic auth, OAuth, Lambda, circuit breaker, and timeout. These new out-of-the-box API policies will work with both Managed Flex Gateway and self-managed Flex Gateway. Additionally, custom policies will work across both versions. 

What gateway should I use?

People often ask which gateway they should be using. Here’s a quick guide to know which gateway to use – and when:

  • Mule Gateway: Use for APIs deployed in Mule runtimes or as a standalone proxy for Mule/non-Mule APIs
  • Flex Gateway: Use if you have high performance or high scale requirements or have requirements to implement a specific architecture
  • Managed Flex Gateway: Use to protect non-Mule APIs, if you need a turnkey, low operational burden solution