architechtetural thoughts about dockerizing the exsting services

we are in the process of dockerizing existing services those use kafka, storm
and the expectation is use to create dockerized builds by integrating with jenkins .

I happened to look at a couple of articles http://blog.howareyou.com/post/62157486858/continuous-delivery-with-docker-and-jenkins-part, they are helpful.

  • How to disable the root access of a docker container?
  • How can I tell if docker has frozen?
  • VirtualBox and Nginx very slowly serving cached static JS and CSS files
  • AWS ECS container logs design pattern
  • Would Docker swarm assist me with managing containers with specific environment variables?
  • Docker init Daemon best practices (PID 1 zombie reaping)
  • I wanted to know the experiences with docker and how much time it took for the dockerizing a typical solution. And are there any best practices ?

  • Error on docker build of React app: Cannot resolve module
  • How to pass environment variable values into files in the docker container I'm trying to run
  • Generation of pdf PDFBox headless docker container fails
  • Should I use Vagrant or Docker for creating an isolated environment? [closed]
  • docker Unable to connect to archive.ubuntu.com:http: [IP: 209.6.3.210 80]
  • Is there any way to provide Run parameters to a docker container image when starting a container from openstack nova?
  • One Solution collect form web for “architechtetural thoughts about dockerizing the exsting services”

    There are lots of best practices: https://docs.docker.com/articles/dockerfile_best-practices/

    I think the “time to dockerize” will depend a lot on how familiar you are with linux. If you’re already used to setting up linux systems, it should be pretty fast.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.