Microsoft Fabric: A Comprehensive Data Management Solution Microsoft Fabric presents a unified, robust platform designed to optimize data management, enhance AI model development, and empower users across an organization. It focuses on integrating data seamlessly, ensuring governance and security, and providing AI capabilities. Microsoft Fabric is presented as an all-encompassing data management solution, providing organizations with tools for efficient data integration,…
N/A
Amazon Redshift
Score 8.7 out of 10
N/A
Amazon Redshift is a hosted data warehouse solution, from Amazon Web Services.
$0.24
per GB per month
Pricing
Microsoft Fabric
Amazon Redshift
Editions & Modules
No answers on this topic
Redshift Managed Storage
$0.24
per GB per month
Current Generation
$0.25 - $13.04
per hour
Previous Generation
$0.25 - $4.08
per hour
Redshift Spectrum
$5.00
per terabyte of data scanned
Offerings
Pricing Offerings
Microsoft Fabric
Amazon Redshift
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Use Microsoft Fabric by purchasing Fabric Capacity, a billing unit that enables each Fabric experience. Pay for every data tool in one transparent, simplified pricing model and save time for other business needs.
Fabric Capacity is priced uniquely across regions.
I would highly recommend Microsoft Fabric, especially for medium to large enterprises aiming to build a robust, scalable, and secure data analytics platform. It effectively unifies various data workloads, streamlining data integration, engineering, and particularly enhancing our ability to create and share reliable Power BI dashboards. The deep integration with Azure AD for features like Row-Level Security is a significant advantage for data governance.
If the number of connections is expected to be low, but the amounts of data are large or projected to grow it is a good solutions especially if there is previous exposure to PostgreSQL. Speaking of Postgres, Redshift is based on several versions old releases of PostgreSQL so the developers would not be able to take advantage of some of the newer SQL language features. The queries need some fine-tuning still, indexing is not provided, but playing with sorting keys becomes necessary. Lastly, there is no notion of the Primary Key in Redshift so the business must be prepared to explain why duplication occurred (must be vigilant for)
[Amazon] Redshift has Distribution Keys. If you correctly define them on your tables, it improves Query performance. For instance, we can define Mapping/Meta-data tables with Distribution-All Key, so that it gets replicated across all the nodes, for fast joins and fast query results.
[Amazon] Redshift has Sort Keys. If you correctly define them on your tables along with above Distribution Keys, it further improves your Query performance. It also has Composite Sort Keys and Interleaved Sort Keys, to support various use cases
[Amazon] Redshift is forked out of PostgreSQL DB, and then AWS added "MPP" (Massively Parallel Processing) and "Column Oriented" concepts to it, to make it a powerful data store.
[Amazon] Redshift has "Analyze" operation that could be performed on tables, which will update the stats of the table in leader node. This is sort of a ledger about which data is stored in which node and which partition with in a node. Up to date stats improves Query performance.
We've experienced some problems with hanging queries on Redshift Spectrum/external tables. We've had to roll back to and old version of Redshift while we wait for AWS to provide a patch.
Redshift's dialect is most similar to that of PostgreSQL 8. It lacks many modern features and data types.
Constraints are not enforced. We must rely on other means to verify the integrity of transformed tables.
I've rated Microsoft Fabric's overall usability as a 4, primarily due to its extensive and multifaceted feature set, which can make it challenging to navigate and determine the optimal functionality for a given task.While the breadth of capabilities is a core strength for large enterprises, it often leads to a sense of being "lost" or overwhelmed for teams like ours that do not have highly formalized roles or dedicated specialists for each Fabric "experience" (e.g., Data Engineering, Data Warehousing, Data Science).
Just very happy with the product, it fits our needs perfectly. Amazon pioneered the cloud and we have had a positive experience using RedShift. Really cool to be able to see your data housed and to be able to query and perform administrative tasks with ease.
The support was great and helped us in a timely fashion. We did use a lot of online forums as well, but the official documentation was an ongoing one, and it did take more time for us to look through it. We would have probably chosen a competitor product had it not been for the great support
Microsoft Fabric integrates data ingestion, engineering, warehousing, and Power BI visualization into one cohesive environment. This "one-stop shop" approach dramatically reduces complexity, minimizes operational overhead, and eliminates the need to integrate disparate tools and manage data across multiple systems. It provides superior scalability for large datasets, supports open data formats, and offers a much broader suite of data engineering and data science capabilities.In essence, Fabric's integrated ecosystem and streamlined operational management were key differentiators, providing a more cohesive, scalable, and efficient solution for our evolving data strategy than combining specialized tools.
Than Vertica: Redshift is cheaper and AWS integrated (which was a plus because the whole company was on AWS). Than BigQuery: Redshift has a standard SQL interface, though recently I heard good things about BigQuery and would try it out again. Than Hive: Hive is great if you are in the PB+ range, but latencies tend to be much slower than Redshift and it is not suited for ad-hoc applications.
Redshift is relatively cheaper tool but since the pricing is dynamic, there is always a risk of exceeding the cost. Since most of our team is using it as self serve and there is no continuous tracking by a dedicated team, it really needs time & effort on analyst's side to know how much it is going to cost.
Our company is moving to the AWS infrastructure, and in this context moving the warehouse environments to Redshift sounds logical regardless of the cost.
Development organizations have to operate in the Dev/Ops mode where they build and support their apps at the same time.
Hard to estimate the overall ROI of moving to Redshift from my position. However, running Redshift seems to be inexpensive compared to all the licensing and hardware costs we had on our RDBMS platform before Redshift.
