We performed a comparison between Layer7 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."It is flexible in how it creates custom policies and uses builds with impressive methods."
"Almost all security features are available out-of-the-box and can be deployed rapidly."
"Easy to use, nice UI, and good search functionality."
"It is a stable product."
"It is fairly stable for the Gateway side."
"What I found most valuable in Layer7 API Management is that you can launch the API from the gateway quickly and securely, making it less complicated to deploy APIs. I also like that Layer7 API Management has a good portal and dashboards and that the dashboards show you statistics regarding how many people used the API, etc."
"For developers to be able to come, sign up, or find APIs."
"It can be scaled as we need. And it can be used in different regions. We have different data centers in the U.S. and Beijing. We use it on-premise, on-cloud, and it can be hosted and used at any place and scaled across the regions."
"Another aspect that we employed in the last year-and-a-half has been their CMA platform component, which hooks to the SEEBURGER Business Integration Suite (BIS) front end. We've been able to set up an automatic testing process for our partners."
"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."
"The tool's performance doesn't get affected by transformation loads. You can write any number of rules, filtering criteria, transformations, etc."
"The entire framework is something that is very easy to use, easy to set up, and extremely straightforward. Once you develop a process and once you get it deployed within the process engine, with the latest 6.52 features, the processing engine is actually smart enough to make a decision as to which process engine has less load, and it can exchange messages with that process engine."
"The solution's capabilities in fulfilling our existing B2B integration requirements are brilliant. Among our multiple customers we connect to SAP systems, JDE, all the various ERPs that you can possibly get, Oracle procurement systems, etc. We haven't come across anything yet — and customers are trying to trip us up — that we can't do."
"With SEEBURGER BIS, you can string as many different activities together in your workflows as you want. You can put them in any order, like a piece of code. One leads into the next, which leads into the next. It is just very flexible from that vantage point. This makes it so easy to use and reduces the number of moving parts that you need to have. It is just a lot less frustrating not having to conform to how some other vendor software works."
"Mapping Designer provides excellent flexibility."
"What would have been a manual process of transmitting data items around between us and third-parties has been automated. SEEBURGER BIS handles the automation and mapping side of the communications. The automation, along with the efficiency around time and cost, has improved our organization. Around 20,000 messages a month have been automated. These typically would be financial/order transactions and confirmations in invoicing that have been automated."
"There could be more integration options included in the product."
"The Portal is not stable."
"One area where it certainly needs to improve is the way it allocates requests, in terms of rate limiting. Also, there is no native Kafka connectivity."
"Layer7 API Management’s price could be reduced."
"The CA API Management solution has good security features, but when it comes to being used in areas like enterprise integration, where it is being used as middleware for all the IT environments, that particular feature is quite limited. It doesn't support as many protocols as an industry standard, competing product should."
"I understand that clients are often concerned about costs. They might be exploring other options due to the high cost associated with our current package."
"The development toolkit used for creating APIs should be more online and user-friendly. Deployment and tracking could also be improved. Tools like Apigee provide a complete online experience along with RESTful APIs, to manage all activities. It is a very nice and user-friendly solution compared to CA."
"The interface should be improved."
"Difficult in handling large amounts of data, like when the file has more than 100MB in size."
"They have their own private cloud. That's the reason we did not go ahead with managing everything by ourselves or moving into the cloud. They said that they're going to be doing it within the next two years, having access to Azure and AWS. That would be something we would like to see."
"Some of the functionality for retriggering documents, where you have to step through a termination process and then retrigger it, versus just being able to restart or retrigger more easily, is a bit challenging, depending on the scenario."
"They made improvements to the email error alerts that go out, for the EDI technical. Those typically go straight out to the partners. Those messages are significantly clearer and easy to read. The same messages in the front end are not nearly as clear. It's supposed to be the same error, but the message that goes out for EDI is really easy for anybody to read and understand, but you have to be really solution-savvy to understand the message in the system itself."
"It's rather difficult to understand, from the application, what's broken and why it doesn't work. We typically need to get support from them directly, and it's usually in a consulting role, to fix issues."
"Java is very old technology and they should move away from it, to anything that's better."
"We wanted to use API. We were told that in 6.52 we could use API management. Later on, we found that API management wasn't that completely integrated into the 6.52 solution, and if you wanted to have the whole API suite you might have to go to 6.7, the latest one."
"The speed of development needs improvement. If you acquire any customization, it can be a slightly slow process. I would like to see more flexibility around customizations. The time frame right now depends on the sophistication and customization, but we have to go through a process of getting them to develop, implement, and test it. This might take a couple of weeks. If it was a simpler system to customize, the time could probably be cut by half or down by even 25 percent of what it would normally take."
More SEEBURGER Business Integration Suite Pricing and Cost Advice →
Layer7 API Management is ranked 10th in API Management with 109 reviews while SEEBURGER Business Integration Suite is ranked 19th in API Management with 37 reviews. Layer7 API Management is rated 8.4, while SEEBURGER Business Integration Suite is rated 8.4. The top reviewer of Layer7 API Management writes "Has great drag-and-drop features and it requires minimal coding ". 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". Layer7 API Management is most compared with Apigee, Kong Gateway Enterprise, Amazon API Gateway, MuleSoft Anypoint API Manager and Microsoft Azure API Management, whereas SEEBURGER Business Integration Suite is most compared with SAP Cloud Platform, IBM Sterling B2B Integration Services, Mule ESB, IBM B2B Integrator and Microsoft Azure API Management. See our Layer7 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.
