6 ms·
Don't do blue-green deploys when you have no revenue. Downtime costs you nothing and at 3,400 visitors a day you'll be lucky to drop a single request while depl
by aahortwwy 6y ago
Don't do blue-green deploys when you have no revenue. Downtime costs you nothing and at 3,400 visitors a day you'll be lucky to drop a single request while deploying.
Pre-compute and cache to reduce your need for beefy servers.
When you can run something on your machine or in the cloud, choose your machine.
EDIT: It's less about saving money and more about not spending it.
EDIT2: Forgot to mention: use SQLite.
- chillfox 6y agoSQLite Really is a bit of a hidden gem.
- rapsey 6y agoNot really hidden when it is one of the most widely deployed pieces of software on the planet.
- bigiain 6y agoSure, but as an underlying dependency for iOS/Android, it's pretty well hidden from casual users...
- krtkush 6y agoThat's true for even a casual website user. They have no idea or care about the underlying database. Every app developer is aware about SQLite.
- chillfox 6y agoI guess not in absolute terms, but it’s mostly overlooked for web apps.
- stevekemp 6y agoCaching is, in general, a good thing. But it's worth thinking about how you do it. I recently sped up a large system by dropping the use of redis entirely - because it was being badly used. During a single request there might be 50+ cache-lookups, each taking a round-trip to a remote redis server to fetch a single key at a time. Batching those up to a set/hash would have been more efficient, but the codebase had evolved in such a way as to make that difficult. Instead of making 50+ redis fetches it turned out that just fetching all the stuff from the database was faster. (There will be refactoring to batch up the key fetches, but for the moment there was a measurable increase in performance under current loads just by removing redis.)
- limteary 6y agoWhy use SQLite? My postgres process doesn't come close to using up enough resources to push me out of even the cheap VPS tiers and I don't have to worry about locking if there's a heavy write load.
- theshrike79 6y agoBacking up an SQLite database is as simple as copying a single file. As long as nothing is writing in the file, you're good.
- mattmanser 6y agoThat's not a reason. Plus setting up a nightly back up of any SQL database, regardless of creed, is like a 10 line cron job.
- ClumsyPilot 6y agoSome developers have never written a cron job. I think the point here is, SQLite setup would provide satisfactory results at this scale. If the choice is betweeen a PAAS database offering and SQLite, you can pick SQLite. If you have skills / are prepared for managing dbserver yourself, then do that.
- aahortwwy 6y agoYeah, fair point. From a cost standpoint it's more about using the same server for your application and your database.