Ariel Lindenfeld - PeerSpot reviewer
Director of Community at PeerSpot
  • 3
  • 248

When evaluating Business-to-Business Middleware, what aspect do you think is the most important to look for?

Let the community know what you think. Share your opinions now!

PeerSpot user
3 Answers
Real User
Mar 24, 2021

As an architect, I prefer open source integration solutions because they very often set the future standards and do not depend on a particular supplier.

Search for a product comparison in Business-to-Business Middleware
JamesLewis - PeerSpot reviewer
Managing Director / Co-Founder at Pro2col Limited
Top 10
Jan 25, 2022

In addition to the comprehensive point below, there are a few others that I'd look for. The evaluation process shouldn't just focus on the product, middleware technologies have been around for decades and 'largely' provide the same functionality, just delivered a different way. I would also be analysing the company behind the software. Questions to consider include:

• How often are new (major) software releases made available?

• What levels of support are offered and do they cover your timezone adequately? Look for SLA's that match your business expectations?

• What level of technical documentation is available - help files, knowledge bases, community forums, etc?

• Does the company have multiple tools that do the same thing - if so, which one will stay the course?

• Is the vendor open and honest about their place in the market during the sales process?

• Do they publish their subscriptions/software renewal rates? If they're not above 95% I would suggest there's a problem.

• Finally, ask for a published roadmap so you can see where the vendor wants to take the product/service.

The key takeaway is that you need to check the software does what you need it to do for now AND in the future. However, equally critical is making sure you don't back the wrong horse (vendor).

it_user651690 - PeerSpot reviewer
Senior B2B Integration Specialist at a financial services firm with 10,001+ employees
Apr 23, 2017

First, how well does it fit my B2B requirements out of the box?
B2B Middleware is not something you could just buy off the shelf. It requires significant technical knowledge, as well as a very specialized knowledge of your business processes and requirements to formalize a solution that will work for company.
Most middleware solutions are more a suite of tools, services and adapters, coupled together by ESB engines. Does this particular suite (or the number of addons you may have to add) cover the full scope you will need? What effort (infrastructure provision, software installation, configuration, and additional development) will it take)? How available are the people and resources for this effort? Does the solution cover all the communications/transport protocols and data types that I need to communicate with my internal and exteral vendors? What are the available data transformation tools like? How difficult is it to onboard my trading partners with this solution? Does it take the ever increasing scope of security and flexibility demands into account? And last, but not least, what expertise is available out there to help build my solution and keep it going?

Learn what your peers think about IBM B2B Integrator. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
656,474 professionals have used our research since 2012.
Related Questions
Rony_Sklar - PeerSpot reviewer
Community Manager at PeerSpot (formerly IT Central Station)
Oct 11, 2021
How do APIs and middleware differ in the way that they are used? 
See 2 answers
Ram Kanumuri - PeerSpot reviewer
Vice President - Digital Integration at Kellton Tech Solutions Limited
Jun 17, 2020
Middleware is logical Software System that provides capabilities to other software applications, databases etc to be integrated. Middleware is analogous with Integration Software. It comes with defined capabilities like communication protocols, data transformation and mapping, connectivity etc. It also bridges physical systems and networks. API, on the other hand is Software Architectural paradigm or a programming "style" for standardizing end-point connectivity of Systems, Applications and Data Integration. In short, Middleware is software logical layer for Integration, while API is dominant trending/recent style/paradigm for Integration. They go together - an API is functional definition of an Integration endpoint, while API Gateway Server is a middleware runtime component where APIs are run/hosted to be consumed by requesting applications and systems. Also API Portal is another middleware component that acts as a directory for APIs enabling their development life-cycle.
Atakan Köycü - PeerSpot reviewer
Co-Founder at Negzel Teknoloji A.Ş.
Oct 11, 2021
The API (Application Programming Interface) can be provided by most middleware. It can be SOAP but generally, REST services.  These two words are quite different in meaning. API refers to callable services, while middleware refers to the product that does the integration work in the integration ecosystem.
it_user7077 - PeerSpot reviewer
BI Expert at a tech services company with 501-1,000 employees
Nov 19, 2014
We're a global automotive supplier looking for B2B products to evaluate. Requirements would be similar to Seeburger BIS. Must already have a presence in the industry. Ideally would be a global provider but not a requirement. Can anyone provide feedback about any of the solutions on the market? What do you like and what don't you like?
See 1 answer
it_user163980 - PeerSpot reviewer
Architect at Tata Consultancy Services
Nov 19, 2014
I think you can try TIBCO Business Connector for B2B alone. Always depending on the requirements. IBM WMB, webMethods, TIBCO, Oracle fusion and Mule. Thanks Prapa
Download Free Report
Download our free IBM B2B Integrator Report and get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
656,474 professionals have used our research since 2012.