feat(interactive): Introduce proxy_server
into interactive
#3778
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Originally designed as a standalone graph query system, but in real world scenarios, disaster recovery capabilities is required.
We plan to offering a deployment approach based on master-slave replication, and in order to avoid modifying the core engine, we plan to separate the fault-tolerant features, encapsulating them in a separate server called
proxy_server
.The proxy_server is designed to
It seems that we can not avoid introducing new
actor
,handler
andservice
definitions.The usage of proxy_server
TODO: Currently heartbeat will only return
OK
, however, we needSNAPSHOT_ID
to be returned.