Tuesday, May 09, 2006

Clustering at the JVM Level to Maintain Business Logic Integrity

Clustering at the JVM Level to Maintain Business Logic Integrity

The typical three-tier architecture keeps the code Java developers need for clustering inside the business logic, making clustering a real chore.
Clustering at the JVM level makes Java applications easier to write and cheaper to run.
by Ari ZilkaApril 14, 2006

The way a typical three-tier architecture separates the concerns of data-management logic, business logic, and presentation logic makes clustering, the practice of deploying a single application on multiple machines, a laborious and expensive task for Java developers. (See Sidebar 1. The Typical Three-Tier Architecture.) With the separation structured the way it currently is, business logic currently includes the code required for clustering. Without a clustering plug-in at runtime, developers are left to cluster their own business logic, the frameworks they use, and in some cases, the container in which it all runs.

Clustering at the JVM Level to Maintain Business Logic Integrity


technorati tags:

No comments: