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

Feature Request: Saving data for recache #27

Open
Gordon-TheTurtle opened this issue Jun 22, 2019 · 2 comments
Open

Feature Request: Saving data for recache #27

Gordon-TheTurtle opened this issue Jun 22, 2019 · 2 comments

Comments

@Gordon-TheTurtle
Copy link

It would be great to add serialization abilities in liquibook for ease of system restart.

@enewhuis
Copy link
Owner

:D yes, great idea! This one is at the top of my personal list. I've hacked partial support for that on a private branch that is storage specific, but perhaps there is a better generic way to do this. I was thinking Liquibook ought to have both a checkpointing and journal recovery feature so that it could be restarted, load checkpoint state, and then play queued incoming orders.

@Gordon-TheTurtle
Copy link
Author

Yeah, that is a use case every one using liquibook would have for recovery purposes.
I propose to use boost serialization abilities as boost is already integrated.
And then let the user use these abilities as per their needs to give a fine-grained control.

It will also enable the user to save any additional data that they might have themselves, in a single call to save latency, and show a consistent state in case of failure in saving.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants