Best Practices for Hosting a Node.js App with SQLite

SQLite can be sufficient for many apps, but you might face scalability issues if you're aiming for more than light usage. Make sure to do thorough testing on memory management in Node.js since its garbage collection can lead to unaddressed stale references. Using prepared statements is a must to protect against SQL injections, and running your Node.js service under a dedicated user can greatly enhance security.

Have you thought about creating a Docker image for your app? It's a great way to handle dependencies and isolate your environment. When it comes to security, ensure you audit your code regularly and consider getting a third-party security review as your app grows.

To host your app, it's a good idea to use NGINX in front of Node.js. While you’re using SQLite, I recommend considering a more robust database like MySQL or MariaDB for better scalability. You can set this up in a single VM or even explore using Docker for containerization. Additionally, make sure to secure your host by following CIS benchmarks to lock things down properly. Keeping your environment secure is key.

I think you should reconsider using SQLite, especially if your app might have multiple users. It’s great for simple, local apps, but for something exposed to the internet, you'll likely want to use Docker to containerize your app and switch to MySQL or PostgreSQL. Also, take care with security; block unnecessary traffic and ensure your database users have the least privileges they need.