We performed a comparison between Microsoft Azure API Management and SEEBURGER Business Integration Suite based on real PeerSpot user reviews.
Find out in this report how the two API Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The ease of use of the solution is excellent."
"The stability and performance are good. It is easy to install, and it scales well too."
"API Management does not take long to deploy."
"The solution is reliable and very stable."
"The solution is quite stable. We have no issues with it. there have been no crashes and we haven't experienced bugs or glitches. It's been quite reliable."
"We're very satisfied with Azure API Management. We've had no issues with bugs, everything runs smoothly, and the connection between the cloud and the on-premise infrastructure was good."
"Azure API is scalable."
"There were no scalability issues."
"The solution helps us automate processes, more on the insurance side. Where they used to have to babysit monthly files, because of size, they don't have to do that with SEEBURGER BIS. They just run the monthly process. Files get collected, translated, and sent to the proper systems, so the babysitting is gone."
"One valuable feature is the scalability. We have not had to add processing power or hardware since we installed it. Also, we are able to create and deploy maps to migrate from another EDI platform very quickly."
"I like that the tool has all the adapters — all the possible protocols that are in the industry. You pay for those adapters but at least it's all in one package. You don't have to get another tool or application to support another partner."
"The product has the ability to handle high volumes of data efficiently."
"It is a JavaScript or a Java-based system within their mapping tool. You can actually write a lot of code in there. We can perform a lot of the translations even within our mapping, whereas we used to have to do custom programming on our back-end systems to fully integrate."
"It has a lot of basic EDI already established for all the main users. Also, it lets me share setups that I had already set up for my first plant. I was able to use them for my second one which was very helpful. I didn't have to start from scratch for my second facility."
"The platform has been very consistent and responsive."
"In our landscape, we have a lot of AS/400s or iSeries and SEEBURGER Business Integration Suite (BIS) has a file service listener that allows data to seamlessly be transferred between the SEEBURGER solution and the AS/400."
"There is always room for improvement. There should be more analytics abilities so you can know how much traffic there is. Log Analyzer isn't well integrated with this solution."
"The user interface needs improvement."
"The hybrid part could be improved because API Management is entirely cloud-based, but some of our resources are on-prem, so formatting is an issue. Our goal is dual implementation."
"Technical support could be more flexible and try to meet the client's needs a bit more effectively."
"If I compare this solution to others I have used in other phases of my life, having APIM being an Azure resource, it is easy to configure and deploy. However, this conversely reduced the flexibility. The difficulty is how do we configure it in a manner that a larger enterprise would probably want it to be. This creates a bit more complexity, working around the constraints of the resource itself. If comparing it to other solutions, it is more of a legacy design with an older approach. The various level components are still around resembling an on-premise type of design similar to other solutions, such as Apigee or Mulesoft. They are still predominantly carrying some legacy design. Which might be suited for organizations where they have a more complex network layout. APIM is easy to deploy, but on the other side of that, it is constrained to how Azure has designed it to be."
"What would make Microsoft Azure API Management better are more APIs. They keep updating their APIs, but it would be better if the solution had more APIs for the services and more integration with other platforms."
"The external policies are impossible to look at and configure."
"Support for GraphQL could be better."
"There are some aspects at the front, the actual queries that you use, that could be improved. They're all very minor to be honest."
"Java is very old technology and they should move away from it, to anything that's better."
"There are a lot of service packs during the year. I know that part is the process for updating features, but sometimes it's difficult to update service packs every month."
"The initial set up was done by SEEBURGER consulting. It can be complex due to various factors, such as server settings, database settings, and security settings."
"There might be some improvements they could make to the portal, but they're not anything that stops me from working."
"In the BIS, if I want to have some API functionalities, that is a separate tool. The integration between the API tool and the BIS is not that straightforward. If they were to combine these tools and give us one suite, that would be helpful. Today I have a lot of partners onboard. I have something like 50,000 partners doing API transactions. If I want to introduce a new tool for API management, I have to do a lot of workarounds. But if it were integrated well within the existing suite, it could be straightforward for me."
"I find the solution quite confusing to use, especially when looking at the tree structure."
"We are a little locked in with understanding the errors that we receive. We are working with their support to prevent these issues when they come into the database. We use a SQL database and believe they can do better when it comes working with large databases. We have had few instances where the system is hanging, which are most likely from the database. We are working with their support to find out the problem and fix their system. We have tried to use their notification system to prevent these issues, but they need to improve their monitoring system."
More Microsoft Azure API Management Pricing and Cost Advice →
More SEEBURGER Business Integration Suite Pricing and Cost Advice →
Microsoft Azure API Management is ranked 1st in API Management with 67 reviews while SEEBURGER Business Integration Suite is ranked 19th in API Management with 37 reviews. Microsoft Azure API Management is rated 7.8, while SEEBURGER Business Integration Suite is rated 8.4. The top reviewer of Microsoft Azure API Management writes "Efficiently manages and monetizes API ". On the other hand, the top reviewer of SEEBURGER Business Integration Suite writes "Gives us the flexibility to hook up to systems using any protocol out there". Microsoft Azure API Management is most compared with Amazon API Gateway, Apigee, MuleSoft Anypoint API Manager, Kong Gateway Enterprise and IBM API Connect, whereas SEEBURGER Business Integration Suite is most compared with SAP Cloud Platform, IBM Sterling B2B Integration Services, Mule ESB, IBM B2B Integrator and webMethods Integration Server. See our Microsoft Azure API Management vs. SEEBURGER Business Integration Suite report.
See our list of best API Management vendors.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
