Events
31 Mar, 23 - 2 Apr, 23
The biggest Fabric, Power BI, and SQL learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register todayThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This chapter introduces the key components of our system and provides an overview of the architecture. These components work together to create a robust and flexible platform for your development needs. Let’s delve into these components and their roles within our architecture.
Some of the key aspects of the Fabric workload architecture are:
It handles data processing, storage, and management. It validates Microsoft Entra ID tokens before processing them and interacts with external Azure services, such as Lakehouse.
The workload Frontend (FE) offers a user interface for job creation, authoring, management, and execution.
User interactions via the FE initiate requests to the BE, either directly or indirectly via the Fabric Backend (Fabric BE).
For more detailed diagrams depicting the communication and authentication of the various components, see the Backend authentication and authorization overview and the Authentication overview diagrams.
The frontend serves as the base of the user experience (UX) and behavior, operating within an iframe in the Fabric portal. It provides the Fabric partner with a specific user interface experience, including an item editor. The extension client SDK equips the necessary interfaces, APIs, and bootstrap functions to transform a regular web app into a Micro Frontend web app that operates seamlessly within the Fabric portal.
The backend is the powerhouse for data processing and metadata storage. It employs CRUD operations to create and manage workload items along with metadata, and executes jobs to populate data in storage. The communication bridge between the frontend and backend is established through public APIs.
The workloads can run in two environments: local and cloud. In local (devmode), the workload runs on the developer's machine, with API calls managed by the DevGateway utility. This utility also handles workload registration with Fabric. In cloud mode, the workload runs on the partner services, with API calls made directly to an HTTPS endpoint.
The workload is packaged as a NuGet package, combining backend and frontend components. The structure adheres to specific naming conventions and is enforced by Fabric for consistency across upload scenarios. The NuGet package designed to represent workloads is structured to include both backend and frontend components.
The backend segment comprises .xml files that define the workload and its associated items, which are essential for registration with Fabric.
WorkloadManifest.xml
- The workload configuration file, required to have this exact name for Fabric's verification.Item1.xml
, Item2.xml
, ...
- Manifests for individual items with flexible naming, following the XML format.The frontend section contains .json files detailing the product and items for the frontend, along with an 'assets' directory for icons.
Product.json
- The main manifest for your product's frontend, which must be named precisely for Fabric's verification.Item1.json
, Item2.json
, ...
- Manifests for individual items with flexible naming, following the JSON format. Each json corresponds to a backend manifest (e.g., Item1.json to Item1.xml).assets
folder - Stores all icons icon1.jpg
, icon2.png
, ...
used by the frontend.The structure, including specific subfolder names ('BE', 'FE', 'assets'), is mandatory and enforced by Fabric for all upload scenarios, including test and development packages. The structure is specified in the .nuspec
files found in the repository under the Backend/src/Packages/manifest
directory.
The following limits apply to all types of NuGet packages, both in development mode and cloud mode:
BE
and FE
subfolders are permitted. Any other subfolders or files located outside these folders result in an upload error.BE
folder accepts only .xml
files. Any other file type result in an upload error.BE
folder can contain one WorkloadManifest.xml
and up to 10 Item.xml
files. Having more than 10 item files in the folder result in an upload error.Assets
subfolder must reside under the FE
folder. It can contain up to 15 files, with each file being no larger than 1.5 MB.Assets
subfolder: .jpeg
, .jpg
, .png
.FE
folder can contain a maximum of 10 item files plus one product.json
file.product.json
must not exceed 50 KB.Assets
folder must be referenced within the item files. Any asset referenced from an item file that is missing in the Assets
folder will result in an upload error.The workload backend (BE) operates on the developer's machine. Workload API calls are transmitted via Azure Relay, with the workload's side of the Azure Relay channel managed by a specialized command-line utility, DevGateway. Workload control API calls are sent directly from the workload to Fabric, bypassing the Azure Relay channel. The DevGateway utility also oversees the registration of the local development instance of the workload with Fabric, within the context of a specific workspace. Upon termination of the DevGateway utility, the registration of the workload instance is automatically rescinded. For more information, see Back-end implementation guide.
The workload backend (BE) operates within the partner's services. Workload API calls are made directly to the HTTPS endpoint, as specified in the workload manifest. In this scenario, the DevGateway utility isn't required. The registration of the workload with Fabric is accomplished by uploading the workload NuGet package to Fabric and subsequently activating the workload for the tenant. For more information, see Manage a workload in Fabric.
Events
31 Mar, 23 - 2 Apr, 23
The biggest Fabric, Power BI, and SQL learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register todayTraining
Learning path
Solution Architect: Design Microsoft Power Platform solutions - Training
Learn how a solution architect designs solutions.
Certification
Microsoft Certified: Fabric Data Engineer Associate - Certifications
As a Fabric Data Engineer, you should have subject matter expertise with data loading patterns, data architectures, and orchestration processes.
Documentation
Add a Microsoft Fabric workload - Microsoft Fabric
Learn how to add, remove, and use a workload in the Microsoft Fabric workload hub.
Microsoft Fabric Workload Development Kit overview - Microsoft Fabric
Learn about building a Fabric workload.
Microsoft Fabric Workload Development Kit - Microsoft Fabric
A landing page for Microsoft Fabric Workload Development Kit documentation