Horizontally scalable backend #22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I want Otter to be horizontally scalable by design. In its current state, it's a fairly simple program, mostly providing an API wrapper around a database. This makes it a good time to restructure the application to make it scalable.
The most important step for this will be to ensure any operations that are performed in the database are atomic and concurrency-safe. All information should be stored in the database.