4 ms·
This is an interesting post, thank you. In my toy barebones SQL database, I store rows alternatedly on different replicas based on a consistent hash. I also ha
by samsquire 3y ago
This is an interesting post, thank you.
In my toy barebones SQL database, I store rows alternatedly on different replicas based on a consistent hash. I also have a "create join" statement, this keeps join keys colocated.
Then when there is a join query issued, I can always join because the join keys are available and the join query can be executed on each replica and returned to the client to be aggregated.
I want building distributed high throughput systems to be easier and less error prone. I wonder if a mixture of scale up and scale out could be useful architecture.
You want minimum network round trips or crossovers between threads (synchronization cost) as you can get.