3 ms·
I’d go with this approach for my next startup, unless I had specific performance requirements. (Having built a company to Series B on the standard Django/Celery
by theptip 4y ago
I’d go with this approach for my next startup, unless I had specific performance requirements. (Having built a company to Series B on the standard Django/Celery/Redis stack).
Very hard to overstate the benefit of having all data in one DB that your developers can trivially run, mutate, and step-debug in your application.
- edgyquant 4y agovery hard to undersell just how bad this is. Now every action on your application it running database queries.
- theptip 4y agoWhich is totally fine for most early-stage applications.
- edgyquant 4y agoIt is, until it isn’t I suppose. I’ve worked at places where the ORM (or equivalent) was nicely utilized and we were able to cache things via redis as we got bogged down then migrate to a multi-layer structure with caching based on date + popularity across a DB cluster, nodql store and browser store (this was really nice.) But: I’ve also had to deal with “SPAs” that evolved a few dozen independent routes a massive backend all coupled to the database with no ORM/class layer. This was not so nice so refactor when it came time to scale