You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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!
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
The text was updated successfully, but these errors were encountered: