Container Orchestration Explained 

And at writing backwards.

Couln't be truer. I almost feel like I'm becoming a cloud-guru, simply because of these videos. Kudos to IBM for this.

@@ericsiggyscott173 They just mirror the video lol

@@ericsiggyscott173 😂😂😂😂

IBM is best at solutions

We love to hear that, Adam!

Glad to hear it, Bala. We appreciate you watching our videos.

See ibm.biz/write-backwards

Thank you, Nagakalyan!

@@IBMTechnology at 5:50 , I have heard Sai stating that as part of netweorking orchestration helps achieve singular point of access to the services (based on the video). Does it mean , the orchestration platform spinf a load balancer/would it be a single IP to all the simlilar services (example front end, back end , data base services).

Thanks for watching!

I have the same question

To help anyone who sees this comment: Containers themselves do not contain an OS.. but what a container does is create a new interface/bridge between the processes inside of the container and the host/baremetal OS. For example, say I make a system call in my program to see what files are in the local running directory of the program. This is done by calling an OS function that does interaction with the kernel. What containers do (which is why it is called virtualization), is it asks the host kernel to create an interface that "lies" to the running process about what it is seeing as its local environment (a "virtual" environment one could say). So when the process asks the kernel through system call what the heck is going on, the kernel gives it a virtual likeness of what is going on. This allows the OS to impersonate different file structures/networking/compute resources different from its actual setup (though not different kernels). Because of this, we can target a specific version of an OS and guarantee our application's local environment by virtualizing it with a container, and gives us an easy way to describe and share our target environment. Containers are not "virtual OSes", they are more aptly described as "virtualization of the OS environment for a group of one or more processes".

You're welcome! 👍

Thank you Ryan!

Writes would be typically done directly to primary DB. at set intervals, there would be a delay in DB syncing primary to replica, this way read from replica is always available. During the synch, the replica would be locked. Kubernetes [container orchestration] is capable of setting up primary and multiple replicas, you just have to define in the YAML file.

We will take a look at that. --Sai

You can write stuff normally and then mirror the video)

@@MinecrafterKost No reason to ruin the illusion. :)

Yes, that's right!

@@svennam92 is it correct to say that the only benefit of using a service mesh (istio) with kubernetes are features like rate limiting, circuit breakers, improved telemetry? I'm asking because we are currently using consul for service discovery and gradually shifting to kubernetes but not sure if we need a service mesh too

And you want 3 backend services? Is any of this relevant for a typical startup that can manage just fine with one server?

Hi Mauro...many people think I do, but here's an explanation of how we make these videos. these videos here: ibm.co/2SA1vGd Thanks for checking us out, San

I thought the same thing... nice. Thanks IBM to clarify our question.. :)