If you were talking to someone whose organization is considering IBM Integration Bus, what would you say?
How would you rate it and why? Any other tips or advice?
IBM is huge once you start it up. There's not a lot of coding, not a lot of method to the mapping, and they have the need for application software management. I'd rate it a nine out of 10. It's stable across multiple platforms and across multiple applications. They're very strong and a trusted brand. They are patient and good friends. One of the only challenges is that it is hard to teach people.
We're just IBM customers. We're not partners and we don't have a relationship with the company. In terms of on-premises vs cloud, I'd suggest users go to the cloud. It obviously depends on the market and the adoption rate. I'd rate the solution eight out of ten.
I'd rate the solution ten out of ten.
My advice for anybody implementing this solution for the first time is to have people from IBM on-site to help you establish the operating procedures and the development procedures. My understanding is that the new release will have a lot of new features, including support for Docker containers. At this point, I don't have any requirements for the new release. It has also been rebranded. This is a good solution from a technical and operational point of view, but they should really remove this technically complicated license controlling. It is very complicated software that you have to install. I would rate this solution a nine out of ten.
My advice for anybody who is implementing this solution is to start with reading the documentation. Have a good understanding of how to integrate Integration Bus with different resources, and to have experience with a synchronized interaction with IBM MQ or Apache Kafka. But IBM MQ is preferable. Also, it is better to have an understanding of the HTTP Interaction and REST API interaction. I also suggest people participate in IBM online learning. There are two courses that go over features that are related to integration development. They are very helpful. They also teach how to develop an integration solution, so it is an interesting program. Additionally, explore the IBM blog about Integration Bus and App-Connect. You can find there a lot of integration patterns. Other Integration solutions require an application server, but with IBM Integration Bus, it doesn't require a special application server. I would rate this solution a nine out of ten.
This is a very large and complex product. It takes several people to understand every feature in it because nobody understands it completely. I am an architect but I also develop. I really love this product and the graphical way of doing things, but there are limitations because you are not doing hundred percent programming. Instead of programming, you are solving some complex functionality needs by configuring, and you have to understand how to do it. For anybody who is implementing this solution, it is important to say that even though I am senior, I'm a junior when it comes to this solution. I was only brought in to work on this two years ago. It requires many years of experience to be good at it. You can't just jump on and be skilled at using it. Even when the people from IBM came and worked on prior applications, they were having challenges. Of course, the nature of the problem that IBM Integration Bus solves is challenging. All of this said, I like the graphical interface and I don't mind working on projects that are long-term. For most of the features, I would rate them ten out of ten. But when it comes to understanding transaction related settings (and other solutions provided via the configuration settings), and the fact that there are so many documents you have to read to find one small thing, I would rate that area a five or six out of ten. Overall, I would rate this solution a seven out of ten.
IIB very flexible.nearly limitless , You can easily overload it with duties that it's not meant to hold. Organizations needs to have strong their architecture team and SOA governance during and After implementation .to avoid overloading the ESB Layer. I would give IBM Integration Bus an 11 out of 10. I have tried solutions from competitors Brands. There is no comparison.
IBM recently changed the name of this solution to IBM API-Connect. With the new name, they have added two new features, such as connecting to the cloud.
I would rate this solution a nine out of 10, because of: * The community. * They provide freeware. * The support that IBM provides. * It fits its purpose. IIB is one of the top-rated solution in this category. If looking for a tool which is SOA compliance, you can blindly go for this particular tool. The most important criteria when selecting a vendor is support. We are looking for the 24/7 support in respect to that particular product. It should be compliant within our business requirements. Technology is evolving day-by-day and should have an additional features added-on as long as we are required to implement those features, e.g. product security. We are using different encrypted algorithms on encryption screens, and these functionalities are widely adopted by IBM.
IIB is a great product. It could use some minor improvements, such as: * IIB toolkit needs design overhaul; maybe some themes. * Current aggregation implementation should be deprecated. MQ independent, as well as an intuitive solution, should be proposed. * App Connect Enterprise (IIB's newer version) might solve the above issue.