New Release: Oracle Transaction Manager for Microservices (MicroTx) 24.2.1
Blog post briefly describing some of the new features in Oracle Transction Manager for Microservices (MicroTx) 24.2.1. It’s also the final post in my series on Where is the Complexity by introducing a new feature in Oracle Database Sagas to support externally managed Sagas that along with Lock-free Reservations can support automatic compensation of Sagas.
Where is the Complexity? Part 4
Almost concluding the series, I cover where the actual complexity for a developer lies and suggest that all choices regarding software architecture are a trade-off and no one size fits all.
Where is the Complexity? Part 3
XA is often portrayed as complex. This post shows how easy it is to use XA and that the complexity is in the transaction management, which is handled for the developer by MicroTx. Check out the minor code modifications necessary to use XA transactions in your microservices.
Where is the Complexity? Part 2
Sagas are all the rage, but implementing them can be complex. They push some of the issues around data consistency onto the developer who needs to provide compensating logic to back out a transaction and deal with dirty reads as Sagas don’t provide isolation. This post exposes that complexity and provides sample code illustrating what a developer needs to do to use Sagas.
Where is the Complexity?
This is the first post in a series on where is the complexity in using distributed transactions as a way to solve the dual write problem. It descibes some of the types of failures that must be addressed by whatever mechanism is being used to ensure data consistency among your microservices.
MicroTx Enterprise Edition Features
This post covers in some detail the features that the Enterprise Edition of MicroTx provides above and beyond what MicroTx Free provides.
MicroTx Enterprise Edition is Now Available
A post announcing the availability of the Enterprise Edition of MicroTx and briefly describing the enterprise features of this release such as resilency, high availability, and scalability.
Sagas Are Great. What’s the Problem?
The commonly accepted solution to solving the dual write problem is to use Sagas. Sagas are an eventual consistency model where data in one microservice may be inconsistent with data in another microservice for a perioid of time.
Integrating Helidon and WebLogic Microservices with Oracle MicroTx
This post shows how to include Helidon based microservices and WebLogic based microservices in the same distributed transaction using XA.
New Release of MicroTx 22.3.2
Post covering the new features in MicroTx 22.3.2 including XA optimizations, Python support for Try-Confirm/Cancel, and more.
Making Try-Confirm/Cancel Easy with MicroTx
This post describes how microservices can adopt the Try-Confirm/Cancel transaction protocol to ensure data consistency across their microservices.
Announcing Oracle Transaction Manager for Microservices 22.3.1
Oracle announces a new release of MicroTx including new features such as clustering support for the MicroTx coordinator.
Making Eclipse MicroProfile Long Running Actions Easy with MicroTx
MicroTx supports the Eclipse MicroProfile Long Running Actions as a form of Sagas. See what it takes to use Long Running Actions in a Java microservice and some cautions about eventual consistency transaction models.
Making XA Easy for Microservices
Using XA couldn’t be easier with MicroTx. See how you can quickly adopt XA transactions in your microservice based applications.
Ensuring Data Consistency in Microservice Based Applications
As application developers adopts microservices, the issue of ensuring that data is consistent among the participating microservices becomes apparent. This blog post describes several techniques that can be leveraged to ensure this data consitency.
Announcing Oracle Transaction Manager for Microservices Free
Oracle releases a new product to help ensure data consistency across microservices by supporting a spectrum of distributed transaction patterns in Java and TypeScript.
Todd Little
Chief Architect, Transaction Processing Products
I’m currently the Chief Architect for a family of transaction processing products at Oracle including Oracle Tuxedo product family, Oracle Blockchain Platform, and the new Oracle Transaction Manager for Microservices (MicroTx). My main areas of focus are on security, privacy, confidentiality, performance, and scalability. My job is to provide the technical strategy for these products to ensure they meet customer requirements.
Prior to being acquired by Oracle, I was Chief Architect for BEA Tuxedo at BEA Systems, Inc. While at BEA Systems, I was responsible for defining the technical strategy and direction for the Tuxedo product family. I developed the Tuxedo Control for WebLogic Workshop that greatly simplified the usage of Tuxedo services from Workshop based applications. I also received two patents for methods allowing design patterns in a UML modeling tool to control the generation of software artifacts.
During my nearly 50 years of software architecture and development experience, I have worked on a wide range of software systems and technology and have 44 published patents. At Science Applications International I worked on microcoded plasma display systems and command, control, and communication systems for naval applications. As a senior software consultant at Digital Equipment Corporation, I was the New York Area Regional Tools Consultant and also helped develop a multi-language multi-threaded distributed object oriented runtime environment with concurrent garbage collection.