Deployment Stages in Fabric

1. Deployment Stages in Fabric

Let's talk about Deployment Stages in Fabric.

2. Introduction to Deployment Stages

In big companies, you never push your updates in production, which are available to all your users. You usually create a development environment where you can store your changes and usually a testing environment where some users can test the new features and provide feedback. When everything is confirmed, you can publish the changes to everyone. This process is crucial to identify bugs before impacting the whole company. There could be more complex stages, but we will stick with the default 3.

3. Deployment Stages in Fabric

That's why Fabric has deployment stages and deployment pipelines. Stages are workspaces flagged as "Development" for working and experimenting, "Testing" for testing the outcome, and "Production", which is available to all the users. Deployment pipelines are processes that move files from one stage to another. This operation is called "deploy". Let's see the characteristics of the three default deployment stages.

4. Development Stage

The development stage is your safe harbor for innovation and experimentation. It's a safe space to try new ideas and approaches where developers can rapidly iterate and make frequent changes without formal approval processes. There is no production impact as changes are isolated from end users

5. Testing Stage

The test environment serves as a quality control checkpoint where changes undergo systematic testing before production. That's where developers identify and fix issues before production deployment and evaluate the impact on performance. It's also where User Acceptance Testing is performed: some selected users can preview and provide feedback.

6. Production Stage

The production environment is where your solution goes live. In Fabric, it's the official workspace that all the users can access. In a production environment, only thoroughly tested changes are deployed and there are stringent security measures compared to the previous stages as real data is involved.

7. Why Deployment Stages are important?

So why are deployment stages so important? First and foremost, they prevent bugs from impacting all users at once, reducing business risks since you test everything before it goes live and you identify issues earlier. But it's not just about preventing problems - they also give your teams the freedom to work safely and provides a controlled sandbox to test without friction

8. Let's practice!

Now, it's time to apply what we've learned. In the upcoming exercises, you'll practice creating deployment stages in Fabric.

Create Your Free Account

By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.