3 ms·
An ungodly amount of reasons. The ability to manage that many, for one. Those poor devops folk who have to deal with that. On a more technical side as an examp
by bpchaps 11y ago
An ungodly amount of reasons. The ability to manage that many, for one. Those poor devops folk who have to deal with that.
On a more technical side as an example, the number of open files can only be so high. You really start to hit the limit when you do things like that, which is when the most interesting kinds application crashes happen. "Just increase the file count." results in "Our report shows that an OldServer did not include a necessary open file limit config change. Engineer #582 has been fired."
- leesalminen 11y agoCLI tooling has solved a lot of the problems that arise from many. Scripts for migration, host transfer, creation and deletion took some time to build out, but do work fine. I suppose we are lucky to have a very consistent workload per logical database. This allowed us to calculate our costs ahead of time. We found that we could keep DB costs at ~$1/customer/month. For a B2B SaaS product we were satisfied with that cost.