Application capacity defines how many users an IT application service can support in a given response time. Another critical factor is the application’s ability to scale, which is dependent upon the application’s architecture.
The FE platform is processing “looking” activity that is typically light on hardware resources. In this case, the FE only needs to be able to rapidly service search or view requests, which can be accomplished with lightweight, inexpensive commodity servers, each partitioned to handle a small subset of users.
If a server fails, users connected to that system are simply rerouted to a remaining FE server. Scaling is simply handled by adding more servers.
In contrast, the BE system needs to be robust, highly-available, highly-scalable, and optimized for database transaction processing (such as the world-class HPE NonStop server). The BE system needs to process thousands of database updates per second, and maintain database consistency.
Exchanging data between the various parts of the application requires a physical network connection and a logical connection. In the travel reservation system mentioned above, once the end user finishes the “looking” phase and books a reservation, the FE application must send the “booking” request to the BE, and return a response back to the user. HPE Shadowbase data and application integration software transforms the booking updates into a format that is then sent to the various FE Servers, and updates them with sub-second latency, automatically updating booked rooms from the reservation catalogue.
Shadowbase Business Continuity software (not pictured) can be used to enable continuous availability, should the backend BE environment fail. This adds in redundancy and ultimately the element of reliability. Scalability is possible since Shadowbase software supports parallelism to scale with an increasing workload.