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

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.

My major use case for SnapLogic is for ETL. It's for data migration purposes. For example, I've used it to move data from SAP systems, across SAP systems, or across Salesforce systems. I've also used SnapLogic to integrate data from Workday or from some downstream enterprise specific applications to Workday.

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

SnapLogic and Pentaho are tools I use collaboratively for data integration. I have good experience with Pentaho and SnapLogic for data migration from one database to another database.

The main use cases of the tool are for data integration and migration from databases.

In most of the use cases, my company uses SnapLogic for the migration of flat files to S3 and other databases. If my company gets flat files, like CSV, PostgreSQL, and XML files, from our clients, what we do is based on some of the business logic and the implementation they send to us. For my company to apply some business logic and implement it on top of the flat files, we will transfer the file using transform logic, after which we will migrate the data into the database, like Oracle or PostgreSQL.

It's useful to move data from one environment to another one, for example, from one database to another one. I can also change data types, delete some dates, update data, and clean data, for example. So it's really useful for us.

We are based in Mexico and our primary use case of SnapLogic is for ETL work. We transfer data from one point to another and depending on requirements, we modify for better results and then report to our clients. We have two types of layers; regular raw ingestion and transformation. We have our own homegrown ETL process where we do a lot of our ingestion process. We use both solutions depending on what is required. SnapLogic is our main solution. I'm a developer and we are customers of SnapLogic.

We are using it for ETL and application integration.

I was utilizing Azure Data Lake block storage as a data lake, and I was performing numerous source extractions from various sources and transferring them to the data lake.

Our company is a partner and uses the solution as our main tool for client integrations. 

The solution works for any sized company to integrate HR, financial, and operational processes that sync data between databases for ETO transformations. 

The solution is effective at syncing data between different sources and targets including Snowflake and other data warehouse systems.

We also use the solution to build many asynchronous and synchronous APIs that serve as the backend for systems and are easy to maintain. 

We primarily use the solution for integrating different applications. It's very flexible and we can use it as either a database or just a set of cloud-based applications.

We use SnapLogic to connect APIs for effectively transferring and integrating data across multiple systems.

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 use SnapLogic to develop internal proof of concept solutions that we later offer to the clients. SnapLogic is a great platform for establishing integrations among various systems or platforms 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. So far, I have not experienced an issue with SnapLogic that was not resolved.

SnapLogic was used for building simple pipelines to call REST API, to get details from a file and call REST API and post those details. It was also used while working with expense solutions for finance posting and other complex solutions.

It's primarily for cloud-to-cloud application integrations.

We are moving the data in Redshift that is from Amazon. 

Our primary use case is for data integration, data applications, and data migrations from SAP data to data in Amazon Redshift.