How does your state store stay consistent, and scale to a large load of readers and writers? Yes if you have the trivial case of a single node state store then

How does your state store stay consistent, and scale to a large load of readers and writers? Yes if you have the trivial case of a single node state store then there is no problem. You scale it by chucking more CPU and resources at it until it can't go any faster. But in the real world that will only take you so far. How does your state store scale out to multiple machines? How does it handle potentially thousands or in extreme cases hundreds of thousands of writers a second? How do you keep multiple nodes in the state store consistent? There's your distributed consensus problem.