• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
  • Knute Snortum
Sheriffs:
  • Liutauras Vilda
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Joe Ess
  • salvin francis
  • fred rosenberger

Docker in Action: primary users of Docker - developers or DevOps?

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Who are primary users of Docker - developers or DevOps?  Should developers read this book?
 
Sheriff
Posts: 7421
504
Mac OS X VI Editor BSD Linux
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm not an author, but I can give an insight from my own experience.

I'd say it depends on the company size, structure. However, worldwide I'd trust both roles/teams equally use that.

If the company is very disciplined about their deployment procedures, policies as it may have a huge and serious (very) consequences because of failed deployment, perhaps DevOps would be the ones who would take care of dockerizing apps and plugging the deployment into the pipeline of release, etc..

If the company works on many different products, projects at the same time, and there are multiple product owners which maye have dedicated developer teams, I'd say software engineers/developers do such stuff themselves as opposed to everything letting to go through DevOps.

But that is my experience having worked in both scenarios.
 
Author
Posts: 11
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There are many use cases for the portability, isolation, and repeatable runtime that Docker images and containers provide.  These use cases are primarily important to software engineers, build & release engineers, platform engineers, and systems engineers.

Software engineers interested in keeping their local development environment clean, avoiding 'works on my machine' problems, and publishing software that can be operated in production easily should find the concepts and practices of containerization useful.
 
Saloon Keeper
Posts: 21593
146
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I can only add my own emphasis to Stephen's response. There are basically 3 ways to ensure that a complex application that you created will install and run cleanly the first time it hits production.

1. Nuke your whole disk and re-install everything every time you run a test (or at least enough of them).

2. Create a VM so that you can do #1 above, but virtually. Vagrant is good for this, as a single command can create a new ready-to-prime system from scratch or destroy it when you're done and do it much faster than a traditional OS install.

3. Put the app in a container.

Of the three, containers are much tidier. The installation process is generally simpler and it's more obvious what files outside of the primary application directories are affected. And, since containers are portable, you can dump the project on some other sucker and run.
 
Don't play dumb with me! But you can try this tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!