A Solution: The Sidecar Pattern

The Sidecar Pattern pairs each service with a second helper part called a sidecar. The sidecar takes over some of the supporting work of the main service. The sidecar and the main service run as separate processes in separate containers, deployed together in the same pod. They talk to each other over localhost, which makes the pair a self-contained unit that is easy to deploy and manage.

Flexibility

Remember how we talked about the lack of flexibility being a major issue with monolithic applications. The Sidecar Pattern addresses it directly