DEV Community

Sina Tavakkol
Sina Tavakkol

Posted on • Edited on

2

40 Days Of Kubernetes (4/40)

Day 4/40

Why Kubernetes Is Used - Kubernetes Simply Explained

Video Link
@piyushsachdeva
Git Repository
My Git Repo

We're going to understand some fundamentals about Kubernetes.
Why, What and How!

Assume we have an application, and it contains some containers such as database, backend, frontend and ... and everyone is happy with them :)

If one of those containers failed, you cannot find a happy person in your team or clients because of a major incident and a downtime.

So we need to take care of them everytime and have some instance of them if the application needs help. I mean, if container A failed, there is at least one another container, let's say container B which can do exactly the duty of container A.

Also, we need something else to manage our workloads such as:

  1. Container Networking
  2. Resource Management
  3. Security
  4. High Availability
  5. Fault Tolerance
  6. Service Discovery
  7. Simplified operations
  8. Resilience
  9. Scalability
  10. Load Balancing
  11. Orchestration and so on.

Image description

But we have to remember: "Kubernetes is not always the solution!"
Specially if we have small application with a few containers, it is waste of resources, money and administration workload on our Operation team.

Image of Timescale

🚀 pgai Vectorizer: SQLAlchemy and LiteLLM Make Vector Search Simple

We built pgai Vectorizer to simplify embedding management for AI applications—without needing a separate database or complex infrastructure. Since launch, developers have created over 3,000 vectorizers on Timescale Cloud, with many more self-hosted.

Read full post →

Top comments (0)

Postmark Image

Speedy emails, satisfied customers

Are delayed transactional emails costing you user satisfaction? Postmark delivers your emails almost instantly, keeping your customers happy and connected.

Sign up