We performed a comparison between Hitachi Lumada Data Integration and SnapLogic based on real PeerSpot user reviews.
Find out in this report how the two Data Integration Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Flexible deployment, in any environment, is very important to us. That is the key reason why we ended up with these tools. Because we have a very highly secure environment, we must be able to install it in multiple environments on multiple different servers. The fact that we could use the same tool in all our environments, on-prem and in the cloud, was very important to us."
"This solution allows us to create pipelines using a minimal amount of custom coding."
"Sometimes, it took a whole team about two weeks to get all the data to prepare and present it. After the optimization of the data, it took about one to two hours to do the whole process. Therefore, it has helped a lot when you talk about money, because it doesn't take a whole team to do it, just one person to do one project at a time and run it when you want to run it. So, it has helped a lot on that side."
"We also haven't had to create any custom Java code. Almost everywhere it's SQL, so it's done in the pipeline and the configuration. That means you can offload the work to people who, while they are not less experienced, are less technical when it comes to logic."
"I absolutely love Hitachi. I'm one of the forefront supporters of Hitachi for my firm. It's so easy to integrate within our environments. In terms of being able to quickly build ETL jobs, transform, and then automate them, it's really easy to integrate throughout for data analytics."
"We're using the PDI and the repository function, and they give us the ability to easily generate reporting and output, and to access data. We also like the ability to schedule."
"We can schedule job execution in the BA Server, which is the front-end product we're using right now. That scheduling interface is nice."
"One of the most valuable features is the ability to create many API integrations. I'm always working with advertising agents and using Facebook and Instagram to do campaigns. We use Pentaho to get the results from these campaigns and to create dashboards to analyze the results."
"What I found most valuable in SnapLogic is the ETL feature, particularly the Transform Snap Pack, for example, any kind of reading or writing on Transform Snaps. Other than that, all the third-party connectivity tools such as the SAP Snap Pack, Salesforce Snap Pack, Workday Snap Pack, even the ServiceNow Snap Pack, I find all those are pretty useful in SnapLogic."
"The API architecture makes it easy for orchestration."
"The feature I found most valuable in SnapLogic is low-code development. Low-code development has been very useful for simple processes, which is required for business users such as extracting details from a file or getting things reported by calling your web service. Calling your web service also becomes easier with SnapLogic because of the snaps available, so if you have the documentation, you can call an API. You don't have to write all those clients to call an API, so that is another feature I found very easy in SnapLogic. Configuring and managing all the file systems also become very handy with the solution."
"They are very good at building out new aspects according to customer requirements."
"SnapLogic is a great platform for establishing integrations among various systems or patterns by using any kind of interface. If something is not supported by predefined snaps – snaps are connectors in SnapLogic – you can create them (custom snaps) or write a script."
"The solutions ability to connect "snaps" or components to the graphic user interface is very intuitive, prevents errors, and makes implementations easy."
"I found SnapLogic valuable and what I found most valuable about it was its ETL feature. I also found its automation feature valuable. It can be used for automating manual activities. It can be used as a middleware for certain transactional data processing and minimal datasets and ETL activities."
"The initial setup is very straightforward."
"Lumada could have more native connectors with other vendors, such as Google BigQuery, Microsoft OneDrive, Jira systems, and Facebook or Instagram. We would like to gather data from modern platforms using Lumada, which is a better approach. As a comparison, if you open Power BI to retrieve data, then you can get data from many vendors with cloud-native connectors, such as Azure, AWS, Google BigQuery, and Athena Redshift. Lumada should have more native connectors to help us and facilitate our job in gathering information from these new modern infrastructures and tools."
"A big problem after deploying something that we do in Lumada is with Git. You get a binary file to do a code review. So, if you need to do a review, you have to take pictures of the screen to show each step. That is the biggest bug if you are using Git."
"The testing and quality could really improve. Every time that there is a major release, we are very nervous about what is going to get broken. We have had a lot of experience with that, as even the latest one was broken. Some basic things get broken. That doesn't look good for Hitachi at all. If there is one place I would advise them to spend some money and do some effort, it is with the quality. It is not that hard to start putting in some unit tests so basic things don't get broken when they do a new release. That just looks horrible, especially for an organization like Hitachi."
"In terms of the flexibility to deploy in any environment, such as on-premise or in the cloud, we can do the cloud deployment only through virtual machines. We might also be able to work on different environments through Docker or Kubernetes, but we don't have an Azure app or an AWS app for easy deployment to the cloud. We can only do it through virtual machines, which is a problem, but we can manage it. We also work with Databricks because it works with Spark. We can work with clustered servers, and we can easily do the deployment in the cloud. With a right-click, we can deploy Databricks through the app on AWS or Azure cloud."
"Since Hitachi took over, I don't feel that the documentation is as good within the solution. It used to have very good help built right in."
"Parallel execution could be better in Pentaho. It's very simple but I don't think it works well."
"The support for the Enterprise Edition is okay, but what they have done in the last three or four years is move more and more things to that edition. The result is that they are breaking the Community Edition. That's what our impression is."
"Although it is a low-code solution with a graphical interface, often the error messages that you get are of the type that a developer would be happy with. You get a big stack of red text and Java errors displayed on the screen, and less technical people can get intimidated by that. It can be a bit intimidating to get a wall of red error messages displayed. Other graphical tools that are focused at the power user level provide a much more user-friendly experience in dealing with your exceptions and guiding the user into where they've made the mistake."
"We'd like there to be more ways for users to get more comfortable and have more experience with the solution to make it easier to use."
"One area for improvement in SnapLogic is the transparency in the flow of data. It needs to have more transparency. Right now, users only have a preview option at the end of any job flow, so at the end of any Snap Pack, there is a data preview option that lets you review the data and see how it's moving. What would make the solution better is more debugging and more access to change data from the preview panel or more functionality in terms of the preview option."
"One of the areas for improvement in SnapLogic is that the connectors for some of the applications should be more available in terms of testing in the dev environment. Another area for improvement is that the logging should be standardized, for example, the integration with an ELK stack should be required out-of-the-box, so you can ship the log and have it in the ELK stack. There should be integration with ELK stack for the log shipping."
"There is room for improvement with APM management and how task execution looks."
"I am looking for more scheduling options. When it comes to scheduling, there are different tools in the market."
"The dashboards regarding scheduled tasks need further improvement."
"Ultra Pipelines provides real-time ingestion but it needs some adjustment."
"What could be improved in SnapLogic is that it was not capable in terms of processing a large number of datasets, but at that point, SnapLogic was evolving. It didn't give a lot of Snaps. I heard recently there are a lot of Snaps getting added and the solution was being enhanced, particularly to connect different data sources. When I was working with SnapLogic six months to one year back, I faced the issue of it not being capable of handling a huge volume of datasets or didn't have much of Snaps, and that was the drawback. If there is any large number of data sets, that's based on or depends on your configuration. If it is a huge volume of data, other traditional ETL tools such as Informatica and Talend can process millions and billions of records, while in SnapLogic, the Snaplex fails or it returns an error in terms of processing that huge volume of data. Informatica, Talend, or any other ETL tool can run for hours in terms of jobs, while SnapLogic jobs fail when the threshold is reached. SnapLogic isn't able to withstand processing, but I don't know if that's still an issue at present, because the solution is getting enhanced and it's been more than six months to one year since I last worked with SnapLogic. There are now a lot of Snaps getting added to the solution, and if it can overcome the limitations I mentioned, SnapLogic could be the go-to tool because currently, it's not being used as much in organizations. It's being used comparatively less compared to other retail tools."
More Hitachi Lumada Data Integration Pricing and Cost Advice →
Hitachi Lumada Data Integration is ranked 6th in Data Integration Tools with 24 reviews while SnapLogic is ranked 5th in Integration Platform as a Service (iPaaS) with 11 reviews. Hitachi Lumada Data Integration is rated 7.8, while SnapLogic is rated 8.2. The top reviewer of Hitachi Lumada Data Integration writes "Saves time and makes it easy for our mixed-skilled team to support the product, but more guidance and better error messages are required in the UI". On the other hand, the top reviewer of SnapLogic writes "Automates manual activities and has helpful documentation that allows users to self-study". Hitachi Lumada Data Integration is most compared with SSIS, Talend Open Studio, Informatica Enterprise Data Catalog, Azure Data Factory and SAP Data Services, whereas SnapLogic is most compared with Matillion ETL, AWS Glue, Azure Data Factory and SSIS. See our Hitachi Lumada Data Integration vs. SnapLogic report.
See our list of best Data Integration Tools 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.
