Leaving Tuxedo without leaving your application
The application is fine. The middleware bill is the problem. Oracle Tuxedo is priced per processor and the numbers grow with the machines, not with the value; audits arrive; the platform you built on becomes a recurring negotiation. None of that makes the ATMI programming model wrong, which is why "rewrite everything" is such an expensive answer.
Fuxedo matches Oracle Tuxedo at three levels, and the levels are the whole trick:
API level. The same C calls with the same semantics: tpinit, tpcall, tpacall, tpgetrply, tpenqueue, tpadvertise, tpbegin, FML32 including boolean expressions. Application source compiles against Fuxedo headers as-is, and the compatibility suite runs the same tests against Oracle Tuxedo 12.2.2 and 22.1 to keep the claim verified.
Command level. tmloadcf, tmunloadcf, tmboot, tmshutdown, tmadmin, qmadmin, ud32 keep their flags and shapes, so operations runbooks, monitoring scripts, and the on-call muscle memory carry over.
System V IPC level. Servers block in msgrcv on the same message queues, the bulletin board lives in shared memory, MSSQ sets share one queue. Kernel tuning and ipcs instincts still apply, and tools like eBPF queue monitoring work on both.
A typical migration: install Fuxedo side by side, build the application against it, boot the domain from the same UBBCONFIG, run the test suite, cut over. SQL resources and Oracle XA stay on Oracle; the middleware does not have to.
There are two honest ways to leave licensed middleware. One is a framework-style rewrite: a modern runtime with a familiar-flavored API and its own configuration semantics, where the application is ported piece by piece onto a new model. That path is really a development project, and it is the right answer when you want to rebuild anyway.
The other way is the brownfield exit ramp, and it is what Fuxedo is: same UBBCONFIG, same commands, same System V mechanics, recompile and go. The estate keeps its ATMI semantics, its operations runbooks, its kernel tuning, and its debugging instincts; the thing it sheds is the license negotiation. Where internals can differ without a program being able to tell, they may; where anything observable differs, that is a bug, and the compatibility suite against Oracle Tuxedo 12.2.2 and 22.1 is there to catch it.
Talk to us about an assessment for your domain: point us at your UBBCONFIG and the service inventory, get back a concrete migration plan and effort estimate.