Multi-zone

In this chapter we consider configuration where multiple group nodes, configured accordingly to multi-node deployment plan. Let assume that these set of groups of nodes are supposed to communicate between each other in ordered way: WebApp1-2 -> Microservices A,B,C -> Microservices D,E,F and provide only specific services outside the business domain that they are support. This idea is shown on the following picture.

Figure 8. JLupin Platform in multi-zone configuration (idea).

JLupin Platform provides the abstract configuration parameter zone that helps a lot in such cases. Each of group of nodes constitute a zone by sharing the unique name of zone applied to JLupin Platform runtime configuration, in the above example we should establish three zones:

@node_1, node_2:

ZONE:
  name: zone_access    # <-- !CHANGE!
MAIN_SERVER:
  name: NODE_1
  location: DC1
SERVERS:
  JLRMC: #JLupin Remote Method Call Fast Protocol
    port: 9090
    [...]

@node_3, node_4:

ZONE:
  name: zone_business    # <-- !CHANGE!
MAIN_SERVER:
  name: NODE_1
  location: DC1
SERVERS:
  JLRMC: #JLupin Remote Method Call Fast Protocol
    port: 9090
    [...]

@node_5, node_6:

ZONE:
  name: zone_datasource    # <-- !CHANGE!
MAIN_SERVER:
  name: NODE_1
  location: DC1
SERVERS:
  JLRMC: #JLupin Remote Method Call Fast Protocol
    port: 9090
    [...]

and configure appropriate communication between them (commands using JLupin CLI Console):

@node_1:

> node peer add node_2 10.0.0.2
> node peer add node_3 10.0.0.3
> node peer add node_4 10.0.0.4

@node_2:

> node peer add node_1 10.0.0.1
> node peer add node_3 10.0.0.3
> node peer add node_4 10.0.0.4

@node_3:

> node peer add node_4 10.0.0.4
> node peer add node_5 10.0.0.5
> node peer add node_6 10.0.0.6

@node_4:

> node peer add node_3 10.0.0.3
> node peer add node_5 10.0.0.5
> node peer add node_6 10.0.0.6

@node_5:

> node peer add node_6 10.0.0.6

@node_6:

> node peer add node_5 10.0.0.5

NOTE that JLupin Edge Balancer is not involved in communication between zone_access and zone_business as well as between zone_business and zone_datasource, it provides services from each zone individually, for example for integration purposes.

In that we have three zone system configuration, where each zone can be developed, deployed, scale and managed individually, but they act as a single, consistent and designed in the secured way point of providing services, as shown in the following picture.

Figure 9. JLupin Platform in multi-zone configuration (implementation).