SnapLogic Reviews

The solution is great due to the fact that it is really flexible. You can follow the snaps, these connectors which you can use to connect to any system. You get the flexibility to write a custom JavaScript or Python script if you need to.

The initial setup is very straightforward.

The deployment is very fast and the solution is extremely easy to configure.

The stability has been very good so far.

The API monitoring could still be improved upon. 

The dashboards regarding scheduled tasks need further improvement.

It's not user-friendly. If you want to find out which task was executed, you have no good dashboards for monitoring. There are no user-friendly charts where you can check which API was called, and how many times or if there was a peak of requests to a certain API.

I've been using the solution for about two years at this point. It's been a while. 

We've been quite happy with the stability. There are no bugs or glitches. It doesn't crash or freeze. The performance is reliable. 

The solution scales well. A company shouldn't have any issues if they need to expand. You can simply add more servers and one SnapLock acts like your workspace. You can plug in your own notes on your own workstation. You can also create additional snap clicks.

Therefore, you get physical scalability in terms of being able to add more servers, however, you can also create different snap clicks, different workspaces, which will ensure your logical scalability. Even if you kept to one organization, you can still have multiple workspaces, one for development and others for UAT or for production. They would all be under that one organization's umbrella.

Everything seems easy and simple in terms of the initial setup. You're accessing that platform via a browser, therefore, you don't need to set up anything. You can use a predefined environment on the cloud and you can easily install your own ground techs. That means you can install your organization on your server. It's all quite straightforward. It's not particularly difficult or complex.

The deployment is pretty fast and typically takes less than an hour or so.

The solution is worth the cost. It gives very good value.

Comparing it to other solutions, such as Oracle, I would say that SnapLogic is pretty much better than the other platforms that I've used previously.

We are an implementation partner for SnapLogic.

So far, I've been extremely satisfied with the solution. I'd rate it at a nine out of ten, as there is always room for improvement in any product.

• It makes creating complicated integrations that would normally be scripted, easy to digest, design, and understand.

• By using snaps instead of functions in code, you can see the building blocks of the integration visually. This helps a lot.

• It is extremely easy to connect to various business systems and product integrations rapidly.

• It automatically sends contracts from Salesforce to Workday, so there was no need for manual data entry.
• By the end of the year, I had created integrations that saved multiple roles worth of time. This allowed the employees to be effective in other areas.

The product can include more canned integrations that can be used.

In the field of integration apps, I see a spectrum of apps where one side is point-and-click with zero technical ability needed, and the other side is a platform where you basically write code.

SnapLogic sits somewhere in the middle. It doesn’t offer enough easy canned integrations for its users like some of the easier to use integration apps.

I have been using the product for about a year.

There were occasional stability issues with various snaps having bugs. It was rare that anything wasn’t fixed immediately.

Scalability was easy. You simply add more nodes to your account and it can scale as large as it needs to.

The customer success manager I had was one of the best I’ve ever had from any software company. I very highly regard the support I received from SnapLogic.

I did not previously use a different system. I do use a free version of Workato from time to time, due to its cost and ease of point and click integrations.

There was no real initial setup. I went to SnapLogic for a day of training, received credentials, and started.

SnapLogic costs can be largely dependent on the cost of their nodes.

It is a higher initial cost than other easy-to-use integration apps.

If they need to build complex integrations and don’t want to use code, look to SnapLogic.

If you want to build simple integrations and send e-mails, there are probably more affordable options.

We looked at MuleSoft. They are on the more code heavy side, but are probably the best option for a very large enterprise.

Lean on the customer success manager.

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.

By using SnapLogic, you can reduce time to market. This platform can be used not just by developers, but also by business analyst and citizen integrators. You don't have to be too experienced or skilled to use SnapLogic as the solution is a low-code enviornment. Everything depends on your IT proficiency. You can use it on a higher level but it's a useful platform for everyone.

The SnapLogic dashboard is good because it gives you a plethora of information for troubleshooting when there's an issue. By using the dashboard, you can find exactly what the cause of the problem was and simulate easily.

There is room for improvement of API management and the dashboard for task execution. However, they have made some nice improvements in that regard recently.

Allowing external services to connect to API management would be great as well.

I have been using SnapLogic for three years. 

SnapLogic's stability has been OK so far. The solution allows organizations to manage their workloads by using different snaplexes, or by using different nodes for specific processes. You can set number of threads that will be used in same time, and by setting different options you can handle the available resources of the platform.

If you want to guarantee some SLA parameters, you can specify which processes to run on which server. The solution is quite manageable. 

From a performance point of view, you can use different type of snaps (connectors). If you have millions of records, you can use bulk snaps to process millions of records in a few seconds.

SnapLogic is scalable. We have some 50 people using SnapLogic in our organization. 

We have had several tech support tickets with SnapLogic and they're quite responsive. When you send in a ticket, they will react within 24 hours and fix your issue within a few days.

The initial SnapLogic setup is fairly straightforward. You can set it up in less than one hour. Even 30 minutes could be enough to create an on-prem SnapLogic environment.

There are several potential SnapLogic deployment strategies. Which an organization chooses will depend on its resources. You can create different SnapLogic deployments if you want to have logical separation of different projects or different environments, or you can use different organizations within SnapLogic. An organization is a workspace in the SnapLogic world. You can have physical and logical separation of different environments within SnapLogic.

The solution can be deployed and managed by a single administrator in a small or medium-sized company. Up to three administrators are enough for an enterprise company.

I work in a company that provides SnapLogic consultancy services. I deploy SnapLogic for other organizations. 

I would rather not say. 

Before choosing SnapLogic, I used TIBCO,  Oracle Fusion Suite and MuleSoft. But considering the profile of the people who will use the solution, SnapLogic is preferable platform because it can be used by business analysts, citizen integrators, and developers. The other platforms required a certain level of skill to use. SnapLogic, on the other hand, is a low-code environment. 

There are cheaper tools on the market, but when you compare what they offer with what SnapLogic offers, you will find that you may pay a little more for SnapLogic, but you get a lot more in return. At the same time, SnapLogic offers the same capabilities that much more expensive platforms on the market offer. 

My advice to those who want to implement an integration platform to try using the free version of SnapLogic and to check all possibilities that SnapLogic offers. This is the best way to see SnapLogic's benefits. 

On a scale of one to ten, with one being the worst and ten being the best, I would give SnapLogic a nine for overall performance.

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.

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.

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.

An additional feature I'd like to see in SnapLogic is the functionality of building streaming applications, for example the Pub/Sub model. SnapLogic currently supports Kafka and other streaming applications, but there's more focus on building streaming pipelines now, so if that feature is there, it'll be very helpful.

I last worked with SnapLogic six months ago. I was one of the early adopters of SnapLogic when it was introduced, and my previous company started working with the solution in 2017. I used SnapLogic for four and a half years.

SnapLogic is a stable solution. It has become more stable now. There's a learning curve on how you will develop an operational application or how you will develop pipelines there, but once you get used to it because it is not like regular programming, once you get used to building the pipelines, SnapLogic is very stable.

SnapLogic is a scalable solution.

Technical support for SnapLogic has been very good, and on a scale of one to five, I'm giving support four out of five.

The initial setup for SnapLogic was straightforward.

We had a consultant from SnapLogic initially for the implementation because we were the early adapters in 2017, but the solution was quite straightforward to deploy.

I evaluated WSO2.

I have experience in both WSO2 and SnapLogic. I worked as a consultant and my client used SnapLogic for retail.

I utilized hybrid deployment for SnapLogic. The company had Plexus, so for the CloudPlex, SnapLogic provided the managed service and for the GroundPlex, it was deployed in AWS.

In terms of the maintenance of the solution, at one point in time, the company had fifty developers working on SnapLogic, and there was also a citizen initiative where citizen users were created, so there were close to sixty developers. There was an operations team of ten people and out of the ten there were seven engineers, and there was a team leader, and then a manager. The team didn't just handle technical errors, as it also provided functional support for SnapLogic.

I'm rating SnapLogic eight out of ten.

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.

The most valuable features are Big Data, integration, and high volume data transfers.

SnapLogic is an Artificial intelligence-based solution.

SnapLogic is a low-code development tool. 

The amount of coding required is very low and the development time is low when designing the pipelines.

It's a fast learning solution.

With SnapLogic, you can cut down the delivery times and send high volumes.

The stability can be improved.

The problem with Snaplogic is convincing the management. SnapLogic is a technical product, which could be the reason that convincing the management is so difficult.

High-volume integration and the number of dependencies should be lower. 

The EPA requires a lot of customization. Many other solutions are programming-oriented, which require a lot of customization.

The support is the most important improvement they could make. In the next release, I would like better support, more online tutorials, online certification courses, and better marketing to help, geared to large businesses and showing them how this solution can meet their requirements.

Also, more integration would be helpful.

I have been using SnapLogic for two years.

When it comes to stability, we have experienced some issues where it says it is not available.

SnapLogic is scalable. They have the load increase and it is able to spin the resources and get the data done.

We have four users in our organizations using this solution.

We won't get help from technical support. We have local support. You won't get any help from the internet.

You have to dig through and identify the issues.

The support team is not very responsive.

Previously, we were using TIBCO.

The initial setup was easy and it took one to two hours to build and deploy it.

It only takes one engineer to maintain this solution.

I completed the implementation myself.

SnapLogic is not expensive. It's reasonably priced.

When you compare SnapLogic with other solutions it can handle higher volume transactions, two or three gigabytes, and even more than 10 terabytes.

I think the master data management, use-cases, and high-volume data transfers are good. Each product has its own strengths and weaknesses. Solutions such as Mulesoft will focus heavily on the engineering soft bundle.

If SnapLogic meets the needs and requirements of the use cases and the business, then I would recommend this solution to anyone who is interested in using it.

I would rate SnapLogic a seven out of ten.

The connection with SOAP is the best feature.

It is a better solution for file transfer.

It needs some more snaps. I would like to see some of the features be changed in some of the snaps.

I’ve used this for four months.

We had no issues with deployment.

We have not yet contacted technical support.

The initial setup was straightforward.

We are doing very well with it.