What is our primary use case?
The primary use case for the solution is infrastructure optimization. Most times the client wants to optimize their integration infrastructure and they want to simplify it. When they feel home-grown solutions are not scaling well for them in terms of complexity, in terms of speed to market, they look to this solution. Projects take long and they break down all the time. That's when the clients start thinking Integration Bus. It's a solution that offloads all the integrations of their system.
What is most valuable?
The solution offers pretty good pricing.
The technical support is great.
The solution is stable and can scale relatively easily.
The user interface is easy to navigate.
The performance is decent.
The solution offers good dashboards.
The management and monitoring on offer are very good.
What needs improvement?
IBM doesn't really have a very strong community surrounding the product. Most of its direct competitors are open source solutions, and those have an excellent and well-developed community around the tech to help users navigate the ins and outs of the product. IBM is lacking in this area. If they had more of a community, more people would know about the product. They should push to create a developer community around it and make the products more accessible to developers.
I've heard some clients are asking for autoscaling capabilities. It could improve DevOps. They might have something similar in other products, however, if they could introduce it within this product at some small level, it would make many clients happy.
For how long have I used the solution?
We've been using the solution in the company for less than a year.
What do I think about the stability of the solution?
We've been pleased with the solution's reliability. It's stable. It doesn't crash or freeze. I don't recall facing any bugs or glitches. It just works well all the time.
What do I think about the scalability of the solution?
The solution scales quite well. If a company needs to expand it out, they can do so easily.
How are customer service and technical support?
Technical support has been good. They're responsive and knowledgeable. We've been satisfied with their support. It's been great.
How was the initial setup?
The implementation is straightforward. It's not complex. What takes a long time, however, is implementing the workflows or projects. That's where the efforts is. In terms of implementation, the implementation is straightforward. However, building the integration of workflows can be a bit tricky.
You have to pick the right project as the first project, due to the fact that you're introducing a new product inside an organization. The first project is important in terms of setting the stage for understanding the underlying functionality. It shouldn't be too complex. At the same time, it should be impactful enough that you get management support going forward. It should be a project that is big enough whereby you can see the impact of the Integration Bus.
What's my experience with pricing, setup cost, and licensing?
The pricing is pretty good. What they charge isn't unreasonable.
What other advice do I have?
We're IBM partner-resellers.
The reason we've implemented the solution is driven more by our clients' demands. The clients want IBM Integration Bus, or they already have some investment in IBM Integration Bus. We want to build capability in it to support the clients. We don't have a level of experience with the solution.
My personal advice to others is to start small so that you give yourself a good preliminary base that's not too overwhelming. Most clients want to do everything with this solution, which is fine. However, it's always better to start small with a departmental project, as opposed to an enterprise-wide kind of thing. It is better to start small and tackle a practical project and get used to everything before going really big.
I'd rate the solution nine out of ten.
Which deployment model are you using for this solution?