JBoss ESB should focus on startup and performance as EAP is heavier than lightweight Java frameworks, which impacts microservices and cloud environments. Improvements should include faster start times and reduced memory footprints. Better cold-start performance in containers should be emphasized. Cloud-native features must be enhanced since many enterprises are shifting to Kubernetes and OpenShift, making EAP more cloud-friendly. This could include providing smaller container images, native auto-scaling support, and improved integration with cloud configuration services. Enhancing the developer experience is crucial; while the current configuration is powerful, it can be complex for newcomers. As an experienced user, I navigate it easily, but newcomers struggle due to heavy reliance on XML configuration. Transitioning to a JSON-based configuration or YAML format would be beneficial, and simplifications in clustering setup for local testing would greatly assist users.
Financial Technology Solution Consultant at Intellect Design Arena Ltd
Consultant
2020-07-05T15:50:32Z
Jul 5, 2020
The EPA, from what I understand, lacks a lot of features and it doesn't really know how to interface with legacy systems or how to develop APIs for legacy systems. I'm not sure if it is possible, however, we would like to see features that allow for legacy systems so that they can continue to be developed and managed well. The solution should provide some more general studio features. We should be able to manipulate the platform in order to do some integrations on our own. There needs to be a bit more flexibility.
Enterprise Service Bus (ESB) is a middleware solution facilitating the integration of various applications and services within an enterprise, promoting seamless data exchange and process automation.ESB serves as a communication backbone, providing a scalable and flexible architecture that integrates disparate systems, whether on-premises, in the cloud, or in hybrid environments. It enables standardized messaging across a multitude of platforms, reducing system complexity and improving...
JBoss ESB should focus on startup and performance as EAP is heavier than lightweight Java frameworks, which impacts microservices and cloud environments. Improvements should include faster start times and reduced memory footprints. Better cold-start performance in containers should be emphasized. Cloud-native features must be enhanced since many enterprises are shifting to Kubernetes and OpenShift, making EAP more cloud-friendly. This could include providing smaller container images, native auto-scaling support, and improved integration with cloud configuration services. Enhancing the developer experience is crucial; while the current configuration is powerful, it can be complex for newcomers. As an experienced user, I navigate it easily, but newcomers struggle due to heavy reliance on XML configuration. Transitioning to a JSON-based configuration or YAML format would be beneficial, and simplifications in clustering setup for local testing would greatly assist users.
The EPA, from what I understand, lacks a lot of features and it doesn't really know how to interface with legacy systems or how to develop APIs for legacy systems. I'm not sure if it is possible, however, we would like to see features that allow for legacy systems so that they can continue to be developed and managed well. The solution should provide some more general studio features. We should be able to manipulate the platform in order to do some integrations on our own. There needs to be a bit more flexibility.