Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!
  • 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
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

How far you can go without full DevOps infrastructure?

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all,

I am just asking because Docker, while simple at the start, requires a complete new mindset related to deployment. And, to me, it looks like to be "production ready" it needs a complete devops infrastructure to be effective.
While experimenting from the command line is quite simple, things can get out of control fast, so the complete "assemble-deploy-manage" shall be in place. Not only Kubernetes or Swarm, but also on the Dev side (whatever you use).

Just my thinking.

Regards

 
Author
Posts: 11
5
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Luca Botti wrote:Hi all,

I am just asking because Docker, while simple at the start, requires a complete new mindset related to deployment. And, to me, it looks like to be "production ready" it needs a complete devops infrastructure to be effective.
While experimenting from the command line is quite simple, things can get out of control fast, so the complete "assemble-deploy-manage" shall be in place. Not only Kubernetes or Swarm, but also on the Dev side (whatever you use).

Just my thinking.

Regards



Great question!

In my experience, most organisations don't have much of a devops infrastructure. Indeed, the company we worked for where we introduced Docker had relatively little.

This is why our book contains a lot of material considered 'impure' Docker - ie not microservices, monolithic and not highly orchestrated 'data centre as an operating system' type work.

Docker helped us turn our monolithic application into a single unit which could be easily shipped for testing or support or dev purposes. We wrote our own simple automation tool to help achieve this - ShutIt

Once this was in place the concepts of phoenix deployment and reproduction of state were more easily digested by devs, test and support alike.

And finally, this could be placed in a DevOps pipeline more easily, as state was more easily recovered.

The book covers all these steps, and is structured to go from 'command line' to fully-orchestrated production deployments.

In terms of things getting 'out of control', this is why Platforms as a Service were created. The one I'm most familiar with (origin/OpenShift) takes care of a lot of the heavy lifting of managing the build and deployment of your images, leaving the dev or ops team to get on with curating this environment.

Ian Miell
 
Ranch Hand
Posts: 343
Mac OS X Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Ian Miell wrote:

This is why our book contains a lot of material considered 'impure' Docker - ie not microservices, monolithic and not highly orchestrated 'data centre as an operating system' type work.

Docker helped us turn our monolithic application into a single unit which could be easily shipped for testing or support or dev purposes. We wrote our own simple automation tool to help achieve this - ShutIt

Ian Miell



I think we are also some impure "Docker" work. Some of our stuff is not microservices at all. Docker is really interesting in the opportunities it seem to provide for all sorts of applications.
 
Ian Miell
Author
Posts: 11
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Palak Mathur wrote:

Ian Miell wrote:

This is why our book contains a lot of material considered 'impure' Docker - ie not microservices, monolithic and not highly orchestrated 'data centre as an operating system' type work.

Docker helped us turn our monolithic application into a single unit which could be easily shipped for testing or support or dev purposes. We wrote our own simple automation tool to help achieve this - ShutIt

Ian Miell



I think we are also some impure "Docker" work. Some of our stuff is not microservices at all. Docker is really interesting in the opportunities it seem to provide for all sorts of applications.



Indeed - it's a very broad and open tool - which makes writing a book on it very challenging!
 
Saloon Keeper
Posts: 22517
151
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Among the things I run in Docker containers:

Gogs: a github-like web application
My Kanban server
Cacti - a web-based network resource monitor
Sonatype Nexus - Maven resource repository and proxy
Jenkins - Build system
Magento (I needed a quick spin-up to support a client)

None of these are what I'd call "microservices". I also run Apache ServiceMix in a container, which itself doesn't qualify as a microservice, but acts as a host for microservices written in Java based on OSGi.

They aren't micro-services, but they're definitely services, and containerizing them makes it easier to keep them from getting all jumbled up with unrelated services. The underlying OS remains relatively clean, and I can spin up and down experimental projects without leaving any residue behind. Or balance my server load by tossing containers from one server to another. Or go the elastic route and spin up multiple instances if it helps me handle loads better.
 
There is no greater crime than stealing somebody's best friend. I miss you tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic