Timeline for How to scale horizontally a microservice that holds a database
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 3, 2021 at 3:48 | answer | added | Chris | timeline score: 1 | |
| Mar 2, 2021 at 18:00 | history | tweeted | twitter.com/StackSoftEng/status/1366810575708319749 | ||
| Mar 2, 2021 at 15:30 | vote | accept | Woody | ||
| Mar 2, 2021 at 15:30 | answer | added | Woody | timeline score: 4 | |
| Dec 20, 2018 at 16:33 | vote | accept | Woody | ||
| Mar 2, 2021 at 15:30 | |||||
| Dec 15, 2018 at 9:16 | comment | added | Clockwork-Muse | Ah, consistency, that quality that's so poorly understood. Consider this peculiarity: If I make two web requests to the same physical machine, one that just reads data and one that changes data, it's completely valid for the read request sent first to return after the later change request, and yet show the original data. Because latency is a thing. When dealing with shared, mutable state, it's best to start with the assumption that all reads are dirty. All distributing the db really does is increase the figurative time between reads and updates, so things are dirtier longer. | |
| Dec 14, 2018 at 20:45 | answer | added | svidgen | timeline score: 8 | |
| Dec 14, 2018 at 20:10 | answer | added | amon | timeline score: 2 | |
| Dec 14, 2018 at 19:45 | review | First posts | |||
| Dec 15, 2018 at 2:55 | |||||
| Dec 14, 2018 at 19:41 | history | asked | Woody | CC BY-SA 4.0 |