-
Notifications
You must be signed in to change notification settings - Fork 52
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
Suggested API #11
Comments
Hey @shlomi-noach I was thinking on providing sensible defaults to be able to spike new applications or services that require throttling functionality, without requiring configuration changes on freno itself. Thus, a request to:
Also, is there any reason why we prefer to call |
@miguelff I was also thinking about defaults, and what I'm concerned about is that we would add an application that calls the API without specifying an Or maybe I'm just being pessimistic. At least, we could keep the existing URI and just have the apps use the name Same can go for
No particular reason. If we find that shorter URIs make a substantial savings for network, we can alias it as much as we like. We can then go for |
Update: we have
|
TODO:
|
Starting with the most basic usage, this Issue will present would-be API endpoints.
/write-request/<app-name>/<store-type>/<store-name>
This is the primary request
freno
would serve: an app connecting and asking "is it OK to write?".examples:
/write-request/spokes/mysql/maincluster
/write-request/gh-ost/mysql/othercluster
Initially we will only support the
mysql
store-type. Other stored may be added in the future.Further comments to this issue will present other API endpoints
The text was updated successfully, but these errors were encountered: