JS SDK v0.4.5 causing excessive WatchDocument requests and server v0.4.4 instability about yorkie HOT 6 OPEN

@hackerwins Since we are using Istio in K8s, we can use Istio(envoy)'s Rate Limit. 

For implementation details, we use istio-ingressgateway as a rate limiter middleware by applying the rate limit configuration envoyfilter, and rate limiting service as a rate limit counter.

from yorkie.

Sorry about that. It wasn't a DDos attack and I think it was my fault. 🥲

I created a new yorkie example around 3:00 on the 27th and ran it locally with yorkie-js-sdk v.0.4.5.
As soon as I ran the project with the new version, it kept sending requests to the server. I freaked out, stopped and ran it again, and the same thing happened, so I captured it.

from yorkie.

It may be possible to respond at the infrastructure layer to defend against DDOS, but I think it is necessary to respond at the application level before that. How about introducing RateLimit?

from yorkie.

I think we can introduce rate limits in a couple of places:

A. K8s Ingress

We can utilize rate limit annotations for a straightforward implementation. However, it's important to note that this approach offers global-wide options, which might limit flexibility.

B. API Server

To have more granular control, we can implement rate limit logic using a gRPC interceptor. This approach allows us to define detailed rate limit rules. Additionally, we could provide project-specific options in the dashboard, empowering developers to manage rate limits for their projects effectively.

@krapie Do you have any opinion for A?

from yorkie.