Edge – Capabilities
4
Edge is comprised of several stateless components that use infrastructure services to persist data:
● Gateway: Routing and API calls processing.
● UIs: Enterprise UI, Developer Portal.
● Infrastructure Services: Persistence of runtime, analytics and management.
● Management Server: Provides REST API for all configuration and management tasks.
Note: Monetization, not shown in the diagram below, is part of Developer Services and leverages Gateway, Analytics
Services and Management Server
Edge – Scalability 5 ● Management Server, Analytics Backend and Developer Portal can also be set up for high availability (HA). Multiples instances of these capabilities within a single zone or across zones is possible. ● Gateway, Infrastructure services, analytics and other capabilities can scale-out independently from each other
Edge – Scalability 6 ● Multi-DC and DR scalability. ● Edge is capable of scaling across multiple DCs/Regions in a active/active fashion. ● Active data replication between sites using eventual consistency
Edge – Component View 8 Each box represents a process. These processes can be can be run on independent of each other or co-located across a limited number of VM/servers.
Edge - Technology Stack 9 Edge components are, in general, Java based. Most components are based on a homegrown technology stack that leverages best in class open source technology under it. Below we highlight some of the underlying technologies used as building blocks.
Scaling by capability 10 ● Given the responsibility and capabilities offered by each component, scalability requirements and how they are implemented may vary. ● In most scenarios, scaling to accommodate higher API volume may impact only components serving live API traffic. ● Analytics data components may have to be scaled in response to increased API traffic and/or raw analytics data retention policy. ● Other components may grow in number mostly driven by high availability requirements for those capabilities
Multitenancy
Planets represent an entire physical installation and it can encompass multiple regions and pods.
Regional Services are shared by many pods across a single geographical region and maintain state and provide an API that works across the pods in a region. Pods are a collection of servers that share logical functions such as a Gateway Pod or an Analytics Pod. Orgs provide logical grouping to secure access to API management services. Orgs are associated with pods for servers – they can either share hardware or be isolated. Environments are virtual routes that allow API bundles to be deployed and tested within and Org. Environments can be associated with pods for servers independently of the Org. Virtual Hosts are similar to Apache Virtual hosts and route traffic to environments based on ports and domain names. Planet P
Edge – Scalability 5 ● Management Server, Analytics Backend and Developer Portal can also be set up for high availability (HA). Multiples instances of these capabilities within a single zone or across zones is possible. ● Gateway, Infrastructure services, analytics and other capabilities can scale-out independently from each other
Edge – Scalability 6 ● Multi-DC and DR scalability. ● Edge is capable of scaling across multiple DCs/Regions in a active/active fashion. ● Active data replication between sites using eventual consistency
Edge – Component View 8 Each box represents a process. These processes can be can be run on independent of each other or co-located across a limited number of VM/servers.
Edge - Technology Stack 9 Edge components are, in general, Java based. Most components are based on a homegrown technology stack that leverages best in class open source technology under it. Below we highlight some of the underlying technologies used as building blocks.
Scaling by capability 10 ● Given the responsibility and capabilities offered by each component, scalability requirements and how they are implemented may vary. ● In most scenarios, scaling to accommodate higher API volume may impact only components serving live API traffic. ● Analytics data components may have to be scaled in response to increased API traffic and/or raw analytics data retention policy. ● Other components may grow in number mostly driven by high availability requirements for those capabilities
Multitenancy
Planets represent an entire physical installation and it can encompass multiple regions and pods.
Regional Services are shared by many pods across a single geographical region and maintain state and provide an API that works across the pods in a region. Pods are a collection of servers that share logical functions such as a Gateway Pod or an Analytics Pod. Orgs provide logical grouping to secure access to API management services. Orgs are associated with pods for servers – they can either share hardware or be isolated. Environments are virtual routes that allow API bundles to be deployed and tested within and Org. Environments can be associated with pods for servers independently of the Org. Virtual Hosts are similar to Apache Virtual hosts and route traffic to environments based on ports and domain names. Planet P
ليست هناك تعليقات:
إرسال تعليق