Jakarta EE is a widely recognized framework for building enterprise applications. It facilitates the development of scalable applications by offering a comprehensive set of specifications, fostering a more efficient and reliable environment for developers.
| Product | Mindshare (%) |
|---|---|
| Jakarta EE | 16.9% |
| Spring Boot | 28.0% |
| Apache Spark | 11.3% |
| Other | 43.8% |
The standout attributes of Jakarta EE are its REST services, configuration capabilities, and persistent facilities. Additionally, it is highly compatible with cloud environments.
The configuration of Jakarta EE could be simplified to enhance its usability for developers.
The ROI from Jakarta EE was highly positive and beneficial for users. It significantly improved the software development process and enhanced the overall efficiency and productivity of our team.
The adoption of Jakarta EE resulted in cost savings, streamlined operations, and increased customer satisfaction. It provided a robust and reliable platform for developing enterprise applications, enabling users to deliver high-quality solutions to our clients.
The flexibility and scalability of Jakarta EE allowed users to easily adapt to changing business requirements and market demands.
The pricing of Jakarta EE is rated as mostly positive.
Jakarta EE is used for business enterprise purposes.
Customers have expressed that Jakarta EE's customer service and support could be enhanced, particularly in terms of improving the accessibility of documentation.
The initial setup of Jakarta EE may be moderately difficult. Users have encountered issues configuring it with Windows, suggesting that there is room for improvement in this area.
The scalability of the Jakarta EE is contingent upon the chosen architecture.
The stability of the Jakarta EE is considered average.
As a robust enterprise platform, Jakarta EE supports the development of dynamic applications through a suite of specifications that ensure consistency, security, and scalability. It enables developers to utilize a broad range of tools, promoting streamlined application transformation while maintaining high-performance standards. Jakarta EE's architecture supports cloud-native development, making it suitable for both traditional and modern applications.
What features stand out in Jakarta EE?In specialized industries like finance and healthcare, Jakarta EE is implemented to meet demanding regulatory requirements and data integrity standards. In finance, it supports secure transactions and compliance. In healthcare, it aids in handling sensitive patient data efficiently, ensuring both security and accessibility.
| Author info | Rating | Review Summary |
|---|---|---|
| Technical Lead at Cellulant Kenya | 3.5 | We use Jakarta EE for building cloud-native applications, finding configuration and monitoring easy, though improvements by incorporating UI-based dependency management like in Spring Boot are needed. We also evaluated Apache Kafka, which I found complex. |
| Senior Java Software Engineer at eDreams ODIGEO | 3.0 | I use Jakarta EE primarily for business enterprise solutions. Its valuable features include REST services, configuration, and persistence facilities, and it is cloud-friendly. However, simplifying configuration would enhance the developer experience. I haven't used other solutions or specific cloud providers. |
| Product Manager/ Senior Software Developer at RedShift | 4.5 | I find Eclipse stable, with good workspace features and improved usability. My main concern is that excessive plugins make the interface slow, and I'd like better integration with newer Java frameworks. Overall, I rate it highly. |
We use it for building dynamic cloud profiles and developing cost-effective cloud-native applications.
Configuring, monitoring, and ensuring observability is a straightforward process. You can readily set up these elements on your local machine to keep track of metrics.
Enhancements in configurations can be achieved by benchmarking against Spring Boot technology. It would be great if we could have a UI-based approach or easily include the specific dependencies we need.
I have been working with it for one year.
I have found it to be quite stable, without any noticeable issues or problems.
When running applications in the cloud, scalability is highly dependent on how you configure it. Factors such as the number of instances you want to scale, and the threshold for scaling based on the quantity of messages or the amount of data, are all customizable based on your application's needs.
While I haven't encountered any issues yet, if I do run into any, it will be important to understand the available support, whether it's from the company or the community. I have a positive impression of the support available so far.
Positive
Due to my experience, it was relatively easy for me to adapt, but newcomers, especially those without prior experience with it, might find transitioning to the cloud more straightforward.
The deployment was done in-house and it was prompt. One of the benefits is that it has a quicker response time.
I would certainly recommend it to other users, especially those interested in quickly setting up APIs and creating applications. I've noticed continuous improvements in the micro profile, with each iteration enhancing the components for cloud use. On a scale of ten, I would rate it a seven.
I primarily use Jakarta EE as a business enterprise product.
Jakarta EE's best features include REST services, configuration, and persistent facilities. It's also incredibly cloud friendly.
Jakarta EE's configuration could be simpler, which would make it more useful as a developer experience.
I've been using Jakarta EE for six months.
Jakarta EE's stability is okay - I would rate it as six out of ten.
Jakarta EE's scalability depends on the architecture you're using.
Jakarta's technical support has a lot of room for improvement, especially in making it easier to find documentation.
Neutral
I would rate the initial setup as six out of ten. It was medium difficult, and there were problems configuring it with Windows, so there's room for improvement.
I would rate Jakarta EE's pricing seven out of ten.
I would give Jakarta EE a rating of six out of ten.
There are seven of us on my team and we all use Eclipse with the same spec of plugins. We're a customer of Jakarta.
I like the work space of the application, specifically the feature that allows us to have a different work space based on the kind of application that we are using. I think the project Explorer is also very useful, and the usability of the application is also very good. It's improved in the last two or three years, previously it was more difficult to use. Eclipse is now on a good track and they have a very good interface.
There could be some improvement on the interface. I think all the customization and all the plugins we can instal make the interface too slow and heavy in some situations. It would be helpful if Eclipse would provide guidelines as to how we should deal with this, although it's much better than it was six or seven years ago.
Additional features that would be helpful would be the integration with the new Java frameworks, like Angular, which should already be integrated in the product because I think the Java and JavaScript developers are moving to Angular. I believe the integration inside the ID should be brought into the product.
I've been using this solution for about 12 or 13 years.
In the last few years, the stability has greatly improved. Right now, I have no complaints about it. For me, right now, it's very stable and I have no problems with it.
I haven't contacted customer support directly because there's always someone via the internet who can solve any problems or difficulties. If I were to use the Eclipse support it would be directly using an online forum or the Eclipse community, but I've never made contact by phone.
I initially used Netbeans because it's a good solution but there were some problems there about ten years ago and we moved.
Initial setup was fairly straightforward. We have a spec of tools and applications that we use on top of the default installation of Eclipse. And because of that, and using them for so many years, we already know the steps and the sequence for installation. Right now, it's very simple to install into the end setup for the tools that we use.
We carry out the deployment ourselves, even using the external web server, the JBoss WildFly, the integration is very good to use inside Eclipse.
There are some good tutorials on YouTube that the Eclipse team has provided and I think it's a good way to get started.
I would rate this product a nine out of 10.
