Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce QoS #270

Open
hackerwins opened this issue Nov 10, 2021 · 0 comments
Open

Introduce QoS #270

hackerwins opened this issue Nov 10, 2021 · 0 comments
Labels
enhancement 🌟 New feature or request hard 🧑‍🔬 Difficult to deal with or require research

Comments

@hackerwins
Copy link
Member

hackerwins commented Nov 10, 2021

Description:

Yorkie is exposed directly to external, which puts it at risk of being overwhelmed by resources by unspecified clients.

The Yorkie PushPull API can contain a lot of data in one request. In addition to the simple number of requests, it is necessary to design for the amount of data contained in the request. It may be helpful to refer to the ETCD kv RPC QoS proposal when designing.

Why:

  • In fact, expensive requests may be common. Some newbies will not follow the best practices of Yorkie.
@hackerwins hackerwins added the enhancement 🌟 New feature or request label Nov 10, 2021
@hackerwins hackerwins added this to v0.2 Nov 17, 2021
@hackerwins hackerwins moved this to Todo in v0.2 Nov 17, 2021
@hackerwins hackerwins removed this from v0.2 Dec 14, 2021
@hackerwins hackerwins added this to v0.3 Dec 14, 2021
@hackerwins hackerwins moved this to Todo in v0.3 Dec 14, 2021
@hackerwins hackerwins added the hard 🧑‍🔬 Difficult to deal with or require research label Jun 2, 2022
@hackerwins hackerwins removed this from v0.3 Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement 🌟 New feature or request hard 🧑‍🔬 Difficult to deal with or require research
Projects
Status: Backlog
Status: Todo
Development

No branches or pull requests

1 participant