To prevent too many request being made, a caching mechanism would be interesting to add. It might be slightly overkill at our stage but it could allow us to reduce request made to the backend and thus reduce the resource usages. We might be able to extend our free resource usage from railway.
Some sections that could be to consider caching
User information (they don't change often, are not that important, are called often)
Notebooks (called often but should also rarely change)
To prevent too many request being made, a caching mechanism would be interesting to add. It might be slightly overkill at our stage but it could allow us to reduce request made to the backend and thus reduce the resource usages. We might be able to extend our free resource usage from railway.
Some sections that could be to consider caching