Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learn Docker - Fundamentals of Docker 19.x

You're reading from   Learn Docker - Fundamentals of Docker 19.x Build, test, ship, and run containers with Docker and Kubernetes

Arrow left icon
Product type Paperback
Published in Mar 2020
Publisher Packt
ISBN-13 9781838827472
Length 592 pages
Edition 2nd Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Dr. Gabriel N. Schenker Dr. Gabriel N. Schenker
Author Profile Icon Dr. Gabriel N. Schenker
Dr. Gabriel N. Schenker
Arrow right icon
View More author details
Toc

Table of Contents (25) Chapters Close

Preface 1. Section 1: Motivation and Getting Started
2. What Are Containers and Why Should I Use Them? FREE CHAPTER 3. Setting Up a Working Environment 4. Section 2: Containerization, from Beginner to Black Belt
5. Mastering Containers 6. Creating and Managing Container Images 7. Data Volumes and Configuration 8. Debugging Code Running in Containers 9. Using Docker to Supercharge Automation 10. Advanced Docker Usage Scenarios 11. Section 3: Orchestration Fundamentals and Docker Swarm
12. Distributed Application Architecture 13. Single-Host Networking 14. Docker Compose 15. Orchestrators 16. Introduction to Docker Swarm 17. Zero-Downtime Deployments and Secrets 18. Section 4: Docker, Kubernetes, and the Cloud
19. Introduction to Kubernetes 20. Deploying, Updating, and Securing an Application with Kubernetes 21. Monitoring and Troubleshooting an App Running in Production 22. Running a Containerized App in the Cloud 23. Assessments 24. Other Books You May Enjoy

Kubernetes service

The moment we start to work with applications consisting of more than one application service, we need service discovery. The following diagram illustrates this problem:

Service discovery

In the preceding diagram, we have a Web API service that needs access to three other services: payments, shipping, and ordering. The Web API should never have to care about how and where to find those three services. In the API code, we just want to use the name of the service we want to reach and its port number. A sample would be the following URL http://payments:3000, which is used to access an instance of the payments service. 

In Kubernetes, the payments application service is represented by a ReplicaSet of pods. Due to the nature of highly distributed systems, we cannot assume that pods have stable endpoints. A pod can...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime