this post was submitted on 13 Jul 2023
62 points (100.0% liked)

Programming

19496 readers
169 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
62
Advice for Operating a Public-Facing API (jcs.org)
submitted 2 years ago by [email protected] to c/[email protected]
3 comments fedilink hide all child comments
 

An OpenBSD developer and the one-man-band behind Pushover gives some advice after 10 years of running a public HTTP API. It's interesting as big companies are happy to publish articles about all the fancy stuff they developed to run some API, but you don't always hear from a sole developer running a service for such a long time.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 14 points 2 years ago

Interesting article, thanks for sharing!

I've run a (nowhere near as popular) public API for just about 10 years now. Definitely relate to the bit where he mentions people simply retrying the same request when they get an error. ๐Ÿ˜‚

I get a lot of students using the API for learning projects, which is great! But it also means my rate limiting is more often protecting my server from accidental infinite loops, rather than anything purposely abusive.