‫Let's talk about a little bit Synchronoss versus asynchronous application, which is the same, the
‫problem we originally raised in the first and the presentation.
‫So Synchronoss application is when you issue a right to the red master replica master node, the client
‫has to wait until that transaction is returned to the master, obviously.
‫Right.
‫Because if you commit a transaction, you have to wait for the authorization to commit in the master
‫or in any database.
‫You have to wait.
‫Right.
‫Once that's done, synchronous replication also forces you to commit to that child replicas or the standby
‫replicas before the client can be unblocked.
‫Cassandra does something similar like this called Khorram.
‫And now you get to a conversion like, OK, Hosain, I have seven standby replicas on my master note.
‫Which ones should I should I wait for the seven of them?
‫That's a little bit of an overkill, if you think about it.
‫Right.
‫That's why Oscars or other database gives you these options, like, OK, wait for the first two or
‫wait for the first one or whenever any of them completes unblock immediately or whatever two of them
‫or any of them or like, for example, these are more important than those.
‫Those two is more important than those three standby replicas like you have done on a one standby replica
‫is a backup and the other are actually active people actually acquiring organs.
‫So you can have the flexibility here so you can control this stuff.
‫You can say, no, I want this as if I am actually want this everything to be fully consistent.
‫So you're going to take the hit, obviously, but you get full consistency, not evangel consistency,
‫because once you write, the transaction cannot fully commit until everything is committed in the master
‫and all the note, if you just turn everything on, you are essentially in a single cluster almost.
‫By the way, this whole thing is called the cluster.
‫Asynchronous replication is what by default, some of the default is like, OK, once you write to my
‫master, I'm done, the client is done.
‫You just can't unlock to the client.
‫This is done.
‫But the data is now.
‫It now has to do more work on a background.
‫Process that writes periodically to those standby replicas.
‫This, obviously.
‫All of a sudden now you have faster throughput, I have faster right, but at the back end, I have
‫a little bit some puppet processes that are doing this, asynchronous jobs and that could eat off the
‫CPU and a lot of work.
‫Right.
‫If you do a lot of these and it could scale and could slow things down, you could definitely get to
‫get eventually consistency.
‫If you can't live with that, you know, fine.
‫But as something people prefer synchronous now over asynchronous forces for certain.