Forum Discussion
Post ProdigyWhich possible Fabric architectures
Hi,
I'd like to know which possible architectures it is possible to implement with Fabric, apart from the medaillon architecture.
Thanks
Hi pmscorca ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.
The Lambda Architecture integrates both batch and real-time data processing, and Microsoft Fabric facilitates this through pipelines, notebooks, warehouses, Real-Time Analytics (KQL), and event streams. A practical example of this approach is the implementation of a greenfield lakehouse in Microsoft Fabric, as outlined in the Azure Architecture Center. This resource includes an overview and an architecture diagram that illustrates the data flow and key components.
This example showcases a greenfield approach to building a scalable data platform using Microsoft Fabric and the lakehouse design paradigm. Fabric seamlessly integrates data storage, processing, and analytics, enabling the creation of a future-proof and efficient data ecosystem from the ground up.You may find the following documentation helpful. Please take a look:
Lakehouse end-to-end scenario: overview and architecture - Microsoft Fabric | Microsoft Learn
Greenfield lakehouse on Microsoft Fabric - Azure Architecture Center | Microsoft LearnThank you and Regards,
Menaka
6 Replies
- andrewsommer
Super User
Fabric is a rather versatile set of tools so there are many different ways you could structure your data architecture.
A traditional data warehouse (Kimbal) set up is easily achievable using the warehouse with star schema and sql endpoints.
Data mesh for a more decentralized architecture. Use the Lakehouse and domains to establish ownership and governance and implement one lake for distributed storage. Then direct lake mode in PBI for domain-oriented consumption.
You could do a Lamda architecture; for your batch layer you have pipelines, notebooks and warehouses. For your speed layer you have real-time analytics (KQL) and event streams. Last, PBI direct lake, KQL queries for your serving layer.
Please mark this post as solution if it helps you. Appreciate Kudos.
pmscorcaOk, but it could be useful to have the reference schema or diagram for each possible architecture.
v-menakakotaCommunity Support
Hi pmscorca ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.
The Lambda Architecture integrates both batch and real-time data processing, and Microsoft Fabric facilitates this through pipelines, notebooks, warehouses, Real-Time Analytics (KQL), and event streams. A practical example of this approach is the implementation of a greenfield lakehouse in Microsoft Fabric, as outlined in the Azure Architecture Center. This resource includes an overview and an architecture diagram that illustrates the data flow and key components.
This example showcases a greenfield approach to building a scalable data platform using Microsoft Fabric and the lakehouse design paradigm. Fabric seamlessly integrates data storage, processing, and analytics, enabling the creation of a future-proof and efficient data ecosystem from the ground up.You may find the following documentation helpful. Please take a look:
Lakehouse end-to-end scenario: overview and architecture - Microsoft Fabric | Microsoft Learn
Greenfield lakehouse on Microsoft Fabric - Azure Architecture Center | Microsoft LearnThank you and Regards,
Menaka
