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

Support for clustering [moved] #32

Closed
lvca opened this issue Dec 10, 2012 · 0 comments
Closed

Support for clustering [moved] #32

lvca opened this issue Dec 10, 2012 · 0 comments

Comments

@lvca
Copy link
Member

lvca commented Dec 10, 2012

This is Issue 32 moved from a Google Code project.
Added by 2010-05-10T08:21:55.000Z by l.garu...@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Enhancement, Priority-Medium, v0.9.24

Original description

While Orient KV supports clustering, OrientDB has a richer model and
clustering it's much more complex to do. We're working to find the best
solution thinking to performance, scalability and partitioning.

In the very first phase it will be a multi-master solution where all the
server are synchronized. In this way all the transactions will be ACID
across the servers. Slower but safer.

In the second one replicas will be supported. Replicas can be used as
reas-only instances and are updated asynchrnonously.
@lvca lvca closed this as completed Dec 10, 2012
lvca added a commit that referenced this issue Oct 15, 2015
tglman pushed a commit that referenced this issue Feb 21, 2024
tglman pushed a commit that referenced this issue Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant