kidmam / 100DaysOfContainersAndOrchestration

Your go-to open source repo to learn containers (Docker, Podman, etc.) and Orchestration (Kubernetes, ECS, etc.) from start to finish.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

100Days Logo

100DaysOfContainersAndOrchestration

Your go-to open source repo to learn containers (Docker, Podman, etc.) and Orchestration (Kubernetes, ECS, etc.) from start to finish.

GitHub Repo stars

WIP

More to come! This project is a WIP (started January 3rd, 2023). Please note that the days are listed below, but are not completed yet.

Why?

Containers, orchestration, and the overall landscape of running modern applications is changing.

When I first started working in tech, the innovative thing was to have a bunch of bash scripts, batch scripts (yes... batch), and PowerShell scripts run workloads.

We would put a couple of binaries (compiled code) on a server, run some commands or scripts to get them started, and boom... our app was up and running.

Now? We don't even need a dedicated bare-metal server to run our code anymore (wow... I've been working in tech for a long time).

Instead, we can just take a micro-sized binary (a container) and run it anywhere (even on our local computer).

So, why am I creating this project?

For a few reasons:

  1. I've seen the transition from bare-metal to VMs to containers.
  2. It's clear that containers are how we're running workloads today.
  3. There are A LOT of different avenues you can do down when running containers.

The third reason above is the big reason why this open-source project is so important.

There are A LOT of ways to run and orchestrate containers in today's world... and it's not just Kubernetes.

There's also multiple different runtimes to run containers...

The reason for this project is to help you dive deep into all of the different avenues you can take to run containers.

How?

100 Days Of Containers and Orchestration will be from both a theoretical perspective and a hands-on perspective.

The truth is that you cannot have one without the other.

You can't implement a solution if you don't understand it or know the "why" behind it.

An example of this is...

Kubernetes is the latest and greatest right now and you want to learn it, but why? Why do you need to learn it in today's cloud-native world?

Or beter yet, why does your organization need to use Kubernetes? Do they actually need Kubernetes? Is there another solution that gives you the same result as Kubernetes in an easier fashion?

As you're going through 100 Days Of Containers and Orchestration, yes, you'll learn the technical pieces and see/use the code... but you'll learn something even better.

The "why" and the "how" that'll help you in implementing a solution like containers and orchestration platforms.

The App

100 Days Of Containers And Orchestration will be a lot of theory and hands-on components for deploying containers and orchestration, but to deploy a container, you need an app.

The app that will be used is the GoWebAPI that I built. It's a web API that can be run anywhere.

You can find it here

Don't worry about doing anything with the app right now as you'll learn everything that you need to do with the app throughout this project.

Days

About

Your go-to open source repo to learn containers (Docker, Podman, etc.) and Orchestration (Kubernetes, ECS, etc.) from start to finish.