How I Took an API Side Project to 250M Daily Requests

Re:How I Took an API Side Project to 250M Daily Requests by kpsychwave on Saturday July 01, 2017 @05:39PM (#14679189)

Given the fast lookup time, it would be useful if you could provide a JS API fot synchronous loading.

Essentially, a blocking script in the dom <script src="...api.js" /> that prepopulates the window object. With clever error handling, this could improve perceived performance significantly.

A few questions:

1. What differentiates you from ip-api.com and other providers?

2. Do you use MaxMind?

3. Is there an option for no-throttling? 100s of simultaneous requests?

I aggregate multiple IP databases for my SaaS (https://www.geoscreenshot.com) and I need highly performant / reliable IP look ups.

[ Parent | on HN ]

Re:How I Took an API Side Project to 250M Daily Requests by Etheryte on Saturday July 01, 2017 @05:42PM (#14679201)

Why would you _want_ a synchronous, blocking script in the first place?

[ Parent | on HN ]

Re:How I Took an API Side Project to 250M Daily Requests by kpsychwave on Saturday July 01, 2017 @09:52PM (#14680351)

For conditionally loading other blocking assets in JS.

For example, if IP is in China, local fallback for Google CDN as it will fail.

[ Parent | on HN ]

Re:How I Took an API Side Project to 250M Daily Requests by Etheryte on Sunday July 02, 2017 @05:09AM (#14681610)

You can also do all of these things asynchronously, without blocking the whole page.

[ Parent | on HN ]

Re:How I Took an API Side Project to 250M Daily Requests by kpsychwave on Wednesday July 05, 2017 @04:28PM (#14705833)

Yes but like all async ops not without expense to the UX.

[ Parent | on HN ]