> Hundreds of writes per second? Those extra milliseconds become a real bottleneck.

Of course it's nicer if the database can handle it, but if you are doing hundreds of sequential non-pipelined writes per second, there is a good chance that there is something wrong with your application logic.

▲

sreekanth850 3 days ago | parent [-]

Not universal, there are systems that need high frequency, low latency, strong consistency, writes.

	▲	hobofan 3 days ago \| parent [-]
		Yes, but for the majority of those, rhose would be individial transactions per e.g. request, so the impact would be a fixed latency penalty rather than a multiplicative one.