However, this is not mandatory
as is shown in the clustering sample we provide later in the chapter. The
exact topology and deployment schema for a ServiceMix cluster has to be
decided based on what level of QOS features we are targeting from each of the
deployed components.
There are multiple benefits which we can leverage from a ServiceMix clustering
topology, a few of them are listed as follows:
Scalability: A software system is said to be scalable if its performance does
not degrade significantly as the load on the system increases. The scalability
of a ServiceMix cluster can be increased dynamically to meet the demand.
You can add the ServiceMix instances to a cluster without interruption of the
deployed service??”the applications and services already deployed continue
to run without impact to the existing consumers.
High availability: Availability is defined as the fraction of time the software
system is up and available to its consumers.
For example, a system with 99.99% availability over a period of 1 year
would be unavailable for:
(1 - 0.9999) X 1 Year X 365 Days X 24 Hours per Day X 60 Minutes per Hour
= 52.
Pages:
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491