14 discussions in the community
we've started seeing some abuse patterns on our websocket endpoints, with clients opening hundreds of connections or sending thousands of messages per...
we're dealing with the classic problem of our mobile and web clients hitting the same core APIs, which often leads to bloated responses or inefficient...
we're in the early stages of designing a plugin architecture for our b2b saas platform, similar to how shopify or figma allow extensions. the goal is ...
we've started seeing some abuse on our websocket connections, with individual users (or bots) opening hundreds of connections or sending thousands of ...
we're discussing implementing a Backend-for-Frontend (BFF) pattern to better serve our different client applications (web, iOS, Android). currently, a...
our team recently completed a migration of about 15 inter-service APIs from REST over HTTP/1.1 to gRPC over HTTP/2. the primary driver was P99 latency...
We're re-evaluating our API strategy, and the Backend-for-Frontend (BFF) pattern has come up. Currently, our web, iOS, and Android clients all hit the...
Our team is working on building a plugin architecture for our B2B SaaS platform, similar to how Shopify apps extend their core product. We want third-...
we just finished migrating about 15 core services from rest to grpc for inter-service communication, and it's been a mixed bag. on the one hand, we've...
We're currently scaling our public API to handle about 10,000 requests per second, and rate limiting is a big part of that. We're trying to decide on ...
we're working on improving our public api rate limiting strategy. currently, we're using a token bucket algorithm at our api gateway, handling about 1...
we're seeing some attempts at abuse on our websocket-based real-time services, mostly in the form of clients opening hundreds of connections from a si...
we're starting to design a plugin architecture for our B2B SaaS platform, aiming for extensibility similar to how Shopify apps work. we want third-par...
we're working on improving our public api rate limiting strategy. currently, we have some basic rate limiting at the edge using our api gateway, but t...