Hi @garddolau ,
Thanks for the reply from lbendlin .
1. “How do we decide how many workspace's should be used?”
- For smaller organizations or projects, one workspace is sufficient.
- For larger organizations, consider creating separate workspaces for each department or for projects of different classifications.
2. “How do we deal with different environments? eg.(dev,test,prod)”
- Different workspaces can be created for dev, test, prod environments.
- You can use naming conventions for different environments, such as Name1_Dev, Name2_Test, and Name3_Prod.
3. “How does wanting to use git integration effect these decisions?”
Git integration in Fabric enables developers to integrate their development processes, tools, and best practices directly into the Fabric platform.
It allows developers who are developing in a fabric to:
- Backup and version control their work
- Revert to previous phases as needed
- Collaborate with others or work individually using Git branching
- Leverage the power of familiar source code management tools to manage fabric entries
For more detailed guidance, you can refer to the official documentation below:
Get started with Git integration - Microsoft Fabric | Microsoft Learn
4. “What naming convension should we use for created objects?”
Use a prefix or suffix to indicate the type and purpose of the object, such as Name1_Dev, Prod_Notebook1.
If you have any other questions please feel free to contact me.
Best Regards,
Yang
Community Support Team
If 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!
