SnapLogic

I have been working in the integration space for more than 10 years, starting my career with SnapLogic, which is a good iPaaS tool for integration. Even taking a look at the market caps, SnapLogic is doing very well.

In any organization when an integration requirement comes, whether it is an on-premises to cloud connect, or whether it is any kind of migration or grabbing data from SaaS tools such as Workday, NetSuite or Salesforce, SnapLogic is a best fit in the market. It has lots of pre-built connectors called Snap-packs, which come pre-built with SnapLogic licenses, so you can make use of all those together. This is the main use case that motivates us to use SnapLogic. There are so many features, and from the user perspective, it is very user-friendly. It is a low-code, no-code platform that can be used for any integration use cases.

I recently completed a Workday migration project. Hitachi wanted a Workday system to be a single source of truth across all Hitachi organization and sub-organization. There we got a use case to integrate the Workday system with all the downstream systems, whether it is for HDS or Hitachi Digital Services, Hitachi Vantara or GlobalLogic. SnapLogic was used in that case. There are so many inbound and outbound integrations, and we integrated two or three kinds of authentication to pull out data from Workday and also to send out any kind of inbound data to Workday. This was our main use case and it was a very big project in Hitachi Digital, the Phoenix project, and all those implementations happened on SnapLogic.

I can also mention that we recently built a professional service automation with the help of SnapLogic, which is the integration between Salesforce and Oracle ERP system, Oracle HCM system, which is used for the HR system in GlobalLogic. Lots of insourced data are brought to the Salesforce platform so that they can tag the right resource to the right project and they can also check the utilization. Professional service automation is a kind of automation that will tag the right people at the right skill set on the right project. For all those to achieve, we used SnapLogic to integrate between Salesforce and the Oracle system.

There are so many strengths of SnapLogic. The first one is that it is user-friendly. It is a low-code, no-code platform where you can drag and drop the Snap-packs. SnapLogic's visual drag-and-drop interface makes it very easier for the developers and integration teams to build any kind of pipelines that require very minimal coding.

There is an extensive connection library. SnapLogic's iPaaS platform offers a large collection of pre-built connectors, called Snaps in SnapLogic. This will always simplify integration with cloud applications, whether it is a cloud application or whether you have to connect with any kind of on-premises application or enterprise system. Deployment and development are very fast in SnapLogic compared to traditional coding approaches such as creating APIs via Python and streaming on some other platforms. You can create your pipeline and deploy it with the help of API management, which reduces the time for any developer. It also has strong cloud integration capabilities.

SnapLogic has the Ultra feature and API management as features. Enhanced account encryption is there, where all account credentials are well encrypted at the backend of the platform. SnapLogic has become a valuable component of our integration strategy in the market, in the India region, APAC region or in the US. Monitoring is also very easy with operational visibility provided through central monitoring in the monitor tab of SnapLogic. Maintenance effort is very minimal, and well documentation is provided. You can refer to any of the Snap documentation if you want to see anything.

Earlier, the organization was following a manual approach. Five years back, they were following a manual approach. Once SnapLogic came into place, there are so many characteristics where some individual teams are using Salesforce, Workday, or different enterprise systems. SnapLogic provides a consolidated platform where we can integrate all the data and share it with the team. We have built lots of automations for our current organization, which is reducing very manual effort. Earlier manual effort was more, but now all the things are automated from one system to another system. Anytime, anywhere, anything if any team wants, we can send that data.

Earlier we were having three to four resources in each individual team taking care of these things, but with the help of automation, everything is automated. The platform team is also doing very well, releasing updates every quarter or every month. They recently released version 4.44. So improvement wise, they are doing very well.

They can enhance the error handling and debugging part. Troubleshooting complex pipeline failures can be time-consuming. We are spending a lot of time on error handling. More detailed error messages and root cause analysis tools can be added, which will definitely improve the developer experience.

In the Ultra real-time integrations, we can monitor the last execution history of only 100 runs. That can be increased, which would be one of the platform improvements that can really be taken. However, they are doing very well because lots of ChatGPTs and AI assistants have been added in the last two years, which makes a very good effect.

SnapLogic is the only platform that provides this kind of visibility to the developers. Anyone, even if they have low experience and are starting their IT careers, can directly jump in and learn SnapLogic. The documentation is very easy to learn. Anyone, even a layman, can refer to that documentation and go through its Snap-pack to understand what configuration has to be done to use this Snap-pack. This makes SnapLogic definitely exceptional in the market. You won't find such comprehensive documentation in other iPaaS tools. The draggable packs truly demonstrate its power in usability.

Governance and security are also well in place in SnapLogic, but there are areas for improvement. They can add more granular role and permission controls that provide greater flexibility for large enterprises. For example, if you have to provide access to 70 users in one shot, that can be improved. More improvements in policy enforcement capabilities are possible as well.

SnapLogic can improve the data lineage part to achieve better end-to-end visibility into data movement. Also, during validation, we can only see up to 2,000 records currently. They can increase that from 2,000 to 20,000.

They can put more visibility on costs and resource visibility, with better reporting on platform usage, processing consumption, and cost optimization opportunities.

I have been using SnapLogic for more than 10 years.

SnapLogic is stable.

SnapLogic has many strengths in terms of scalability. It handles growing data volumes and you can process numerous volumes as per business needs. When expenditure expands, such as when the business is expanding and the number of employees increases, there won't be any effect on integration. It supports enterprise-wide integration and has a cloud-native architecture. Everything is on the cloud, and you don't have to worry about platform maintenance. Hybrid and multi-cloud support is there, with many reusable integration assets. The throughput is very high in this platform.

Overall, combining all those things, it ultimately supports business growth. New applications, data sources, and business processes can be added without major architectural changes. If you need to deploy your on-premises application, you can. If you need to use cloud-to-cloud connectivity, you can go to the cloud architecture, but all are in a single place. You just have to log in to elastic.snaplogic.com, and your entire solution is there.

Gyan Solution is the organization that provides customer support. When we create any ticket in Zendesk, they quickly respond. If their development team is needed for some assistance, they coordinate very well from the US to India, because Gyan Solution is in India, Hyderabad, and the complete core development team is in the US.

They are providing the best customer support to the organization and the vendors. Whatever they do, they keep you informed over the ticket in Zendesk every minute. They are also very good in follow-ups; if you are not responding for eight weeks, they will follow up with you, and after your confirmation, they will close the ticket.

I checked Boomi in my free time and in my previous organization. I found it complex to use as an iPaaS platform. Whatever the connectors, there are more than 600 connectors SnapLogic provides, and you won't find such a variety in Boomi and MuleSoft. That was the biggest motivation to switch. The development approach is very easy in SnapLogic. After comparing these platforms, we realized SnapLogic is the right solution for us. In the previous organization, they switched from Boomi to SnapLogic.

I checked Boomi. I don't find that to be a fitting enterprise solution for the market. That's why we opted for SnapLogic. It also has a complete central API management platform, so data integration and API management can both be done in SnapLogic. With one solution, we are achieving two goals.

Earlier there was a manual approach. When we came to the organization, we suggested that this is the platform you can utilize as an integration architect. Looking at the time consumption, we have saved 50 to 70% through the low-code platform. We have created so many reusable components where we don't have to spend the time. We can simply go and use them. The onboarding part is also faster for new applications because there are so many connectors you can use. We don't have to spend time on quicker troubleshooting and centralized monitoring, which reduces issue resolution time. Suppose there was an issue resolution time of 10 hours for the previous manual effort; now it is reduced to one hour or half an hour. The business team can also deliver integration projects in days or weeks instead of months. We have saved manpower, reduced months of effort, and created many reusable components, which definitely leads to cost savings. We see a 60% reduction in integration development time, a 40% faster onboarding process of new applications, and a significant decrease in manual operations through workflow. This is quantified.

We save time because there were so many manual efforts happening. With the introduction of SnapLogic, we have automated all the processes in Hitachi and GlobalLogic. Those kinds of manual efforts and manpower savings have definitely been reduced.

Based on my research and integration career, I have seen many products such as Workday, MuleSoft, and IBM MQ. After analyzing all those and lots of implementations, I found SnapLogic as a very useful and user-friendly integration tool.

In the overall comment in the integration journey, I have worked with many vendors and organizations. SnapLogic has been a valuable integration platform for every organization. It's not only for those who are using it but also for those who are not using it. If they will analyze their infrastructure or system, they will see this is the right platform for integration. It enables faster development, improved automation, and seamless connectivity. It supports on-premises applications, cloud applications, and Salesforce. The low-code, no-code approach, extensive connector options, and AI assistants such as Snap, Iris recommendation, transformation recommendation, and mapper recommendation, all contribute to improving operational efficiency for every organization using it. Those who are not utilizing it definitely need to evaluate, analyze, and compare it with their systems.

DevOps capabilities such as CI/CD implementation, integration with GitHub, GitLab, everything is provided. SnapLogic is a robust, scalable, and user-friendly platform that has helped us to reduce development time, automate many business processes, and support enterprise growth, especially with low-code, no-code capabilities and broader connector options, more than 600. I would rate this platform a 9 out of 10 overall.

SnapLogic is my primary automation and integration platform that I use daily. A specific example of how I use SnapLogic day-to-day involves a number of different syncs, such as having CRM data from Salesforce syncing over to our Zendesk instance for our support teams and similarly, Salesforce going to Marketo for our marketing teams. We have various third-party platforms that we're sending logs to, such as Elastic and Zilla for security and governance, and we have various data transformations, gathering and aggregating data from various systems and then spitting that out to dashboards and Google Sheets or Tableau in various different places.

We have been focusing on AI use cases with SnapLogic lately, specifically on different sales-focused ones like a daily task looking at different Salesforce reports and trying to gather various context from Salesforce and maybe some other different systems to create a full context picture using an LLM to aggregate that, put together a report and send that on to some of our reps for them to action on.

The best features SnapLogic offers are its ease of use, flexibility, and within the interface itself, being able to rearrange the different snaps and easily see the flow of data going through the pipeline. Having the multiple outputs, being able to validate and preview data is extremely helpful in development. It is fairly straightforward and easy to use and can quickly get something up and running, at least for development.

The ease of use in SnapLogic comes from a lot of the pre-built account features, making it easy to use the different snaps for various platforms and getting the authentication portion straightforward. If I am doing a more traditional development thing, getting that authentication piece can be a bit time-consuming, and then being able to share those across multiple pipelines is extremely useful. The layout, as I mentioned, makes it easy to see how data is flowing through the pipelines, which makes it really easy for me to build and if I need to troubleshoot a pipeline someone else built, it is fairly easy to get in there and understand what is going on, even if I have not seen it before.

SnapLogic has positively impacted my organization as it is my primary automation platform and integrations, touching pretty much all of my major systems. It integrates and syncs data between all of my major platforms and has created more of these time-saving automations and the AI-assisted ones, which are bringing quicker calls to action for my teams in critical places. It has been a net positive for my team and the organization.

One thing I do not like about SnapLogic is some of the pre-built snap packs. If I want to integrate with a new system, I have to pay to get access to those. There have been a couple of instances of just different account types that I was not able to get working within SnapLogic and had to use a third party to get that data. Generally having to pay more to get access to the full feature set is a downside.

Regarding SnapLogic's AI capabilities, I find that the AI capabilities for the most part are locked behind pay, and I have not purchased many of them. I do use SnapGPT occasionally and know some other teammates who have recently gotten access and have not used the platform before tried that, but as we reviewed the pipelines that it built, they were not exactly great and we had to go through and fix a lot of things for them. It is nice when I am developing and trying to figure out an expression, as it is generally quite useful, but I cannot really speak much to the security and governance portion of it.

Regarding SnapLogic's AI capabilities, I think its accuracy and reliability of output are quite good with the expressions, but in my limited experience, the pipeline builder portions of it have not been great.

I have been using SnapLogic for roughly two and a half years.

SnapLogic is stable for the most part, although there was a pretty significant outage maybe two to three months ago, but other than that, it generally is.

The scalability of SnapLogic has been great.

I have not really used customer support much.

I was not on the team at the time we switched from Workato, but I know we were drawn to SnapLogic because the feature set and integration capabilities seemed a better fit for the team, and to grow long term.

I have seen a return on investment with SnapLogic. It is integrating all of my major platforms and we have a whole bunch of various automations for all different teams across the organization, and we are seeing a lot of time savings.

My advice to others looking into using SnapLogic is to consider the positive features I have mentioned before, as well as being aware of the downside of having to pay more to unlock more features. I give this review a rating of eight out of ten.

I have been using SnapLogic for 12 years and it continues to run effectively. SnapLogic serves as an integration platform in our IT application team to exchange data from one application to other applications and perform the transformations required if they are ever needed.

We have various types of sources. It can be SaaS applications and on-premise applications. Based upon the business requirements and other factors, we extract data from the various sources, either from the specific Snap Packs or through the REST APIs. Some applications generate files and place them on file servers. We use all methodologies, including SnapLogic Snap Packs, direct connectivity with those sources, or file-based integrations. We also use SnapLogic as an API. With the help of that, we extract all the data from the sources. We perform the business transformations wherever required as per the target system needs or the business requirement needs. Then we connect the target applications, either through dedicated Snap Packs such as Workday, Salesforce, Oracle ERP, SQL Server, any third-party applications, or SaaS applications if we have the Snap Pack. Otherwise, we use SOAP services, REST methods, or API-based integrations to connect the target applications.

We have ample and a variety of use cases. It can be batch-to-batch jobs, integrations, scheduled integrations, API-based integrations, and all these things. Currently, we are assessing SnapLogic API and features so that we can deploy all our existing APIs and build new APIs while having the complete API lifecycle management within our organization. Many of the use cases are API-based, and we need to be more secure about our APIs.

The best feature of SnapLogic is that we can access it through a normal UI with normal internet connections from the default Google Chrome browser. As a developer, the low-code, no-code approach is a very good feature of SnapLogic. Additionally, SnapLogic has enhanced its existing features by providing SnapGPT or suggestions so that any new learner wanting to learn SnapLogic can quickly adopt this new technology and become very advanced in a lesser time.

SnapGPT is a feature we haven't actively used and we don't have that much of an active subscription for it. However, from what I know about SnapGPT, since we enabled it as a trial version after requesting it from our customer success managers, we have seen that it is good for very new learners who want to learn SnapLogic and cross-train in it. When I mention the low-code, no-code aspect, if you are doing any kind of transformations and routing your incoming data or applying filters based upon conditions, we have multiple options. If we have to route data to multiple destinations, we have the router Snap. If we have to apply conditional routing, we have conditional Snap Packs for that. That is why I prefer it as a complete low-code, no-code solution. That is a good advantage of SnapLogic.

Nothing major stands out regarding areas of concern. Since I started using SnapLogic approximately 12 years ago, at that time there were very few features. Nowadays, it keeps enhancing and continuously comes with new features and additional capabilities. That is a very good advantage. I think nowadays if any new learner and training people want to learn SnapLogic, it is very easy to adopt, comparatively to when we started approximately a decade ago.

SnapLogic definitely needs some kinds of improvements as per the current market and current AI world and current technology. At this moment, I can say there is one feedback on how SnapLogic can improve. There is a very small example: in SnapLogic, if we have to whitelist so many IPs, then you have to go one by one and add IPs manually. There should be some kind of a mechanism so that it can take input from any CSV files or something so that it can do bulk uploads. The IP whitelisting is the area that SnapLogic definitely has to improve. It is a bit painful because if you want to whitelist some Salesforce IPs, Salesforce provides complete IP ranges that you have to go through manually. Sometimes if you mistakenly select something, then all your existing IPs that you have added are gone. I have faced this issue personally, so definitely SnapLogic has to improve in that area.

IP whitelisting is currently the top area on my mind for improvement. I don't think of any other areas that need improvement right now.

I have been using SnapLogic for 12 years and it continues to run.

SnapLogic is stable. Sometimes it is unstable, but I must say that is not completely because of SnapLogic. There might be some things that I am not aware of because I am still a learner. Even though I have been working in SnapLogic and managing all the infrastructure and administration for the last 12 years, I can say I am still learning and might be making some mistakes. However, sometimes we see that SnapLogic is unstable during patch releases or Snap Pack releases.

SnapLogic is known for its scalability. If you see the name SnapLogic called Elastic SnapLogic.com, you know what elastic means. That means you can stretch it any way and it works on the Triple-A platform. The Triple-A methodology means anything, anywhere, anytime. That means you can connect any system or application anytime, whether day or night, scheduled or dynamic, and anywhere, whether it is cloud or on-premises.

Customer support is good. Whenever we generate tickets in Zendesk, support engineers are assigned and they get back to us and follow up. However, if there is any kind of support required from the customer success support team, they need to evaluate and check with their internal engineering team, which takes time. Otherwise, I would not say that customer success support is not doing good. They are doing a very good job, and I definitely appreciate that.

I have worked on Informatica and Informatica Cloud, and sometimes I have used MuleSoft. We have also done some POCs with Dell Boomi. Broadly, I haven't extensively used Dell Boomi, as I was doing some POCs, but choosing SnapLogic was not my decision; it was the organization's decision. However, I have some other integration platform experience as well. I have worked on MuleSoft and Informatica and Informatica Cloud. Dell Boomi I have evaluated through POCs. However, we haven't done any full-fledged deliverables on it.

Definitely, there is money and time saved. For example, currently I don't have specific metrics to share. However, if you have seen the return of investment, currently I don't have any detailed information to provide.

The pricing model of SnapLogic is something I have a complete personal opinion about. I feel SnapLogic is very expensive compared to others. When I compare the cost from other applications or competitors, SnapLogic looks like a costly tool. However, it is meeting our requirements. Definitely, on the costing side, it's my personal opinion on what I feel. We have taken this solution, so it appears costly. Even though it is an organizational cost, it does appear that way.

I haven't much used the AI capability of SnapLogic, so I cannot comment on what the pros and cons of these AI capabilities are. However, any product using AI capabilities is using much better methodology and graph technology methodology to reach the actual requirements and concerns from the customer or users and drill down to the actual requirement so that they can give the best possible matching answers to the user.

It is a mixture of everything. We have some integrations running on the completely private cloud and many of the integrations that we have are on-premises. We are using on-premises Groundplex servers also. We are using SnapLogic cloud provider that AWS.

As I mentioned, we evaluated MuleSoft, Dell Boomi, and SnapLogic. On top of that, we recently evaluated one technology called Pentaho for an integration platform. However, we found that SnapLogic is the best option currently on the market, so we have gone with it.

Customer support is good. Whenever we generate tickets in Zendesk, support engineers are assigned and they get back to us and follow up. However, if there is any kind of support required from the customer success support team, they need to evaluate and check with their internal engineering team, which takes time. Otherwise, I would not say that customer success support is not doing good. They are doing a very good job, and I definitely appreciate that.

I would scale things to eight, or between 8 to 8.5, on a scale of 1 to 10. I would definitely say that if they have some kinds of requirements, they should choose SnapLogic because SnapLogic is currently up to date and as per the current IT industry market and other factors, I don't think any other solution or platform is available in the current IT world which can meet customer integration requirements. My overall rating for this product is 9 out of 10.

Our main use case for SnapLogic is building and managing data integration pipelines between different systems, especially for automating API-based workflows. It helps streamline data movement, transformation, and orchestration without heavy manual intervention. For example, in our day-to-day work, we use SnapLogic to integrate data between internal systems and external services. The typical pipeline involves fetching data from an API, transforming it based on the business requirements, and loading it into another system or database. This automation reduces manual effort, ensures consistency, and allows us to handle updates in near real-time.

In addition to core data integration, we use SnapLogic for workflow orchestration and monitoring. It helps manage end-to-end data flows with better visibility, error handling, and retries. We also leverage its reusable pipelines and connectors to standardize integration across teams. This reduces development time and ensures consistency, especially when working with multiple APIs and systems. Overall, it plays a key role in making our process more efficient.

One of the best features SnapLogic offers is the intuitive drag-and-drop interface, which makes it easy to build and manage pipelines without heavy coding. It also allows both technical and non-technical users to quickly create integrations. Another key strength is the wide range of pre-built connectors that help integrate multiple systems, APIs, and databases seamlessly. I also find its scalability and real-time processing capabilities very valuable. It can handle larger volumes of data and supports both batch and real-time integration, which is very important for building reliable and responsive data pipelines.

The drag-and-drop interface has made my work much faster and more efficient by simplifying how pipelines are built and managed instead of writing complex code. I can visually design workflows by connecting different components, which reduces development time and makes the logic easier to understand. It is also very helpful for debugging and maintenance. I can quickly identify whether a pipeline is working or failing, or make changes directly in the flow and test updates without much effort. This visual approach improves productivity and makes it easier to collaborate with team members, especially when explaining or modifying integrations.

SnapLogic offers strong support for automation and scheduling. It allows us to schedule pipelines or trigger them based on events, which is really useful for building fully automated workflows without manual intervention. Another valuable feature is its built-in error handling and retry mechanism. Instead of pipelines failing completely, we can design flows to handle exceptions gracefully, log issues, and retry where needed. This improves reliability in production. The reusability of pipelines and components is a big advantage. We can create modular pipelines and reuse them across multiple use cases. This saves us time and keeps everything consistent and scalable.

The learning curve for advanced use cases with SnapLogic could be improved. While basic pipelines are easy, more complex transformations and debugging can still be a bit challenging. Another improvement would be in error messages and debugging clarity. Sometimes the errors are not very descriptive, which makes troubleshooting take longer than expected. Performance tuning and visibility can be better for large-scale pipelines, as having more granular control and deeper insights into execution performance would really help.

One improvement would be version control and collaboration. While SnapLogic supports reuse, tighter integration with better change tracking would make team collaboration smoother, especially in larger environments.

I have been using SnapLogic for around six months to one year as part of my integration and automation work.

SnapLogic is very stable in my experience.

The scalability of SnapLogic is very good, especially since we are deploying this in a hybrid cloud. The Groundplex nodes are performing very well, and we are connecting to the API through our local SnapLogic portal. Overall, when it comes to scalability, SnapLogic performs very well.

I raised a couple of tickets with SnapLogic's customer support. We faced some technical challenges, but the experience went very well. I can rate SnapLogic customer support nine out of ten because they are very interactive and helpful.

SnapLogic is our first solution for this purpose.

We have seen the return on investment with SnapLogic. The time savings and the productivity of the engineers across our team have improved. It improved our productivity by fifteen percent and shifted work from IT to business users. In terms of cost savings, it has also reduced costs by seventy to eighty percent. The case studies indicate that we are achieving a good percentage of ROI.

SnapLogic follows a subscription-based pricing model, which is quite flexible but can feel premium depending on the scale. Pricing is usually tiered and customized based on factors such as the number of systems, data volume, and features required, so it is not always straightforward upfront. In terms of setup cost, it is relatively low compared to traditional on-premises tools. Since it is cloud-oriented, it does not require heavy infrastructure investment. This makes initial onboarding faster and more cost-efficient.

I recommend that instead of going to the Groundplex node, teams use SnapLogic for SaaS-based solutions because running the Groundplex node creates additional operational overhead for the team. To go better and smoother, it would be very good if teams use SaaS that has strong resilience compared to hosting it on-premises. Overall, SnapLogic is a very good tool. From the practical standpoint, it delivers integration quickly, reduces manual work, lowers dependency on multiple tools, and improves team productivity. It has helped us to move faster. I would rate this product an eight out of ten.

I connect system to system, and sometimes I do applications to applications as well. When required, I build some APIs in SnapLogic and expose them to customers.

From a general automation perspective, when a business wants to automate a particular use case, it can be anything. For example, tickets are getting created in ServiceNow where I need to automate the ticket creation with the information I receive back to Jira or something similar. I connect with systems such as ServiceNow and Jira and automatically create an automation workflow that connects these two systems to make the process automated, which saves manual effort.

I work on many use cases across different domains, such as HR, sales, and many other domains. I use SnapLogic in the regular way, as it needs to be used.

From an impact perspective, SnapLogic really helps me as a middleware level platform. It helps me to automate many integration workflows. As for improvements, the monitor that I currently use sometimes gets stuck and I am not able to expand and view the child pipelines in a much easier way. On the monitor part, I can do some fine-tuning, which would help the developer, citizen integrator, or any support person easily monitor the pipelines and easily access the pipeline logs. That would be very beneficial. There are also many other areas that I can work on where I see that these areas would be beneficial for a larger group and I can try to implement those points.

I cannot share the exact numbers or percentage, but I can say that SnapLogic has really helped my team in saving time because due to this automation, I do not need to do the manual activity. The person's effort is saved, the time is saved, and many other things are improved. Due to this automation, I see better results compared to the manual ones because the logic I have added to the automation is more specific and more static. Sometimes when I do it manually, I might end up making some small errors, but as I have built it as an automation workflow, there will not be any minor issues. This is considerably a good time-saving solution.

The best feature is that it is easy to use because it provides a UI level and drag and drop options, which are simply easy for anybody to kickstart and use much easier compared to some complicated ones.

Another valuable feature is that SnapLogic has been providing more connectors, which means more Snaps when compared to the past. This gives developers or citizen integrators the ability to connect various new systems or applications as well.

For new users who have started to explore SnapLogic, they can simply understand from the name what each Snap does. For example, file reader and file writer make it clear what the exact functionality will be. The catalog provides easy drag and drop and connect capabilities. The AI assistant helps me with some examples referring to what the next Snap I can use will be. This kind of additional feature benefits the new users who are going to use SnapLogic for the first time. This adds ease to their experience.

I use many features and I feel they are good. SnapLogic is compatible in many areas and provides better features when compared to other integration tools.

One area would be improving the monitor. Another few things I would mention is that I would like better logs to debug in case of any issues, other than just understanding from the pipeline statistics level. I would appreciate some additional logs where on a need basis, I can enable the slots and the traces will be available at the server level so that I can capture the end-to-end what is happening, such as request, response, and things. This feature would be really helpful at the time of critical P1 issues, which I can use.

As I mentioned earlier, with few corrections in the monitor and logging and few other areas that I correct and improve, SnapLogic will be much more scalable than others. This is the reason I have given this rating.

I have been using SnapLogic for around 7.5 years.

For reusable ones, I am building some pipelines where I am actually using the reusability concepts. Performance-wise, it is completely based on the server setup that I have. This is something based on the business use case or based on the business I will be thinking it and putting up the server capacity. Performance-wise, I do not see any issue.

I have been using SnapLogic from the beginning.

I would say time saved.

As of now, nothing.

I would suggest that if someone is looking for data integration, application integration, and API building in one tool, then SnapLogic is one of the options which they can give a try.