If we step back, what is the main thing you are trying to solve here? Is it the write throughput? Ho
If we step back, what is the main thing you are trying to solve here? Is it the write throughput? How many writes per second do you want to support, and how long does each write take?
Maybe I missed it in the thread above, but adding queues also comes with complexity and their own throughput problems, so want to make sure you are not solving a problem that doesn't exist.
1000 writes at the same time once will just be serialized, and eventually all go through. Now if you have 1K writes per second consistently, that will almost certainly trigger an overload error to be returned to you and queries starting to be rejected.
Maybe I missed it in the thread above, but adding queues also comes with complexity and their own throughput problems, so want to make sure you are not solving a problem that doesn't exist.
Original question: This might be a dumb question if a 1000 users try to write to the database at the same time or make a query it won’t fault correct.
1000 writes at the same time once will just be serialized, and eventually all go through. Now if you have 1K writes per second consistently, that will almost certainly trigger an overload error to be returned to you and queries starting to be rejected.
