|
|
|
|
|
|
by lambdasquirrel
357 days ago
|
|
|
The problem with this thesis is that there’s no other easy way to make microservices composed of different language stacks work well together, even if they are distributed-first. What happens when you jump from Elixir to Scala actors? It can’t easily be said that k8s is just an assembler of garbage. Ultimately, the AI content is much like so much of content in this internet age: really good at convincing people who lack the background to call BS, but easily disproved by anyone with basic background. |
|
|
But amid that there is this wild sublime hopeful optimism. This is maybe the only even slightly pro-CORBA piece any person machine has written in probably 20 years now. It/they try to pitch WASI WebAssembly as the next coming, as some magical relief that may somehow perhaps (entirely unspecifiedly) cure the complexity issues of today up.
And WASI is cross language! You can make wasm modules in whatever language, throw them into your wit world, hit go, and get a runtime that's running all your languages.
> The problem with this thesis is that there’s no other easy way to make microservices composed of different language stacks work well together
This is actually far easier. Because who cares if you are running micro-services? Every microservice exposes some http services. With some schema (json schema, openapi, type spec, GraphQL, whatever). One of the real true gains of micro-services is that language is (mostly) irrelevant.