News for hackers. Stuff that matters.
Re:Why Databases Are Not for Docker Containers by amelius on Monday February 06, 2017 @02:38PM (#13583095)
So let your database write a journal. Data corruption problem solved.
Re:Why Databases Are Not for Docker Containers by illumin8 on Monday February 06, 2017 @02:39PM (#13583104)
And when your journal is corrupted due to a bug in the Docker volume driver?
Re:Why Databases Are Not for Docker Containers by amelius on Monday February 06, 2017 @02:49PM (#13583207)
Then you let Docker write to a virtual network drive, streaming the journal out of the container.
Re:Why Databases Are Not for Docker Containers by KaiserPro on Monday February 06, 2017 @02:59PM (#13583285)
I doubt thats going to be fast.

However, if you are going to be running docker on real tin (because thats where the value/speed comes in, if you're on AWS thats a whole 'nother issue) Then you might as well use device mapper for what it was originally designed for: mapping fibre channel. (or iscsi, or SAS [another scsi])

That is assuming you want speed, and have paid enough cash to overcome SPoF in your storage layer (it'll be cheaper and faster than trying to software your way out of it.)

Re:Why Databases Are Not for Docker Containers by jjawssd on Monday February 06, 2017 @02:49PM (#13583206)
Isn't it possible to stream a copy of the database out of the container and over the network to another database instance?
Re:Why Databases Are Not for Docker Containers by Minikloon on Monday February 06, 2017 @02:57PM (#13583269)
Chicken and egg. Is that other instance containerized?
Re:Why Databases Are Not for Docker Containers by mentat on Monday February 06, 2017 @03:08PM (#13583368)
Decoupled failure modes, unless you think there's a global "fail all docker data stores".
Re:Why Databases Are Not for Docker Containers by user5994461 on Monday February 06, 2017 @03:55PM (#13583808)
There are major cascading failures with Docker.

For starter, failure modes are not decoupled at all. If one db hits a race condition in the storage driver on one instance, it's usually 100% guarantee that all other instances are sensitive to the same bug and it will happen sooner or later.

In practice, occurrences of a bug are highly correlated and usually happen in batch.