Goal
Provide READUS with a real persistent storage layer
Details
I don’t care much what DBMS is chosen, as its details should be abstracted away behind the existing repository pretty well. The valuable data will be text blobs and images, so a NoSQL store of some flavor might be the best bet. I would not be opposed to implementing a few back ends and seeing which ones work well for us (ex. A “Mongo” project and a “MySQL” project both in the same PR).
Requirements
- At least one project is added, which implements the contracts laid out in the “Storage” project.
- A dockerfile/docker-compose section is added to the project so that this can still be run locally. This is not necessarily how we’ll do things in production so it doesn’t have to be that neat.
Goal
Provide READUS with a real persistent storage layer
Details
I don’t care much what DBMS is chosen, as its details should be abstracted away behind the existing repository pretty well. The valuable data will be text blobs and images, so a NoSQL store of some flavor might be the best bet. I would not be opposed to implementing a few back ends and seeing which ones work well for us (ex. A “Mongo” project and a “MySQL” project both in the same PR).
Requirements