4 ms·
But as your web application database grows more complex and larger, how do you intend to make them keep up with the 2k req/sec load?
by jerryji 17y ago
But as your web application database grows more complex and larger, how do you intend to make them keep up with the 2k req/sec load?
- axod 17y agoWhy would anything need to go to db? :/ Going to db should always be a last, final resort. People often seem to think a db is the only way to write any webapp, and that everything must depend on the db. That's bad architecture. In the case of Mibbit, db access is only done for writes, lazily, in the background. The bottlenecks for me, are CPU, network, and ram. And yes, you can throw servers at it, if you're frivolous and don't intend to make any money. I decided to go the other way and be profitable ;)
- kingkongrevenge 17y agoThe vast majority of web applications are straight-up CRUD. Not making that all about a normalized schema is the stupid mistake. As far as relational DBs being the problem, that's more a matter of the free ones not cutting the mustard. Oracle and DB2 can handle jaw dropping load in the hands of an expert.
- kingkongrevenge 17y agoCurious if you considered using something like csql or gigabase for a main memory DB? Sounds like you wrote some custom in memory db yourself.