> Now you have a network overhead problem if the containers are on different machines, so there's something called a "pod" to make them run on the same machine.

> Now you have a network overhead problem if the containers are on different machines, so there's something called a "pod" to make them run on the same machine. This is not correct. A pod is a collection of processes which share the same life cycle. They are expected to scale simultaneously, shut down simultaneously, and restarted simultaneously. > This is what the author calls a "sidecar". The author may be tangled in his own jargon. This assertion is also quite wrong, and appears to sprout from your misconception of what a pod is. The concept of a sidecar is very old and well established. A sidecar is a process that is designed to run alongside a master application to augment or offload is functionalities. You can define a pod so that one process is the master application and one or more applications are sidecars. There is no overlap or misconception. > Cloudflare says a "sidecar" is another container inside a "pod", but one that is for some auxiliary function rather than being one of the main microservices doing the work. Hence the name "sidecar". The link in the article for "sidecar" is to the author's book, so you have to pay to find out for sure. The concept is decades old, probably older than you and me. No need to depend on Cloudflare or the author's books to check that out.