-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Epic: Get rid of db-sync #9198
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
Labels
Comments
Old workspace cluster table PR: #8539 |
1 task
This was referenced Sep 26, 2022
This was referenced Nov 7, 2022
This was referenced Nov 14, 2022
Merged
This was referenced Nov 22, 2022
This was referenced Nov 29, 2022
5 tasks
continues here |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
This is the epic for getting rid of
db-sync
, which was already discussed at length in the context of "Simplified Multi-Meta" in this RFC.Context
Value
Acceptance Criteria
db-sync
Measurement
db-sync
deployment anymore, and we're still able to deploy to prod 🙃Notion
Discussion related to this epic is in Notion.
Tasks
latency
toxic.slow-server
deployment which connects tomysql
through Toxiproxy.proxy
to route websocket connections with theslow-database
protocol header to theslow-server
deployment.slow-database
websocket connection header from websocket connections from dashboard based on the value of a feature flag./api/*
endpoints #14960api/*
connections to the webapp team #14962server
JSON RPC-API #14964server
endpoints #14965slow-server
. #15297slow-server
. #15298auth/workspace-cookie
redirect #15328slow-server
#15655The text was updated successfully, but these errors were encountered: