Standalone, Clusters / Failover clusters and Load balancer in AX 2012

 

Topology AX Client configuration Server configuration (SC) Cluster configuration (CLUSTERC)
Standalone AOS Environment

One client, one AOS

AXCLIENTC1:

AOS1

AXCLIENTC2:

AOS2

AXCLIENTC3:

AOS3

SC1:

AOS1

AOS2

AOS3

 

Side by side configuration.

Multiple AOS’s (not clustered)

One client, several AOS

AXCLIENTC1:

AOS1

AOS2

AOS3

SC1:

AOS1

AOS2

AOS3

Important AOS’s order in the AX Client configuration. If AOS1 is down, client will be connected to AOS2, if AOS2 is down then client will be connected to AOS3. It means, that first available AOS will be used to fulfill the connection request by a client.

Clusters without a dedicated load balancer.

One client, several AOS combined into cluster

AXCLIENTC1:

AOS1

AOS2

AOS3

SC1:

AOS1

AOS2

AOS3

CLUSTERC1:

AOS1

AOS2

AOS3

Once a client starts, it receives the list of active AOS instances in the cluster, sorted by workload.

If AOS1 is down, client will be connected to AOS2, if AOS2 is down then client will be connected to AOS3.

Clusters with a dedicated load balancer.

One client with AOS which is load balancer

AXCLIENTC1:

AOS1

                      

 

SC1:

AOS1

AOS2

AOS3

CLUSTERC1:

AOS1 – load balancer

AOS2

AOS3

The load balancing AOS instance is dedicated to distributing the user load. Once a client starts, it connects to the load balancing AOS instance. Then, the load balancing AOS returns a list of active AOS instances that exist in the cluster sorted by the workload.

If AOS2 is loaded enough, then client will be connected to AOS3. But in case if AOS1 is down, there will not be ability to connect to another AOS. To solve this case, use the next topology.

Failover cluster with a dedicated load balancer.

One client several AOS combined into cluster and one AOS is load balancer

AXCLIENTC1:

AOS1

AOS2

AOS3                      

SC1:

AOS1

AOS2

AOS3

CLUSTERC1:

AOS1 – load balancer

AOS2

AOS3

The load balancing AOS instance is dedicated to distributing the user load. Once a client starts, it connects to the load balancing AOS instance. Then, the load balancing AOS returns a list of active AOS instances that exist in the cluster sorted by the workload.

If AOS1 is loaded enough and/or down, client will be connected to AOS2, if AOS2 is loaded enough and/or down then client will be connected to AOS3.

The only one difference from third topology is; such configuration (with Load balancer) is used in highly loaded system. Such dedicated load balancer will be in charge of responding to requests about active AOS instances with less workload. Otherwise, without load balancer, some AOS can slightly slow down while it determines available AOS with less workload.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s