It boils down to: - optimise the amount of data you send (see graphql/this perso... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

crispyporkbites on Aug 31, 2020 | parent | context | favorite | on: How should we build the APIs of tomorrow?

It 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 on Sept 1, 2020 [–]

I 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/

Join us for AI Startup School this June 16-17 in San Francisco!
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact