Feedback template

Axon Framework 5 M1 Survey

We, the Axon Framework team, are very happy to announce the first milestone of Axon Framework 5. While not a complete release, we are excited to share the progress we’ve made so far.

The biggest motivator for a Milestone release is to gather feedback from the community.
So we encourage you to try it out and share your thoughts with us.

Scope

It’s important to note that this is not a complete release. Only a part of the complete feature set is implemented. For an overview of the features included, and the features that are still to be implemented, please refer to the following post: Axon Framework 5 Roadmap

Try it out

We encourage you to try out the milestone release and share your feedback with us.
You can follow the instructions in the Getting Started with Axon Framework 5 guide to get
familiar with the new features and changes. After that, please share your feedback with us with the template down below.

Reward

We appreciate the time you take to try out Axon Framework 5 M1 and share your feedback with us. We feel we should reward you for that. As such, anyone who fills in the survey will get an honorable mention in the Axon Framework 5 README file once released, by your GitHub username and/or name.

Feedback template

Please copy the following template to a new discuss post and fill it in as much as you like. The more details, the better.

  1. How much experience do you have with Axon Framework 4 and earlier?

    • None
    • I experimented a bit
    • I wrote an application
    • My application went to production
    • I am the expert in my team
    • Allard comes to me for questions about the UnitOfWork
    • Feel free to elaborate if you’d like: _______________
  2. How would you rate your Event-Sourcing knowledge?

    • None
    • Basic
    • Intermediate
    • Advanced
    • Expert
    • Feel free to elaborate if you’d like: _______________
  3. How would you rate the overall experience of using Axon Framework 5 M1?

    • 1: Very poor
    • 2: Poor
    • 3: Average
    • 4: Good
    • 5: Excellent
    • Feel free to elaborate if you’d like: _______________
  4. What did you like most about Axon Framework 5 M1?

    • Asynchronous core
    • Simplified configuration
    • Dynamic consistency boundary
    • The new Given-When-Then test fixtures
    • (Lambda-based) Stateful command handlers
    • New module structure
    • Other: _______________
    • Feel free to elaborate if you’d like: _______________
  5. Do you think Axon Framework 5 improves the developer experience compared to Axon Framework 4?

    • Yes, definitely
    • Probably
    • Maybe
    • Not sure
    • Probably not
    • Definitely not
    • Feel free to elaborate if you’d like: _______________
  6. How long did it take you to get started with Axon Framework 5 M1?

    • Less than 1 hour
    • 1-2 hours
    • 2-4 hours
    • More than 4 hours
    • Feel free to elaborate if you’d like: _______________
  7. How intuitive did you find the new configuration system?

    • Very intuitive
    • Somewhat intuitive
    • Neutral
    • Somewhat unintuitive
    • Very unintuitive
    • Feel free to elaborate if you’d like: _______________
  8. Did you try out the new dynamic consistency boundary feature? If so, how would you rate it?

    • Yes, I loved it!
    • Yes, it was okay
    • Yes, but I didn’t find it useful
    • No, I didn’t try it out
    • Feel free to elaborate if you’d like: _______________
  9. Did you construct custom EventCriteria? If so, did you find it intuitive?

    • Yes, it was easy to construct what I needed
    • Yes, but it was a bit tricky
    • Yes, but I found it very difficult
    • No, it was very confusing
    • No, I didn’t try it out
    • Feel free to elaborate if you’d like: _______________
  10. Would you consider using Axon Framework 5 in a production project once it reaches a stable release?

    • Yes, definitely
    • Probably
    • Maybe
    • Not sure
    • Probably not
    • Feel free to elaborate if you’d like: _______________
  11. Do you have any suggestions to improve the new features in Axon Framework 5 M1?

    • Yes — please describe: ________________
    • No, everything is perfect!
      • Feel free to elaborate if you’d like: _______________
  12. Do you have any additional feedback or comments that weren’t included in the other questions?

    • Comment 1: _________________
    • Comment 2: _________________
    • Comment 3: _________________
  13. How would you like to be mentioned in the README file?

    • GitHub username: _______
    • Name: ______
    • Both _______ and ______
    • I prefer to remain anonymous

Thank you

We want to thank you for taking the time to try out Axon Framework 5 M1 and share your feedback with us. Your input is invaluable in helping us improve the framework and make it the best it can be. Be sure to keep an eye on our social media channels and the AxonIQ website for updates on future releases and milestones.

1 Like

Hi,

Thank you very much for providing us with a first milestone. I would happily try it out. It seems that currently the starting guide points to a non existing URL though.

Best regards

Nils

1 Like

Hey Nils-Christian!

The link was, as you might have expected, a place holder. I have just fixed it by setting the actual URL. Curious to hear your opinion on milestone 1! :pray:

Hi Steven,

Thank you. I am currently reading and working through the guide. So far very exciting.

Some quick side notes:

  • It seems that the link to the demo on Github (https://github.com/AxonIQ/university-demo) is either incorrect or not a public repository. You might want to check that.
  • At the moment I cannot access axon-configuration in Version 5.0.0-M1. Maybe this has still to be mirrored to Maven central and will be available in some hours?

Best regards

Nils

Happy to hear the changes come across as exciting, Nils!

Now, concerning your pointers:

  1. I missed making the sample public, my apologies for that. It should be available for everybody right now.
  2. The axon-configuration module was intentionally not released, as we will be phasing it out entirely. The university demo also doesn’t use that module, so this is a misser in the getting started. We’ll adjust that ASAP; thanks for pointing it out!

A bit more on the axon-configuration module: we are removing it, as such a package requires an accumulation of all Axon Framework modules. However, we want people to have a choice, instead of being forced to pull in everything.

As such, each module has its own ApplicationConfigurer instance, building on the ApplicationConfigurer it depends on. The axon-messaging module has, for example, the MessagingConfigurer that depends on the basic ComponentRegistry and LifecycleRegistry. The axon-modelling in turn has a ModellingConfigurer, which depends on the aforementioned MessagingConfigurer.

I hope that clarifies some of the changes in that area.
Looking forward to further feedback!