The CHA facilitates scalability and availability by providing the necessary capability to share among containers and provide persistency support to data put into the CHA Server. The value of CHA is that CHA can greatly simplify the application architecture and reduce the need for extensive program changes when new screens or new logic or new channels are added or changed. Besides, CHA also simplifies the extra coding overhead required for communication among the many shared components. For example, if more business services need to communicate with existing services, no extra API is required to be added for existing services to obtain data from new one, and new services do no need to understand and use new APIs provided by the existing services. The new and existing services can refer to the enterprise-wide well-defined CHA hierarchy, even if they are across containers.
Leveraged on CHA, the complicated communication and architecture between multi business services and multi containers will be greatly simplified as shown in the figure below:
Note Shared CHA does not mean Remote CHA only. Although "share" is basic advantage for Remote CHA, the Local Context can still be shared if you define context as business service interface parameter.
