SnapLogic Reviews

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.

SnapLogic is very user-friendly. There's not a lot of code, it's mainly snaps. It also gives you the opportunity to use other languages, such as Python, and to easily connect to other systems. If there isn't a snap that fits your needs, you can always use snaps that let you code pretty much any language you need. One of the cool things is that SnapLogic tries to stay up to date on all of the new snaps and all of the new logics available. We're able to manage a large amount of data through SnapLogic.

Ultra Pipelines is great in terms of real-time ingestion and real-time jobs but it needs some adjustment. Also, you get the application and enough sources but they don't really ask the correct questions on how to handle the resources and provide the correct information to our team in order to avoid any system problems. We've been seeing some latencies now and then due to the nodes that we currently have available, and due to the lack of knowledge on our SnapLogic Pipelines. In addition, there are snaps we don't need but that affect the latency of the work and I'd like to see some training videos so our developers can have the best practices on how SnapLogic should be used. 

I've been using this solution for three years. 

The stability isn't too bad. We've had some issues with the escalation process, but not something that's affected our work. There seem to be some things that need to happen through the whole process, and it might require getting together with the SnapLogic developers to get a complete understanding of what we might be doing incorrectly, or gaining sufficient knowledge so that we can make sure we follow each step accurately. 

Some of the jobs that we had scheduled were killed and we weren't really able to see what they were or to notify the team that managed those SnapLogic Pipelines. We needed to ensure they were properly run, or executed in the correct format after we had implemented the upgrade. It was a misunderstanding of how the process works. 

Scaling took us a little extra time. We worked through it but we needed to get a better understanding of what we were doing as a team in terms of the configuration and the setup and that took some time. 

Customer support is very helpful and they respond quickly. 

Positive

I wasn't fully involved in the setup. We have it in the cloud, installed on AWS and we have it installed on GCP. My team says that the initial setup is pretty easy and there is good documentation available. Deployment takes a couple of hours because we do some testing. Upgrading takes a couple of minutes and there's no problem when that happens, we're not even aware of it.

It's important to test everything you're doing and ask any and all questions so that you're fully prepared for any issues that might arise during installation or testing.

I rate this solution eight out of 10. 

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. 

I have been using SnapLogic for a year. 

I would rate the performance of the solution as two out of ten. 

Our company hasn't yet deployed the solution at the production end, so there are no active users. Due to its poor performance, our company is concerned about SnapLogic's scalability. Our organization adopted the solution's normal pipeline instead of the Ultra pipeline; the scalability of the normal pipeline is quite low. I would rate the solution's scalability as two out of ten.

When communicating about the issues with the support team, they recommend using the Ultra pipeline, but it's too late for our company now, they should have suggested it earlier. I would rate customer support a two out of ten. 

Negative

In our organization, we had an internal EDI platform developed using MapForce, but there were some drawbacks, so we shifted to SnapLogic. Before shifting to SnapLogic, our company also tried to use Jitterbit, but it wasn't suitable for us. 

After setting up the pipeline for SnapLogic in our company, we found multiple bugs when the conversion process was initiated. The deployment process of the solution was complex.

One of the partners of SnapLogic was assigned to our company to assist in setting up the conversion pipelines; we did not have a good experience with the partners, and they were not friendly or gracious. SnapLogic recommends that a third party assist with the deployment. In our organization, the entire deployment process, including the pipeline building, took more than a year. The vendor handles the maintenance of the solution. 

From the ROI perspective, the price is extremely high. I would rate the pricing as one out of ten. 

Presently, in our company, we are building an internal EDI conversion tool, we are planning to switch from SnapLogic to this internal product. 

In our company, we use the cloud version of SnapLogic as a SaaS platform, and additionally, Microsoft Azure is used as the cloud provider. 

If the EDI conversion pipelines had been built properly, we could have implemented the solution in three months. Our company had to wait a year for the product setup to be completed. Based on my experience, I would not recommend SnapLogic to others. I would overall rate SnapLogic as two out of ten. 

We are using it for ETL and application integration.

The simplicity of the tool and the wide availability of connectors or snaps are most valuable to me. The API architecture makes it easy for orchestration.

I am looking for more scheduling options. When it comes to scheduling, there are different tools in the market. 

I have been working with SnapLogic for the past four years.

I have found SnapLogic to be stable.

I have found SnapLogic to be scalable.

Technical support is very responsive and great.

I worked with Informatica. The cost with SnapLogic is better. With Informatica, I have to get the application integration as a separate license, but with SnapLogic I can get it all in one place for one price.

When it is a marketplace, it is seamless, but when it is on our own infrastructure, it involves the launching of the node configurations. If it is a general installation, I do not think it is complex.

The pricing is better than Informatica and the license is renewed on an annual basis. The price depends on the volume of the data and the infrastructure you are choosing.

I would rate SnapLogic a nine out of ten.

• Fast deployment
• Very flexible integration capabilities
• An important tool for building prototypes and MVPs than can seamlessly turn into production jobs
• Easy automation of interdependent data workflows

• My teams can connect to new partners and data sources in hours, not days.
• We complete more work and integrate faster, allowing us to prove ROI quicker on new ideas.
• Provides independence from other support teams, where my work may not be a priority.
• Has created a tool to answer “what if” questions quickly.
• Faster design of new products.

Connecting to data behind enterprise firewalls has been tricky, but for reasons that SnapLogic cannot always control.

I have used SnapLogic for three years.

We have had above 99% uptime over the three year span.

There have been no scalability issues.

Support is A+. The support has been a key reason why we continue to use SnapLogic.

We have several internal tools to accomplish what SnapLogic provides. They range in maturity and usefulness, but ultimately they all have trouble with one piece of the puzzle. In terms of connecting to our many third-parties, for example, SnapLogic was the most flexible and provides the fastest path to production.

The setup is seamless. It just involves a few phone calls and some training. The interface can take a few hours to get comfortable with. While the GUI looks simple, proactive technical problem solvers are needed to really shine.

They have pricing/usage tiers that are easy to move up or down. Forecasting use was not something I spent time on.

I evaluated MuleSoft, Informatica, and internally built tools.

If you have real issues to solve, simply get started. The time to observe SnapLogic’s ability to solve your problems will be equal or less than doing traditional vendor vetting/investigations.

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.

The client has seen great benefits from this particular project and its use of the SnapLogic tool, which they plan to continue to use for the next two years. They are pleased with the subscription and the associated cost.

SnapLogic is an IPA tool that leverages a low code environment to connect to multiple sources, extract data, and store it in Azure data lake. SnapLogic is a low-code, low-investment solution that required me to design best practices and orchestration rules for multiple data pipelines.

SnapLogic should have some inbuilt protocol mechanism in order to speed up.

Each snap is expensive if requested on a one-off basis; however, it may be wiser not to opt for a review unless absolutely necessary. In such cases, there is no need to pay for the review.

I have been using the solution for three and a half years.

The SnapLogic platform has very little downtime. I have only encountered one technical issue with the solution's environment that took 24 hours to resolve. Since I am a developer, the support system was slower than the production one from the SnapLogic side, as it is hosted on the SnapLogic cloud. Otherwise, I have not encountered any issues.

The client initially purchases a certain amount of load, as with any AWS or cloud service. When demand increases, elasticity can be added by making an additional payment. The solution is scalable.

The initial setup is a five out of ten, so if the staging layer, target, and permissions are all in place when we begin work on a project, then it should take no more than two weeks to deploy.

The implementation is completed in-house.

We employed the incremental model of development, starting with the bare minimum load and system requirements. As the project progressed, we increased the bandwidth accordingly. When the further expansion was needed, we provided the client with a valid case study to justify the increased request. We further discussed what additional elements would be added and how they would affect the bandwidth. By scaling the solution incrementally the cost is controlled and more beneficial to the client.

I give the solution a seven out of ten.

The SnapLogic platform is enhanced by the use of a snap called Map or snap, which is believed to be powered by IRIS Intelligence. Understanding how these snap works are essential for mastering the SnapLogic platform.

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. 

The solution has solved many problems for our customers and has improved their operations. 

For one use case, a Canadian company deploys the solution to provide APIs for their web publications. 

For another use case, a UK company deploys the solution to provide synchronous integration between Salesforce and their own legacy on-premises systems to ensure there are no gaps in data.

For a third use case, a large cable operator in the US uses the solution to easily migrate data warehousing from Redshift to Snowflake.  

The solutions ability to connect "snaps" or components to the graphic user interface is very intuitive, prevents errors, and makes implementations easy. 

The patterns, API management, and account encryption are really good when building a flow for integration. 

The dashboard is a great feature that highlights any real-time errors or activity and includes three months of statistics. 

The solution could improve its API management. 

I am a certified architect who has been using the solution for five years. 

The solution is really stable with no issues. 

We used to have issues with releases in the last three years all releases have been stable and free of errors. 

The solution is elastic and scalable by asking for more resources in the cloud or enhancing ground resources to make them more powerful. 

Support was not very good in the beginning but has improved over time as support staff has become more experienced. I am satisfied with the answers I get from support. 

There is some room for improvement but overall support is medium. 

I rate support an eight out of ten. 

Positive

The initial setup is really simple compared to other tools and technologies. It takes about ten minutes to complete automatic migrations. There is also an option to utilize other tools such as GitHub to directly sync code between environments. 

There are multiple deployment choices that are based on the data and endpoints. 

The full cloud option is maintained by the solution with execution machines that sit in the cloud and require no maintenance. 

If you want to maintain the execution machines and call notes, you have the option to use the solution on-premises behind your firewall. 

The hybrid architecture is a combination of the cloud and on-premises deployment options. 

Our company implements the solution for customers. 

The solution itself is reliable so success depends on developers building and properly testing their projects. 

Projects that are built correctly require little maintenance and manage themselves or require one person at most. Extremely complex projects might require management by one to five people. 

None of our clients have moved away from the solution so the ROI must be good. Some clients have been using the solution for eight years. 

The solution has made building and deploying much simpler than MuleSoft and is a better option for moving large amounts of data. 

MuleSoft is faster for building APIs which is its main function.  

The solution used to be CTO based but now has a wider field of implementation so there is no limitation to how or where you can use it.

The solution is suitable for any kind of organization. Before implementing, ask an experienced consultant about the solution's benefits and how it might be a good fit to your architecture and needs. 

I rate the solution a nine out of ten. 

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.

Creation of re-usabe components,ease of use and hybrid integration (Groundplex and Cloud) makes Snaplogic a better player in the market. 

We're able to use the solution as a hybrid deployment. It's one of the solution's main advantages. You can also have multiple applications connected.

We can integrate multiple solutions, including Jira.

We have a semantic layer and are able to pull all the data from different applications using APIs.

The solution is easy to implement and easy to use. It's basically just drag and drop.

The user interface is very simple. It's easy for anyone to pick up and adopt.

The solution isn't ideal for complex processing or logic. We use another solution for that.

I'm not sure if this solution can integrate with Docker, but if it can't they should work to make this possible as Docker makes it easy to get huge amounts of data and has very good policies.

I've been using the solution for six months.

The stability of the solution is very good. It's why we are using it. We haven't experienced any bugs or glitches that would make us concerned that the solution isn't stable.

The scalability is good, but it's much more scalable on the cloud. It's plug and play and is usable as soon as we move and upload our data. It may take a bit of configuration, but it's definitely scalable with a few easy adjustments.

We've never contacted technical support. Our company is able to manage issues internally and has team members that troubleshoot problems.

We do also use Informatica, and if we need to do complex processing or logic, including machine logic, we use that instead of SnapLogic. Combining these two tools creates quite an advantage for us. SnapLogic has a lot of reusable components in the pipeline and integrating the two together makes for a quite scalable solution.

The initial setup of the solution is very easy. We didn't find any complexities.

We have CSV leaders and have continuous integration for continuous deployment. We put all of our pipelines into the central system and go into production.

The time it takes to deploy the solution depends on the company. The volume of data, latency, or other factors will dictate the amount of time it will take.

We have our own in-house team that handles the implementation.

We use the solution on a daily basis.

I'd advise other companies that if it's combined with other tools it will make for a very strong solution.

I'd recommend the product. We already have clients on it and many of our team members have tested it.

I'd rate the solution six out of ten overall, simply because, as a solution, it's still growing. It's not mature yet. If it had simpler logic processing, I'd probably bump it up to an eight. It's easy to use, scalable and reusable and it's overall a great product.

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

The product is easy to use and has many connectivity options.

They should expand in terms of features for SaaS-based market requirements in different sectors similar to Dell Bumi, AbLogic, Azure, Google, Oracle, etc. There could be more AI capabilities included in the product.

I haven't come across any downtime issues.

The product is scalable as per customers' infrastructure requirements.

The user interface is friendly for initial setup. It is a low-code and very intuitive platform.

The license model is based on consumption. They charge for the number of connectors.

I rate SnapLogic a six out of ten. If you have a cloud-based business requirement, you should go for it. But, if your business requires multiple integration tooling, look for other options.