INTRODUCTION

Extreme Transaction Processing - What & Why

Extreme Transaction Processing (XTP) is an exceptionally demanding form of transaction processing. Transactions of most high-end (more than 10,000 concurrent accesses or 500 transactions per second) or ultra-high-end (more than 100,000 concurrent accesses or 5,000 transactions per second) requirements or more would require this form of processing.

Gartner defines XTP as an application style aimed at supporting the design, development, deployment, management and maintenance of distributed TP applications characterized by exceptionally demanding performance, scalability, availability, security, manageability and dependability requirements.

Very much like traditional TP systems, XTP applications are aimed at enabling efficient, reliable concurrent and real-time access (read/update) to a shared database by executing application programs commonly referred to as "transactions."

The first and foremost adoption of XTP can be observed amongst the financial institutions (a one-millisecond advantage in trading applications can be worth $100 million a year to a major brokerage firm, by one estimate), whose prime requirements are more processing capability, but without requiring exponential increase in hardware costs, in areas such as fraud detection, risk computation, and stock trade resolution, to profit from minute, fleeting price anomalies and to mask their intentions via "time-slicing," or carving huge orders into smaller batches so as not to move the market.

What is Federated ESB (Enterprise Service Bus)?

Federated ESB (FESB) provides the ability to use multiple service registries and administration domains while mapping the disparate registries into a federated set of services. The federated ESB facilitates service interactions with multiple ESB implementations. One master ESB to which several dependent ESBs are federated to provide a subset of services that are applicable throughout the enterprise.

Fig 1. Federated Enterprise Service Bus