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

load balancing technique #173

Open
REDAL opened this issue Mar 11, 2021 · 3 comments
Open

load balancing technique #173

REDAL opened this issue Mar 11, 2021 · 3 comments

Comments

@REDAL
Copy link

REDAL commented Mar 11, 2021

Hi SLeekDB Community,

what about adding a load balancing for SleekDB, by making it replicate data between multiple points, and saving the sync state, each time sync is made

@Timu57
Copy link
Member

Timu57 commented Mar 11, 2021

Hi @REDAL
That sounds very interesting. What would the use case be like? If SleekDB is split/ replicated on the same drive, that would not make any difference. The only thing that could make a difference is splitting/ replicating it over multiple drives.

@REDAL
Copy link
Author

REDAL commented Mar 19, 2021

Hi @REDAL
That sounds very interesting. What would the use case be like? If SleekDB is split/ replicated on the same drive, that would not make any difference. The only thing that could make a difference is splitting/ replicating it over multiple drives.

I am talking, about replication over multiple servers, not same drive

@netomarchiori
Copy link

Hi @REDAL
That sounds very interesting. What would the use case be like? If SleekDB is split/ replicated on the same drive, that would not make any difference. The only thing that could make a difference is splitting/ replicating it over multiple drives.

I am talking, about replication over multiple servers, not same drive

SleekDB saves files to a folder. I you have GlusterFS in your server and point your document store to a GlusterFS, there you go, replicated files across all your servers!

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

No branches or pull requests

3 participants