Downloaded 85 times
![Martin Fowler on Microservices:
In short, the microservice architectural style [1] is an approach to
developing a single application as a suite of small services, each running
in its own process and communicating with lightweight mechanisms,
often an HTTP resource API. These services are built around business
capabilities and independently deployable by fully automated
deployment machinery. There is a bare minimum of centralized
management of these services, which may be written in different
programming languages and use different data storage technologies.](https://image.slidesharecdn.com/microservicesatscalewithdockerandkubernetes-amsjug9-2-2017-170216124137/85/Microservices-at-scale-with-docker-and-kubernetes-AMS-JUG-2017-5-320.jpg)
Uploaded byArjen Wassink
Microservices at scale with docker and kubernetes - AMS JUG 2017
The document discusses the concepts of microservices, Docker, and Kubernetes, highlighting their advantages and drawbacks, particularly in the context of scaling applications. It explains microservices as a method to develop applications as a suite of small, independently deployable services while noting the complexities that come with managing distributed systems. Additionally, it provides architectural insights into Docker and Kubernetes, emphasizing their roles in container management and orchestration in cloud environments.
More Related Content
Similar to Microservices at scale with docker and kubernetes - AMS JUG 2017
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
Microservices at scale with docker and kubernetes - AMS JUG 2017
- 1. Micro services atscale with Docker and Kubernetes 9-2-2017 – Amsterdam JUG
- 2. Bedankt voor jullieaandacht “Once you stop learning, you start dying” - Albert Einstein ARJEN WASSINK Principal Consultant a.wassink@quintor.nl @ArjenWassink
- 3. The Menu 1. IntroMicroservices 2. Intro Docker 3. Kubernetes 4. Rolling updates 5. Persisted volumes 6. Stateful services
- 4. 4 Raspberry Pi2B Quadcore 900MHz, 1GB RAM, 16GB SD-card Pi Stack case D-Link network switch Anker USB power adapter Nice white cables Total Cost: +/- EUR 300
- 5. Martin Fowler onMicroservices: In short, the microservice architectural style [1] is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies.
- 6. Microservices: Scaling isimportant https://www.nginx.com/blog/introduction-to-microservices/
- 7. Microservices: advantages ● Theservices themselves are very simple, focussing on doing one thing well; ● Each service can be built using the best and most appropriate tool for the job; ● Systems built in this way are inherently loosely coupled; ● Multiple developers and teams can deliver relatively independently of each other under this model; ● They are a great enabler for continuous delivery, allowing frequent releases whilst keeping the rest of the system available and stable.
- 8. Microservices: drawbacks ● Complexdistributed systems ● Diverse technology stack ● More software projects to manage ● Reliability and performance ● Exponentially more service instances to manage
- 9.
- 10.
- 11.
- 12.
- 13. Docker at scalewith Kubernetes
- 14. Everything at Google runsin containers Launch over 2 billion containers per week.
- 15. web browsers BorgMaster link shard UIshardBorgMaster link shard UI shardBorgMaster link shard UI shardBorgMaster link shard UI shard Scheduler borgcfg web browsers scheduler Borglet Borglet Borglet Borglet Config file BorgMaster link shard UI shard persistent store (Paxos) Binary Developer View What just happened?
- 16. Enter Kubernetes Greek for“Helmsman”; also the root of the word “Governor” • Container orchestrator • Runs containers • Supports multiple cloud and bare-metal environments • Inspired and informed by Google’s experiences and internal systems • Open source, written in Go Manage applications, not machines
- 17. web browsers Scheduler kubectl webbrowsers scheduler Kubelet Kubelet Kubelet Kubelet Config file Kubernetes Master Container Image Developer View What just happened?
- 18.
- 19.
- 20. Pods, Replication sets& (auto)scaling Pod con- tainer con- tainer Deployment Replication Set Pod con- tainer con- tainer Pod con- tainer con- tainer
- 21. Services Pod con- tainer con- tainer Service Cluster IP:port <10.0.0.20:80> NodeIP:port <10.150.42.191:88> Pod con- tainer con- tainer Pod con- tainer con- tainer Loadbalancer Kube Proxy (IP Tables) API server Watches
- 22.
- 23. Worker Node Persistent StorageNode Persistent Volumes Pod con- tainer con- tainer Persisted Volume Persisted Volume Claim Persisted Volume Mount
- 25. Quintor Resources • Docker -Build, Ship, and Run Any App, Anywhere – www.docker.com • Kubernetes - Accelerate Your Delivery – kubernetes.io • Creating a Raspberry Pi cluster running Kubernetes – tinyurl.com/rpi-k8s-cluster @ArjenWassink