Skip to content

Latest commit

 

History

History
50 lines (32 loc) · 2.92 KB

server_client.md

File metadata and controls

50 lines (32 loc) · 2.92 KB

Docker Client VS Server

Every application/product we use follows client-server architecture either directly or indirectly. Take an example of facebook, twitter, gmail etc. all these applications are based to client-server architecture.

Let's try and understand what do we mean by a client and server. There can be many literal interpretations of the terms client and server when it comes to it's usage, but in general all those means the same.

Index

Client

Client is sort of a gateway or an interface which let's you use the product. It is a layer between a user and some complex implementation which runs the product, Client takes care of providing the user with abstracted layer of interface through which user ends up using the product.

Back to Index

Server

Server is nothing but a compute compatible machine which runs the product and gets requests from clients, Which in turn is recepted and decoded to understand what is it client wants. Servers are responsible for running the product and perform the tasks requested by the client.

Back to Index

Now, we understand what client and server means in computing. Let's dive into what is a Docker Client and Docker Server.

Image

Image courtesy: https://www.xenonstack.com/blog/docker-application-solutions/

Docker Server

Docker as we all know by does all things containers. It provides a container runtime, It is manages container storage, networks, image builds and many other services. No doubt it requires compute power to perform all these tasks. Docker server is nothing but a compute instance (VM, Personal Computer etc.) which is responsible for running docker daemon process which in turn manages all the services provided by docker.

Docker client

To communicate with the docker daemon to execute a certain task like running a container, build some image that are all done via docker client. Now, you'd have probably guessed it, The Docker CLI. Along with Docker CLI, Docker daemon also exposes a REST API which can be used to programmatically access services exposed by the daemon.

A subset view of docker's client and server.

Image
Image courtesy: https://docs.docker.com/engine/docker-overview/

Note:

Soul purpose of this tutorial was to understand the docker client-server architecture, There are several other topics to cover like, What is Docker Registry? These topics among some other advanced ones are explained in future tutorials, Keep following. Happy Dockerizing!

Go to Beginners Index