Introduction
this is part 3 from the journey it's a long journey(360 day) so go please check part 1 and 2, and if you need to walk in the journey with me please make sure to follow because I may post more than once in 1 Day but surely I will post daily at least one 😍.
And I will cover lot of tools as we move on.
Why use both VM and Docker
let's take a case where our team members someone use windows other Mac other Linux , every system have an different configuration .
Let's take another example : in this case our development environment is windows / Mac and our server is Ubuntu . our deployment server have a certain configurations such as Firewall settings . So a good idea here to use same system on both local and deployment (also testing environment) .
Here came the Hybrid system between VM and Docker containers .
so we get something like this figure.
And I like to mention that there is a tool called Vagrant , it will be the second tool in this journey where you can configure VMs using a vagrant file . so you can also ship it with the code so it will be easy to get same configuration on all the environments!
also I like to mention that it's flexible and freedom to move your system between different cloud / servers providers so let's called it
Build once , deploy everywhere.
Top comments (0)