Interestingly enough, the Qt framework (very common in cars) uses a rather clever trick to avoid that. The QtWayland module allows to create your cluster on the compositor level instead of application level. That way, each widget can be its own process and crash at will. QtRemoteObjects even sync C++ object across either the network or QNX IPC so the logic can also be in its own process and crash at will.

In a way, it's like microservices, but completely implicit to the developers, without explicit serialization and all the way to the "individual pixels" on the screens.