Share your experience using DBSync Cloud Workflow

My main use case for SnapLogic is migrations from Boomi and other SQL databases to SnapLogic. Regarding the SQL database, I'm not going to disclose the customer name, but I can give you some highlights. It was financial data for a Fintech organization. They wanted to move from their PNL and GL data. All these migrations and the benefits data, which they have to send to the third-party system, moved from another iPaaS system to SnapLogic because of delays and latency, which was the biggest issue for them. So, we built up plenty of data lakes and migrated the data back to SnapLogic.

Similarly, for the SQL database, it wasn't only the latency, but they were also facing issues where people were unnecessarily writing a lot of triggers. They didn't think that was the correct way because there was no alignment or streamlining in terms of process design or the reusable storage of technical resources. They wanted to identify and streamline the entire process, as well as build some kind of reusable process. I have also found that SnapLogic, or perhaps Boomi or MuleSoft, whatever the customer is going to choose, has some kind of edge in terms of processing data quickly and with a reduced amount of latency. I don't know what changes they are going to do with the help of agent AI, all the pipelines, and DataBricks, and all these things, and how they are going to put the data in perspective within the application. That is the use case I can tell you.

The best features SnapLogic offers include the different integration patterns you can quickly adapt. Manipulation is easy with the data. When I'm saying easy, I mean that there are a lot of ways to get different data sources into one place, and then you can do a lot of customization. It is easy as well. For a person who doesn't have that kind of exposure, they can quickly adapt. There is no space to say, 'I don't know this system.' If your basics are clear, then you can quickly adapt. So, it is a quick adoption from SnapLogic's side. The second thing is that the kind of features they are providing for the different integration patterns is really unique.

You can build a lot of quick JMS connections. There are inbuilt connections for the likes of SuccessFactors, Salesforce, and Oracle where you can get the data from the ERPs. Then you can do the data manipulation and map the data to the destination system, and send the data to SFTP, to an S3 bucket, or via the API. You can build the API as well within that suite, and then manipulate the data over there. Accordingly, you can utilize the RBAC system in a better manner.

SnapLogic is coming with a lower latency rate when it comes to a huge number of pipelines and the huge terabytes of data they need to read and then they need to write. Especially if they can look towards Apache Iceberg or DataBricks or anything Spark, in terms of how these systems handle the kind of data they are going to send. So there is a quick turnaround to processing the data for any of the downstream systems.

I believe that SnapLogic impacts the organizations I work with as a contractor. It is really useful for them, especially for new use cases that are quickly adapted with a quick turnaround. It is very useful in terms of testing and realization. Especially when there are unique features in SnapLogic, the entire chain and transport management system for sending the whole config from development to quality and from quality to production is really fantastic. This gives a different kind of aspect to the customer as well, to quickly make changes in development with a quick turnaround. In no time, they can send the data from dev to production.

The latency is the biggest issue across iPaaS. That is the important part. I have worked not only with SnapLogic, but also with MuleSoft, Dell Boomi, and Jitterbit. They are all fine, but they have different kinds of functionality. They all have similar kinds of problems in different domains. But as I mentioned, SnapLogic has a little bit of an edge because of its functionality and inbuilt functions for Fintech, as compared to the others. This I can say firmly.

They need to assess themselves. In this day and age, as I mentioned earlier, terabytes of data need to be read and then have a quick turnaround for downstream systems, especially for GenAI or any LLMs. Then they can definitely improve themselves because right now, most things, in fact, the GenAI, ChatGPT, Cloud, Anthropic, and so many others, require data quality with perfection and more precision. But for all of that, we require a data pipeline that can be read without latency and without any delay, for any reason. So if they can improvise that over the cloud, that would be really fantastic and a really good achievement for them. Not only for them, but for the customer as well. Then no matter what, people cannot leave SnapLogic. They need to be there with the snaps.

I don't know much about that. I haven't referred to the documentation that much. But support is something that is pretty obviously required, rather than just providing videos. Technical support is required. The roadmap also needs to be very clearly mentioned and specified. Be specific in which domain they are going to do what, if they are coming out with that roadmap. Otherwise, overall, if they are going to improve their entire system as I mentioned earlier, for the reusability concept and the data pipeline concept, then they will definitely do some magic in the future.

From the HR point of view, or for HR tech, improvement is required. A couple of connectors are not working with all the relevant APIs, and there is always a restriction in terms of fetching the data. So that is why I chose six. From the Fintech point of view, if you are asking on a scale of one to 10, then I would give it an eight out of 10. It is a huge one. There is always a margin for improvement, so that is why I chose eight. If you talk about HR, sales, or any other domain, there is a significant amount of improvement required.

I have been working in my current field for close to 18 years.

SnapLogic's scalability is huge. There is a huge amount of scalability. That is why I put it on the scale of six. There is an area for improvement. Once that area of improvement is already done, or about to be completed, then it will definitely be a nine out of 10.

Customer support for SnapLogic is neither bad nor good. It is okay, normal. Sometimes it is very good, sometimes there is no response.

Neutral

I did a lot with Boomi. I love Boomi a lot, along with SnapLogic. Where we switched to SnapLogic, it wasn't from Boomi. The customer chose SnapLogic over the traditional way of working, such as a SQL database, Oracle database, or some other iPaaS solution, which was not Boomi. They switched because the traditional solutions did not fit their commitment or approach to making an ecosystem out of the cloud. That is why they switched to SnapLogic. Everywhere I have worked where SnapLogic is used, they were all in Fintech. Fintech has huge, secured, and very cumbersome numeric logic. They don't have a huge population within the organization, but they require very complex calculations which they would to complete easily. This allows them to connect with it over many years. So if they would want to switch from or to SnapLogic, they need the entire ecosystem as it is: process optimization, approach, documentation, etc. That is why they chose SnapLogic.

I have evaluated other options. Honestly speaking, I gave the suggestion for both Boomi and MuleSoft.

I am a contractor, so I can work. I know this. I did not work with a partner, reseller, or any kind of relationship for anyone.

Time was definitely saved with SnapLogic. Money, I don't know. I'm not part of the pricing and setup, so I can't say. I can't comment on that. It is not that fewer employees were needed, but time was definitely saved, and our process was optimized with the help of SnapLogic. That I can say for sure.

Before using SnapLogic, I had a different opinion.

I would rate SnapLogic a six on a scale of one to ten.

I don't really remember if you are talking about metrics, but I can give you one example where we built around eighty odd interfaces out of three hundred interfaces that needed to be migrated from Oracle. It worked really well. It was fantastic in terms of processing, latency, data manipulation, and the downstream system. For one interface, we had to send it to more than thirty places in different time zones with different scheduling. We heavily customized those interfaces, and it really works well.

I would tell others looking into using SnapLogic to use it. Take it, use it, and use it. You can't go beyond SnapLogic. SnapLogic is not going to give you any kind of bad experience, definitely. Because any solution that has a huge amount of scalability, there is a probability that a solution SnapLogic is not going to feel uncomfortable for any customer expectations.

Good luck. Do great things and have great achievements. I would love to see and then move myself also onto SnapLogic's new roadmaps. You will definitely do some wonders with SnapLogic.

My usual use case for Catalyst by Zoho involves a recent client from approximately two months prior who operates a business related to kiosks in the US. They ran a proper management system for those kiosks inside Zoho Creator through a custom application. They wanted a solution for their internal users and technicians to guide them to their kiosks with a map view similar to Google Maps but with their company's specific functionalities. This includes markets, zones, and all kiosks assigned to technicians. Multiple technicians can run their own check-ins and integrate AI to check if there are any faults with any kiosk.

I created two applications inside Catalyst, and both work within the same creator. One application is fully integrated with AI and allows technicians to open the camera and point it towards the kiosk. The system guides them with directions such as move left, move right, and move forward or backward, taking a picture automatically from the perfect angle. It processes the image and provides results indicating if anything is wrong with the kiosk, then submits that data into the company database for an AI summary and a proper overview of all kiosks in the zone.

The second application is the map application, which we call Pathfinder, and it is fully integrated with Google APIs for navigation and Maps API. It shows the technicians a complete map based on their login, detecting which user is logged in and displaying their market. They can choose kiosks to check in, and the application will guide them by drawing a path similar to how Google Maps navigates. Once they reach the kiosk, the second application triggers and opens the camera for submitting all the AI checks.

I find the features and capabilities of Catalyst by Zoho to be valuable, especially regarding its backend and frontend. When creating widgets inside CRM, Creator, and other areas, they usually lack backends, meaning they cannot be directly integrated with third-party applications such as AI or Google services. Therefore, deploying a website in Catalyst is a significant feature for web applications, alongside serverless functions and database schemas, which are also valuable features.

I utilize Catalyst by Zoho's Function as a Service extensively, relying on serverless functions which serve as the backend. I mostly employ them instead of the frontend, making frequent use of Advanced IO, Basic IO, and Cron jobs. Unlike Deluge in Zoho, which only supports execution up to five minutes, the functions can execute for longer periods and include delays for handling API limits, allowing for better file management and decoding.

The integration capabilities of Catalyst by Zoho with other Zoho and third-party applications are somewhat limited. Unlike other Zoho applications, Catalyst lacks built-in connections, as seen in the last update, which provides them only for specific applications. Users cannot build connections with most applications as in Zoho Flow, CRM, or Creator. Instead, authentication via tokens and API usage is required. Even with the tokens, I consider it the best tool available for integration.

I believe the areas of Catalyst by Zoho that could be improved in the future include Python support. Currently, it only supports an outdated Python version. Python 3.15 is current, but the only available version is 3.9, limiting the ability to install many libraries and deploy applications effectively.

Regarding improvements for data encryption and identity management, when building an application inside Catalyst and later integrating it with other applications, I find that it does not work well with other Zoho applications, even though they share the same organization. They do not have the same origin, and facing CORS errors while embedding them is a significant issue. The need for authenticating iframes back and forth is not ideal, making the experience less favorable.

In terms of data storage options in Catalyst by Zoho, I have not used it extensively. I have primarily utilized it for processing tokens and caching, and to that extent, I perceive it as good. However, I believe if we were entirely dependent on it, the performance might not be satisfactory.

For the stability and reliability of Catalyst by Zoho, I would rate it around eight.

I would assess Catalyst by Zoho's scalability at seven. The last update introduced improvements, but there is still plenty of room for enhancements, and although GitHub integration has been added, existing features still require improvement.

I usually participate in the initial setup and deployment of Catalyst by Zoho, and I almost handle everything involved in the process.

My usual setup process for Catalyst by Zoho involves my clients who mostly have Zoho One. For those with a completely custom idea in mind, I suggest using Catalyst by Zoho since many are not aware of it. With Zoho One, you can create a Catalyst by Zoho account without additional costs, and it integrates well with Zoho One. So far, all the functions and applications I have deployed in Catalyst by Zoho have never required extra data usage payments or credits, making the initial setup straightforward. I use the terminal for running the applications.

Regarding the pricing and licensing of Catalyst by Zoho, I understand that if you have Zoho One, your charges depend on your usage and how many credits you purchase. However, I am not aware of the specific licensing details for Catalyst by Zoho.

I have used the data encryption and identity management features of Catalyst by Zoho for authentication, but my experience has not been very satisfactory as it lacks robustness.

Initially, I build the function locally before deploying it inside Catalyst by Zoho, indicating that my customers prefer it deployed on the cloud.

While I express some complaints about certain features not working as they should, I would say generally it is reliable. If I encounter an error, I can always visit Catalyst by Zoho and understand that it will function properly. I give this product an overall rating of nine.