Re:Amazon Ion – A richly-typed, self-describing, hierarchica...
by jkhdigital on Friday November 19, 2021 @10:57PM
(#29285433)
Classic example of a leaky abstraction, and the principle that implementation details inevitably become undocumented API behavior.
[ Parent
| on HN ]
Re:Amazon Ion – A richly-typed, self-describing, hierarchica...
by kabdib on Friday November 19, 2021 @11:24PM
(#29285544)
A lot of "transparent RPC" systems are like this. "It's just like a normal function call, it's sooo convenient" . . . until it isn't, because it involves the network hardware and configuration, routing environment, firewalls, equipment failure . . .
Re:Amazon Ion – A richly-typed, self-describing, hierarchica...
by andylynch on Saturday November 20, 2021 @05:12AM
(#29286835)
I’ve worked on systems like this too - the max packet size is very well documented.
Then post trade it all gets turned into FIXML which somehow manages to be both more verbose and less readable.