Enduro/X Core

Hi Subramanya,

Thanks for inquiry.

Could you share any case studies or real-world examples of successful migrations from Oracle Tuxedo to Enduro/X? I’m particularly interested in learning:

There are customers which has migrated from the Oracle Tuxedo to Enduro/X, some of them are listed down here (just scroll down for the users): https://mavimax.com/
Exact details for projects, I cannot disclose here. But yes, there are customers which has migrated, and having years of operations without issues.

What key considerations and challenges were encountered during the migration?

Some customers have done migration fully on them own, some acquired migration time support from us, where additionally some missing functionality were identified and Mavimax did implement that on SoW bases.
For the migration processes you can inspect https://www.endurox.org/dokuwiki/doku.php?id=endurox:v8.0.x:guides:migration_tuxedo the guide was built based on experience what got during these customer migrations.

There is also demo video how the migration process looks like: https://www.youtube.com/watch?v=6gVHbFCZMss

What steps or tools were used to facilitate the transition?

Please study the migration guide.

Basically you rebuild your code base against Enduro/X headers and libraries. For runtime there is tool ubb2ex which converts UBB config to Enduro/X format as close as possible.
There might be differences for JOLT/SALT/WSH accesses. We have endurox-connect package which offers way to expose XATMI services as standard rest services.
Additionally we have bindings to Go language (endurox-go), which gives powerful way for interacting with other systems, web services, etc. Thus invoke or consume web service can be with few lines of code.

What does the pricing model for Enduro/X look like—especially in comparison to Oracle Tuxedo?

For pricing please see this page: https://mavimax.com/products/prices-and-licensing
Basically you can run Open Source version if you comply with AGPLv3, or you can choose paid binary license, where AGPLv3 restrictions are removed.
For the binary license, key difference in pricing between us and Oracle is that we do not count CPUs, but Operating System instances running Enduro/X based applications (thus unlimited cpu for that OS), also the OS instance price is much lower than Tuxedo counter part.

Additionally, I noticed that there hasn’t been much activity in the Enduro/X forums close to an year now.

Customer support is provided within non-public projects. Thus here in public forum activity is low, it is used mainly for general questions.

Hi Madars,

Thanks for your quick response.

Our application is primarily developed in C/C++, so Enduro/X Core appears to be the most suitable option for our middleware needs.

Our SAAS product is deployed across multiple production environments, along with several development and test instances.

Could you please clarify if there is differential pricing between development/test and production deployments?

Understanding this would help us better plan our licensing and infrastructure strategy.

Thank You!

Hi,

Answered in PM.