Summary

In this chapter, we used the Oracle Database both from local and global transactions. You also experienced that mixing services using both local and global transactions does not work as you might imagine at first. Global transactions worked without any effort in application code and you might wonder why you would ever need to use local transactions. That feeling is shared by many users of Tuxedo. The most common reason for not using global transactions is squeezing out the last bits of performance. The performance overhead of transactions is small but they are not free. But even in those cases, it pays to have two implementations of the service as we did with the COUNT and COUNTXA services, one for each transaction type. After all, the code is the same and the only difference is in the server initialization.

Now you know how to develop servers for global and local transactions and how to configure the Tuxedo application in each case. You also know how to access the database...