Comment by aussieguy1234
14 hours ago
This is highly relevant to the recent craze over microservices, which has settled down now (after un-neccasarily complicating systems at multiple companies).
14 hours ago
This is highly relevant to the recent craze over microservices, which has settled down now (after un-neccasarily complicating systems at multiple companies).
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.
2 replies →