looked around, actually love the idea of basing this on CDI instead of bloated Spring Boot.
How are transactions handled? Often I need to "do all of these things, or do none of these things" and often that includes sending emails or JMS Messages
Helidon has its own transaction manager, but the real issue here is that EclipseStore does not support transaction management out the box. Java objects are modified in memory, but stored with an explicit store() call. So in your transaction rollback you just need to reload the original data from the storage using the EclipseStore Reloader, and overwrite the dirty copy in memory. You have to track yourself which Java objects may have been changed.
I am looking into supporting LocalTransactions natively and its actually quite easy, so that might drop soon.
Also working on a full database based on eclipsestore called ZeroZ DB (zeroz4j-db). I might switch the web app development framework to use that, and that will give multi JVM capabilities and also txns out the box.
How are transactions handled? Often I need to "do all of these things, or do none of these things" and often that includes sending emails or JMS Messages