SnapLogic Reviews

I utilize SnapLogic for data migration and data integration projects. I use it mainly as a middleware tool, working with a lot of SAP data. By transferring SAP data into more cost-effective databases, I can run analytics without the high cost associated with SAP provider analytics.

I find SnapLogic to be user-friendly, especially for beginners with limited experience in data engineering or ETL. The interface is interactive, allowing me to quickly learn how to run pipelines and achieve production-ready results swiftly. This agility translates to cost savings, especially for smaller projects and proofs of concept, as less time and effort are needed to deliver results.

I mainly use it for data integration and some API tasks.

I find the reusability and the snaps to be very valuable features. There are quite a lot of snaps that are pre-delivered and available for use. The level of control in terms of the granularity of process control is quite good. 

I also like the whole child-parent pipeline feature; it allows me to break up a process into smaller pieces and then have one big pipeline that controls these smaller pipelines.

In our company, we used the solution to build a SnapLogic pipeline in a non-production environment. Presently, our company is releasing it to the production environment. We have used SnapLogic in our organization for integrations. An EDI pipeline is built first, and then SnapLogic is utilized to convert EDI format to JSON and vice versa.  

Leveraging the internal systems in our company we are connecting to the SnapLogic API and sending the data, and then the converted files are obtained from SnapLogic.

The biggest issue we have faced in our company with SnapLogic is regarding the EDI format. For instance, suppose if 20 EDIs are shortlisted then SnapLogic will convert and provide only those specific 20 EDIs. If a new version of EDI arrives later or if there is a need to use a different existing EDI version, then you need to get back to SnapLogic and complete the setup before initiating the pipeline. 

SnapLogic is a combination of API management and an ETL tool, like Informatica. You can use it as an ETL tool if you want. You can create your APIs, and manage them. You can keep it as a real-time pipeline. You can have it like a scheduled one. It has many flavors. You can try whatever you want. However, mostly we use it as a real-time scheduler.

It's a not-bad, low-code solution. You can directly pull, drag and drop. Even if you have some coding to be done, you can do it on your own. You can do it in Python. It's more developer-friendly, and development can be done at a very faster phase. Once you develop, on the fly, you can see all the data and how the data is getting transformed, and how data is available. 

It's a very easy-to-use tool. Most importantly, for any new developer, if you want to onboard, it's very easy.

The initial setup is simple. 

The solution has multiple dashboards. 

I work as a solution architect, mainly focusing on integrating new software entities. Due to a client's needs to evaluate products, SnapLogic was considered, and we conducted some Proof of Concepts and suggested its use.

So, our end customer is one of the medical equipment companies. They were looking for an integration solution, so we analyzed their requirements and determined what would best suit their business.

It is used for data integration projects. It is very efficient and quick, especially when compared to MuleSoft, which is a bit slower. SnapLogic had a good UI. The data we were dealing with was not extensive, so SnapLogic works well for our customers now in terms of usability and speed.

SnapLogic has the concept of pipelines, which is beneficial as it does not require much intervention from our end. If there are any minor changes needed, customers simply take a copy of the existing pipeline, customize it, and easily rebuild it. This feature is very useful for our customers.

Not much technical background is needed if we are working with SnapLogic. That is a good thing.

Coming from an integration background, it took me just one and a half months to understand it properly. However, someone new to the industry might need about three to four months to start building programs easily.

It's similar to other tools like Boomi. But, it's a smaller player, not as widely adopted. SnapLogic may be easier to use, with less coding, but I think that more comprehensive solutions will handle a wider range of tasks. I found it difficult to achieve what I needed with SnapLogic.

We used SnapLogic to integrate various systems and some cloud systems, including our main CRM system and Microsoft Dynamics system. There were also HR and other specialized systems involved. Tools like Boomi can do similar things.

I'd install a local Snaplex (the SnapLogic runtime engine) to access local network resources. With cloud-based Snaps, you can talk to cloud or SaaS systems like Dynamics Online or Salesforce.

I used SnapLogic for ETL purposes, particularly for automating manual activities, for example, automating validation reports, checking and generating email, etc.

The business problems solved by SnapLogic involved setting manual work or manual validation that my company runs in the backend database which is connected using Snaps, then the validation is put as a query into these Snaps, which SnapLogic validates. The solution will generate the results, then sends a report to your email ID, so activities that used to be manual are now automated.

My company also used SnapLogic for ETL processing, particularly various inputs, CSV files connected with Redshift, including databases and adjacent files inputs. The solution can do file-level processing, take data from one data source, and put it into the other data source, so small ETL projects.

You can also take advantage of the SnapLogic pipelines. When a pipeline is created, you can get the URLs from that pipeline which can be triggered from AWS Lambda or any other triggering service. A vendor will provide a set of files that need to be processed. It's not a huge file as it's like transactional data that a vendor provides every week, so my company creates a pipeline where the team configures data in Lambda, so whenever a client drops that particular file for processing, the URL gets triggered, and the SnapLogic job will also be triggered. The SnapLogic job will pick the file from AWS from three locations or any source, then it does the transformation and loads it into the Redshift database of my company, and then the data will be used for several downstream and reporting purposes.

ETL is the major purpose for SnapLogic in the company where it does the transformation by fishing data from one source and putting it into the other. Automation is another purpose.

When we get a requirement from the business, we'll get the mapping documents. Based on the mapping documents, we'll map the issues.

Everything is very good.

It's good for mapping for the company.

We have a lot of use cases that we can apply to this solution. 

They are very good at building out new aspects according to customer requirements.