News for hackers. Stuff that matters.

A comment on eBPF will help solve service mesh by getting rid of sidecars. Parent comment

Re:eBPF will help solve service mesh by getting rid of sidecars by p_l on Thursday December 09, 2021 @10:25AM (#29498362)
In a world without (D)COM, I find it's much, much harder to make common base libraries and force people to use them, especially if you can't also force limit the set of toolchains used in the environment.
[ Parent | on HN ]
Re:eBPF will help solve service mesh by getting rid of sidecars by outside1234 on Thursday December 09, 2021 @10:41AM (#29498602)
The network is the base library - that is the shift you are seeing. You make a call out to a network address with a specific protocol.

Also, as an aside, I think WebAssembly has the potential to shift this back. In a world where libraries and programs are compiled to WebAssembly, it doesn't matter what their source language was, and as such, the client library based approach might swing back into vogue.

[ Parent | on HN ]
Re:eBPF will help solve service mesh by getting rid of sidecars by jjtheblunt on Thursday December 09, 2021 @04:09PM (#29502965)
> The network is the base library

you remind me of the 20+ years ago Sun Microsystems assertion "The Network IS the Computer".

citation: https://www.networkcomputing.com/cloud-infrastructure/networ...

[ Parent | on HN ]
Re:eBPF will help solve service mesh by getting rid of sidecars by rhizome on Thursday December 09, 2021 @10:20PM (#29506053)
Well they did put the dot in dot-com.
[ Parent | on HN ]
Re:eBPF will help solve service mesh by getting rid of sidecars by p_l on Thursday December 09, 2021 @10:52AM (#29498787)
WASM isn't a valid target for many languages, that's one thing.

Two, the case is about the library to interact with the network, so... There's also implementing the protocols.

[ Parent | on HN ]