An overview about Containerization & Microservices.

1. A Primer to Containerization &
Microservices
Shiju Varghese

2. About Me
• Consulting Solutions Architect
• Focused on Go and Google Cloud
@shijucv | https://medium.com/@shijuvar

4. Agenda
• Introduction to Microservices
• Introduction to Containerization
• An Overview of Container Ecosystem
• Microservices on Containers

5. Microservices

6. Monolith Microservices
• Composed of a suite of small
services.
• Each service runs in its own
process.
• Greater flexibility for scalability.
• Put all business capabiliKes
into a single applicaKon.
• ApplicaKon runs in a single
process.
• Scales horizontally by running
mulKple instances of monolith.

7. Microservices is an architectural style in which software
applications are composed of a suite of independently
deployable, small, modular services. Each of these
Microservices focuses on completing one task that
represents a small business capability. They
communicate with each other using language-agnostic
protocols such as Representational State Transfer
(REST), or messaging systems.
In a nutshell, Microservices are small, autonomous
services that work together.

8. » Software broken up into functional components.
» Componentization via Services in which each service
is packaged as one unit of execution.
» Independent, autonomous process with no
dependency on other Microservices.
» Services are organized around business capability.
» Decentralization of Data Management.
» Independently replaceable and upgradeable.
Autonomous Services around Bounded
Context

9. Communication between Services
» Synchronous
» REST
» Asynchronous
» AMQP
» RabbitMQ, Apache Kafka, Cloud native Pub/Sub

10. Key Benefits
» Tackles the problem of complexity.
» Flexibility for Polyglot technology stack.
» Resilience.
» Flexibility for Scalability.
» Ease of Deployment.
» Organisational Alignment.
» Composability.
» Optimising for Replaceability.

11. Deploying Microservices

12. Unit of Deployment
» Physical Server
» Virtual Machine (VM)
» Container

13. Deployment Patterns
» Multiple Service Instances per Host
» Service Instance per Host
» Serverless Deployment
» AWS Lambda
» Google Cloud Functions

14. Running Microservices on Containers

15. A collection of independent, autonomous
containers participating in an application
defines the Microservices architecture.
Microservices - Unit of Deployment of
as Container

16. Container
» Lightweight Linux environment.
» Hermetically sealed, deployable app.
» Separate apps from infrastructure.
» Develop app against an idealized OS - A static Linux
environment.
» Popularized and revolutionized by Docker.

17. Why Do Developers Like It?
» Reliable deployment
» Static application environment; Immutable infrastructure
» Portability
» Separate applications from where it runs
» Repeatable runnable artifact
» Run anywhere
» Speed and Lightweight
» Boots in seconds
» 100 -1000 containers on one machine.
» Loosely Coupled
» Compose apps from autonomous Microservices

18. Docker
Docker is an open-source engine to easily create
lightweight, portable, self-sufficient containers
from any application. The same container that a
developer builds and test on a laptop can run at
scale, in production, on VMs, private cloud,
public clouds and more.

19. » Open platform for containers.
» An ecosystem for build, ship, and run distributed
applications.
» A lightweight container virtualization platform.
» Built on LinuX Containers (LXC)
» Written in Go language.

20. Components of Docker
» Docker - A portable, lightweight runtime and
packaging tool for building containerized apps.
» Docker Hub - Software as a Service platform for
sharing and managing Docker images.

21. Docker Fundamentals
» Docker Images - Images hold your apps.
» Docker Registries - Registry for sharing Docker
images via Docker Hub or private registry system.
» Docker Containers - Create containers from Docker
images to run apps.
» Dockerfile - A text document that contains
instructions to build a docker image.

22. Docker Compose
Compose is a tool for defining and running multi-
container Docker applications.

23. # golang image where workspace (GOPATH) configured at /go.
FROM golang
# Copy the local package files to the container’s workspace.
ADD . /go/src/github.com/shijuvar/go-web/taskmanager
# Setting up working directory
WORKDIR /go/src/github.com/shijuvar/go-web/taskmanager
# Get godeps for managing and restoring dependencies
RUN go get github.com/tools/godep
# Restore godep dependencies
RUN godep restore
# Build the taskmanager command inside the container.
RUN go install github.com/shijuvar/go-web/taskmanager
# Run the taskmanager command when the container starts.
ENTRYPOINT /go/bin/taskmanager
# Service listens on port 8080.
EXPOSE 8080

24. // Build image from Dockerfile
$ docker build -t taskmanager .
// Run Docker image and publishing a web app
$ docker run —publish 3000:8080 —name goweb —rm taskmanager

25. Container Clusters
» Docker Swarm
» Google Kubernetes
» CoreOS Tectonic
» Apache Mesos

26. Container-Centric Micro OS
» CoreOS
» Ubuntu Snappy
» RancherOS
» Red Hat Atomic Host
» VMware Photon

27. Containerization on Cloud

28. Container as a Service (CaaS)
» Google Container Engine
» Amazon EC2 Container Service

29. Shiju Varghese
gophermonk@gmail.com