Replicating service?

[jphastings]

I can see that orbitdb replicate <database> lets me replicate a single DB, is there a way to replicate a large list of databases?

If we use the orbitdb version of twitter as an example, is there a way to replicate every user's stream so that if a user goes offline before anyone else "follows" them (their orbit & ipfs nodes become inaccessible) then someone else can still follow them and retrieve their tweets from some kind of replicating service?

1. Does something like this exist, or would I need to write it?
2. At what scale of replication am I likely to run into scaling issues?

Thanks!

[BartKnucle]

It all depends on how you implement you database logic.
Let's say you have a single share user db. Each user can register inside it.
You can on sync of that db trigger the sync of the complete user db.

The scalling part depend on your ipfs setup and environnement. It should scale but you'll have to run stress tests.

[aphelionz]

@jphastings There are updates on this front. The community has been busy with pinning services!

In no particular order:

• https://github.com/JoinColony/pinion
• https://github.com/3box/3box-pinning-node
• https://github.com/Jon-Biz/orbitdb-pinner

Also, I'm transferring this to the Field Manual repo so we can go into more details

[jphastings]

Thanks folks! I'm very late replying here, but this info is super helpful (and, as you say, the community has delivered!)