Orbit-db: [Question] Database replication

Created on 4 Dec 2017 · 5Comments · Source: orbitdb/orbit-db

Hi there,

I am now developing a twitter like web application using orbit-db.
Assume I have a userA who starts a nodeA. He stored all his tweets in a feed type database called tweetsDB. userA posts 1000 tweets in total stored in database tweetsDB.
Now another useruserB on nodeB wants to see the most recent 5 tweets of userA.
So userB would try to connect to tweetsDB.
Does that mean userB has to download (replicate) the whole tweetsDB including those 1000 tweets in order to see the most recent 5 tweets?

Thank you

question

Source

shd101wyy

Most helpful comment

Hi @haadcode ,

Thank you much for your reply. It's extremely helpful.
I have a few other questions here. I just want to make sure that I understand everything correctly before I continue my project with the fancy orbit-db library ;)

You said that I could use await db.load(5) to load the database with 5 latest operations (tweets) locally or listen to replicated event for the data update happened remotely. Is there a way to load the 5 oldest operations first instead of the 5 most recent operations?
When database is replicated from another remote database, does it replicate everything randomly or is there an order of replication like starting from the latest to the oldest?
When two users try to update an entry in database at the same time, what would happen? For example, two users click the like button in a tweet at the same time.
For the document store type database, how fast is it to query an entry by its _id. I would assume that in the worst case it would be O(n) because the data is stored in a linked list?
Is there a way to stop replicating the database and then resume from where I stopped?
If I use orbit-db in browser, how will the database be stored? IndexedDB?

Thank you very much for your patience.

shd101wyy on 6 Dec 2017

👍3

All 5 comments

In short: no, they don't need to replicate 1000 tweets to display 5 :)

You can do this by giving the load() function a number of entries to load, eg. await db.load(5). OrbitDB will then load the database with 5 latest operations (tweets) and emit ready event and finish loading. After that, it'll load the rest of the 1000 tweets in the background.

Does that help?

haadcode on 6 Dec 2017

And in case where userB doesn't have any of userA tweets, you don't need to do anything special but to open the database and userB will start replicating userA tweets automatically. You can listen for the replicated event to learn when the database has updated.

haadcode on 6 Dec 2017

Hi @haadcode ,

You said that I could use await db.load(5) to load the database with 5 latest operations (tweets) locally or listen to replicated event for the data update happened remotely. Is there a way to load the 5 oldest operations first instead of the 5 most recent operations?
When database is replicated from another remote database, does it replicate everything randomly or is there an order of replication like starting from the latest to the oldest?
When two users try to update an entry in database at the same time, what would happen? For example, two users click the like button in a tweet at the same time.
For the document store type database, how fast is it to query an entry by its _id. I would assume that in the worst case it would be O(n) because the data is stored in a linked list?
Is there a way to stop replicating the database and then resume from where I stopped?
If I use orbit-db in browser, how will the database be stored? IndexedDB?

Thank you very much for your patience.

shd101wyy on 6 Dec 2017

👍3

@shd101wyy I know this is very, very late but I still think answering your question will be helpful to others as well.

You said that I could use await db.load(5) to load the database with 5 latest operations (tweets) locally or listen to replicated event for the data update happened remotely. Is there a way to load the 5 oldest operations first instead of the 5 most recent operations?

Yes, certain data stores have an iterator function that can probably help you.

When database is replicated from another remote database, does it replicate everything randomly or is there an order of replication like starting from the latest to the oldest?

Replication will start from the exchanged "heads" i.e. the latest entry or entries in the DAG, and replicate from there by following the next field inside of the entries.

When two users try to update an entry in database at the same time, what would happen? For example, two users click the like button in a tweet at the same time.

OrbitDB implements the ipfs-log, which in turn uses something called Lamport Clocks to ensure that even if they press the button a the _exact same microsecond_, they will be properly sorted.

For the document store type database, how fast is it to query an entry by its _id. I would assume that in the worst case it would be O(n) because the data is stored in a linked list?

That sounds right.