Closed simisoz closed 2 years ago
If you'd like to contribute the code, we'd love to see how it might look and work. 😊
On Oct 19, 2017, at 13:46, simisoz notifications@github.com wrote:
Motivation for or Use Case
Regarding JHipster microservice approach can we consider to align JHipster with to CQRS and Event sourcing using Axon Framework as an alternative approach for microservices.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
This is a huge feature request with few details on what you want to do. You are free to create a module/fork the generator to demonstrate your idea (code speaks better than words 😄). We are welcoming collaboration with companies to support their frameworks/platforms. Sadly we currently have too much on our hands to tackle yet another integration work.
I'd like to see how this might work, so I'm putting a bug bounty on this.
this is huge work. I use Axon framework, even if you can generate some boilerplate start code, you will be stuck with generating a CRUD version and you would probably end up to refactor all the CRUD because it is usually not the approach for CQRS/ES, furthermore when you have a process or saga that will modify multiple aggregates, crud cmd/event might not fit and often you want to be explicit about the cmd/evt which CRUD is not.
This issue is stale because it has been open 30 days with no activity. Our core developers tend to be more verbose on denying. If there is no negative comment, possibly this feature will be accepted. We are accepting PRs :smiley:. Comment or this will be closed in 7 days
this is huge work.
Closing. Please reopen if you're interested in working on this feature. It might need to be an alternative to the current CRUD feature.
Motivation for or Use Case
Regarding JHipster microservice approach can we consider to align JHipster with to CQRS and Event sourcing using Axon Framework as an alternative approach for microservices.