Home/ Questions/Q 7171829
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T15:29:32+00:00

I have a requirement to produce a prototype (running in a J2EE compatible application

  • 0

I have a requirement to produce a prototype (running in a J2EE compatible application server with MySQL) demonstrating the following

  • Demonstrate ability to distribute a transaction over multiple database located at different sites globally (Application managed data replication)

  • Demonstrate ability to write a transaction to a database from a choice of a number of database clusters located at multiple locations. The selection of which database to write to is based on user location. (Database managed data replication)

I have the option to choose either a Spring stack or a Java EE stack (EJB etc). It would be useful to know of your opinions as to which stack is better at supporting distributed transactions on multiple database clusters.

If possible, could you also please point me to any resources you think would be useful to learn of how to implement the above using either of the two stacks. I think seeing examples of both would help in understanding how they work and probably be in a better position to decide which stack to use.

I have seen a lot of sites by searching on Google but most seem to be outdated (i.e. pre EJB 3 and pre Spring 3)

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I would use the JavaEE stack the following way:

    • configure a XA DataSource for each database server
    • according to user’s location, a Stateless EJB looks up the corresponding DataSource and get the connection from it
    • when broadcasting a transaction into all servers, a Stateless EJB has to iterate on all configured DataSources to execute one or more queries on them, but in a single transaction

    In case of a technical failure, the transaction is rolled back on all concerned servers. In case of a business failure, the code can trigger a rollback thanks to context.setRollbackOnly().

    That way, you benefit from JavaEE automatic distributed transaction demarcation first, and then you can use more complex patterns if you need to manage transaction manually.

    BUT the more servers you have enlisted in your transaction, the longest the two-phase commit operation will last, moreover if you have high latency between systems. And I doubt MySQL is the best relational database implementation to do such complex distributed transactions.

    • 0