Quarkus support

[languitar]

I am currently evaluating frameworks for realizing the transactional outbox pattern in a quarkus context. Thus the question, whether quarkus support is generally planned or possible here?

[cer]

A couple of points.

First, when we added support for Micronaut we refactored Eventuate into

• Core functionality
• Framework (Spring/Micronaut) specific modules - e.g. component assembly

This should make it straightforward to support other frameworks, such as Quarkus.

Second, we've seen increased interest in Quarkus and we plan to start work on it very shortly.

[languitar]

Thanks for the quick feedback!

I've seen the separation but getting a grasp on how to implement this on my own is not too easy with all the different modules being involved. Is there any documentation on how to implement framework-specific modules?

[ra002890]

I have started to work with Quarkus too. My team is being prepared/planning to start help on Eventuate Quarkus version development. So, @cer can you give us some instructions to start it, or can us follow the Micronaut implementation as a pattern and then send it to you though merge requests?

[cer]

@ra002890 @languitar I'm excited to hear that you are interested in contributing to the Quarkus implementation. We don't have any specific documentation on what to do unfortunately.

The simplest advice to create quarkus modules for that correspond to the micronaut modules, starting in eventuate-common. e.g. eventuate-common-quarkus-jdbc, which would 'emulate' eventuate-common-micronaut.

There are modules in various modules that need to be 'quarkified':

• eventuate-common
• eventuate-common-messaging
• eventuate-messaging-X
• eventuate-tram-core

You can see the list here.

One more thing. The plan to have separate repositories, such as eventuate-common-quarkus, to avoid overloading the existing repositories.

And, yes, finally collaboration would be via pull-requests. You would need to sign a CLA