|
|
|
|
|
by flowerpot
3889 days ago
|
|
Maybe I'm missing the right articles or I'm thinking about this the wrong way, but I can't seem to find any resources on how people run databases in these kinds of infrastructure stacks. I mean I have no problem understanding how I can deploy my 12 factor application on kubernetes for example and load balance to those, but persistence seems to be missing. Do people just use Amazons/Compose/etc Database offerings and don't worry about it themselves? |
|
1. Using AWS services where we can (DynamoDB)
2. Provisioning more "traditionally" to instances, and managing those independently of the Mesos scheduler
3. Experimenting with scheduler based solutions[1] (which are still pretty bleeding edge, but are promising)
As I mentioned, EMC are (to me) doing the most interesting stuff here[2] because they're leaning on a lot of existing production systems like EBS and Mesos' own scheduler.
[1]: https://github.com/mesos/elasticsearch
[2]: http://blog.emccode.com/2015/10/08/enabling-external-volume-...