jonathan-kosgei

I haven't worked with it yet, but it looks to me to be a Python framework just like Japronto or Flask but one that is focused heavily on building APIs.

It would also take some work to scale

We aggregate the data from a couple of sources, see https://ipdata.co/about.html

Thanks! I'm excited to try this and benchmark it against my current setup!

The article is about building a fast and highly available API distribution architecture. You could just as well apply it to anything you want to build.

I will agree that it's not for everyone. And would probably more likely appeal to indie makers like myself.

If anything it's closer to - How I built a multi-regional apigateway API with multiple creative workarounds despite there being no official way to do it and it only becoming possible to do so 5 months ago :)

Awesome! thanks for sharing! I'm always looking for optimizations. Any idea whether fastly would support running out of specific regions? Or how many endpoints they have?

Thanks! :)

I had no idea apistar existed, it certainly didn't come up when I was doing my research. But it looks pretty full featured, thank you for this!

Thanks! They do! And the best part is by the time you start getting charged it's because you've grown and are probably already making $$. Enough at least for the business to pay it's own expenses :)

Good point

Hi! The author here :) I recommend just using a text logo for starters. With maybe an icon from flaticon.

Here's one from Shopify that should be decent https://www.shopify.com/tools/logo-maker

I used API Gateway and Lambda to serve 20M API calls last month on ipdata.co for a little over $100.

Something to note, latencies decrease with increased usage due to fewer cold starts. I've seen latencies as low as 17ms in our busiest region with ~40ms in less busy regions.

Hey vinrob, big fan!

I'm running https://ipdata.co which is an IP Geolocation API. It's been 5 months so far with 20M API calls served last month. The project is not yet providing the majority of my income however there's been tremendous and very promising growth!

By IP address, referer and api key.

I'll mock up something really simple that does just that in the next couple of weeks.

Thanks!

Lambda + API Gateway + Dynamodb

$X could be spread out over the lifetime of the consumer to remove the initial costs of setup.

I'd probably do the same thing. If I'm not using a service a lot I don't want to pay for it or I only want to pay when I use it.

Otherwise for constant usage I'd prefer to be able to know my spending ahead of time.

There's actually a free tier of 1500 requests a day for development.

Thanks for all the feedback and sorry for the connection hiccup.

This is still a very early version of the service. Account management is currently limited to signing up via Stripe and getting an email with your API key and a how to get started guide :)

I can make the free tier more obvious, you really don't need an account or credit card to get started with the API that's why "Get Started" links to the docs. You can just copy and paste the commands/code examples and get started. I see now that's it's not at all clear and will fix this.

Otherwise I'd say the pricing units are really just the number of calls. A really interesting idea might be to have a comparison on the site between my service and Maxmind's web service!

Some really basic account management like you describe is very much in the works. There're currently no accounts on the site. But it's something I'd like to do possibly offering a higher free tier quota to users who sign up, so that I'm able to communicate with them and have stats on conversion etc

It's actually $0.001 per call

Please try now.

Please follow this link https://ipdata.co/ the site is up, just checked.

What I do is ask the user to sign up for the new plan and refund them on a prorated basis for their usage of the first.

But good point I should make this more clear in the faqs.

I'm looking to either cut some of the plans or move to cost per usage, maxmind offer downloads of their data. If I remember correctly their webservice is charged per request but is way more expensive compared to my fixed plans. Whereas I charge by based on an API usage bucket.

A fixed monthly absolutely does, because;

1) I can offer discounts on annual prepayments which helps cash flow and gives the user a bargain

2) The payment is upfront and there's no need to send dunning emails at the end of the month when several user's card payments fail.

I actually do both those things! I have a free tier of 1500 requests a day and once you subscribe you get an email when you're at 90% your usage.

It's actually called on each page load so I imagine you'd 100% go for the flat rate :)

This wouldn't make it easier for users to figure out :)

And to handle traffic spikes. I however pad my user's daily quotas (by a percentage of their plan) to be able to handle temporary spikes up to a certain point.

Thanks for replying. To give you some context the API is ipdata.co pricing at ipdata.co/pricing.html I've gotten feedback from multiple users that my pricing is overwhelming. The API is pretty much feature complete and my main focus right now is selling.

Thanks :) It's less geared towards censorship and more toward keeping potentially malicious users at bay for example preventing credit card fraud, preventing users from signing up for multiple free trials that kind of thing.