A pod is a collection of containers. The original suggestion was to pair them, so you’d have a backend container and a frontend container living within the same

A pod is a collection of containers. The original suggestion was to pair them, so you’d have a backend container and a frontend container living within the same pod. This is wasteful for the reasons I listed. You can shove the backend and the frontend into the same container, but it’s needless. > The most likely scenario in that case would be having a backend-for-frontend pattern, so the FE and its BFF would still go in the same pod, and the other services would probably go in different pods. They are still two different concerns and don’t need to both be served from the same pod (the BFF pattern doesn’t even remotely require this). You of course can do whatever you want, but shoving different things together (even if coupled via an API) is an anti pattern.