We performed a comparison between SEEBURGER Business Integration Suite and StreamSets based on real PeerSpot user reviews.
Find out what your peers are saying about SAP, MuleSoft, IBM and others in Business-to-Business Middleware."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."
"We use Message Tracking, which is a very good feature. Message Tracking has about 300 to 400 business people who can find documents and ask the integration team about them. For example, they looking for a document that the vendor or trading partner tells them that they sent, but they don't see it in the ERP system yet. So, they go to SEEBURGER Message Tracking, which can tell them if we received it already from the outside and what happened, e.g., if it went to SEEBURGER BIS or if it's already in the ERP system. It's a very simple tool to use. They also can use that tool to see the source document."
"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."
"When orders come in they go into our ERP system directly, so there is integration there."
"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."
"It's a very robust solution and it's very configurable. Before this product we would use an ESB-type of solution which required us to write code and go through a process. We can configure the SEEBURGER solution much more easily, instead of writing code... It can handle large files very well."
"The solution is flexible when it comes to adding integrations. It is much easier to use than the other tools we have to move the files. Across the board, we can move files in a short amount of time compared to our other existing tools."
"The product has the ability to handle high volumes of data efficiently."
"The most valuable would be the GUI platform that I saw. I first saw it at a special session that StreamSets provided towards the end of the summer. I saw the way you set it up and how you have different processes going on with your data. The design experience seemed to be pretty straightforward to me in terms of how you drag and drop these nodes and connect them with arrows."
"In StreamSets, everything is in one place."
"Important features include that it comprises lots of functionality to connect data from various sources through connector availability, scheduling pipelines at any time, and integration with third-party and security solutions for encryption."
"StreamSets’ data drift resilience has reduced the time it takes us to fix data drift breakages. For example, in our previous Hadoop scenario, when we were creating the Sqoop-based processes to move data from source to destinations, we were getting the job done. That took approximately an hour to an hour and a half when we did it with Hadoop. However, with the StreamSets, since it works on a data collector-based mechanism, it completes the same process in 15 minutes of time. Therefore, it has saved us around 45 minutes per data pipeline or table that we migrate. Thus, it reduced the data transfer, including the drift part, by 45 minutes."
"What I love the most is that StreamSets is very light. It's a containerized application. It's easy to use with Docker. If you are a large organization, it's very easy to use Kubernetes."
"The UI is user-friendly, it doesn't require any technical know-how and we can navigate to social media or use it more easily."
"Also, the intuitive canvas for designing all the streams in the pipeline, along with the simplicity of the entire product are very big pluses for me. The software is very simple and straightforward. That is something that is needed right now."
"The scheduling within the data engineering pipeline is very much appreciated, and it has a wide range of connectors for connecting to any data sources like SQL Server, AWS, Azure, etc. We have used it with Kafka, Hadoop, and Azure Data Factory Datasets. Connecting to these systems with StreamSets is very easy."
"API connectivity needs improvement as well as the GUI. The GUI hasn't changed that much in 10 years, but of course, that's already been updated. I would say I'm excited about the screenshots but that's about it."
"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."
"Their traditional model is a vendor flow. We are looking to do a customer-based flow, which which require significant development from SEEBURGER Business Integration Suite (BIS). We are working with them to do this using their WebEDI. It is a brand new area for them, but it could be an option in the future."
"We don't have much access to the logs or what's happening. So we have to log a ticket with SEEBURGER. We only get a message that something has failed... we have to open a ticket with SEEBURGER for them to tell us exactly what the issue is... I would like us to be able to be more self-sufficient."
"The solution's documentation is not up to the mark and needs to be improved."
"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."
"Difficult in handling large amounts of data, like when the file has more than 100MB in size."
"I would like there to be a feature that could handle the limited server."
"Visualization and monitoring need to be improved and refined."
"The design experience is the bane of our existence because their documentation is not the best. Even when they update their software, they don't publish the best information on how to update and change your pipeline configuration to make it conform to current best practices. We don't pay for the added support. We use the "freeware version." The user community, as well as the documentation they provide for the standard user, are difficult, at best."
"StreamSet works great for batch processing but we are looking for something that is more real-time. We need latency in numbers below milliseconds."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"Sometimes, when we have large amounts of data that is very efficiently stored in Hadoop or Kafka, it is not very efficient to run it through StreamSets, due to the lack of efficiency or the resources that StreamSets is using."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"Currently, we can only use the query to read data from SAP HANA. What we would like to see, as soon as possible, is the ability to read from multiple tables from SAP HANA. That would be a really good thing that we could use immediately. For example, if you have 100 tables in SQL Server or Oracle, then you could just point it to the schema or the 100 tables and ingestion information. However, you can't do that in SAP HANA since StreamSets currently is lacking in this. They do not have a multi-table feature for SAP HANA. Therefore, a multi-table origin for SAP HANA would be helpful."
"The data collector in StreamSets has to be designed properly. For example, a simple database configuration with MySQL DB requires the MySQL Connector to be installed."
More SEEBURGER Business Integration Suite Pricing and Cost Advice →
SEEBURGER Business Integration Suite is ranked 5th in Business-to-Business Middleware with 37 reviews while StreamSets is ranked 8th in Data Integration with 24 reviews. SEEBURGER Business Integration Suite is rated 8.4, while StreamSets is rated 8.4. The top reviewer of SEEBURGER Business Integration Suite writes "Gives us the flexibility to hook up to systems using any protocol out there". On the other hand, the top reviewer of StreamSets writes "We no longer need to hire highly skilled data engineers to create and monitor data pipelines". 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, whereas StreamSets is most compared with Fivetran, Azure Data Factory, Informatica PowerCenter, SSIS and IBM InfoSphere DataStage.
We monitor all Business-to-Business Middleware 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.