I'm maintaining a sizable enterprise Jakarta EE application that's currently running on Payara, heavily dependent on JSF and PrimeFaces. We're looking to modernize and shift towards a cloud-native architecture, and I'm considering using Quarkus. However, I'm concerned about how well PrimeFaces is supported. Has anyone here moved a large JSF application to Quarkus? Are there significant limitations with PrimeFaces compared to using a full server like Payara or WildFly? Or should we stick to Payara/Jakarta EE 10 for the sake of stability? I'd appreciate any insights!
4 Answers
Honestly, if you're not leaning towards serverless architecture, I wouldn't recommend the switch. Payara shines in terms of reliability and support for Jakarta EE. Enjoy what you have, it's a solid platform!
Before you dive into migration, it's worth asking why you want to switch in the first place. If you're currently using Payara, which is a pretty modern app server, maybe it's not necessary unless you have specific performance or scaling needs. Stay put unless you’ve got a killer reason!
Migrating from WildFly to Quarkus with a JSF front-end is definitely doable! I did it myself and found it wasn’t too complicated, especially when starting off with proof of concepts. It took under a week to get most of the app running in Quarkus after thorough testing. Just be mindful of the project structure and the potential issues with EJBs and MDBs, particularly if you're dealing with two-phase commits.
If you're looking at Quarkus, check out 'qurakus faces.' It's essentially a way to run JSF and PrimeFaces on Quarkus, and it might be worth your time. You can find it on GitHub—give it a look!
Wow, sounds like you navigated quite the journey! What were the biggest challenges you faced during the WildFly to Quarkus transition?