Do we need to create a Separate datalake for Microsoft Fabric? How do we integrate the datas inside it?
Loading
Do we need to create a Separate datalake for Microsoft Fabric? How do we integrate the datas inside it?
Know the answer? Post it — somebody with the same question will find it here.
Sign in to answer this question
It is the same account you read, post and publish with — and you will come straight back to this page.
Janarthanan SPosted Aug 10, 2023, 10:30 AM
Not required to create a Separate datalake for Microsoft Fabric. Microsoft Fabric has own lake called as One Lake. One Lake provides a single, unified, logical data lake for the whole organization.
Saravanan GanesanPosted Aug 14, 2023, 1:13 PM
No, a separate data lake isn't required for Microsoft Azure Service Fabric. Instead, integrate data by leveraging Azure's various storage services such as SQL Database, Cosmos DB, or Blob Storage. Microservices within Service Fabric can access these data sources using their respective APIs. Configure secure connection strings, store configurations in Azure Key Vault, and set up service-to-service communication for data sharing. If needed, Azure Data Factory or Stream Analytics can automate data ingestion. Choose data solutions aligned with your app's architecture and scalability needs.
Mohammad HussainPosted Aug 8, 2023, 12:43 PM
It think no, you do not need to create a separate data lake for Microsoft Fabric. Microsoft Fabric includes a built-in data lake called OneLake. OneLake is a single, unified data lake that can store all of your organization's data, regardless of its source or format. This makes it easy to integrate data from different sources and to use it for analytics and machine learning.