Caching API
Have an API that checks if the last data is valid and just serves the cached. Apparently Next.js has a native one but I can just build it my-self to know how it works I guess. Probably gonna do it with redis server side for the querying stuff IF its different it’ll update it for the next person Caching
accessing other APIs
maybe look up what flask is
unrelated maybe https://www.youtube.com/watch?v=utJ66ZevCU4 — this one is if you have multiple microservices on different EC2 instances. Dont really need it here i guess
Docker containers
- for the database
- takes a backup before every update or insert
- resets to the latest backup in case there is an error
- one for the backend server itself
- do i need one for the email one? not unless Im implementing one to email me if one of them crashes
- which i do no know how i would do in docker(dont know how im supposed to read statuses and what not)
- restarts the container if there is a crash
- do i need one for the email one? not unless Im implementing one to email me if one of them crashes
- Not sure where the 0Auth stuff go yet, probably have a top level Microservice like architecture with the monolith doing the auth stuff and if it passes sending it to the DB manager server
security
encryption for the user password part somehow.Auth0 JWTs for the login page and the page that edits, deletes and adds new projects to the database. Have access tokens, refresh tokens, and all the other stuff.
Elasticsearch
Using |AWS, and elastic search to index all the blog posts and make searching much easier, and also using it as a right through cache so no need to take make needless search queries to the DB.
sql for updating the db(this is just for me incase i have to reset my warp)
mysql -u root -ppassword -e “DROP DATABASE Projects” mysql -u root -ppassword -e “CREATE DATABASE Projects” mysql -u root -ppassword Projects < Schema.sql
URL Processing
Right now i change it from the s3 bucket to the CDN in the frontend which im assuming exposing ur bucket url is not a good idea, so have to put it behind the CDN in the backend.
Each URI structure: https:::s3:bucketaddress/projectName/pictureNe
It is fully stored in the DB Should I convert it to the CDN URI when im storing in Open Search and keep the original in the RDS or should i do both CDN
Nope ill just fix it runtime when im returning image URLs