Proposal to Deprecate and Remove the Vertx Module

10 views
Skip to first unread message

Manuel Finelli

unread,
Sep 25, 2025, 12:45:02 PMSep 25
to narayana-users

Hi community,

I am writing to propose the deprecation and subsequent removal of the Vertx module from the Narayana codebase.

During the recent release of Narayana 7.3.0.Final, I noticed that we have never officially released or advertised the Vertx module, and its presence in our code base doesn't seem to serve a clear purpose for the community.

An alternative is to move it to our quickstart repository, where it could be of more use as a standalone example. However, given that the module has not been actively developed or used, I believe it's best to deprecate it and eventually remove it completely. This will help simplify the Narayana project, reduce maintenance overhead, and ensure our codebase only contains modules that are actively supported and valuable to our users.

Please let me know your thoughts on this proposal.

Best regards,
Manuel

Michael Musgrove

unread,
Sep 26, 2025, 5:10:58 AMSep 26
to Manuel Finelli, narayana-users
I think the best location is in the quickstart repo because the Narayana Vert.x maven module is a set of examples, not an API, that show how to integrate the Narayana Software Transactional Memory implementation, STM, (some docs links include https://www.narayana.io//docs/project/index.html#_stm and https://jbossts.blogspot.com/search?q=stm) into a Vert.x 3 environment, ie the module cannot be integrated directly into Vert.x applications, rather it serves as an example of how a developer would do that integration.

But integrating STM into a Vert.X application is definitely something that can provide significant performance benefits to applications that make use of software based transactional memory.

--
You received this message because you are subscribed to the Google Groups "narayana-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to narayana-user...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/narayana-users/ae8f94e0-a3fa-4a25-849c-3ee65a75fa71n%40googlegroups.com.

Michael Musgrove

unread,
Sep 26, 2025, 5:13:23 AMSep 26
to Manuel Finelli, narayana-users
Note also that quarkus makes heavy use of Vert.X and that STM is available as a quarkus extension (https://quarkus.io/extensions/io.quarkus/quarkus-narayana-stm/).

Tom Jenkinson

unread,
Oct 28, 2025, 10:36:51 AM (3 days ago) Oct 28
to narayana-users
Thank you for mentioning that. I feel that given the dependency on Narayana STM in quarkus (e.g. https://github.com/quarkusio/quarkus/blob/e69c13b2b7e5682e16f4969cc4e0a5cfa7fadd01/bom/application/pom.xml#L4935-L4938) we shouldn't remove it from the main Narayana repo as it demonstrates a purpose for the community and would be expected to be kept maintained and having the code in the quickstarts instead might not be expected?
Reply all
Reply to author
Forward
0 new messages