So I spent like 2 weeks learning docker and configuring it for one of company’s project. After that, I wanted build and deploy containers to production. Started reading online, freaked out and now I have changed my mind, we don’t really need docker in production, too much issues, too much risk, really, like 70% articles from search results are talking about issues they faced using docker, and that’s fucking a lot, comparing to the gain (which in our case is just easier deployment for small projects).

Oh and did I tell you that we don’t have pipelines in our deployment process? Well, we don’t ...

Though, for development docker is fucking awesome.

  • 0
    Were the issues more on niche applications or also in common applications ?
  • 0
    IMHO there seems to be a noticeable "blur" between different roles. Are you developing or are you also responsible for devops?
  • 0
  • 0
    @FilipeRamalho I think it doesn’t matter, you will mostly face the same issues. Anyway, those articles are mostly about large enterprise applications with millions of requests, running microservices as separate containers, running other n services to deal with data persistence and stuff and of course dealing with distributed servers. In short apps with real infrastructure, and for them using docker really makes sense.

    And just to mention a few of these issues are OS kernel bugs that docker team doesnt fix, docker policy on breaking changes and the one that kept me away from docker was data persistence (imagine if your mysql container crashes, you kind of lose all your data). And extra to that you need to be extra careful with running commands in all those containers.

    Of course, there are workarounds, but is it worth your time?

    In my opinion docker for common or small niche apps is overkill so it’s better to deploy your apps in old school way.
  • 1
    @gintko I looked a bit into docker and one of the questions I had was about data persistence and yes that's really not ideal.
  • 1
    @nbamaral well, developers should know a little bit devops too, small companies usually can’t afford to hire professionals, and dealing with hosting companies is a fucking nightmare. And developer himself is responsible for his local environment too (docker, vagrant). And in my case, I just having fun learning things, but yeah docker in production that’s quite too much for me.
  • 2
    Learning (and knowing how everything works) is useful and commendable . Taking the responsibility for a good deployment, while being payed just as an ordinary developer is a big step you should consider.
    Just an heads up. Now it's your app and your concept, tomorrow you're expected to do it for someone's else latest fad.
    I do both, but I usually just have to deal with myself anyway 😛
Your Job Suck?
Get a Better Job
Add Comment