Fuxedo logoFuxedo

What works, what is next, how to follow

Status

Fuxedo is under active development and usable today for development and testing; the compatibility suite runs unmodified against Oracle Tuxedo 12.2.2 and 22.1 on every commit, which is the project's definition of "matches".

Done and verified

The ATMI client and server API (tpinit, tpcall, tpacall, tpgetrply, tpforward, tpreturn, tpadvertise/x with TPSINGLETON and TPSECONDARYRQ), FML32 with Oracle-compatible field ids and boolean expressions, VIEW32, XML buffers with tpxmltofml32 and BUFTYPECONV, STRING and CARRAY, tpimport/tpexport. Administration: tmloadcf, tmunloadcf, tmboot, tmshutdown, tmadmin, qmadmin, ud32, tmipcrm, crdl/crlog, the MIB classes, and runtime updates (adv, unadv, suspend, resume, changetrace). Operations: MSSQ sets with secondary queues, REPLYQ, automatic restart with MAXGEN/RESTART/GRACE. Transactions: multi-group 2PC with per-group TMS servers, a folder-based TLOG, and heuristic detection. /Q queues as folders and files with TMQUEUE and TMQFORWARD. Networking: GWTDOMAIN gateways with dmadmin, TLS links with trust-on-first-use pins, and workstation clients via WSL and WSNADDR. Python throughout via tuxedo-python, whose demo runs against all three homes.

Known gaps

Honest list, no asterisks: data-dependent routing (*ROUTING section) is parsed but not enforced; EventBroker (tppost/tpsubscribe) is a stub; conversational tpconnect/tpsend/tprecv is untested end to end; cross-domain transactions (DMTLOG) are designed but not implemented; tmadmin's diagnostic surface (bbparms, dump, shmstats) is thin; FML32 indexes are not stored (a flat layout by design, at a small lookup cost). Multi-machine MP clustering is deliberately out of scope.

Roadmap

In rough order: cross-domain transactions with the DMTLOG device, data-dependent routing, EventBroker, and a compile-time compatibility switch for the 12.1/22.1 behavior divergences. The gap list and the API coverage matrix live in the repository, updated as items land.

Follow the project

Watch the repository for releases (GitHub emails on new ones if you watch with "all activity"), subscribe to the releases RSS feed, read the commit stream, or write to hello@fuxedo.io for the occasional project letter. Versioned releases and their notes will live on the GitHub releases page; the first tag is planned once the DMTLOG work lands.