[jimktrains2]

65ms feels like a lot. I guess you can cache it so you're only calling once per IP.

[jonathan-kosgei]

I understand what you mean, but every other provider from the tests I've done comes in at double our speeds some even over plain HTTP. We only serve requests over HTTPS

More importantly the performance is consistent and you'd get the same performance wherever you were in the world.

[jimktrains2]

Why compare to another API endpoint? You should compare it against accessing a local database.

[jonathan-kosgei]

Comparing a network call vs filesystem i/o wouldn't be a useful comparison for someone deciding between different third part API providers.

[jimktrains2]

Why not? I can load an IP database locally, so it's an option and a "competitor" to a 3rd party API. That's what I'm comparing it to, not against other APIs.

[jonathan-kosgei]

It's pretty obvious that hitting your local disk is going to be a lot faster than making a network call. Make the right decision for your use case.

[JoeAltmaier]

Maybe in this case. But historically, exactly this decision point has oscillated. It's caused reversals in distributed computer design for decades. First the networks were slow and disks were (relatively) fast - so each machine had one. Then networks went Ethernet, and disks started disappearing. Disks got down to a few ms access time and they came back. Then Gigabit came around. Then SSD.

Today I'd say it depends upon exactly what your network data source latency measures out to. The answer could go either way.