Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
50 Kubernetes Concepts Every DevOps Engineer Should Know

You're reading from   50 Kubernetes Concepts Every DevOps Engineer Should Know Your go-to guide for making production-level decisions on how and why to implement Kubernetes

Arrow left icon
Product type Paperback
Published in Jan 2023
Publisher Packt
ISBN-13 9781804611470
Length 278 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Michael Levan Michael Levan
Author Profile Icon Michael Levan
Michael Levan
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Part 1: First 20 Kubernetes Concepts – In and Out of the Cloud
2. Chapter 1: Kubernetes in Today’s World FREE CHAPTER 3. Chapter 2: Getting the Ball Rolling with Kubernetes and the Top Three Cloud Platforms 4. Chapter 3: Running Kubernetes with Other Cloud Pals 5. Chapter 4: The On-Prem Kubernetes Reality Check 6. Part 2: Next 15 Kubernetes Concepts – Application Strategy and Deployments
7. Chapter 5: Deploying Kubernetes Apps Like a True Cloud Native 8. Chapter 6: Kubernetes Deployment– Same Game, Next Level 9. Part 3: Final 15 Kubernetes Concepts – Security and Monitoring
10. Chapter 7: Kubernetes Monitoring and Observability 11. Chapter 8: Security Reality Check 12. Index 13. Other Books You May Enjoy

Investigating stateless and stateful apps

At a high level, applications come in two forms – apps that need data stored and apps that don’t care whether the state of the data is stored. Let’s think about two different scenarios.

When you log in to your Gmail account, or another email service provider, everything stays where it’s supposed to be. You can see the emails in your inbox, the sent messages, the emails in your trash bin, and so on. The application/platform stays how it’s supposed to be because the data is stateful. Now, on the opposite side of the spectrum, let’s take www.google.com into consideration. When you go to www.google.com in a web browser, you always have a fresh start. The entry box to type in your question is there, but the results to the previous question that you asked Google isn’t there. It’s always a fresh, clean slate. That’s because www.google.com is stateless, as in, it doesn’t just...

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 $19.99/month. Cancel anytime
Banner background image