Page History

Welcome back.

Starting this step let's look at Docker in combination with Microsoft visas a prerequisite for these specific steps is an understanding of Microsoft visas.

We have a couple of videos in the appendix to help you understand what is a Microsoft is and what are the advantages of Microsoft visas.

I would recommend you to check out those videos before going further with the next steps.

If you already have an understanding of Microsoft visas then go ahead.

A lot of people talk about the advantages of Microsoft visas.

Microsoft visas do not come for free.

There are a lot of challenges which are associated with Microsoft visas and docker plays a crucial role in solving a number of these challenges in this step.

Let us get a 10000 feet overview of these challenges and how Dhaka helps in solving these challenges in a micro services architecture.

Instead of building one large monolith we will build a number of smaller micro services.

It might be 10 micro services hundred micro services or thousand micro services.

Each of these micro services can be built with different technologies.

Because these micro services are very small the number of deployments increase exponentially.

If you have a monolithic application and you are doing little 10 deployments per day.

If you build the same application in a micro services architecture you might be doing a hundred or a thousand deployments per day. 

Let's say you're billing Microsoft is one with Java.

Microsoft is two with Python.

Microsoft is 3 with no jobs.

If you have different deployment procedures for each of these micro services then it becomes really really difficult to maintain. 

And that's where Docker really helps.

Irrespective of whether Microsoft uses the Java micro services or Python micro servers or nodes micro servers are built using any other technology you can create an image which can be run anywhere.

So Docker helps you to build a jolly image or Python image or an object image and once you have a darker image the way you run it is very very similar.

So Docker makes development easier by helping us to adopt new technology faster.

We don't really need to worry about how to deploy something that we need to do is to create an image following the standards and irrespective of the kind of application the image can be deployed and  you'll have fewer enviornment issues you'll no longer have issues thing.

It works in my local because it's the same container image which can be run in local as well as in your neuron.

So if something does not work on the environment there is a high chance it will not work on your local machine as well and the other thing is the operations becomes very very easy because you have consistent deployment automation across different environments and different technologies.

As far as the operations is concerned they don't really need to worry about what's inside the Docker image as long as the Docker image is good and it runs the application well.

You can take it and deployed wherever you would want and because of this you can have consistent deployment automation across different environments and different technologies.

If all your micro services are built up as containers then you can also build a lot of technology around these containers.

You can have standard procedures for monitoring for scaling deployment and you can make use of container orchestration tools as well.

I think Docker provides a lot of flexibility for your MAC Services architectures and I think it is playing one of the most crucial roles in the evolution of Microsoft PCs and their jobs as well.