Comment by rusk
13 hours ago
Micoserices or Monolith. It’s like being caught between the devil and the deep blue see. It’s a pity domain sockets never took off but I guess TCP/IP is the only truly cross platform IPC mechanism …
13 hours ago
Micoserices or Monolith. It’s like being caught between the devil and the deep blue see. It’s a pity domain sockets never took off but I guess TCP/IP is the only truly cross platform IPC mechanism …
Aren't Windows's named pipes very similar?
I believe so.
I don’t think either that or domain sockets are quite as ubiquitous as TCP sockets though.
The issue I see with domain sockets is that although they may be supported for example by spring, you can’t rely on a consistent cross platform experience which is perhaps (anachronistically?) a core ethic of the Java community.
I would favour domain sockets as to make a component go from being embedded to networked would require a small but significant implementation step.
But established best practice unfortunately disagrees with me.
The more interesting thing on Windows would actually be COM, which is something like Java interfaces but for native code, that are optionally cross-process.
1 reply →