Bug: Workspace creation is non-atomic

[wafelmolt]

Just set up an Huly instance for my non-profit and the first time, I ran into a transactional issue.

My workspace would be "partialy" created because my S3 instance was not set up correctly.

The workspace creation seams to be a 2-steps action :

• Creation of mongodb collection
• Creation of associated bucket

In fact, my particular case is tied to misconfig, but to me, it means that this will happen in a situation where my S3 is simply not joinable for any reason.

Huly platform should implement a mechanism for handling a transactional state verification of the workspace creation to ensure consistency.

As the application system is mainly microservices oriented, I would suggest 2-phase commit, saga pattern or single local transaction.

[wafelmolt]

+ I guess that this issue should be mirrored to https://github.com/hcengineering/platform

[kbaegis]

I'd been curious if I could use Postgres instead of Mongo too. I have an S3 endpoint as well, but I'm going to have to manually rip out minio and replace.

[wafelmolt]

Hi @kbaegis . I guess you are misunderstanding my point. This has nothing to do with used technologies but rather design issue.

Moreover, using Postgres for Huly seams out of context because it is mostly tightly coupled with mongo atm.