0 reactions
A New Node.js library
When you scale a Node.js backend using `node:cluster`, you run into a surprisingly annoying problem:
**How do you rate-limit external APIs like Stripe or OpenAI while making sure all workers share the same rate limit?**
The first solution that comes to mind is usually: *"Just use Redis."*
But does it really make sense to introduce additional infrastructure complexity, network overhead, and an entire external dependency just to coordinate a few API calls coming from the same server?
That's exactly why I built **cluster-rate-limiter**.
A Node.js library that gives you coordinated rate limiting across workers, powered entirely by Node.js's native IPC messaging, with no Redis and absolutely zero external dependencies.
Rather than diving into the internals here, here's what you get out of the box:
* **Zero Setup:** Install it and start using it. No additional infrastructure required.
* **Developer-Friendly API:** The `run()` method accepts your `fetch` call or any function directly, along with all its arguments. No complicated callback patterns.
* **Two Types of Limits:** Supports both Semaphore-based concurrency limits and Duration-based rate limits for enforcing strict time windows, such as those imposed by Stripe APIs.
* **Typed Errors:** If a request times out waiting for permission, the library throws a clear, specific error that you can easily translate into an HTTP `429 Too Many Requests` response.
And when it comes to performance, the core data structure for tracking request timestamps uses a **zero-allocation approach** built around a `Float64Array` ring buffer.
This eliminates the need for repeated array reallocations and significantly reduces garbage collection pressure under heavy load.
If you're interested in the low-level details, I've explained the ring buffer implementation and how it reduces memory overhead in the README.
If you're running a clustered Node.js backend and want to avoid the overhead of introducing Redis just for rate limiting, check out the links below, explore the architecture, and let me know what you think!
#js #programming #dev #technology
When you scale a Node.js backend using `node:cluster`, you run into a surprisingly annoying problem:
**How do you rate-limit external APIs like Stripe or OpenAI while making sure all workers share the same rate limit?**
The first solution that comes to mind is usually: *"Just use Redis."*
But does it really make sense to introduce additional infrastructure complexity, network overhead, and an entire external dependency just to coordinate a few API calls coming from the same server?
That's exactly why I built **cluster-rate-limiter**.
A Node.js library that gives you coordinated rate limiting across workers, powered entirely by Node.js's native IPC messaging, with no Redis and absolutely zero external dependencies.
Rather than diving into the internals here, here's what you get out of the box:
* **Zero Setup:** Install it and start using it. No additional infrastructure required.
* **Developer-Friendly API:** The `run()` method accepts your `fetch` call or any function directly, along with all its arguments. No complicated callback patterns.
* **Two Types of Limits:** Supports both Semaphore-based concurrency limits and Duration-based rate limits for enforcing strict time windows, such as those imposed by Stripe APIs.
* **Typed Errors:** If a request times out waiting for permission, the library throws a clear, specific error that you can easily translate into an HTTP `429 Too Many Requests` response.
And when it comes to performance, the core data structure for tracking request timestamps uses a **zero-allocation approach** built around a `Float64Array` ring buffer.
This eliminates the need for repeated array reallocations and significantly reduces garbage collection pressure under heavy load.
If you're interested in the low-level details, I've explained the ring buffer implementation and how it reduces memory overhead in the README.
If you're running a clustered Node.js backend and want to avoid the overhead of introducing Redis just for rate limiting, check out the links below, explore the architecture, and let me know what you think!
#js #programming #dev #technology
0 reactions
The Shirky Principle Explained: Why Teams Preserve the Problems They Solve
#technology #programming #dev
#technology #programming #dev
0 reactions
My intent with using LLMs is to use it as a search engine and not as an explainer or even teacher.
I think it would be bad to use LLMs as a 24/7 teachers because even human teachers that are 24/7 available would be bad.
I will use LLMs in my future still, but the use of it is my decision to make.
I have already studied a bit of cs50 and understand the basis of the basis. But I think finding solutions yourself without using llms for any explaining is good. You could possibly use it as a search engine where you ask simple questions instead of mentioning your whole problem.
#programming #dev #technology
source
I think it would be bad to use LLMs as a 24/7 teachers because even human teachers that are 24/7 available would be bad.
I will use LLMs in my future still, but the use of it is my decision to make.
I have already studied a bit of cs50 and understand the basis of the basis. But I think finding solutions yourself without using llms for any explaining is good. You could possibly use it as a search engine where you ask simple questions instead of mentioning your whole problem.
#programming #dev #technology
source