5 ms·
Enjoyable read but not much here. Strange that there's no concept of edge computing or caching referenced in the article, from what I could tell.
by jayd16 6y ago
Enjoyable read but not much here. Strange that there's no concept of edge computing or caching referenced in the article, from what I could tell.
- alonsonic 6y agoAgree, the author doesn't paint the picture of what might be coming. Would love to hear from the HN crowd on what's coming next in API design. I see a lot of buzz around grpc, will this be the next standard?
- crispyporkbites 6y agoIt boils down to: - optimise the amount of data you send (see graphql/this persons agent idea) - optimise where you send it to/from The latter has a hard limit of c, which we’ll always try to move towards. Distributed computation helps, but trades off speed/consistency. The question then becomes whether you can have an inconsistent model for those few seconds.
- adamkl 6y agoI always thought this was a pretty interesting take on the future of web applications/APIs, and aligns pretty closely with what you describe: https://tonsky.me/blog/the-web-after-tomorrow/ https://tonsky.me/blog/the-web-after-tomorrow/
- fallous 6y agoYou invite the problem of eventual vs strong consistency, split brain issues, etc. There's a reason that the two hard problems in computing are naming things, cache coherency, and off by 1 errors.