2 ms·
Did you think about technical solutions to this? You list one obvious one (limiting the Stripe import for free plans to the 30 days you actually display), but
by nostrademons 11y ago
Did you think about technical solutions to this? You list one obvious one (limiting the Stripe import for free plans to the 30 days you actually display), but the other one I would've looked at immediately is to avoid storing the raw data for free plans entirely, compute your metrics on the fly, and store only the computed metrics. 1000 customers * 30 days * 25 metrics (based on your homepage) * 4 bytes/metric = 3MB, which is trivial for any database to process.
In general, I think most engineers these days overuse databases. At Google, common wisdom was "never, ever hit the disk during routine serving", and when I was in the financial industry we'd regularly process the NYSE TAQ data (50GB, about 2B trades) on a single machine nightly.
It'd be really, really nice to have growth gated on technical problems. :-)
- zrail 11y agoThe biggest problem with that plan is Stripe's API limits, which (as far as I understand) are placed on the parent key, not the account key. Also, having to maintain two different ways to compute all of the metrics shared between the two account types seems problematic from a complexity standpoint. Edit: I can't speak for the team and I've never worked on Baremetrics' code base, but I have developed against the Stripe API quite extensively.