4 ms·
The security, and overall application stability attack vector, is why I now vouch for processes with OS IPC instead of shared libraries, even if it requires mor
by pjmlp 2y ago
The security, and overall application stability attack vector, is why I now vouch for processes with OS IPC instead of shared libraries, even if it requires more resources.
It doesn't fully sort out the trust issue though, even if everything is sandboxed in some fashion.
- uticus 2y agoI know of IPC, but it has never occurred to me to view as an alternative to shared libraries. It's an intriguing viewpoint I'm having trouble wrapping my mind around. Are there battle-tested real-life examples of IPC being used where shared libs could have been used instead?
- pjmlp 2y agoVSCode would be one such example. All the stuff using Android intents, out-proc COM extensions in Windows, XPS in macOS, are other relevant set of examples. I assume you are kind of new to the computing world, OS IPC is how we extended applications almost 40 years before shared libraries became common feature across all major operating systems. Naturally with them being around, shared memory in-process was much easier, and less resource intensive. IPC calls require processes, which take more kernel resources, and context switch. Microservices isn't a new concept, rather re-branding. Sun had as marketing quote, "The network is the computer", exactly because of how it used to be.