There is some lag in the GUI. There have been some performance issues and maybe it's because of the application data.

I know that Message Broker was a very tightly copied product with another IBM product, that is, IBM MQ. I would like to have a little bit more decoupling from the IBM MQ because it should not be a prerequisite for IBM WebSphere Message Broker usage.

The goal is to minimize dependency and avoid frequent releases of a new version of the solution. Ideally, it is preferred to have a single version of the solution that can be sustained for a period of two to three years with only minor upgrades rather than a complete overhaul.

The solution can be improved by making the product lightweight, as it is currently a weighty product.

Stability and pricing are areas with shortcomings that need improvement.

My biggest complaint about this product is the price. The cost is a significant reason why we're looking at other products right now.

Technical support is very slow and needs to be improved. Significant improvement is needed, especially when dealing with a tier-one client.

They are just now looking at Cast for their streams product, so they are a bit behind when it comes to technology. I no longer look to IBM for new technology.

If you want to connect to the database, it provides solutions in India, but you have to purchase it separately. They are not mature enough and we have difficulties using them. They are expensive and not worth the money we are spending on them.

I feel with IBM, when you want certain functions or features, you have to continuously purchase add-ons.

Scalability needs improvement, it was easy to scale before microservices and Docker.

Technical support is good but they could have a better response time.

I think that they should provide us with some kind of capabilities that can be deployed. For example, if they have integration nodes that can be deployed separately instead of having a new, big server that has different components, to give us the capabilities to deploy everything on our own instead of building them up together. It would benefit us when it comes to scaling and building.

The user interface is designed mainly for experts, much in the way a BPM or another integration tool is. The administration console is ok because it's used by the administration team or the technical team.

The external interfaces have limitations compared to vertical technologies such as JS frameworks like React or Angular that have lots of capability for UI and UX design.

This tool can be challenging when you use it for a really complex solution, or if you try to use it for a purpose other than what it is designed for. For example, using it as a BPM tool will be challenging.

When choreography is necessary, the product doesn't work. IBM has to take a different approach to maintain the software as a service solution. The price could also be lowered.

The solution can add container engines such as docker.

The solution is very expensive and has room for improvement.

The size of the container used in the deployment is still a bite large and I think it should be improved and become lighter.

It would be useful to make container deployment easier .

I haven't completely tested the solution. I have a CMM BPM background, and recently moved to work on this so I'm only now getting exposure in this particular area. It's difficult to comment at this early stage but I find the installation configuration is quite difficult compared to other solutions. The other issue is that I don't have cloud, and we can't get any cloud where IBM is moving. I'm not sure whether we can move this application to the Azure or AWS cloud solutions. It's a major challenge and we still haven't had any kind of official documentation from IBM as to how we can move forward on that.