explain Kubernetes like I'm five and if you're lucky i may share my legos with you
For further actions, you may consider blocking this person and/or reporting abuse
explain Kubernetes like I'm five and if you're lucky i may share my legos with you
For further actions, you may consider blocking this person and/or reporting abuse
Node.js doesnβt stop from running other operations because of Libuv, a C++ library responsible for the event loop and asynchronously handling tasks such as network requests, DNS resolution, file system operations, data encryption, etc.
What happens under the hood when Node.js works on tasks such as database queries? We will explore it by following this piece of code step by step.
Yisus777 -
Zach Rabie -
Jochem Stoel -
Amar Prakash Pandey -
Once suspended, rapidnerd will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, rapidnerd will be able to comment and publish posts again.
Once unpublished, all posts by rapidnerd will become hidden and only accessible to themselves.
If rapidnerd is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to George Marr.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag rapidnerd:
Unflagging rapidnerd will restore default visibility to their posts.
Top comments (4)
When the kindergarten goes to visit a museum or play in the park, you need a couple of grown ups to take care of you.
The grownups are the ones that
One big difference between this example and an orchestrator, is that k8s doesn't hesitate to "kill" instances that misbehave and start new ones.
!remindme 3 days
Wait, this isn't Reddit.
Kubernetes is just a Theme Park :)
Blogged a longer explanation here
My favorite material about this:
Docker runs containers. Kubernetes orchestrates containers. Orchestration is how you stitch multiple containers together into a greater whole: for example, you can have several application containers (and scale out to add more application containers at runtime) talking to a database container. It's possible to do this with Docker alone, but prohibitively complicated at the low level of individual containers. The language of "pods", "services", "deployments", and so on that Kubernetes employs lets you operate at the level of multiple interacting containers instead.