Okay, I added some basic suggestions to that leader election Jira. Between everything I’ve dropped in this thread, I don’t see why anyone could not fix leader election and leader sync up or come up with good replacements or make good improvements, so I’ll just leave it at that.
Finally, if anyone is interested in why/how I think the current design can scale very well and with great performance and that it’s scalability can’t remotely be judged by the current implementation performance or extrapolating current implementation choices, I’ve outlined some key frames on implementation changes to the current design that would allow it to scale and perform. It’s not a prescription, it’s an example implementation that can be super scalable, super fast, super stable. Other implementation choices could also do this. Still others could be even less scalable and performant than the current one. In the current system, implementation often gets confused for design. Sometimes the edges of such things can be fuzzy regardless. Some people have specific needs they would create a design to favor. Some have specific features they would design to favor. I would do a variety things different in a new design. The NoSql type features would likely go. Real-time search would not be done a document at a time. Some of these personal choices would ripple around in a system design. This is not the system I would design. It’s an implementation that meets the current design that scales and performs at a high level. https://gist.github.com/markrmiller/5cf1dc414b626583ffb25ee1aee914f7 -- - Mark http://about.me/markrmiller
