- Need to run many decentralized APIs ? Do not want to use a central gateway ?
- Want to protect your API or Application with Application Firewall functionality ?
- Throttle heavy load to protect your APIs and services ?
- Want to deploy API Gateway next to each individual API, as a "sidecar" in a service mesh ?
...
Ceptor Microgateway in its standalone mode includes Ceptor Console, Ceptor Configuration Server, Ceptor Session Controller and Ceptor Statistics Server as well as an embedded or external database for APIs (if used as an API Microgateway).
What is an API Microgateway ?
An API microgateway is a proxy (reverse and regular) server which sits close to an individual microservice.
As a result, it provides value to the developers by extracting governance, discovery, observability and stability in a reusable component and gives value to the operators by exposing the Policy Enforcement Point (PEP) and Security Controls in a centralized control panel. And, thus, you end up with a system that is a service mesh allowing one to externally control service monitoring, availability, tracing, request (version) routing, resiliency testing, security and policy enforcement, etc., in a consistent way across all services in an enterprise.
What is a Web Microgateway ?
...
| Code Block |
|---|
bin/ceptor_microgateway |
Using Docker
At Docker Hub, you can find the Docker Image ceptor/ceptor-base-microgateway:latest which contains a deployment/configuration for a Ceptor Microgateway configured as an API Gateway along with an embedded Derby database - connect to Ceptor Console at https://localhost:4243 and to the gateway on port 8443.
...