Open anamansari062 opened 1 year ago
This feature gives a database approach to Storyblok.
Over 10 architectural patterns were laid out and 7+ were discussed with Storyblok representatives which led to the conclusion that trying to fit a database-like use case to Storyblok is a waste of effort for our use case and we'd be better off with a full-fledged database service
The effort to integrate Storyblok was taken in order to understand the viability of headless CMS systems proposing as an alternative to BaaS services for a set of use cases.
The functionalities we needed for our use case are as follows:
Description