Timeline for Persistent Storage with Docker in Production - Which Solution and Why?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 25, 2018 at 18:05 | vote | accept | TJ Zimmerman | ||
| Jul 28, 2017 at 18:06 | comment | added | James Shewey | Possibly related: devops.stackexchange.com/questions/742/… | |
| Jul 28, 2017 at 17:55 | comment | added | James Shewey | What kind of data? Database data? Pictures? Text files? | |
| Jul 28, 2017 at 11:51 | answer | added | lakshayk | timeline score: 4 | |
| Jul 12, 2017 at 15:37 | comment | added | Ta Mu | teams I have worked with in this context have good experiences with Cassandra as storage backend for a set of mucroservices but the focus is rather on reading than on writing data | |
| Jul 4, 2017 at 7:49 | comment | added | Tensibai | For the 4: Kubernetes play well with azure to create Persistent Volumes as Azure Disk. NFS has a history of bad locking mechanism, in case of error in the orchestrator you may corrupt your files kinda easily. | |
| Jul 3, 2017 at 18:01 | history | edited | TJ Zimmerman | CC BY-SA 3.0 |
added 74 characters in body
|
| Jul 3, 2017 at 17:29 | review | First posts | |||
| Jul 3, 2017 at 17:30 | |||||
| Jul 3, 2017 at 17:21 | history | asked | TJ Zimmerman | CC BY-SA 3.0 |