"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."
"In StreamSets, everything is in one place."
"I have used Data Collector, Transformer, and Control Hub products from StreamSets. What I really like about these products is that they're very user-friendly. People who are not from a technological or core development background find it easy to get started and build data pipelines and connect to the databases. They would be comfortable like any technical person within a couple of weeks."
"It is really easy to set up and the interface is easy to use."
"StreamSets data drift feature gives us an alert upfront so we know that the data can be ingested. Whatever the schema or data type changes, it lands automatically into the data lake without any intervention from us, but then that information is crucial to fix for downstream pipelines, which process the data into models, like Tableau and Power BI models. This is actually very useful for us. We are already seeing benefits. Our pipelines used to break when there were data drift changes, then we needed to spend about a week fixing it. Right now, we are saving one to two weeks. Though, it depends on the complexity of the pipeline, we are definitely seeing a lot of time being saved."
"I like SharePlex's Compare and Repair tool."
"Because of the volume of the transactions, we heavily use a feature that allows SharePlex to replicate thousands of transactions. It's called PEP, Post Enhancement Performance, and that has helped us scale tremendously."
"There are some capabilities within SharePlex where you can see how the data is migrating and if it still maintains good data integrity. For example, if there are some tables that get out of sync, there are ways to find them and fix the problem on the spot. Since these are very common issues, we can easily fix these types of problems using utilities, like compare and repair. So, if you find something is out of sync, then you can just repair that table. It basically syncs that table from source to target to see if there are any differences. It will then replicate those differences to the target."
"One of the most valuable features is data transformation. We have some legacy systems which are in old technology, like SOAP, whereas the new ones are in REST. So we use BusinessWorks to transform data from one format to another, from SOAP to REST."
"Good TIBCO BusinessWorks features are the admin console and the ability to roll back to the previous version."
"It is a seamless and sophisticated tool."
"The most valuable part of the solution is the ease-of-use and ease of deployment."
"Good performance and reliability."
"Areas for improvement would be the cloud fitness of the product and the ease of migrating to newer versions."
"It is very stable. It is a market leader, and it has connectors to many of the legacy systems. It also has enterprise cloud connectors."
"The most important thing is that it is easy for developers to work with."
"The logging mechanism could be improved. If I am working on a pipeline, then create a job out of it and it is running, it will generate constant logs. So, the logging mechanism could be simplified. Now, it is a bit difficult to understand and filter the logs. It takes some time."
"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."
"We create pipelines or jobs in StreamSets Control Hub. It is a great feature, but if there is a way to have a folder structure or organize the pipelines and jobs in Control Hub, it would be great. I submitted a ticket for this some time back."
"We've seen a couple of cases where it appears to have a memory leak or a similar problem."
"I don't know how easy it would be to change the architecture in an already implemented replication. For example, if we have a certain way of architecting for a particular database migration and want to change that during a period of time, is that an easy or difficult change? There was a need for us to change the architecture in-between the migration, but we didn't do it. We thought, "This is possibly complicated. Let's not change it in the middle because we were approaching our cutover date." That was one thing that we should have checked with support about for training."
"I would like more ability to automate installation and configuration in line with some of the DevOps processes that are more mature in the market. That would be a considerable improvement."
"I would like the solution to have some kind of machine learning and AI capabilities. Often, if we want to improve the performance of posting, we have to bump up a parameter. That means we need to stop the process, come up with a figure that we want to bump the parameter up to, and then start SharePlex. Machine learning and AI capabilities for these kinds of improvement would tremendously help boost productivity for us."
"Cloud fitness is lacking"
"The container-based image is too large and this makes auto-scaling difficult."
"Could be more user friendly in the development area."
"This solution's cloud could be improved. I don't know whether it was because we didn't have the internal expertise or if it was the product itself, but since they came later—I think only two or three years into the cloud—after many other iPaaS that had been in the cloud for longer, I feel that maybe they haven't matured in terms of the cloud."
"The Business Studio tool can be improved, which is the tool for designing the processes. Improving the Business Studio tool will make this solution more stable. It has a steep learning curve, and it is pretty tough to learn."
"Its price can be improved. For medium enterprises, it is a very expensive tool. In the market, you won't get many resources for this solution. You won't find many developers in the market very easily. The latest version of TIBCO (6.4 or 6.x) is not very stable. It has got many issues. We have raised this with TIBCO, and they are taking a lot of time to come up with a fix, which is making us move away from this product. Some of the performance-tuning aspects are also missing in version 6. They should provide performance-related fixes, which will be helpful for the customers. If you are migrating from the current version to the container-supported version, it is quite expensive. The product has evolved, but it is very pricey. That's one of the challenges. They have provided all the features that are there in other products, but this is a platform upgrade. The platform has completely been changed from 5.x to 6.x, and we can't use the same environment. We can't run both versions on the same server as VM. The development environment is entirely different. In version 5.x, there was a proprietary designer. Now, it has common plug-ins developed on top of Eclipse."
"TIBCO BusinessWorks could be improved with cloud support."
"Scaling with the solution is costly because if we need to scale up, we have to buy more memory. That means more money. Solutions like Camel or Pulsar come with built-in options to scale horizontally, vertically, region-wide or country-wide."
Quest SharePlex is ranked 20th in Data Integration Tools with 3 reviews while TIBCO BusinessWorks is ranked 7th in Data Integration Tools with 10 reviews. Quest SharePlex is rated 9.0, while TIBCO BusinessWorks is rated 8.0. The top reviewer of Quest SharePlex writes "Real-time replication means our data is available almost instantaneously if an issue occurs in one of our data centers". On the other hand, the top reviewer of TIBCO BusinessWorks writes "Useful features, but needs monitoring and cloud improvements". Quest SharePlex is most compared with Oracle GoldenGate, AWS Database Migration Service, HVR Software, Qlik Replicate and SSIS, whereas TIBCO BusinessWorks is most compared with Mule Anypoint Platform, Spring Cloud Data Flow, Boomi AtomSphere Integration, webMethods Integration Server and Informatica PowerCenter. See our Quest SharePlex vs. TIBCO BusinessWorks report.
See our list of best Data Integration Tools vendors and best Cloud Data Integration vendors.
We monitor all Data Integration Tools 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.
