4 ms·

Thanks, thats how I understood it. The tradeoffs are quite seductive, in my experience most companies do not operate their software on a scale where they reall

Thanks, thats how I understood it. The tradeoffs are quite seductive, in my experience most companies do not operate their software on a scale where they really have to scale out, but they run multiple instances simply to increase availability. But then those are probably the same kind of companies that will probably not have the required network hardware, and won't for many years to come. I'm thinking about stuff like Redis or distributed caches like Hazelcast, maybe even Zookeeper and friends. Any ideas where this could shine? Cloud vendors could manage the hardware part, but is this model attractive to them, essentially being constrained to single-node performance?

hardwaresofton 10y ago
I thought of mostly the same things (redis/some other database), maybe also IoT? This, in combination with the ultra low power wifi post that recently went up (https://news.ycombinator.com/item?id=13135607 https://news.ycombinator.com/item?id=13135607) seem like they would go together. I think cloud vendors would definitely charge a pretty high premium for this, since it requires more than zero work on their part. Also, aren't most simply-distributed databases constrained to single node performance (for writes, assuming one master)? I feel like you could work in fast reads to this scheme too, if you required replicas to have a complete log in order to respond to a read, since it's all or nothing. The possibility of a slightly (1 op) stale read is possible though.