Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove support for PostgreSQL -- investigation #79

Open
helicalbytes opened this issue Aug 30, 2022 · 0 comments
Open

Remove support for PostgreSQL -- investigation #79

helicalbytes opened this issue Aug 30, 2022 · 0 comments

Comments

@helicalbytes
Copy link
Contributor

helicalbytes commented Aug 30, 2022

This is a simple application and most likely always will be.

Although support for multiple databases seems useful, SQLite provides more than adequate performance and functionality and removing support for Postgres would simplify the code base and the CI/CD implementation.

SQLite provides all the functionality we need. Backups can be completed via file copy of the single file database, or programmatically. And the docker container can map an external volume to the container's file system for persistence.

SQLite does have a performance issue with write-heavy workloads. It obtains a lock on the whole database during writes. But any writes to the database that we have would be milliseconds in length and infrequent, so that shouldn't be an issue.

Are there any counter arguments to this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant