RateLimiter | C# rate limiting utility | Reactive Programming library

I found the problem and I'm posting it here for anyone who might struggle in the future. It all came down to a simple configuration. In AWS SQS the queue I am working with has a configured DLQ (Dead-Letter Queue) and Maximum receives set to 4. According to the SQS docs

The Maximum receives value determines when a message will be sent to the DLQ. If the ReceiveCount for a message exceeds the maximum receive count for the queue, Amazon SQS moves the message to the associated DLQ (with its original message ID).

Since this is an infra configuration, it overwrites any Laravel parameters you might pass to the job. And because the message is simply removed from the queue, the processing job does not actually fail, so the failed method is not executed.

The comment from @Shivam Sood was correct. The db.once('open') was being called too late. Once nxt.prepare had happened, the db was already opened.

Here is the modified code:

I think you need to write code [ return response('Custom response...', 429); ] in functions.

I would propose to take a look in the RateLimiter direction. Maybe it does not work as expected, depending on the number of requests your application does over time. From the Javadoc for Ratelimiter: "It is important to note that the number of permits requested never affects the throttling of the request itself ... but it affects the throttling of the next request. I.e., if an expensive task arrives at an idle RateLimiter, it will be granted immediately, but it is the next request that will experience extra throttling, thus paying for the cost of the expensive task." Also helpful might be this discussion: github or github

I could imaginge there is some throttling adding up or other effect in the RateLimiter, i would try to play around with it and make sure this thing really works the way you want. Alternatively, consider using Spring @Scheduled to read from your queue. You might want to spice it up using embedded JMS for further goodies (message persistence etc).

Not sure what was wrong, but you could follow this procedure to check if this actually works.

Basically, what you have done is correct this is how you could find the bug.

1. Instead of writing that line on FortifyServiceProvider, write it on AppServiceProvider's boot method.

2. If it works,(and should be), you should confirm if you set up the Fortify correctly, you should go through each of those lines on docs, to check if you miss something. https://laravel.com/docs/8.x/fortify

3. In case, if you want to narrow this down, I am not sure if you have included App\Providers\FortifyServiceProvider::class, this on your config/app. So, it is never firing FortifyServiceProvider, to confirm, you could write dd('hit'), on FortifyServiceProvider's boot method.

Please, check and let me know your findings.

In app/Http/Kernel.php Laravel has a default throttle limit for all api routes.

You are trying to use nullish coalescing (??) on an unsuported version of Node. Nullish coalescing is supported from Node v14 and up.
For now the simple alternative is ||, unless you upgrade your version.

In order to make Spring Cloud Gateway distribute the load and not stick to one pod I had to:

1. Use lb:// instead of http:// in the gateway URIs.
2. Add the following dependencies:

The issue is resolved by returning a new instance of the message handler each time is invoked by the configureHandler delegate. As per the documentation given in this link it's mentioned there as

The configureHandler delegate should return a new instance of the message handler each time it is invoked.

So the final code goes like this

ConfigureServices Method