3 ms·
Don’t know about expected usage but 10K rows seems like low number to me. If you mean 10K req/s then perf starts to matter but usually it’s SQL queries that fai
by machiaweliczny 4y ago
Don’t know about expected usage but 10K rows seems like low number to me. If you mean 10K req/s then perf starts to matter but usually it’s SQL queries that fail first if you have 100K+ rows. In general good caching solves most of stuff + read/write separation. That’s all from my poor experience.
What I mean is that these scaling problems don’t have much to do with app logic but having nice core is good so :thumbsup:
- ChrisMarshallNY 4y ago10K is a rounding error, to most folks, around here. The app (and the demographic that it Serves) are very security and privacy-conscious, so security and privacy are the main coefficients. Most folks would be disappointed in how few features the app boasts, as each feature is a potential compromise. I'm glad to have low usage, as a result. I wrote the backends, as well as the frontend, and have avoided third-party dependencies, all around. It seems one of the first casualties of fast scaling is security. I really didn't want to take any chances. An overly-complex architecture is begging for security compromises.