Filesystem and Database are not cutting the problem space right

Workflows

Two different workflows are available:

Static workflow

The static workflow does not allow collaboration, you can not attach dynamic volumes to your static filesystem.

On the other hand, the master branch (production environment) of your website will be writable and undo/redo will be available. That's the old workflow thus we will keep it to not disrupt existing users/websites.

Collaborative workflow

To use the dynamic filesystem, you will have to enable the collaborative workflow. Let's see how it's different.

Say you want to implement a new feature or add a new blog post. You can't do that on the master branch (production environment) so you will create a new development branch. You do this by cloning your master branch which includes both the static filesystem and the dynamic filesystem. That way, you have complete freedom to try anything. If you spot a bug on the live website, it will still be there after creating a feature branch. The only change will be that you are now in a safe playground.

It's like cloning your website also cloned your database.

Note that cloning is both free and instant in Boomla due to data deduplication.

Once you are done and happy with your changes, you can publish the static filesystem of your development branch. The dynamic filesystem will not be published, it will be dropped. That way, you are free to implement a new shopping cart system and even test drive it a couple of times without worrying that your changes will affect the live inventory.

 

from Hacker News https://ift.tt/3fANBPx