No post body was provided.
Ask HN: What infrastructure would you use to host an open, free JSON-based API?
1–10 of 11 posts
Re: Ask HN: What infrastructure would you use to host an open, free JSON-based API?
#2It would help if you have some additional context. Use case, volumes, cost objective...
Re: Ask HN: What infrastructure would you use to host an open, free JSON-based API?
#3given the limited amount of context, i would go with:
kotlin+jooby+jersey
Re: Ask HN: What infrastructure would you use to host an open, free JSON-based API?
#4Heroku is the easiest set up imo
Re: Ask HN: What infrastructure would you use to host an open, free JSON-based API?
#5The free tier of AWS Lambda gives you up to 1 million calls per month. You could use this for the actual fulfillment of your data. Paired with AWS API Gateway (1 million calls for free per month for the first year), it seems that you could do this relatively cheaply.
The only thing I haven't accounted for here is if you're querying against some sort of database, which would incur additional hosting costs.
Re: Ask HN: What infrastructure would you use to host an open, free JSON-based API?
#6Django / Zappa
Which is basically AWS lambda / gateway with minimal setup and extremely cheap.
Re: Ask HN: What infrastructure would you use to host an open, free JSON-based API?
#7FaaS/Serverless will be a good starting point for something like this, so either AWS Lambda, Azure Functions or Google Cloud Functions will be good enough.
Re: Ask HN: What infrastructure would you use to host an open, free JSON-based API?
#8What's the nature of your data? Is it static or dynamic?
Re: Ask HN: What infrastructure would you use to host an open, free JSON-based API?
#9In the odd case that the json is static hugo and s3 make for a painless deployment.
Re: Ask HN: What infrastructure would you use to host an open, free JSON-based API?
#10What's the nature of your data? Is it static or dynamic?
^ important. If you're trying to provide free access, I always seek ways to mitigate cost. If the API can be slowly updating, like once a day or w/e, then I stick everything behind a static CDN or something such that it should cost you next to nothing. Just a small CPU somewhere to build the JSON endpoints per update cycle.