Fabric Monday 09: Organizing Workspaces

[@VijayVenugopalanChettiar]

Thanks Dennes! That is very very useful!

[@muftkuseng5924]

If we would have a DEV, TEST, STAGING, PROD Environement, would we have all these workspaces 4 times? This seems like a lot. Do you plan to do any CI/CD Videos and how you would reccomend to tackle this?

[@DennesTorres]

There are many evolutions since this video. Two of them were the support to folders and the branch out. This end up requiring 3 sets of Dev/Test/Prod, which I'm actually using: 1. One set for the data objects and for the objects which are still limited to be in the same workspace as the data objects 2. One set for the code objects where you would like to make branch outs for the developers 3. One set for the "front-end", reports and semantic models

[@muftkuseng5924]

@ i love how you take your time to answer my questions. Thanks! do the pipelines still need to be where the targets are or is this restriction not there anymore? Do you put them still in the data workspace? Is your code workspace only notebooks or other objects aswell? Do you maybe have an blog post about it? Id love to dive deeper in this topic.

[@DennesTorres]

@@muftkuseng5924 The pipelines evolved and enable access to objects in different workspaces. This was recent, I wrote about this when it happened. However, the high performance feature is very recent. Before it, the cost of pipelines were way higher than the cost of notebooks. In this way, at the moment my code development flow has only notebooks, but it's only by chance.

[@muftkuseng5924]

@@DennesTorres thanks! So many updates and changes. Its really hard to keep up as someone who just started 4 months ago. Sometimes i just read about limitations while they are already gone and thats sometimes confusing. I really appreciate you taking your time to answer my questions.