5 ms·
Look higher up the problem domain and solve it without requiring a consensus protocol.
by hughrr 5y ago
Look higher up the problem domain and solve it without requiring a consensus protocol.
- cortesoft 5y agoHmm, how do you have high availability consistent data without a consensus protocol? No matter where in the problem chain you move, you have to eventually solve that problem.
- hughrr 5y agoEasy you push the configuration to every target. Then they are logically consistent. We did this for 30 years fine before someone invented this stack on deployments much larger then the average consul or vault deployment these days. I had something running 15,000 dynamic rps on Apache about 15 years ago. People are blinded from simplicity by complexity. Eventually complexity owns you. You can only own simplicity. At the end of the day this is one way to solve a problem that doesn’t need to be solved that someone has convinced you is a problem.
- asadawadia 5y ago>Easy you push the configuration to every target. Then they are logically consistent. What does this mean? This doesn't mean anything? Are you saying to push the DB to the client?
- caffeine 5y agoI think he’s saying you have a cronjob with an rsync to every client
- cortesoft 5y agoPeople need distributed consistent data for a lot of things besides configuration.
- yencabulator 5y agoPeople say they do, but then they proceed to read stale data from replicas all the time...
- rubiquity 5y agoNot sure why you’re being down voted as this is definitely the path forward. The industry and research have both explored the polar opposites of weak consistency protocols and linearizibility and consensus on the other end. Understanding your domain and knowing how you can step down to something weaker than consensus will be critical for future applications.