Implement rate limiting about beeping HOT 6 OPEN

In memory database is fine, Redis is great for distributed BeePing cluster as well. By default we can use memdb and we can implement Redis for advanced BeePing installation after.

from beeping.

It sounds great but I don't want to store any data on disk for scaling reason, I want to be full stateless on BeePing. I'll think of a convenient way to do this.

Thanks !

from beeping.

I don't think it'll be possible to actually store any data persistently without doing that. I suggested memdb for that reason, because it runs entirely in-memory. Redis is another option for that as well. You'll have to have some persistence across time timeframe that you want to check for rate limiting. I'd be happy to hear of other options you come up with though, this can pose an interesting engineering problem 😄 .

Aaron (insp3ctre)

from beeping.

Just to be clear, I won't be able to dedicate the time to implementing a database into BeePing to solve this problem. However, if you implement it, I'd be happy to look it over.

Cheers,
Aaron (insp3ctre)

from beeping.

Hi Aaron,

For sure it will be my work, there is a lot of refactoring needed for this feature. I'm still looking for time to do this but be certain our discussion on this issue will be implemented on BeePing.

Thanks for your review proposal.
Yann

from beeping.

Awesome, I look forward to seeing it!

Cheers,
Aaron (insp3ctre)

from beeping.