hi all, the author of the article here :) The book that is linked has been translated into 4 languages and does a good job explaining what is a sidecar. No nee

hi all, the author of the article here :) The book that is linked has been translated into 4 languages and does a good job explaining what is a sidecar. No need to buy, you can download it for free from here https://developers.redhat.com/books/kubernetes-patterns https://developers.redhat.com/books/kubernetes-patterns The article is for Kubernetes savvy readers, and the main takeaways (which I agree I failed to convey clearly) are these: - You can consume generic capabilities from a sidecar through HTTP/gRPC, rather than include these capabilities into a microservice's runtime as a library. - There are many sidecar examples today (some in a Pod, some shared) Envor, Cloudstate, Skupper, etc. Sidecar is an implementation detail. It can be with containers in a Pod, or it can be a shared sidecar per namespace or host machine - next to a monolith. The best example today, that provides generic developer primitives as a sidecar is Dapr. - Kubernetes Operators encapsulate operational knowledge into executable form and shipped to software consumers as an "Ops-included" mentality. I explained in more details the concept of consuming distributed system capabilities from sidecars in this article http://www.ofbizian.com/2020/05/multi-runtime-microservices-architecture.html http://www.ofbizian.com/2020/05/multi-runtime-microservices-... and webinar https://www.youtube.com/watch?v=CZPEIJFJV9k https://www.youtube.com/watch?v=CZPEIJFJV9k