157 discussions in the community
So, I've been trying to figure out how to make an API faster, you know, the kind that gets way more reads than writes. It's started to get a little sl...
hey everyone, i'm working on a new project with a few external consumers and we're thinking about how to handle api versioning. we've seen different a...
we're building a new api that's expected to have a massive amount of reads but very few writes. think real-time analytics dashboards. we're considerin...
hey everyone, im architecting a new set of microservices and we're gonna need a clear strategy for api versioning. we want to avoid breaking changes f...
hey all, i'm wrestling with api rate limiting for a new service. we've got a lot of users behind shared ips, like corporate networks or public wifi. i...
hey everyone, im working on a new service and we're at the point where we need to think about api versioning. we want to make sure we can evolve the a...
Hey everyone, I'm designing a new API endpoint for creating a resource that has a bunch of optional attributes. I'm trying to figure out if I should p...
So, I've been mulling over stateless versus stateful API designs, particularly when you're working with microservices. Stateless APIs get a lot of pra...
Hey everyone, I'm trying to figure out API rate limiting for a new service we're building. I'm stuck between tracking limits per user account or per I...
hey everyone, i've been thinking a lot about how to handle api versioning as our services grow. weve used the url path versioning (like /v1/users) so ...
hey ppl, im wrestling w a common api design choice and wanted to get ur thoughts. when filtering collections of resources, when do u prefer using quer...
Hey everyone, I'm trying to figure out service discovery for our microservices, and it's getting crazy. Services are popping up and disappearing all t...
i've been thinking about idempotency for POST requests lately, specifically for operations that create resources. it's straightforward for PUT or DELE...
hey everyone, im thinking about the best way to handle API versioning as our system grows and changes. weve seen a few approaches like URL versioning ...
Hey everyone, I'm trying to nail down a consistent and secure way to handle authentication across our microservices. We've been looking at JWTs, OAuth...
hey everyone, im working on scaling up our microservices and have hit a common roadblock, rate limiting. we're using an API gateway, but as traffic gr...
hey everyone, i'm trying to decide on the best way to handle api versioning for a new microservice. should we go with the classic /v1/users and /v2/us...
hey everyone, ive been thinking a lot about scaling our databases recently. we're hitting some limits with our current setup, and sharding seems like ...
Hey folks, i'm wrestling with ensuring message order when multiple producers might send messages related to the same entity to a message queue. we're ...
hey everyone, ive been wrestling with api versioning lately. it feels like every time we introduce a breaking change, we either have to force a migrat...
