Forum Discussion
Microsoft Fabrics best practice architecture for Datawarehouse
Hi there,
Anyone aware of best practice Microsoft Fabric architecture, specially for datawarehouse experience, covering all best practices for availability, security, governance, connectivity, data flow etc.
Hi mshujaweb ,
Thanks for the reply from vdgarcia .
Here is the architecture diagram about fabric lakehouse and warehouse for your reference:
If you want more detailed information, please refer to the official documentation below:
Lakehouse end-to-end scenario: overview and architecture - Microsoft Fabric | Microsoft Learn
Data warehouse tutorial - introduction - Microsoft Fabric | Microsoft Learn
I found a blog that was helpful in delving into the use cases, differences and architectural design of Lakehouse vs Data Warehouse.
If you have any other questions please feel free to contact me.
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
4 Replies
Hi mshujaweb ,
Here are some summaries of data warehouse availability, security, governance, connectivity, data flow, etc:
- Data storage: store data using Delta-parquet format for ACID transactions and interoperability without multiple copies of data.
- Cross-database querying: use multiple data sources to gain insights quickly without duplicating data.
- Data Connectivity: Connect to a variety of data sources by introducing, loading, and transforming data at scale through pipelines, data streams, cross-database queries, or COPY INTO commands.
- Performance Management: Autonomous workload management using a distributed query processing engine ensures optimal performance.
- Availability: Suitable for users of all skill levels.
- Security: RBAC and the principle of least privilege are implemented to restrict access to sensitive data.
- Data Management: Maintain metadata using a data catalog to ensure data discoverability.
If you have any other questions please feel free to contact me.
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!Thanks Yang for your response and helpful tips on all those points. Are there any architecture diagrams as well, visio or otherwise, that we can refer to, for Microsoft Fabrics ?
Hi mshujaweb ,
Thanks for the reply from vdgarcia .
Here is the architecture diagram about fabric lakehouse and warehouse for your reference:
If you want more detailed information, please refer to the official documentation below:
Lakehouse end-to-end scenario: overview and architecture - Microsoft Fabric | Microsoft Learn
Data warehouse tutorial - introduction - Microsoft Fabric | Microsoft Learn
I found a blog that was helpful in delving into the use cases, differences and architectural design of Lakehouse vs Data Warehouse.
If you have any other questions please feel free to contact me.
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Hi, Yang,
In a scenario like the one at the company where I work, which decides to have an internal development team to use Microsoft Fabric and, through external companies, supply the needs that the internal team does not have the capacity to meet. What would be the best practices to configure a development, quality and production environment with third parties that allows version control and avoids as much as possible the constant re-configuration of connections for each environment?
Thank you very much for your attention.
