IT Analyst. at a tech services company with 1,001-5,000 employees
MSP
Top 5
Low-code and makes configuring and managing all file systems handy; has snaps that allow users to call the web service easily
Pros and Cons
  • "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."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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.

Buyer's Guide
SnapLogic
April 2024
Learn what your peers think about SnapLogic. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
769,662 professionals have used our research since 2012.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

SnapLogic is a scalable solution.

How are customer service and support?

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

How was the initial setup?

The initial setup for SnapLogic was straightforward.

What about the implementation team?

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.

Which other solutions did I evaluate?

I evaluated WSO2.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
it_user656295 - PeerSpot reviewer
Business Systems & Operations Manager at a manufacturing company with 11-50 employees
Vendor
You can see the building blocks of the integration visually.
Pros and Cons
  • "By using snaps instead of functions in code, you can see the building blocks of the integration visually. This helps a lot."
  • "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."

What is most valuable?

  • 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.

How has it helped my organization?

  • 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.

What needs improvement?

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.

For how long have I used the solution?

I have been using the product for about a year.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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

What other advice do I have?

Lean on the customer success manager.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Evan Hovorka - PeerSpot reviewer
Evan HovorkaDirector - Digital Media and Data Products at a retailer with 10,001+ employees
Real User

I agree, the visual component helps in building work flow but really shines when transitioning ownership to other people (cross training). The picture provides built in documentation of what is intended.

Buyer's Guide
SnapLogic
April 2024
Learn what your peers think about SnapLogic. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
769,662 professionals have used our research since 2012.
Architect at VTR
Reseller
Top 20
Offers good UI, efficient and quick when it comes to integration and does not require much intervention from our end
Pros and Cons
  • "Despite having no prior experience in SnapLogic, we managed to build, test, and prepare it for release in just three hours, handling heavy data efficiently."
  • "The problem is that SnapLogic doesn't offer a wide variety of connectors. For example, integrating with Salesforce is not that easy."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

The best thing about SnapLogic is the connectors it offers and the support it provides to deal with the records. One use case involved fetching data from SAP ERP and sending it to Terradata. This process was a bit tricky with MuleSoft, but with SnapLogic, it was crisp and quick.  

Despite having no prior experience in SnapLogic, we managed to build, test, and prepare it for release in just three hours, handling heavy data efficiently.

It's for CSV transformation, which is comma-separated transformations.

What needs improvement?

The problem is that SnapLogic doesn't offer a wide variety of connectors. For example, integrating with Salesforce is not that easy, unlike with MuleSoft, which is much easier and also provides a development kit allowing developers to customize or create their own connectors. But SnapLogic lacks this feature.

So, it's not easily customizable.

For very complex integrations, like those involving 10 input systems and 20 output systems with a variety of data transformations, I wouldn't recommend SnapLogic. You will feel lost somewhere.

When dealing with such complex integrations, you often encounter issues managing large datasets. SnapLogic recommends breaking the process into smaller pieces and then deploying them, but sometimes, our requirements are different and require handling multiple systems simultaneously.

In future releases, I would like to see better customization. Currently, we have certain connectors, and if we need to build on top of those— tailor them more closely to our business needs—then customization becomes necessary. But here, that process is a bit tricky. I want it to be simpler.

For how long have I used the solution?

I have been using it for two years. 

What do I think about the stability of the solution?

I would rate the stability nine out of ten.

What do I think about the scalability of the solution?

It is a scalable product. I could easily manage it. So, I would rate it a nine out of ten.

We had enterprise businesses for SnapLogic. 

How are customer service and support?

Some of my queries took some time to resolve, meaning we had to wait longer to get those answers.

How would you rate customer service and support?

Positive

How was the initial setup?

I would rate my experience with the initial setup an eight out of ten, with ten being easy. It is not a ten because when someone is trying to develop it, it takes time to understand their own specific keywords. They're not very standard. Initially, it takes time to set it up, but once it's set up, it runs very smoothly.

I did it on a hybrid environment where the customer used their AWS.

The deployment part is very easy. I would rate it a nine point five out of ten, with ten being easy. It just takes minutes.

You just need to create the pipelines. You can have the same pipelines in different environments. You just change the environment, and it quickly takes the values and processes them. There's not much else to do.

What's my experience with pricing, setup cost, and licensing?

I just evaluated the free version. Since SnapLogic started incorporating AI, particularly the AI version they're promoting, the price has gone up and is on the higher side. Although not much has changed, the cost has increased. However, when comparing it with solutions like Apigee or MuleSoft, it still offers better value.

So, it's still considered affordable.

What other advice do I have?

I would recommend using it. Just understand the requirement. If you need to develop something quickly and it's not too complex, then definitely opt for SnapLogic.

Overall, I would rate the solution a nine out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer:
Flag as inappropriate
PeerSpot user
PeerSpot user
Technical Architect at a tech services company with 10,001+ employees
Real User
Low-code, high-volume data transfer that cuts down the delivery time, but the support team is not responsive
Pros and Cons
  • "SnapLogice is a low-code development tool."
  • "The support is the most important improvement they could make."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using SnapLogic for two years.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

Previously, we were using TIBCO.

How was the initial setup?

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.

What about the implementation team?

I completed the implementation myself.

What's my experience with pricing, setup cost, and licensing?

SnapLogic is not expensive. It's reasonably priced.

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Associate Software Engineer at a tech services company with 11-50 employees
Real User
The connection with SOAP is the best feature. It needs some more snaps.
Pros and Cons
  • "The connection with SOAP is the best feature."
  • "It needs some more snaps. I would like to see some of the features be changed in some of the snaps."

What is most valuable?

The connection with SOAP is the best feature.

How has it helped my organization?

It is a better solution for file transfer.

What needs improvement?

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

For how long have I used the solution?

I’ve used this for four months.

What was my experience with deployment of the solution?

We had no issues with deployment.

How is customer service and technical support?

We have not yet contacted technical support.

How was the initial setup?

The initial setup was straightforward.

What other advice do I have?

We are doing very well with it.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free SnapLogic Report and get advice and tips from experienced pros sharing their opinions.
Updated: April 2024
Buyer's Guide
Download our free SnapLogic Report and get advice and tips from experienced pros sharing their opinions.