Fahim khan
@morfes.bsky.social
Senior Software Developer | Full stack developer | MEAN | MERN | Golang | Rust | Javascipt | Typescript | Nodejs | Nestjs | React | Angular | Nextjs | Expressjs | AWS | Psql | Mongo | Neo4j | Backend | Frontend | Web3 |
So I can't cash my service that responds with
status: 200
body: error
🥲
/s
status: 200
body: error
🥲
/s
August 20, 2025 at 6:03 AM
So I can't cash my service that responds with
status: 200
body: error
🥲
/s
status: 200
body: error
🥲
/s
RPS from 1,000 RPS to 2,000 RPS. To understand why this is true, you can see that of the 2,000 inbound requests, 1,000 (50%) can be serviced by the cache, leaving 1,000 requests to be serviced by your serving layer.
August 20, 2025 at 5:09 AM
RPS from 1,000 RPS to 2,000 RPS. To understand why this is true, you can see that of the 2,000 inbound requests, 1,000 (50%) can be serviced by the cache, leaving 1,000 requests to be serviced by your serving layer.
Imagine, if you will, that you have a request-serving layer that can handle 1,000 RPS. After 1,000 RPS, the system starts to return HTTP 500 errors to users. If you place a cache with a 50% hit rate in front of this request-serving layer, adding this cache increases your maximum
August 20, 2025 at 5:09 AM
Imagine, if you will, that you have a request-serving layer that can handle 1,000 RPS. After 1,000 RPS, the system starts to return HTTP 500 errors to users. If you place a cache with a 50% hit rate in front of this request-serving layer, adding this cache increases your maximum
