Dividing the functionality of an application into separate processes can be considered as the Sidecar pattern. The Sidecar design pattern allows you to add many features to an application without the need for additional configuration and code of third-party components.
Just as a sidecar is attached to a motorcycle, similarly in software architecture, a sidecar application is connected to the parent application to extend or enhance its functionality. The sidecar application is loosely coupled with the main application.
Sidecars are a great way to share code between multiple services, especially the operational stuff as you mentioned. In a few projects at work, I've relied on Kubernetes to manage the sidecar stuff.
Dividing the functionality of an application into separate processes can be considered as the Sidecar pattern. The Sidecar design pattern allows you to add many features to an application without the need for additional configuration and code of third-party components.
Just as a sidecar is attached to a motorcycle, similarly in software architecture, a sidecar application is connected to the parent application to extend or enhance its functionality. The sidecar application is loosely coupled with the main application.
nice introduction, thanks
Nice article Fernando.
Sidecars are a great way to share code between multiple services, especially the operational stuff as you mentioned. In a few projects at work, I've relied on Kubernetes to manage the sidecar stuff.
Also, thanks for mentioning my article! 👍