-
Notifications
You must be signed in to change notification settings - Fork 1k
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
refactor(server): Refactor replica #472
Conversation
Signed-off-by: Vladislav Oleshko <[email protected]>
std::unique_ptr<base::IoBuf> io_buf{new base::IoBuf(128)}; | ||
unsigned consumed = 0; | ||
RETURN_ON_ERR(ReadRespReply(io_buf.get(), &consumed)); // uses parser_ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really like the whole we-are-throwing-bytes-around-manually vibe. A parsed response with RAII semantics (drop or re-assign) would be really handy... But its likely over-engineering
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the moment you get me a PoC with "set" only replication that includes full-sync and the journal - you do whatever refactorings you want plus 👸🏼 to marry plus half 👑 .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PoC is in the replication branch 😎 I'll do the refactoring sometime later. Its just the more hard code we have, the more efforts we need in the future to fix it all
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Lets keep it like now if everything is fine |
Migrating replication branch on main, part 5
The replica became an manageable 1k LOC mess 🤯 Time to fix technical debt 🔧 🔨
Mixed implementation: