Fought a war with Django to migrate from sqlite to postgres. Documented the 'gotchas' I ran into in my latest video:
Why did I go through the effort to migrate everything from slqlite? To be honest, I didn't 'need' to use postgres. According to the sqllite documentation, it's perfectly fine to use it for websites this like mine.
SQLite works great as the database engine for most low to medium traffic websites (which is to say, most websites). The amount of web traffic that SQLite can handle depends on how heavily the website uses its database. Generally speaking, any site that gets fewer than 100K hits/day should work fine with SQLite. The 100K hits/day figure is a conservative estimate, not a hard upper bound. SQLite has been demonstrated to work with 10 times that amount of traffic.
The goal of this site is to teach me how to design stable, scalable web applications that can handle large amounts of traffic. Blogthedata.com might not get over 100K hits/day, but it's very possible that my next position has me working on an application that experiences that kind of traffic volume.
Onward and upward!
Comments
- No comments yet.

John Solly
A hands-on AI practitioner who transitioned to a CTO role to broaden my impact.
Most of my career has been dedicated to developing spatial systems at Esri, startups, and federal agencies. Currently, I lead technology strategy for Leidos' Health IT division, supporting agencies such as SSA, VA, and HHS.
My primary focus is the convergence of spatial computing and AI, enabling machines to interpret the physical world and applying these capabilities to meaningful missions.
Please reach out if you are interested in spatial systems or advancing AI within the federal government.




0