Hey folks,
So, I’ve been diving into this whole Domain:port/api thing lately, and man, it’s a rabbit hole. Like, I get it—it’s super flexible and all, but there’s gotta be some best practices, right?
First off, security. Don’t just slap a Domain:port/api out there without at least some basic auth or rate limiting. I’ve seen people get burned hard by bots hammering their endpoints.
Also, naming conventions. Keep it clean, y’know? Don’t make your Domain:port/api look like a toddler mashed the keyboard. /api/v1/resource is way better than /api/randomstuff/12345.
And for the love of all things holy, document your Domain:port/api. Nothing worse than trying to figure out someone else’s spaghetti code without a clue.
What’s your take? Am I overthinking this, or is there more to it?
Cheers!
So, I’ve been diving into this whole Domain:port/api thing lately, and man, it’s a rabbit hole. Like, I get it—it’s super flexible and all, but there’s gotta be some best practices, right?
First off, security. Don’t just slap a Domain:port/api out there without at least some basic auth or rate limiting. I’ve seen people get burned hard by bots hammering their endpoints.
Also, naming conventions. Keep it clean, y’know? Don’t make your Domain:port/api look like a toddler mashed the keyboard. /api/v1/resource is way better than /api/randomstuff/12345.
And for the love of all things holy, document your Domain:port/api. Nothing worse than trying to figure out someone else’s spaghetti code without a clue.
What’s your take? Am I overthinking this, or is there more to it?
Cheers!