3 ms·
Congrats guys. If this works as advertised, this is huge. When I'm making API calls from my app to different services, I know for a fact that there is no extr
by orarbel1 8y ago
Congrats guys.
If this works as advertised, this is huge.
When I'm making API calls from my app to different services, I know for a fact that there is no extra latency that might be caused by a third-party. How do you deal with maintaining low-latency while still having to re-route my original API call?
Again, as someone who dealt with many APIs over the years, I think this kind of service is game-changing.
- sgrove 8y agoGreat question, we spend a lot of time on overall latency questions. If you're hitting a single API endpoint (imagine getting a tweet without getting the user information), we'll introduce an overall latency of ~100-ms. So this may well be slower, and might not work depending on your use case (though we have plans for working on lowering the overall latency). But if you hit more than one API endpoint, or especially if you're jumping between API services, we'll deliver a really big win, in part because of declarative nature of of GraphQL. As we descend each node we know that we can execute the subsequent API requests concurrently, so this usually ends up being an automatic win. And if you're doing something like joining against Salesforce data, we can automatically switch the query to use the SOQL/batch API, which can be both faster and significantly cheaper, all without changing the implementation on your side.