We recently migrated some code to quarkus. My experience:
The good:
* The quality is there. If they claim it is supported, it works. It gives reasonable error messages, etc..
* The documentation is very good, which makes the onboarding experience nice. Give a java dev the site, and they are up and running on their own in minimal time.
* The support on their zulip chat is also very good. People are both friendly and have deep knowledge. Most questions are answered in an hour.
* The development speed is fast. If you file a bug report, it might appear in the next version a week later
The bad:
* If you have (enterprise) stuff that's not yet supported, you'll suffer. The oracle jdbc database driver cost us graalvm. soap took a lot of time to get working.
* cloud integration is a bit too magic for its own good. Quarkus tries to hide complexity by generating config files, executing openshift and docker commands, etc.. But if anything goes wrong, it is hard to find out what it tried to do and how it failed. The options in application.properties are only half-documented and it is hard to map them to the corresponding options of the underlying tools. Error messages are out of context. I ended up debugging maven and reading the source code.
All in all, I am convinced it is a good tool. It has both an open source feel and enterprise class support, combining best of both world.
The good:
* The quality is there. If they claim it is supported, it works. It gives reasonable error messages, etc..
* The documentation is very good, which makes the onboarding experience nice. Give a java dev the site, and they are up and running on their own in minimal time.
* The support on their zulip chat is also very good. People are both friendly and have deep knowledge. Most questions are answered in an hour.
* The development speed is fast. If you file a bug report, it might appear in the next version a week later
The bad:
* If you have (enterprise) stuff that's not yet supported, you'll suffer. The oracle jdbc database driver cost us graalvm. soap took a lot of time to get working.
* cloud integration is a bit too magic for its own good. Quarkus tries to hide complexity by generating config files, executing openshift and docker commands, etc.. But if anything goes wrong, it is hard to find out what it tried to do and how it failed. The options in application.properties are only half-documented and it is hard to map them to the corresponding options of the underlying tools. Error messages are out of context. I ended up debugging maven and reading the source code.
All in all, I am convinced it is a good tool. It has both an open source feel and enterprise class support, combining best of both world.