3 ms·
> the per-user ID write bottleneck The basics is to have less machines but more powerful. It helps to handle the targeted bursts. The advanced is to have a la
by user5994461 10y ago
> the per-user ID write bottleneck
The basics is to have less machines but more powerful. It helps to handle the targeted bursts.
The advanced is to have a layer of queuing before the ingestion, where you can do magic with distribution rules, rate limiting and dropping peak traffic.
- kornish 10y agoYep, you're absolutely right. In multitenant SaaS apps with extremely uneven distribution of traffic, it's pretty common for large customers to get their own dedicated DB servers. > The advanced is to have a layer of queuing before the ingestion, where you can do magic with distribution rules, rate limiting and dropping peak traffic. And batch loading – don't forget batching!
- user5994461 10y agoI didn't mean to have special databases, that is another level of optimization. I mean to have bigger servers for everything. For instance, a farm of 4x 10cores servers is likely to process data more consistently than 10x 4cores servers.