If you’ve got a number of APIs working at the same time, to keep your business running smoothly, you need something that throttles your traffic, monetizes your applications and monitors your security - and that’s exactly what you get with our API Gateway.
Our solution acts as an entry point for all your APIs and:
- Enforces API publishers’ policies
- Validates subscriptions
- Collects useful metrics
- Controls pre-determined quotas
The best bit? You don’t need coding. You don’t need to customize it. And you manage it all in one place; your Publisher Portal.
- Bulk policy enforcement (via the Publisher Portal)
- Easy authorization and authentication
- Automatic quota alerts
- Configure your own custom thresholds
- Sales metrics hand-delivered in your reports
- Manage traffic and API spikes with no fuss
- Schema validation and token management
- Built-in subscription validation and auto-renewal facility
- Set usage quotes, rate limits, and request time-outs
- Event-driven patterns implement gateways with high concurrencies
DigitMarket API Gateway?
Scalability Made Simple
Our gateway supports OpenAPI and custom-based HTTP models and breaks all requests down into events that can be processed in parallel, so you’ll never fall victim to the bottleneck effect.
How this looks in practice?
In theory, this leaves you with infinite scalability options; your hardware is the only limit.
Unlimited and Exclusive Options
Modeled on multi-gateway architecture, our solution allows you to create as many gateways as you like. Either create a new instance yourself (northbound mode) or let your customers set-up one of their own (southbound mode), but keep control with the northbound’s visibility settings - for partners, internal, and external developers, etc. to set-up exclusive, on-demand gateways.
Automatic Threshold Management
With built-in auto-scale capabilities, our gateway easily copes with limit breaches by automatically cloning a new gateway and attaching it to the cluster - all without you lifting a finger!
Providing you configure “auto-scaling” in the target Cloud environment (private, AWS, or otherwise) our API Gateway is always horizontally scalable.
Flexibility and Choice at Hand
We understand you’ll want to keep sensitive, customer information on-site, but that non-sensitive APIs are okay on the hybrid cloud, for example. So, we created our gateway in a way that allows a central management interface to control all your instances for you - so you can get on with the rest of your day.
By combining our market-leading DigitMarket API Gateway with our API Developer Portal and Publisher Portal, you’ll arm your business with a complete API management solution that:
- Accelerates and revolutionizes your digital transformation programme
- Benchmarks success for the rest of your industry
What is DigitMarketTM API Manager (DM-APIM)?
DigitMarketTM API Manager (DM-APIM) is a complete package to help manage your APIs and make them into tools that propel your business forward.
Our API Management product, “DigitMarketTM API Manager” has four components that work in unison to provide the following basic runtime functionality:
The Publisher Portal
The API publishers configure the APIs, API packs, usage plans, usage policies and so on using this portal. Key features:
- Create secure API proxies.
- Create API packs from multiple APIs.
- Advanced Policy library with facility to share policies across multiple APIs.
- Workflow/approval cycles on policy lifecycle.
- Configure transformations at API and resource levels.
- Ability to create multiple usage plans with different set of runtime policies for each plan Ex: Basic, Gold, Silver, Platinum, etc.
- Ability to selectively deploy and manage plans on different gateway runtime instances from a single screen.
- Near-real-time statistics visualisation.
- Advanced and highly granular role-based access control for all features - API Visibility, management, publishing and consuming.
The Developer Portal
The developers discover, explore, try out and subscribe to the publishers’ APIs using this portal. The publisher can tailor the appearance of the developer portal as per their needs. Key features:
- Developer self-registration.
- Ability to search and navigate the portal with the same user experience of an online store; with clear listing of most popular APIs, What's new, API price, description, etc.
- Facility to manage the subscriptions through an easy interface.
- Ability for internal and external developers, API providers to quickly view statistics of their API usage.
- Facility for API providers to easily expose/create APIs by proxying existing endpoints and attaching policy templates.
- Help / support ticket system built-in for API developers to report issues, bugs, etc.
The gateway enforces the policies defined by the publishers, validates the subscriptions, collects metrics, and enforces quotas. The gateway is configured and managed using the publisher portal. No coding or customisation is required. Key features:
- Event-driven paradigm used to implement the gateway, hence high concurrencies can be achieved easily.
- Policy enforcement (details of each policy is described in our answer to the next question).
- Cluster-wide policy enforcement.
- Quota overrun alerts with configurable threshold.
- Transaction recording for analytics.
- Multi-gateway runtime architecture to support isolation of high-traffic, high-volume APIs. Configuration and management is central though.
- Subscription validation and auto-renewal facility.
OAuth Authentication Server
- Token management.
- Supports OAuth custom grant types.
What happens when the Gateway encounters heavy traffic?
The gateway architecture supports very high concurrency as it is significantly different from traditional HTTP engine architecture. A traditional HTTP engine uses thread pools to handle request-response pairs. Each request is allocated a dedicated thread from the thread pool. Most of the requests involve an external interface, such as a database request or a third-party service call. When the thread waits for a response from external interfaces, it is idle, as it cannot be re-used to perform other tasks. Each thread consumes operating system resources such as CPU and memory, so there is a physical limitation to the number of threads in a pool to support concurrent requests.
Our gateway is built on Vert.X, which follows a different architectural approach. It uses an event bus instead of a thread pool. Any request that involves waiting for a response is pushed to the event bus, and does not consume OS resources. The event resumes asynchronously when a response is received from external interface. Hence, there is no wastage of OS resources when HTTP requests are being processed, thereby significantly increasing the concurrency for very high volume of requests. The same architecture is used by the security engine to perform OAuth and other policy enforcements, so security heavy, high-volume transactions are supported without requiring high-end hardware.
Does the API Gateway have the capability to auto-scale?
The gateway deployment architecture supports “Auto-Scale” capability, where thresholds can be configured for each gateway virtual machine. Once the threshold increases the limits, the system automatically clones a new gateway virtual machine, and attaches it to the cluster. The system is horizontally scalable, when the “Auto-Scaling” is configured in the target Cloud environment, such as AWS or on a private Cloud environment such as VM-Ware or OpenStack.
What are the functionalities of the Micro-gateway?
The gateway component of DigitMarketTM can function both as a central gateway and multiple instances of micro gateways. It can be deployed on separate containers/machines and function as a service mesh. The micro gateway instances can be configured and monitored via the common Admin UI of the DigitMarketTM API publisher portal. It supports hybrid management topologies; i.e central management and distributed management at the same time.
Digital Enablement Platform
digital capability for Pure Planet