Timeline for Distributed database algorithm
Current License: CC BY-SA 3.0
21 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 29, 2018 at 2:28 | answer | added | Kain0_0 | timeline score: 1 | |
Nov 28, 2018 at 23:02 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Oct 29, 2018 at 23:00 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Sep 29, 2018 at 22:00 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Aug 30, 2018 at 21:01 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Jul 31, 2018 at 20:01 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Jul 1, 2018 at 19:19 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Jun 2, 2018 at 7:55 | history | tweeted | twitter.com/StackSoftEng/status/1002821008808607745 | ||
Jun 1, 2018 at 19:05 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
May 2, 2018 at 18:54 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Apr 2, 2018 at 18:07 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Mar 3, 2018 at 17:52 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Feb 1, 2018 at 17:05 | answer | added | JimmyJames | timeline score: 0 | |
Feb 1, 2018 at 15:04 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Jan 2, 2018 at 15:03 | answer | added | Brendan | timeline score: 0 | |
Jan 1, 2018 at 18:04 | comment | added | Derek Elkins left SE | How many nodes do you expect to be in a cluster (i.e. involved in the consensus algorithm)? If it is more than, say, 7, or so, then you probably want to take a different approach where a small number of nodes perform the consensus algorithm to appoint some other node as a primary in a primary-backup configuration. This is how Kafka works, for example. If you intend to use this "seriously", I would strongly recommend attempting to get an existing, tested solution to work. These algorithms are very easy to get wrong, and it is very difficult to tell when they are incorrectly implemented. | |
Jan 1, 2018 at 16:36 | comment | added | Erik Eidt | You want orderly updates while allowing multiple members to be simultaneously updated?? You will either have to serialize updates, accept inconsistency, arbitrarily choose to loose certain updates, and/or constrain to a smaller problem. Any of those might work for your domain, whatever that happens to be. Sometimes getting more clarity on the domain will help reveal a workable solution. | |
Jan 1, 2018 at 9:05 | history | edited | Doc Brown | CC BY-SA 3.0 |
link added
|
Jan 1, 2018 at 8:56 | review | Close votes | |||
Jan 16, 2018 at 3:03 | |||||
Jan 1, 2018 at 8:24 | review | First posts | |||
Jan 2, 2018 at 7:33 | |||||
Jan 1, 2018 at 8:23 | history | asked | C B | CC BY-SA 3.0 |