Separate collections initialization from service logic

[danibix95]

Context

As it was initially designed, CRUD Service is in charge of many different operations, such database initialization (e.g. collections and their indexes creation), document validation and CRUD operations on the connected database.

As time passed by, we observed that users gets often confused by the database initialization. In fact, it is not always clear what happens when somebody modifies a collection definition, the set of indexes associated to a collection and the possible errors/slowdowns that may arise whenever it is not possible to create or modify a collection index.

Desired Solution

CRUD service should only responsible for CRUD operations, while database initialization should be carried out separately in another system.