4 ms·
The way you handle persistence is by using storage volumes mounted form the outside. Don't put the data in the container, only the software, which then can be
by johannes1234321 3y ago
The way you handle persistence is by using storage volumes mounted form the outside. Don't put the data in the container, only the software, which then can be replaced. Then managing is similar to other environments. For updating you don't replace rpm/deb packages and restart, but replace the container using the same volume, which should trigger the dbms-specific update routine. Similarly you do backups similar to outside container world (depending on DBMS and your exact choice, from filesystem snapshot to logical backup (dump) or something more or less smart in between)
- Alifatisk 3y agoSo all the containers access the same volume on the host? Does that scale well or will it bottleneck at one point? Or is that when you have a layer of cache inbetween like Redis?
- johannes1234321 3y agoNo, not the same volume, a volume. Each container can mount an arbitrary amout of volumes. It scales as well as your machine scales. A container is nothing but a process with restrictions on which filesystem subtrees kt can see, what resources (CPU, memory) it may use and which networks it can access, with some tooling to manage self-contained images of directory structures.