I don't want to spend time converting my schema and data to SQLite format. SQLite doesn't fully implement the SQL standard so certain things that I'm using today are missing. I have tables with array columns for example, and I'd have to spend extra time fixing these tables, adding join tables, etc.
I have customers that need reports generated from the database and shared with them. I have certain reporting tools that require a SQL connection to generate these reports and they don't support SQLite. I'd have to find a new tool that does and self-host it which would then eat up more system resources.
For security reasons, I use separate SQL logins for these reporting situations and SQLite doesn't support multi-user - since it's just a file there's only one set of "user credentials" -- if you can access the file, you can open a sqlite connection.
For Dokku or something like it: yes, it saves time with server administration. Makes it easy to deploy an app - otherwise you need to write some script yourself that logs in via SSH, copies your binaries over, and manages the process on the server (or does something equivalent to pull the latest docker image, kill the old app if any, etc). Also need to install services like Postgres manually and screw around with config files. Doable, just requires extra time and I'd rather spend my time building apps vs. doing too much maintenance.
No worries:
For SQLite:
I don't want to spend time converting my schema and data to SQLite format. SQLite doesn't fully implement the SQL standard so certain things that I'm using today are missing. I have tables with array columns for example, and I'd have to spend extra time fixing these tables, adding join tables, etc.
I have customers that need reports generated from the database and shared with them. I have certain reporting tools that require a SQL connection to generate these reports and they don't support SQLite. I'd have to find a new tool that does and self-host it which would then eat up more system resources.
For security reasons, I use separate SQL logins for these reporting situations and SQLite doesn't support multi-user - since it's just a file there's only one set of "user credentials" -- if you can access the file, you can open a sqlite connection.
For Dokku or something like it: yes, it saves time with server administration. Makes it easy to deploy an app - otherwise you need to write some script yourself that logs in via SSH, copies your binaries over, and manages the process on the server (or does something equivalent to pull the latest docker image, kill the old app if any, etc). Also need to install services like Postgres manually and screw around with config files. Doable, just requires extra time and I'd rather spend my time building apps vs. doing too much maintenance.