The middleware with four decades on the clock
Oracle Tuxedo is middleware for building and running distributed,
transactional business applications. A client calls a named
service with a typed buffer; the system routes the
request over an operating-system message queue to a server process that
advertises that service; the server replies; and the whole exchange can
run inside a distributed transaction that coordinates databases and
queues together. Administrators boot the system from a text
configuration (UBBCONFIG), monitor it through a bulletin
board in shared memory, and manage queues, transactions, and services
from command-line tools.
It is old, and it is everywhere. If you have used a bank, paid by card, or topped up a phone in the last thirty years, the odds are good that a Tuxedo domain sat in the request path.
Tuxedo started in 1983 at AT&T, growing out of the DUX (Database for Unix) and TUX (Transactions for Unix) projects; the name is a backronym for Transactions for Unix, Extended for Distributed Operations. It passed through Unix System Laboratories and Novell, became the foundation of BEA Systems through the 1990s and 2000s under the name BEA Tuxedo, and arrived at Oracle with the BEA acquisition in 2008, where it lives on as Oracle Tuxedo, current releases 12.2.2 and 22.1. If a job posting, a resume, or a support contract says BEA Tuxedo, it is the same product family; the administrator commands and the C API survived every owner. (The history above condenses chapter 1 of Modernizing Oracle Tuxedo Applications with Python, Packt 2021.)
Under the marketing word "middleware" sits a concrete mechanism, which is why Tuxedo systems age so well:
Tuxedo did service orientation before the term existed, and transactional microservices before the word was coined; the vocabulary changed around it, the machinery did not.
Banks, card processors, telecommunication providers, government systems, and the back office of enterprise software you already own: several Oracle applications ship Tuxedo under the hood. It is usually invisible until the day it becomes your problem: a license renewal, an audit, a retiree who was the last person to understand the domain.
Fuxedo is an open source implementation of the same API, the same administration commands, and the same System V IPC machics, verified against Oracle Tuxedo 12.2.2 and 22.1 in continuous integration. Applications recompile against it; administrators keep their runbooks. For the reasons teams migrate and how the move works, see the migration page; for a hands-on taste, the quickstart boots a domain in five minutes.
Is BEA Tuxedo the same as Oracle Tuxedo? Yes. BEA Systems owned and developed Tuxedo from the mid-1990s until Oracle acquired BEA in 2008; Oracle Tuxedo is the direct continuation, and modern releases still boot configurations written for the BEA-era releases.
What is Tuxedo used for? Transactional services in banks, card processing, and telecommunications: account balance lookups, payment authorization, rating and charging, and the integration glue between them, usually with decades of accumulated business logic that nobody dares rewrite.
Is Tuxedo still supported? Oracle sells support for 12.2 and 22.1 releases. Unsupported or license-constrained installations are exactly where open source alternatives such as Fuxedo, or modernization through the tuxedo-python bindings, enter the picture.
What is a Tuxedo application? A set of servers grouped in a domain, each advertising services, plus clients that call them, plus the configuration (UBBCONFIG), the bulletin board, and the queues that tie it together.
What are the Oracle Tuxedo alternatives? Honest ones: rewrite onto a modern framework (a development project in disguise), move to a different XATMI-flavored platform (porting effort varies), or recompile against Fuxedo, which targets API-, command-, and IPC-level compatibility so the application and the operations habits carry over. The migration page compares the shapes.