3 ms·

I love how the major issue, that both this article, and the original article warn about is: don't use docker on 'CORE APPS'.... That says all you need to know

I love how the major issue, that both this article, and the original article warn about is: don't use docker on 'CORE APPS'.... That says all you need to know about the trustworthiness of Docker. EVEN DOCKER PROPONENTS caution against using it in 'important' apps.... What apps are people investing time in that aren't 'important'? Is there a coffee machine that is ok to use for a docker app somewhere?

sheeshkebab 10y ago
AWS was also considered not a fit for running "core" apps and databases... look where we are now. Docker is certainly having some teething issues - and things like kubernetes are certainly WIP. But I wouldn't be as skeptical - plenty of companies use it in production already, for "core" apps.
- nickthemagicman 10y ago
  Interesting, yeah I truly see the potential of the idea. It's definitely the future. Really glad to see Google and others getting on board and giving them the resources they need.
user5994461 10y ago
> Is there a coffee machine that is ok to use for a docker app somewhere? Most coffee machines are docker ready. To guarantee you the best experience, you will need to setup a pair of coffee machines, plus an orchestration system that will be responsible for swapping them automatically when one ran out of coffee. Note: There are only prototype of orchestration systems. Nothing for sale in the corner shop yet. --- More seriously... Not important: Most internal, development, and test systems Somewhat important: Web applications, various support micro services. (They all are stateless, with multiple instances, and reactive failover by their respective load balancers). Critical: Most databases (especially the ones without multi-master mode and automatic failover), trading applications, payment systems, accounting systems, databases with money $$$
- nickthemagicman 10y ago
  Haha a coffee load balancer. I love that idea. I'm sure Amazon will have a coffee machine web service they offer for $2000/month. ACS. This whole ordeal has actually been a really really good lesson for me about mature vs less than mature apps. It's been really enlightening to read the posts and discussion.
flurdy 10y ago
I interpret that as don't use X (in this case Docker) with your most essential services. Initially. Get your teeth cut, make some mistakes, establish routines, etc with your internal apps, your low traffic services, etc. Be patient, then once comfortable and confident your start to roll it out to your core, heavily integrated services in production. Having just come off a year at large(very large) government department that have 100s of core services running in Docker in production, I think the tech is ready, but not sure if every company is ready.
- nickthemagicman 10y ago
  Hmmmm, if you need ton's of workarounds and there's a huge learning curve to learn the weird quirks(bugs), I don't think the tech is necessarily stable...

sheeshkebab 10y ago

AWS was also considered not a fit for running "core" apps and databases... look where we are now. Docker is certainly having some teething issues - and things like kubernetes are certainly WIP. But I wouldn't be as skeptical - plenty of companies use it in production already, for "core" apps.

nickthemagicman 10y ago
Interesting, yeah I truly see the potential of the idea. It's definitely the future. Really glad to see Google and others getting on board and giving them the resources they need.

user5994461 10y ago

> Is there a coffee machine that is ok to use for a docker app somewhere? Most coffee machines are docker ready. To guarantee you the best experience, you will need to setup a pair of coffee machines, plus an orchestration system that will be responsible for swapping them automatically when one ran out of coffee. Note: There are only prototype of orchestration systems. Nothing for sale in the corner shop yet. --- More seriously... Not important: Most internal, development, and test systems Somewhat important: Web applications, various support micro services. (They all are stateless, with multiple instances, and reactive failover by their respective load balancers). Critical: Most databases (especially the ones without multi-master mode and automatic failover), trading applications, payment systems, accounting systems, databases with money $$$

nickthemagicman 10y ago
Haha a coffee load balancer. I love that idea. I'm sure Amazon will have a coffee machine web service they offer for $2000/month. ACS. This whole ordeal has actually been a really really good lesson for me about mature vs less than mature apps. It's been really enlightening to read the posts and discussion.

flurdy 10y ago

I interpret that as don't use X (in this case Docker) with your most essential services. Initially. Get your teeth cut, make some mistakes, establish routines, etc with your internal apps, your low traffic services, etc. Be patient, then once comfortable and confident your start to roll it out to your core, heavily integrated services in production. Having just come off a year at large(very large) government department that have 100s of core services running in Docker in production, I think the tech is ready, but not sure if every company is ready.

nickthemagicman 10y ago
Hmmmm, if you need ton's of workarounds and there's a huge learning curve to learn the weird quirks(bugs), I don't think the tech is necessarily stable...