Open DeadmanAbir opened 1 day ago
Hi @DeadmanAbir,
May I work on this issue will solve it by using redis
to save user's ip
With RateLimiterRedis
It is very easy
We can customize it like
const rateLimiter = new RateLimiterRedis({
storeClient: redisClient,
keyPrefix: 'rateLimiter',
points: 2, // 2 requests
duration: 24 * 60 * 60, // 24 hours
});
Hi @DeadmanAbir,
May I work on this issue will solve it by using
redis
to save user's ip WithRateLimiterRedis
It is very easyWe can customize it like
const rateLimiter = new RateLimiterRedis({ storeClient: redisClient, keyPrefix: 'rateLimiter', points: 2, // 2 requests duration: 24 * 60 * 60, // 24 hours });
Hi @DeadmanAbir,
May I work on this issue will solve it by using
redis
to save user's ip WithRateLimiterRedis
It is very easyWe can customize it like
const rateLimiter = new RateLimiterRedis({ storeClient: redisClient, keyPrefix: 'rateLimiter', points: 2, // 2 requests duration: 24 * 60 * 60, // 24 hours });
Hey do we have to deploy redis by our own or it's free of service?
@DeadmanAbir We have to deploy it our self but we can use a free tier from render.com
or other because we will be using it for only ip rating
@DeadmanAbir May I implement the fix
@DeadmanAbir We have to deploy it our self but we can use a free tier from
render.com
or other because we will be using it for only ip rating
render is slow ig for free tier. Is there any alternative options to go for inhouse deploments?
Implement rate limiting to the backend of our LinkedIn Agent, restricting each unique user to 2 accesses every 24 hours in the playground. This is crucial as we are providing in-house API keys for LLMs and Proxycurl, necessitating controlled usage to prevent abuse.
src/app/api/agent/route.ts
By implementing this rate-limiting feature, we enhance the security and reliability of our LinkedIn Agent backend, ensuring resources are used appropriately and service availability is maintained for all users.