2 ms·
"Scaling code is great, but don't pay the price for 10^8 when you're never going to pass 10^3." I am responsible for applications both where holding open a DB
by jerf 8y ago
"Scaling code is great, but don't pay the price for 10^8 when you're never going to pass 10^3."
I am responsible for applications both where holding open a DB transaction as I describe would be suicidal levels of stupid as I expect hundreds of events per second as the applications hits maturity, and perfectly acceptable because the load of the application is measured in single-digit write sessions per week. (They're high-value sessions on a per-session basis, having massive effects, but there aren't a lot of them.) It's obviously a fail to engineer the 10^8 system to 10^-2 standards; it's less obviously a fail, but still a fail, to make the opposite error.
- atombender 8y agoI was talking about the operational aspect, not scalability. Read my first paragraph again. :-) I don't see any huge issues with the design in terms of scalability.