We performed a comparison between Amazon Redshift and SnapLogic based on real PeerSpot user reviews.
Find out what your peers are saying about Snowflake Computing, Microsoft, Amazon Web Services (AWS) and others in Cloud Data Warehouse."Redshift has an advantage when it comes to administration, making it easier to manage and collaborate."
"I find the most valuable features to be the MPP style of processing, which mostly all of the data warehouses provide. The ability to integrate all other AWS services, such as NSS and S3, with little effort is very helpful. The service is well maintained, there are update patches frequently."
"Has a very user-friendly SQL editor and it's very easy to use the connectors."
"I like the cost-benefit ratio, meaning that it is as easy to use as it is powerful and well-performing."
"Easy to build out our snowflake design and load data."
"The most valuable feature is its scalability."
"The initial setup of this solution is straightforward."
"The product offers good support for the data lake."
"The connection with SOAP is the best feature."
"The product is easy to use and has many connectivity options."
"By using snaps instead of functions in code, you can see the building blocks of the integration visually. This helps a lot."
"SnapLogice is a low-code development tool."
"It is a scalable solution."
"It is a stable solution."
"It's more developer-friendly, and development can be done at a faster phase."
"SnapLogic is a great platform for establishing integrations among various systems or patterns 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."
"Running parallel queries results in poor performance and this needs to be improved."
"It lacks a few features which can be very useful, such as stored procedures"
"I would like to improve the pricing and the simplicity of using this solution."
"In our experiments, the handling of unstructured data was not very smooth."
"We are using third-party tools to integrate Amazon Redshift, they should create their own interface on their own for it to be easily connected on the AWS itself."
"It takes a lot of time to ingest and update the data."
"The OLAP slide and dice features need to be improved."
"There are physically too many pipelines for a company of this size to maintain. For a data scientist, it's very difficult to learn the data in all of these different environments."
"The solution isn't ideal for complex processing or logic. We use another solution for that."
"SnapLogic should have some inbuilt protocol mechanism in order to speed up."
"I don't think the support has better knowledge about technologies and tool support. There were lots of times when we had an issue, and it took me quite a long time to explain the problem. I feel like some of the support staff don't know their product well."
"We'd like zero downtime in the future."
"One area for improvement in SnapLogic is the transparency in the flow of data. It needs to have more transparency. Right now, users only have a preview option at the end of any job flow, so at the end of any Snap Pack, there is a data preview option that lets you review the data and see how it's moving. What would make the solution better is more debugging and more access to change data from the preview panel or more functionality in terms of the preview option."
"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 would like to see more performance-related dashboards, ones that display the cost of a pipeline, for instance. Also, it would be helpful to have management dashboards for overseeing pipelines and connections."
"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."
Amazon Redshift is ranked 4th in Cloud Data Warehouse with 58 reviews while SnapLogic is ranked 6th in Integration Platform as a Service (iPaaS) with 20 reviews. Amazon Redshift is rated 7.8, while SnapLogic is rated 8.0. The top reviewer of Amazon Redshift writes "Provides one place where we can store data, and allows us to easily connect to other services with AWS". On the other hand, the top reviewer of SnapLogic writes "Easy to set up, easy to use, and is low-code". Amazon Redshift is most compared with AWS Lake Formation, Snowflake, Teradata, Vertica and Microsoft Azure Synapse Analytics, whereas SnapLogic is most compared with AWS Glue, Azure Data Factory, IBM InfoSphere DataStage, Informatica Cloud Data Integration and SSIS.
We monitor all Cloud Data Warehouse reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
Snaplogic
I've found Matillion to be very intuitive and easy to use...
I wish I could answer that question, but my expertise is limited to SSIS only.
As far as I know 'talend' could be a better choice compare to the other tools.
you can address your question to our SAP department solutions@jet-bi.com
Informatica is the way forward
it depends on the infrastructure you are using and what's the total cost of ownership being authorized for the implementation. You can see the "Data Integration" partners within AWS-Redshift in the below link-
aws.amazon.com
Informatica undoubtedly is one of the best in the list. It's a great ETL tool but surely expensive in License.
Microsoft's SSIS is a light weight tool but not as robust as Informatica. Certain other software's like Talend and Matillion are also good. Talend has an open source option where developers can build their own APIs and then productionize those APIs and that's cost effective as well.
Traditionally SQL is a plus, automation is only by a ETL is smarter.
Any ETL tool that moves data to it's own server for processing will add overhead and will not use Redshift's power ( more specifically parallelism). It is recommended to use standard SQL for data processing.