62
Advice for Operating a Public-Facing API (jcs.org)
submitted 1 year ago by otl@lemmy.sdf.org to c/programming@programming.dev
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
[-] Fenzik@lemmy.ml 8 points 1 year ago

some esoteric devices and plugins don't support them. In fact, some don't even support HTTP POST properly and will only be able to put form parameters in the URL query string (though you still need to insist on requiring a proper POST method, don't be an animal).

This gave me a chuckle. Good, practical advice for smaller APIs. Bigger orgs are likely to have distributed tracing etc but for a one man show it’s good to have input on what’s proved actually useful and necessary.

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

Programming

17207 readers
210 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 !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz