webMethods Microgateway

Along with distributed microservices architectures comes the challenge of managing microservices security. Designed to sit closer to business logic and protect it, webMethods Microgateway is your solution. This independent gateway—lightweight, agile and fast—works with webMethods API Gateway or as a standalone solution to secure your microservices in a distributed environment. Highly efficient, the gateway uses a very small footprint and is fast to deploy.

IT needs better and faster ways to scale infrastructures to meet dynamic business demands. That’s why microservices architectures are trending. Small, independently deployable services built around business capabilities are ideal for rapid development and continuous delivery.

With a distributed architecture, you need to be able to scale up and down quickly while serving many more systems and gateways you don’t want to overload.

webMethods Microgateway answers this requirement perfectly. With a “micro” footprint, you can:

• Manage API access to your microservices across a distributed architecture
• Prevent main gateways from overloading
• Reduce the impact from routing and traffic through a single gateway while supporting east-west traffic  

• Secure and mediate API access to microservices
• Apply routing policies and throttling to manage consumer-provider connectivity
• Optionally federate microgateways with API Gateway for centralized management and monitoring
• Deploy in multiple form factors to support different scalability and management goals
• Easily provision and scale across microservices architecture
• Very low runtime footprint
• Fast start-up

Multiple form factors

Provision webMethods Microgateway as a Java^® instance or as a Docker^® container with a micro-Linux^® host. As a self-contained Java app, the microgateway is a “headless” implementation that’s independent, lightweight and agile. In a “Dockerized” configuration, the microgateway includes a micro-Linux host and is scalable and lean.

Flexible deployment patterns

Microservices architectures need different levels of granularity and control—so webMethods Microgateway gives you options. In a standalone deployment, the microgateway can run independently from the microservice. When the microservice dies, the microgateway continues to function. This option is preferable when the microgateway hosts multiple APIs and needs to be scaled independently.

In a sidecar deployment, the microgateway runs close to the business logic. It scales together with the microservice but likely only contains policies for a single microservice. This option leaves no network gaps and eliminates potential latency issues.

Seamless failover with service registry support

In a microservice landscape, service registries maintain information about service instances and their endpoints. If a microservice becomes unavailable in the cloud, a service registry will enable you to automatically failover to another running instance. If you choose a service registry, the microgateway sends a request to the service registry to discover the IP address and port where the service is running. Improve service availability in the cloud by configuring a registry for endpoint management.

Traffic monitoring and control

Throttle traffic with policies to manage the load on provider services. Apply limits to service invocations during a specific time interval for identified clients. Log all traffic requests and responses for analysis.

Accelerate your API programs and build a rich API ecosystem with Software AG, named a leader by two leading analysts. Software AG was ranked a Leader in API management in the Forrester Wave^™ and Gartner Magic Quadrant. See why you can trust your API management to Software AG. Read the reports.