NASA’s new dark energy space telescope can also detect killer asteroids
technologyreview.com·3h ago
Data Science
Simon Willison's Blog·22d ago·5 min read
lobste.rs is now running on SQLite
TL;DR
Lobsters, a community site, has successfully migrated from MariaDB to SQLite after evaluating various options since 2018. The migration resulted in reduced CPU and memory usage, and a significant decrease in hosting costs.
✦ Why It Matters
Consider evaluating SQLite for your own projects to potentially reduce costs and improve performance.
Key Takeaways
- Evaluate SQLite for small to medium web applications
- Monitor resource usage post-migration
- Consider single-server architectures for cost efficiency
- Review database management practices for optimization
Full Summary
Lobsters, a community-driven site, began its migration from MariaDB to SQLite in August 2018, initially considering PostgreSQL before opting for SQLite last year. The migration was completed recently, and the site now operates on a single Virtual Private Server (VPS) with a primary SQLite database file of approximately 3.8GB.
Additional databases include a 1.1GB cache, a 218MB queue, and a 555MB rack_attack database for managing abusive requests. The transition has led to significant improvements, including a reduction in CPU and memory usage, and halved VPS costs once the MariaDB server was decommissioned.
This case study highlights the effectiveness of using SQLite for web applications, demonstrating that substantial performance gains can be achieved with minimal infrastructure.