1 00:00:00,090 --> 00:00:02,370 ‫All right, guys, that was awesome. 2 00:00:02,430 --> 00:00:03,570 ‫That was pretty cool. 3 00:00:03,780 --> 00:00:10,230 ‫I talk a little bit time because it's obviously replication is is a little bit difficult to implement. 4 00:00:10,230 --> 00:00:12,200 ‫And this is just with two instances. 5 00:00:12,210 --> 00:00:13,800 ‫You saw how much work we did. 6 00:00:13,800 --> 00:00:13,980 ‫Right. 7 00:00:14,430 --> 00:00:18,240 ‫So the pros and cons of replication the process, you get horizontal scalability. 8 00:00:18,600 --> 00:00:21,780 ‫I wouldn't say for free, but it it it's nice. 9 00:00:22,260 --> 00:00:23,880 ‫You wreathes are scalable. 10 00:00:23,880 --> 00:00:24,720 ‫You're right. 11 00:00:25,350 --> 00:00:29,960 ‫You can scale your rights if you do active replication or multi master application. 12 00:00:29,970 --> 00:00:32,210 ‫But to me I wouldn't go there. 13 00:00:32,220 --> 00:00:37,410 ‫I mean, the conflict resolution is a pain in the butt to fix. 14 00:00:37,590 --> 00:00:39,480 ‫So I don't I don't like to go there. 15 00:00:39,480 --> 00:00:42,360 ‫I try to optimize my rights as much as possible. 16 00:00:42,360 --> 00:00:48,480 ‫For a single instance, I make my BFE database server that accepts a lot of writing. 17 00:00:48,480 --> 00:00:48,870 ‫Good. 18 00:00:48,870 --> 00:00:49,260 ‫Right. 19 00:00:49,560 --> 00:00:52,140 ‫And the rest of the stuff I just I optimize for reading. 20 00:00:52,260 --> 00:00:52,990 ‫That's my mind. 21 00:00:53,480 --> 00:00:54,120 ‫That's just me. 22 00:00:54,120 --> 00:00:55,230 ‫You might disagree. 23 00:00:55,230 --> 00:00:57,150 ‫I'd like to see what you think. 24 00:00:58,290 --> 00:01:00,000 ‫Region based queries. 25 00:01:00,000 --> 00:01:05,940 ‫Now you can put all these standby replicas or backup replicas in different and different regions and 26 00:01:05,940 --> 00:01:08,070 ‫you can scale your reads, which is awesome. 27 00:01:08,280 --> 00:01:15,120 ‫So your application, you can keep your application close to any database and in any region. 28 00:01:15,330 --> 00:01:24,480 ‫So you don't have to have your your database in Atlanta and your client application in, I don't know, 29 00:01:24,630 --> 00:01:25,500 ‫Singapore. 30 00:01:25,590 --> 00:01:33,060 ‫That's just a recipe for disaster, because if you if you washed my wire, shocking progress and other 31 00:01:33,060 --> 00:01:35,700 ‫databases, videos I. 32 00:01:37,610 --> 00:01:45,680 ‫Database protocols are very, extremely chatty, and because it's built on top of DCB, it's even Chadi, 33 00:01:45,680 --> 00:01:48,850 ‫you're right, because of the acknowledgement you have to do. 34 00:01:48,870 --> 00:01:55,110 ‫And if you have, like, sending a lot of queries or big queries, those have to be split into smaller 35 00:01:55,150 --> 00:01:59,930 ‫and smaller packets, which need to be acknowledged, which kind of adds to the latency of the things 36 00:01:59,930 --> 00:02:00,440 ‫you need to do. 37 00:02:00,560 --> 00:02:04,200 ‫So keep your applications close and your database closer. 38 00:02:04,220 --> 00:02:08,410 ‫That's just an advice I'd like to give everybody cons, eventual consistency. 39 00:02:08,420 --> 00:02:09,220 ‫I don't know if this is a con. 40 00:02:09,260 --> 00:02:10,640 ‫Some people like this feature. 41 00:02:11,360 --> 00:02:18,710 ‫If you if you if you're building a system with Instagram and likes, who cares if you have, like, 42 00:02:18,890 --> 00:02:21,830 ‫I don't know, 700 likes versus 750. 43 00:02:21,980 --> 00:02:22,270 ‫Right. 44 00:02:22,450 --> 00:02:26,900 ‫If you read it again, if you don't get the correct number of like there's not that big of the deal. 45 00:02:26,900 --> 00:02:27,200 ‫Right. 46 00:02:27,470 --> 00:02:28,790 ‫So I've enjoyed the consistency. 47 00:02:28,790 --> 00:02:29,650 ‫You might live with it. 48 00:02:29,840 --> 00:02:31,300 ‫That's that's absolutely fine. 49 00:02:32,150 --> 00:02:34,270 ‫Slow writes obviously. 50 00:02:34,310 --> 00:02:34,580 ‫Right. 51 00:02:34,600 --> 00:02:35,000 ‫Yeah. 52 00:02:35,210 --> 00:02:36,340 ‫In case of Synchronoss. 53 00:02:36,740 --> 00:02:43,760 ‫Well, depends on how many what's the configuration of your rights and the replica rights. 54 00:02:43,770 --> 00:02:44,120 ‫Right. 55 00:02:44,180 --> 00:02:49,970 ‫Like if you're pushing to three or two or four or five, then you have to wait your transaction, have 56 00:02:49,970 --> 00:02:50,280 ‫to wait. 57 00:02:50,280 --> 00:02:55,370 ‫So you have slower write what appears to be slower from the client perspective. 58 00:02:55,370 --> 00:02:57,770 ‫And when I say client, I mean the back application here. 59 00:02:58,670 --> 00:03:05,120 ‫And it is complex to implement when it comes to multi master. 60 00:03:05,120 --> 00:03:05,440 ‫Right. 61 00:03:06,110 --> 00:03:11,450 ‫At least your application is very complex to implement, especially when it's come to multi master with 62 00:03:11,450 --> 00:03:12,440 ‫conflict resolution. 63 00:03:12,890 --> 00:03:13,920 ‫I would not go there. 64 00:03:14,330 --> 00:03:17,240 ‫All right, guys, that was a video on application. 65 00:03:17,240 --> 00:03:18,740 ‫I hope you enjoyed it. 66 00:03:18,830 --> 00:03:19,730 ‫Let me know. 67 00:03:19,820 --> 00:03:20,870 ‫What do you guys think? 68 00:03:20,880 --> 00:03:22,120 ‫What do you think of our application? 69 00:03:22,130 --> 00:03:23,570 ‫I'm going to see you on the next one. 70 00:03:23,600 --> 00:03:24,770 ‫You guys stay awesome. 71 00:03:24,770 --> 00:03:26,570 ‫Thank you so much for your support. 72 00:03:26,570 --> 00:03:27,170 ‫I appreciate it. 73 00:03:27,630 --> 00:03:27,980 ‫Goodbye.