Containers made the sidecar pattern ubiquitous. However, a few years ago I recall reading about a pattern for desktop applications where, instead of having a monolithic desktop app handle logging and monitoring, a parent process was responsible for launching the main desktop app, perform health checks and monitoring its lifecycle, and even handle over-the-air updates or relaunch the desktop app in case of failure.
In this case, the main desktop app would be designed as a kind of sidecar which handles the bulk of responsibilities, while the parent process handled monitoring.
Does anyone happen to come across this pattern?
Aucun commentaire:
Enregistrer un commentaire