arpitthool / blogger-app Goto Github PK

We need a caching feature to make the app more fats and efficient. This functionality will be helpful when we have a lot of blogs(data).

Possible Solution : Redis cache implemented via a docker container.

Different roles like : Admin, Normal users. So that admin can manage all blogs and users.

Kubernetes support is needed for app as we plan to ultimately deploy the app suing AWS EKS

Currently, we have a PostgreSQL docker container that hosts our database. When this container is deleted, whatever changes are made to the database also go away. Hence, there is a need to persist this new data.

Possible Solutions: Docker volumes, bind mounts or external database such as caches, obj storage, or file storage.

Currently we have to separately build the docker images for backend and frontend apps. We need to point the docker-compose file to these directories so that docker handles the building of these images directly.

Create a landing page

The README needs to be updated to record the new steps to start project with docker-compose

Refactor code to create files: +page.svelte, +layout.svelte, +page.ts, +page.server.ts, etc to use Svelte efficiently.

Research RabbitMQ to implement this.