Amazon Redshift is very fast, has a very good response time, and is very user-friendly. The initial setup is very straightforward. This solution can merge and integrate well with many different databases. It scales very easily and has a good cost-benefit ratio. It is very powerful and performs well. The data processing is very fast and can do analytics on the fly.
Amazon Redshift should have more cloud-native tools that integrate with it as Microsoft does with the Azure ecosystem. There is some missing functionality that can make Redshift difficult to work in. If you are analyzing a lot of data, the load performance-wise can be very low.
Microsoft Azure Synapse Analytics can handle large amounts of data - in the petabyte range. You can scale up and down as much as you want. It has a pay-as-you-go protocol, so you only pay for what you use. The speed is very good and the architecture is excellent. You are in control of what you need, which is a huge advantage.
Microsoft Azure Synapse Analytics can be a very complicated product to use. The setup can be very complex. We had some issues with dashboard reporting - we found there were bugs in the platform when dealing with specific types of queries. This solution did not meet the necessary security protocols for some of our clients.
Conclusion
Both of these solutions are very stable, scalable, and flexible. Each of these products has their own unique ecosystems that are very competitive with each other, making them both great solutions to use. Although they are very similar, there are some features and functionalities that make them unique and attractive depending on the type of enterprise you operate. We are a smaller enterprise and overall our team felt based on ease of use, support, and where we are headed, we have started to migrate everything over to an AWS ecosystem and chose Amazon Redshift. It is the solution our clients liked best as well.
Hello peers,
I am a BA at a medium-sized tech services company. I am currently researching ETL tools.
Which solution do you prefer: KNIME, Azure Synapse Analytics, or Azure Data Factory? Can you please provide a comparison between these three solutions?
Thank you for your help.
A couple of questions before starting the feature comparison: i. Are you fine with an open-source solution? ii. Any specific reason you have listed ADF? iii. Who will be using these tools and how much learning curve is involved within the team? iv. What kind of data you are dealing with? v. Is data privacy an important factor? vi. Are you looking for only a cloud-based solution or open to a hybrid solution also? vii. What is the maturity level of the team when it comes to working on the cloud ........ These are just a few of the many questions basis which we do self-assessment or measure our preparedness. Let me know if you need more insights. Happy to help!!
Sr. Architect - Data warehousing & BI at Molina Healthcare, Inc.
Apr 27, 2023
I believe Synapse is not an ETL tool. ADF is one optional ETL tool for a Synapse Data warehouse.. What Are the Top ETL Tools for Azure Data Warehouse? | Integrate.ioI'd like to step back and pose a bigger option. You see, ETL means making a copy of data you have already. Have you considered a data fabric or mesh, where the data is used where it lies now? Consider this if your data is already used by some systems, but you need to do a more comprehensive analysis of it.I always want to reduce the replication of databases. The concept of build yet another database to "replace" all the others rarely works out that way. I'd rather beef up the origination system, or use a replica than build a huge portfolio of ETL programs and an army of ops, data governance, and system support to keep them in sync. Finally, if you really need an ETL tool, i.e. copies of all that data... look for existing talent in your staff. Otherwise, expect to hire some people experienced with the new tool that can advise on design and development and mentor existing staff.
Hello peers,
I am a Software Engineer Trainee for a large media company.
I am currently researching the migration process between Netezza and AWS Redshift. Can you please provide some information, links, or research papers about this migration?
Thank you for your help.
Amazon Redshift is very fast, has a very good response time, and is very user-friendly. The initial setup is very straightforward. This solution can merge and integrate well with many different databases. It scales very easily and has a good cost-benefit ratio. It is very powerful and performs well. The data processing is very fast and can do analytics on the fly.
Amazon Redshift should have more cloud-native tools that integrate with it as Microsoft does with the Azure ecosystem. There is some missing functionality that can make Redshift difficult to work in. If you are analyzing a lot of data, the load performance-wise can be very low.
Microsoft Azure Synapse Analytics can handle large amounts of data - in the petabyte range. You can scale up and down as much as you want. It has a pay-as-you-go protocol, so you only pay for what you use. The speed is very good and the architecture is excellent. You are in control of what you need, which is a huge advantage.
Microsoft Azure Synapse Analytics can be a very complicated product to use. The setup can be very complex. We had some issues with dashboard reporting - we found there were bugs in the platform when dealing with specific types of queries. This solution did not meet the necessary security protocols for some of our clients.
Conclusion
Both of these solutions are very stable, scalable, and flexible. Each of these products has their own unique ecosystems that are very competitive with each other, making them both great solutions to use. Although they are very similar, there are some features and functionalities that make them unique and attractive depending on the type of enterprise you operate. We are a smaller enterprise and overall our team felt based on ease of use, support, and where we are headed, we have started to migrate everything over to an AWS ecosystem and chose Amazon Redshift. It is the solution our clients liked best as well.