express-rate-limit VS Ts.ED

express-rate-limit is an npm library that provides a rate limiting middleware for Express, so it's easier to limit repeated requests to all APIs or only to specific endpoints. The middleware allows you to control how many requests the same user can make to the same endpoints before an application starts returning 429 Too Many Requests errors.

I think the readme gets included automatically even if you don't specify it in the files field, ditto for package.json.

Compare https://github.com/express-rate-limit/express-rate-limit/blo... to https://www.npmjs.com/package/express-rate-limit?activeTab=c...

Agree with you about the other points.

Express-rate-limit: A simple to use rate limiter for your Express apps. This can protect your applications from being overwhelmed by too many requests.

Implementing API rate limiting in your Node.js project is an important step toward maintaining the stability and reliability of your application. With the use of packages like express-rate-limit or rate-limiter-flexible, you can easily set limits on requests and prevent abuse of your API by malicious users.

One option would be to bake rate-limiting middleware into your service. For example, in express-rate-limit you can define a keyGenerator function that takes an HTTP request and extracts the key that should be rate limited. I assume there are similar middleware packages for other frameworks. This approach would get the job done and it would be transparent to your customers.

We are using Express, so we added the middleware express-rate-limit to our server-side code. If you are using Flask, there is Flask-Limiter. If you are using Django, there is Django Ratelimit. Laravel includes basic rate limiting.

The rate limiting middleware limits the number of requests that come from a specific user, IP address or location within a given window (period of time). This can be achieved using a package called express-rate-limit as middleware

is your server express? i have used this package with Redis https://www.npmjs.com/package/express-rate-limit works pretty well

The last feature is a rate limit to prevent spam. Highscore has no auth system all endpoints are public and can be accessible by anybody. That's why adding a rate limit is useful to prevent abuse requests for a malicious users. For this, I used the very good express-rate-limit library which does the job perfectly. Like all other features, you can configure the rate limit using env variables.

Ts.ED - Controller-based (DI supporting) backend framework that seems to offer quite a lot (although I'm wary of it being quite close to Nest.js)

Take a look at ts.ed. They have some similar feature

has anyone looked at tsed.io

As a developer, it's always important to find ways to streamline the development process and save time. For the past two years, I've been using Ts.ED as the framework for all of my applications and it's been a game-changer. Not only has it allowed me to gain back lost development time, but it's also been the foundation for my open-source project HighScore.

I use Ts.ed as framework, go to this site to known more about this awesome framework.

Because of this, I decided to create a base template of a REST API created with NodeJS, using Ts.ED as the base framework and TypeScript as the programming language. This template tries to follow the principles of Domain Driven Design and implements a Clean Architecture/Hexagonal Architecture to try to rely as little as possible on the infrastructure and the framework while keeping in mind at all times the language and the needs of the business logic.

I love Ts.ED https://tsed.io

I'd also love to shout out Ts.ED which is another great Typescript framework that I've written production applications with. It's a natural fit for anyone who loves .NET applications, it's why I chose it.