4 ms·
> But what about Configuration Management systems? They’re designed to solve this kind of routine by running one command. The problem with this for most of the
by derefr 10y ago
> But what about Configuration Management systems? They’re designed to solve this kind of routine by running one command.
The problem with this for most of the developers you see praising containers, is that with a containerized setup, you've already got the rest of your deployment process down to `docker service update --image myorg/myservice:1.3.0 myservice`
(And, in fact, maybe you're even running that code against immutable-infrastructure container-host OS like CoreOS.)
And now, you're suggesting that these developers would have to add this whole other process just for managing the deployment of the DBMS package—and probably the OS it's running on, too. (Maybe they would even have to add process to manage the VM it's running on, if they were doing everything else until now using autoscaling + swarm auto-join.)
Developers put DBMSes in containers because they're developers, not DBAs. If you are a DBA, then obviously this will seem wrong to you. A DBA wants to manage a DBMS using the DBMS's tooling. Developers, meanwhile, essentially want to manage DBMSes as part of the same "release" as their apps—being able to "pin a dependency" to a specific DBMS version; update the DBMS as part of a commit and see the whole updated stack go through CI to integration-test it; etc. These are development-time concerns that—at small scale—usually override operation-time concerns.
- tracker1 10y agoThis is why I appreciate DBaaS offerings... It makes more sense to run DBs at least closer to the hardware, outside containers, but most developers don't want to be DBAs, so it's better to pay for someone that has all the maint/update scripts written, and not have to deal with many of those issues.
- dgfgfdagasdfgfa 10y agoSure, but then you have other issues with black box databases: 1. Lack of control over configuration and tuning of database. 2. Little control over semantic upgrades, i.e. security updates should be automatic, but one breaking compatibility should not be, but MAY be necessary or desired, so it needs to be possible to upgrade. 3. Failover isn't easy, and the way of handling it is often app- and load-specific. Granted, this won't matter to many people, but there are a lot of reasons not to entirely outsource database concerns from dev.
- PaulKeeble 10y agoActually they ought to matter to everyone, or rather at some point they do matter. Data is different, data has to be upgraded in place, its genuinely not immutable but this isn't also true of the software above it, Databases are software like any other and they should have a similar release cycle because if they don't its much harder to test and push updates.
- koffiezet 10y agoIf you run database containers on a bare metal docker/container os (coreos/rancher/...), your DB's will probably be running a lot closer to the hardware than they would in a VM.
- user5994461 10y agoAnd what's gonna install CoreOS? And what's gonna install Docker? And what's gonna configure Docker? And what's gonna give a configuration to run the Docker image and how?
- sqldba 10y agoThis sounds right to me. As a DBA containers appear to be a nightmare. I'm employed as an absolute expert in my product. A developer may know how to use Docker but are they an expert? Now... * Who is going to look after the middle ground when the database is in the container? * Who is going to be responsible for rewriting enterprise tools to discover those instances to gather metrics? Because none of the traditional methods (WMI, registry keys, etc) are going to work. You've just broken SCCM, ServiceNow, and everything else under the sun. * Who owns the patching? Because WSUS can't discover it and isn't going to be able to patch inside a container. * Who owns the backups? You know backups are complicated right and not just an on/off switch? You have to schedule the backup, but also make sure you're scheduling the backups in a standard way across your hundreds of hosts (now containers), and then validate those backups are actually being taken, and test those backups regularly. Developers couldn't care less about this stuff - it's someone else's problem - my problem - until it's in a container and then nobody is going to do it. * And when something breaks in between, and the business suffers a massive loss of data, who are they going to sue? A liability-free open source project? I don't think so. There's more to being a DBA than just stuffing it in a container and saying, "she'll be right mate".
- kiallmacinnes 10y agoThese are all valid concerns, but, none seem specific to databases and - for companies who have moved even parts of their infrastructure to containers - have been deemed acceptable. (Also, while you mentioned all Microsoft tools here, the same issues apply to Linux based containers)
- koffiezet 10y agoMost of your arguments comes down to "this doesn't fit in my world where windows is king, so it won't work for me". That however, is not a problem of containers. While I don't consider myself to be a pure DBA, I do know Postgres quite well, and manage quite a few both "classic" deploys in a VM and containerized instances. I was the one who created a default Postgres setup/image/config that our devs use, which when it's used correctly and as documented, when it is deployed to production, it is exactly the same as managing a normal instance. For the devs it's simple, their local env is a checkout of a sample env, copy that to their new project, docker-compose up, and they have a database running with pretty much the same config they would get in test, acceptance and production. No surprises, we both know what to expect. Backups? Still the same. Patches? I tell my config management to a pull a new postgres image on the servers and restart the db images during a maintenance window. This makes it actually a lot easier than updating the non-containerized services. > and the business suffers a massive loss of data This scenario should be recoverable in the first place, and should be tested on regular basis. I'm actually setting up a process to automatically verify database recovery using containers, which makes stuff like this a lot easier and more convenient. Spin up container, restore backup to it, full vacuum analyze, pg_check, select counts from every table, select random records from every table, and if possible spin up a test instance of the application (again, very easy if that also runs in a container) where we can run unit tests against the restored database. > who are they going to sue? A liability-free open source project? So when have you last heard about someone suing MS or Oracle when they had data loss? I suggest you read your license agreements... Our entire business runs on such "liability-free" open-source projects. Linux, Postgres, GNU userland, Python, GCC, clang, Boost, Wildfly, Java, ... and it worked out pretty well for us. We're not some hipster startup with nodejs, angular and mongodb "cloud" apps, we provide some mission-critical services for clients that are banks, oil companies, governments, ... with corresponding SLA's. The attitude of our (very tech-focused) management is simple: we don't need liability umbrella's when we _own_ the technology and know what the hell we're doing. If something does go wrong, this would mean that yes, we would be responsible, no point in hiding.