API Gateway Architecture

{{container}}{{container layoutStyle="columns"}}(((

This micro-learning will focus on describing the general architecture of the API Gateway. After this microlearning, the background of the API GW architecture should be clear

3

4

Should you have any questions, please contact academy@emagiz.com.

5

6

* Last update: October 20th, 2021

7

* Required reading time: 10 minutes

8

9

== 1. Prerequisites ==

10

* Intermediate knowledge of the eMagiz platform

11

* Good working experience in the Design phase Architecture and Deploy Architecture

12

* Created several API gateway integrations

13

14

== 2. Key concepts ==

15

16

* Single lane -> Single runtime per types

17

* Double lane -> Two or more runtime per type to handle failover setups

== 3. Architecture considerations ==

23

24

=== 3.1 Architecture components API Gateway ===

25

26

The following picture displays a general architecture of the API Gateway. This picture has been taken from the eMagiz Design Architecture section as that illustrates the below key points.

27

28

[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-apigw-architecture-1.png]]

Key notes

1. Gateway runtime

The Gateway has a separate runtime where the associated gateway flows are deployed in. The exit gates and all entry flow are the typical flow types present in this runtime, next to the usual infrastructure flow

33

2. Location runtime

34

The Gateway runtime is located in a Cloud machine, and is specifically put on the Connector machine. The Connector machine has the ability to allow incoming data (secured) traffic from outside the Virtual Private Cloud that each client has. The Core machine does not have this option due to security reasons. The eMagiz Cloud handles the proper and secure routing to the API gateway.

35

3. Gateway only runtime

36

These are system that act as application user of 1 or more operations made available in the API Gateway. In case the system is only connected in the Design phase as such an application user, than that system only acts as input for User Management. The system doesn't need to be deployed as a runtime on the Connector machine, and should therefore be placed on an excluded machine. In the picture above, Exact online is such a system.

37

38

=== 3.2 Single lane Cloud setup ===

39

40

Single lane setup in eMagiz means that all runtimes are provided once in the architecture diagram * there is no failover or clustered approach for the runtimes. For the API Gateway, this means that you have the following machines available. In this example, you have the messaging patterns components as well with the objective to see such cases as well.

41

42

* Core 01 --> holds the JMS Server and the messaging process container

43

* Connnector 01 --> holds the API Gateway container and the messaging runtimes

44

45

[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-apigw-architecture-2.png]]

46

47

=== 3.3 Double lane Cloud setup ===

48

49

Double lane setup in eMagiz means that all runtimes are provided at least twice in the architecture diagram * there is a failover for the JMS runtimes and gateway containers. For the API Gateway, this means that you have the following machines available. In this case you need to make sure that the flows are duplicated properly across the containers in Deploy * Containers. By default eMagiz will spread all flows over both gateway containers.

50

51

* Core 01 --> holds the JMS Server and the 1st messaging process container

52

* Core 02 --> holds the backup JMS Server and the 2nd messaging process container

53

* Connnector 01 --> holds the 1st API Gateway container

54

* Connnector 02 --> holds the 2nd API Gateway container

55

56

The choice to create a double lane API gateway is to be done where there is a requirement for very high performance around response times and throughput. Please contact eMagiz to discuss such options.

57

58

[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-apigw-architecture-3.png]]

59

60

=== 3.4 Hybrid Cloud setup ===

61

62

In the [microlearning](advanced-api-management-running-part-of-your-api-gateway-solution-on-premise.md) you can find the reasons and configuration for running the exit gates in on-premises runtimes. A view of such a architecture is displayed here:

63

64

[[image:Main.Images.Microlearning.WebHome@advanced-solution-architecture-apigw-architecture-4.png]]

=== 3.5 Memory ===

For now the memory requirements for API Gateway are the same as for Messaging flows. Please refer to the [microlearning](expert-solution-architecture-determining-needed-memory.md).

== 4. Assignment ==

There is no specific assignment for now. The correct use of the Design architecture is explained in this [microlearning](crashcourse-platform-design-understanding-design-architecture-basic.md).

76

77

== 5. Key takeaways ==

78

79

1. API Gateways can be part of a mixed landscape of Messaging, Event Streaming and API Gateways

80

2. A single lane setup is usually sufficient for most cases

81

3. Hybrid setups are possbible but please be sure the ask the right questions before implementing such

82

83