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. 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!


Back to Home
John Solly Profile Picture
John Solly Profile Picture

John Solly

Hi, I'm John, a Software Engineer with a decade of experience building, deploying, and maintaining cloud-native geospatial solutions. I currently serve as a senior software engineer at New Light Technologies (NLT), where I work on a variety of infrastructure and application development projects.

Throughout my career, I've built applications on platforms like Esri and Mapbox while also leveraging open-source GIS technologies such as OpenLayers, GeoServer, and GDAL. This blog is where I share useful articles with the GeoDev community. Check out my portfolio to see my latest work!