Everybody forced here rip in 2023 top should be baseball hobby six box haste number 11 random teams fine at these results Find these results any time at lane sports cards calm. We'll go ahead and get started chipper had a better prime That's for sure. I will say that But as far as like an entire 20 years. Yeah All right, let's get started. Let's do it everybody. I'll be fair. I'll be fair Chipper will also won an MVP and was close to winning a couple others Underneath them Rangers win that world series things might be different for guys like Beltray and Nelson Cruz Especially Nelson Cruz in the right field out there. Oh boy. If you just caught that ball Things are way different. Josh Hamilton Nelson Cruz. Who are the big pitchers for them at the time? That's all he believes to go down though. Yeah Oh And now Hamilton's are on the Rangers at that point was he in 2011 He was still a Philly it took him a while to get ready for the Phillies because it's really kind of stunk at a certain point They're like, oh, they're gonna trade and they're gonna trade I've never got traded J rod if I'm ready. Ah, Cliff Lee. There you go. That's the one Yankees all Oswald Paraza rookie out of 150 nice blue They're a colony and Ken's were met like Natalie talking about Hamilton. Yeah I was talking about Hamilton and Cruz and Beltray with the big hitters there even prime Elvis Andrus We're talking about the Rangers talking about To they there's a gold Bryant's to 75 for the Rockies There's there's there's expletives that I want to say to that but I can't here we go Mets rookie auto red ink to 10 Francisco Alvarez monster hit Holy cow mark II Mets fans went from like yeah world series this year to have y'all seen how many homers Francisco So, yeah, that's definitely a nice card to hit right now clean auto with the red ink red parallel Jersey card Ozzy Albee's to 99 Atlanta so undervalued That's nice here we go Vladimir Guerrero Exposed go to the Nats Tribute to Olympus autograph to 199 Dude was an animal He's unbelievable unbelievable Make sure you tag that one grants on the Nats on that one Like hitting homers while like on a knee as he was swinging That was it right there was just so much pure power. They were like even from one knee He's cranking out these 450 foot bombs. I bring this up a lot But it's stuck in my mind where someone threw a pitch in the dirt and off the balance No, he had a homer off of one. It was not up to dirt a homer. No way Mount Castle I'm sure he was on the Rangers. He has hit a homer where it literally bounced before he saw You got to bring it up and show me fools and yachty do a relic 25 nice one Cardinals because he's done that multiple times Not hit a homer multiple times, but he's hit balls that have bounced before the weight multiple times really hit the dirt Yeah, I feel like I'm in back for a key auto buddy Kennedy to 199 That Vaughn just called Francisco Alvarez second coming of San Eleon himself We're also talking about career wars for Chipper and Beltray and Vaughn brought up Steve Pierce's career war Which is 9.9 Which is honestly more than I would have guessed triple relic is Tony Gwynn Padres, so I'm at a 25 nice I'm one of those people that like doesn't Like I don't care about war. Where is he relevant to me?  You got Graves Matt also not under 50 A lot of these like advanced stats just in my opinion Because one position could Johnson India Randy Johnson and triple relic Mets Mike Piazza to 199 Teams don't care about it either Like I understand it like I think they do care about it to an extent in terms of like Like signing like stuff like that. I think teams put it into consideration But I don't think a team is gonna be like oh we have to go and trade for this guy because he has a 13 war It's like no God Steve Carlton left the on the nicknames out of to 99 for the Phillies Nice card Phillies. Yeah, well Mike, that's why he won't be a Hall of Famer That is true. At least there's that like at least, you know, he won't be a Hall of Famer cheater to 99 Luis Castillo Marinus. Once he retires you'll never have to hear his name again Ray's Royals dual relic wonder Franco Bobby Whit Jr. I Love a 2022 Ricky short stops there wit and one hundred one ninety nine should be a random Yeah, we're just Tampa a razor combo Brandon E with the rays and the Royals Rory C random at the end on this one Mike were you happy with the white paper? Who did you want Mike was very happy? I was in here. I think I was so On Monday like oh my god Ripken insurers are Brett Beatty rookie auto to 99 Mets Nice hit Mets Yeah, same Ray Sanberg and a Xander Jersey card for the Red Sox number to 75 I thought that there was a chance Langford could have gone second overall Mike. I ask you that every day She's not gonna answer me He y'all from your office It's crazy.  Who's who's third-pick twins? Tigers, it's not a crazy Max Clark is very good.  That'd be crazy He's got the pop. He's got like what 70 power or something like that and same blue Bob Babe Ruth Rangers need out Jim Palmer auto the one that a nine Orioles Knocking against Durand. He's been very good, but he's Especially by a guy like this at top Four-pick Shet Griffey Jersey card Bellinger as a Dodger to 181 Okay, they must have they must have only his jersey must be smaller than some other guys Yeah, Mike I'm not saying like get rid of Durand, but I'm saying like you could replace Langford with Durand as your everyday starter for sure Yeah, Durand becomes your utility your super utility Seaver and chipper like the Chris Taylor Bligh 11 twins auto to 75 One of those or a championship team needs a Chris Taylor classic breaking Brad joke have her home bligh 11 Vaughn do you think he calls him Jim Palmer's when he makes him Ryan Chris Bryant's oh man. Oh man. What is it? Oh come on Diamondbacks Corbin Carroll to 99 green rookie auto Mamma Mia Oh My god Corbin Carroll Colby C with the corp that Colby C that same initials it was meant to be We will get it magged Beautiful dual bat relic you lay him in as the 50 for the white socks Yeah, they're not as easy to pull in this like it and find us you see a lot more rookie autos But in this there's a lot of that stuff, too And the rookie autos not like a rookie autos set it's just tribute autos. That's a whole set. Oh my god, dude Michael Harris rookie out of 150 Box three circle the wagons Congrats braves Holy cow Jared P with Atlanta blue color match, too Mike, I wish I was Unfortunately, but my next show is gonna be the national Corbin burns. I think a lot of people's next show unless you're like super regional or do all the shows that your next show is a national Moda 75 Yankees By wagon I did when I was a kid one of those like red horse and buggy Yeah, you know which one I save on gas Got a triple relic is by the bigger era junior blue jays to 99. I got to order more. Hey, though I was gonna say force goes through a lot of hay. I Get a price of hay I get it delivered to the Five dollars, I don't know I don't know how you buy a hay other than you go somewhere near Halloween or something.  I was in a haystack one. It's just super itchy would not recommend like rides or like the like Halloween like hey maize and like stuff like that. Yeah, it's all itchy George Brad who got to 99 green to grumb rangers Pirates cannot Smith and G but rookie out of the 150 Thank you, Simi, there's a farm that doesn't every year. I know maybe like hayrides Should we do us? Should we do LSE team hayride? All of us doing evades would be a disaster. We'd be out there for like 48 hours. Oh, they're missing the missing card shot Some see rid of 50 Mets that would for sure I'm not bad 75 Jersey Mount Castle Or maybe you might actually disappear at least escaped the room like Kwan Buxton Palacios twins rookie Otto out of 199 Jermaine Palacios Think he's a tiger and finest Big Mac big poppy Caleb Killian cubs rookie Otto out of 50 And we need something low-numbered now. We didn't get a big vet in this case Lou Bob dual relic to 99 white Sox It's pretty cool though Mets again, it's a Keith Hernandez the 50 on the iconic perspectives auto Like 3d thing there like a shadow box Keith Hernandez Mets Doesn't heal Hall of Fame or somehow Jock Peterson Xander and triple relic is a kershaw Dodgers 250 of the snack boy Vaughn here Keith Hernandez Vaughn, I think Donnie Donnie with the flubber comment last week broke broke Vaughn Vaughn is broken Mike now the national won't be back in AC and they're voting for it to potentially be back in 2020 6 it's down to three places Atlantic City Chicago and Atlanta Atlanta come on Atlanta final three Atlanta let's go Atlanta. I haven't done a national in Atlanta since it's like 98 or something like that. I will say It'll be brutally hot Yeah, next year is Cleveland this year is Chicago Rock and Roll Hall of Fame. Let's go Candid's not far from there either, right? How far so high It takes only to get Tampa with traffic dude Jram in the auto to 199 guardians there we go guardians Well, I'm sure it will be the Cleveland one's actually really good. I enjoy it. There's a there's a Ferris wheel in the location Mullins and Cruz got Jersey Rizzo for the Yankees Lane, what's your favorite Muppet? I ask you that I say Rizzo Like Rizzo the rat He's got it. Oh nice Adley rookie One and 18 packs on these Do you count like any like? go hoes like That like John row space or is it literally just the moth the moth it's got a Moreno rookie auto J's the 25 nice Like his rocker Hall of Fame is literally in Cleveland. Yeah Ferris wheel dismantled. All right. Well, I guess we'll skip Cleveland to then. Oh, if there's no Ferris wheel I don't know how I feel about that location. We'll just send a wrench to Cleveland We'll stay I'll just be on zoom the whole time sitting here. Just like hey everybody Tom Glavin auto to 99 for the And oh, that's awesome Ortiz and Manny dual Jersey Red Sox number to 199 I Gotta bring back up I gotta bring back up the all-time home run derby. I'd have Manny in my home run derby That's fair to 75 Joey Votto that's more than fair that's like the biggest derby moment of all time Votto to 75 Michael Harris a second rookie auto to 150 Atlanta Okay. All right, that's a second blue as well So who would be your eight all-time home run derby? Me personally, you know, everyone's personal eight would be very different because it's what you would find the most entertaining. I'll go Manny Give me a Frank Thomas Triple relic Bregman. I'm going with the guys. They're gonna hit them far I don't care about the figure to win or not to 199 Bregman aster triple jersey or what we're looking for Yeah, Mike, I was kind of waiting for that one Big poppy one in 2010 I think I'd probably okay. Yeah me. I'd go big poppy. I'd have we saying they have to have So Manny poppy who else did I say was my other one big hurt give me Ryan Howard that's four Um Tim Hudson auto a is the 75 I five now I need three more. All right now. It's getting tough. Now. I wrap You could have like, yeah, there's very few teams you could actually have like Jersey car Brandon Woodruff Brewers to one ninety nine These are one the Red Sox or one the teams with history and then the Rangers Let me go Show hey, Ohtani, I Feel like he needs a redo from last year. He was in it last year And it was bad. He needs a redo because he launches in game home was like 48 feet all the time Yeah, that's what they were saying this year during the home run derby. They were like Perez the 99 Royals They're like Ohtani is too good in game to like do this as like Gunnar Henderson rookie Orioles with both of the base rookies congrats on that And it's two per case in the base Well Orioles Let's go. You got him We got him whoo the 75 gold Ali ruchman rookie auto There we go. That is a monster hit. I can't wait for the market to start appreciating how good he truly is Andy a whoo Andy Yeah, market has always been no stay away from catchers. Adley is a generational catch.  He just stays a catcher goes down as one of the best catchers ever You can just D age and catch like you can just do low like prayer like Salvador Perez had a long career dual Jersey Glavin For them that's the one ninety nine He's playing a lot more first base now and de-aging a lot more, but he's still got pop in the bat So Earned stripes Pratt patch auto 4-5 Eloy Jimenez Oh my god. Yeah, the relic autos are pretty rare in this but when you hit you hit The jumbo patch auto Kusay are oh my god How rare are the earned stripes they have to be super earned stripes number all number to 50 or less Red is to 10 so this one's even lower than that. Maybe it's maybe the checklist is wrong. Oh, no, that's disgusting though That's going in a mag. That's just too pretty Wow, wow, wow. Yeah guys tribute is on fire more breaks this evening with Sam And we got triple relic and all on our Ronaldo Cardinals the 75. Oh God the rookies came out in that case for sure. Oh, yeah Let me set up this Yeah, it was awesome. Let me set up the random here. We got One more tribute case, right? Yeah, just one more. All right. Let's do this random here guys Raise All right, raise Royals do a relic wander and Bobby with junior to 199. Yeah, I agree Chris is disgusting We'll go six times five and one or was up top gets it one two three four five and six go into the Royals There you go a couple of great 2022 rookie short stops there Also, just having a good season this year, too. He's like one of the only bright spots on the road. Yeah Some of the other guys are good too, but He's the true bright spot. They're getting there. They're getting there kind of like what the Orioles were a few years ago Forgetting there They don't have quite the juice in the pharmacy, but they still got some guys Parallels we had Salvy Perez de Grom Castillo Chris Bryant Mariano Rivera Tom Sieber and Joey Vado relics Royals got the Whitten wander Aranato, Glavin with the Mets Woodruff and Alex Bregman Manny and Poppy Anthony Rizzo Melt bar and grilled sounds good Zach. I'm in Clayton Kershaw Louise Roberts ride Mount Castle anyone that isn't like allergic likes grilled cheese. I think Vlad jr. Eloy Jimenez Cody Bellinger, Sandra Bogarts who doesn't like butter cheese and bread together melted Yatsa Gwynne who holson Molina and Ozzy Abbey's Oh my god, I can't look at that right now. We have a break. I can't look at that. Oh My god, Jadis brought it up over there Zach I looked at the laptop screen and man, there was a grilled cheese probably about as uh, stood my hand up Yeah, it's probably that big for the six inch tall grilled cheese Anyway, autos of Jram Palacios for the twins Jim Palmer buddy Kennedy Vlad Guerrero going to the Expos going to the Nationals there Michael Harris the second rookie auto to 150 Kenan Smith and Jigba Michael Harris to 150 Paraza baby Galavin Carlton a lefty nickname auto for the Phillies Tim Hudson for the A's verb lie 11 Keith Hernandez Caleb Killian Matt Olson and a Gabriel Moreno blue J's nice one there to 25 Crazy patch auto four or five Eloy him and has earned stripes. That's a great looking set this year I'm I'm wanting to pull that every case now That's a pretty decent checklist too, there's a lot more names and there's a higher number parallel suits They're not incredibly rare Rookie auto red that's in Francisco Alvarez huge hit for the Mets. Good Lord 75 rookie out of the Retchman Orioles and Rookie auto to 99 Corbin Carol Diamondbacks Case is what dreams are made of right there moving on to number 12 everybody


Welcome everyone to this breakout session. We are live in Detroit. Welcome also to our virtual audience. Our talk today is one VT org to rule them all. High availability in a distributed system. Distributed database system. And the distributed database we'll be talking about is WITES. My name is Deepthi Sigreddi. I'm a maintainer and technical lead for WITES, which is a graduated CNCF project. And I'm a software engineer at PlanetScale. Hello, I am Manan. I'm also a maintainer at Office Desk and a software engineer at PlanetScale. We'll start with a WITES overview. WITES is a cloud native database, but it originally started as a scaling solution for MySQL at YouTube. And from those beginnings in 2010, it has evolved to become a general purpose distributed database that is suitable for many workloads and many use cases. WITES is massively scalable. If we look at some of the numbers, the largest instances of WITES run to 20,000 terabytes, which is 20 petabytes, 22,000 replicas, 250,000 simultaneous connections, though that is not a limit. You could go higher and so on. And one of the ways WITES achieves the massive scale is through sharding, which we will not talk about in this talk, but we have a maintainer talk tomorrow where you can learn more about how WITES does sharding. WITES is also highly available. That is going to be the focus of this talk. And WITES is MySQL compatible, both 5.7 and 8.0 versions. We'll now get a brief overview of the architecture of WITES. So clients talk to WITES through a proxy called VTGate, and VTGate receives the client request, which can be either MySQL or GRPC. Those are the two protocols it supports and routes them appropriately to the backend MySQLs. So in a sharded WITES system, you may have multiple shards, but in each shard, there is a primary MySQL and there are one or more replicas. And VTGate figures out which shard to route it to. And when we run in this primary replicated mode, we have to make sure that each shard is highly available. In addition to this query serving path through which VTGate receives the queries and routes them to the backend MySQLs, there is also a control plane, and this is where VTORC comes in. There is a WITES control daemon, which takes management commands from users through CLI or the web UI and executes them. There is VTADMEN, which powers our web UI, and then there's VTORC. So let's go through a little overview of VTORC and then we will have a demo. What is the problem that VTORC is trying to solve? The main problem that VTORC is trying to solve is resiliency to MySQL failures. So we are running MySQL in a replicated mode, but even then if the primary MySQL goes down, we have to deal with that failure mode. And we need to be highly available and that's the problem that VTORC is solving. However, while ensuring high availability, you also want to be able to make sure that the data is durable. If a transaction has been accepted by the system, then it shouldn't be lost. That data should be persisted somewhere. And during this process of detecting and recovering from failures, we want to minimize the time taken for the recovery. So what was the state of the art before we built VTORC? There was OpenARC Orchestrator, which was a different open source project that a lot of large MySQL deployments used to deal with failures at the MySQL level. And there was an integration with Wittes. The integration worked well enough most of the time, but not all of the time. In addition to that, the way durability was provided by Wittes was through semi-synchronous replication, which we will go through in a minute. And that configuration in Wittes didn't really work well all of the time. We discovered failure modes where the semi-synchronous mode setting would be lost. Whatever the user intended would not get set on the MySQL. So over time, we discovered all of these problems with the orchestrator integration and how semi-sync was implemented in Wittes. And we decided that this thing needed to be rebuilt from the ground up. So VTORC is now GA. We announced Wittes 15 general availability yesterday and VTORC went GA yesterday. But VTORC is already in production. There are at least two deployments that we know of where VTORC is being used to do unplanned failures and to deal with primary failures. So I'll just give you a minute to read this quote from a user of Wittes who's deploying VTORC with Wittes in Kubernetes using the Wittes Kubernetes operator. Let's get a little deeper into what VTORC is doing. We talked about what functionality it provides, but how does it do that? So VTORC is the agent that is monitoring the Wittes cluster and detecting the failures. So it has logic to check for certain conditions at periodic intervals and flag failures. And once it detects a failure, it goes through a repair or recovery mechanism. The way VTORC achieves durability is through replication. Or in general, the way Wittes achieves data durability is through replication. So one primary more than one replica gives us guarantees that any transaction that's accepted by a primary is replicated to at least one replica. So that in case of a disk failure or a node failure, you don't lose the data that a client thinks has been persisted. And the way we achieve high availability is through failover. So when a failure is detected, we call it an unplanned leader election. But in the normal course of things, you have to upgrade software, you have to upgrade hardware, whatever it is. In the normal course of things, you want to be able to do planned failovers so that the system remains available through maintenance operations. And that's Wittes' general strategy for high availability, and VTORC is the agent that enables those things. The design principles on which VTORC is built came from consensus systems. So consensus in a distributed system is a problem that people in academia and industry have been working on for many years now, I think 40 plus years. And there are well-known algorithms to solve the consensus problem. In Wittes, what we did was that a group of us studied some of these algorithms and then we came up with an engineering approach. So this approach prioritizes performance over theoretical correctness. Not to say that the system is not going to be correct, but just that we did not prioritize writing a formal specification and validating it. We've taken an engineering approach to solving the consensus problem. And we are not interested in purity in the sense that we don't have to be the consensus algorithm. So Wittes has a topology server which can be at CD or zookeeper or console where we store some state and it is used for discovery. So we actually lean on the topology server to provide the persistent state that can help us in recovery. Wittes is a single leader system and one of the principles we are trying to maintain is that we need to be able to fulfill requests while respecting the durability policy that has been chosen by the user. And durability versus availability is a trade-off and that's a configurable trade-off so that people can decide which is more important and under which situations. We have also separated the planned leader election from the unplanned leader election. So there is the normal operation of the system which is very high QPS. We expect Wittes systems to get millions of queries per second for reads or writes versus leader elections are much rarer. So planned leader elections in a Kubernetes environment maybe once a day or once a week or in a non-Cubernetes environment maybe even rarer. And unplanned leader elections are expected to be relatively rare. So we've separated these things to say that the way you achieve consensus for normal operations is very different from the way you do it for the leader election process. The system should be able to make forward progress and we need to be able to deal with race conditions. Given that VTARC is an agent, it itself is susceptible to failures which means that you may be running multiple VTARCs and they may be running in multiple regions and we have to deal with failure modes for VTARC itself. So whatever we came up with has been written up in a blog series by one of the founders of Wittes, Sugusugmaran, and we have a link to it towards the end. So what we came up with in terms of leader election is that leader election has three distinct stages. There's revocation, revoking the previous leader, election, choosing a new leader and propagation, which is any requests that were accepted by the previous leader and acknowledged to a client need to be propagated by the new leader to all of the followers or replicas. So in a planned leader election revocation is actually much simpler than in an unplanned leader election and this is one of the reasons we've separated those two. In a planned leader election, because the current leader is still available, you just ask them to step down before selecting a new leader. So it's an orderly transition. A new leader is chosen. It's possible that there are still some completed requests that have not been propagated to all of the replicas. The system will make sure that they get propagated to all of the replicas. So that's what a planned leader election looks like. So as an example, the leader changed and the yellow arrows which represent replication have all moved over to the new leader. An unplanned leader election is a little bit different because in order to revoke the leader in an unplanned leader election, we have to be able to reach a sufficient number of followers. So I'm calling that M and what M is we will find out in a little bit. But once revocation is complete, things look the same as for a planned leader election. A new leader is chosen and how the new leader is chosen also depends on the durability policy and completed requests have to be propagated. So let's say that leader became unavailable and a new leader is chosen. All of the replicas now replicate from the new leader and the previous leader is out of the topology. We've talked a fair amount. I've said durability policy quite a few times. So I want to talk about what exactly a durability policy is in the Wittes context. So the definition of durability that we are working with is that if a client request has been acknowledged, any changes that that client made to the data are persistent and are not lost. So we are talking about not losing data. So data loss is what we want to avoid. MySQL has a synchronous replication mode and a semi synchronous replication mode. And with the right parameters, it's you can configure semi synchronous replication in such a way that any right to the primary will be blocked unless an acknowledgement is received from at least one replica. And the acknowledgement from the replica doesn't mean that that transaction has been completely applied to the replica. It only means that the replica has received it and persisted it in a way on disk essentially. So what the durability policy is defining is basically how this is configured for Wittes. Semi-sync is the foundation, but with the durability policy, you can configure which replicas are eligible to be promoted as a primary. For whatever reason, some replicas may not be eligible. How many semi-sync acknowledgments are required for each primary? Most people use one, but there may be situations where people won't use two acknowledgments. Which replicas are eligible to send those acknowledgments and so on. And what durability policies give operators of Wittes is increased flexibility in their configurations, in their topology, in how they lay out their replicas for worldwide replication or across data centers, regions, availability zones, those kinds of things. So now I'll hand it off to Manan. Thank you, Deepti, for that introduction. And now that we've looked at what durability policies are and how Wittes tries to ensure durability, we can go ahead and look at the revocation phase in a little more detail and look at exactly what M is that Deepti alluded to in a few slides ago. So how do we know that we have been able to reach sufficient tablets to guarantee safety? To answer that question, we first have to look at a different concept called intersecting quorums. We just saw in Semi-Sync that in order to accept a transaction, a primary requires some amount of Semi-Sync acts coming from the replicas. So a primary along with the set of replicas that are sending the Semi-Sync acts together from a set of tablets that can accept transactions. This set of tablets which is capable of accepting rights is one quorum for accepting rights. There can be many such possible quorums. In order to guarantee safety during the revocation phase, we should be able to reach at least one tablet from each of the possible quorums. The intent is that if there are unreachable tablets which can form a quorum, they would accept rights which we don't want them to do. The reason is that an unreachable tablet and a tablet which is down are virtually indistinguishable from the VTR perspective. Let's take an example to make this even clearer. Let's say that we were in a scenario where we had six tablets in which you only require three tablets to accept transactions. If, for example, something was network partitioned like so that you had two VTR instances running but on two different sides of the network partition with three tablets on either side. In this situation, if you do not check for the revocation phase at all, each of those VTR instances can actually promote one primary and that primary will be able to accept rights because you only require two more Semi-Sync acts. So we would have one primary elected here, one primary elected here and that would not be a correct situation because you could very well be in a split-drain scenario. Two of these primaries accepting rights, they can diverge because they could have accepted different rights. They aren't replicating to each other because they're network partitioned. So in this case, it would not be safe for any of the VTR instances to proceed because from this VTR instances perspective, there are three tablets which can form a quorum that it can't reach and the same for the other one. There are three tablets that it can't reach which can also form a quorum. So in this case, it's not safe for either of the two VTR instances to proceed. If, for example, on the other hand, we were network partitioned such that five tablets lie on the same side and one tablet was on the other. In this case, that VTR instance can make forward progress because it can reach five tablets and it is enough to guarantee revocation because the one tablet which is there on the other side, it can't actually accept rights because two Semi-Sync acts are required and we can reach enough tablets to guarantee that that tablet never gets that many acts. I hope this concept is clear. Let's take a look at the demo. So the demo that we're going to look at, it's actually going to be in two parts. The first part is going to use a Semi-Sync durability. For that, we're going to use a Semi-Sync key space and the durability policy that we're going to use is Semi-Sync. The way that it works is that any replica can be the primary tablet. The primary tablet only requires one Semi-Sync act to accept transactions and any other replica can send those acts. In our example, we're going to have four replicas, zone 100, 101, 102 and 103. So if you take a look at the VTR admin page for this, here's a free space, the Semi-Sync key space, and it's running with the Semi-Sync durability policy. And if you take a look here, we have four replicas, one of which has been promoted as a primary. So if you take a look at the corums that can accept transactions because any tablet can be the primary and any other tablet can send a Semi-Sync act. Essentially, any two tablets together can accept a right because one of them can be the primary and the other can send the act. For example, in this case, 100 can be the primary and 101 can send the act and that is enough to accept a right. So overall, this is what the corum set for accepting rights would look like. Any two tablets can accept a right. So if you take a look for corums that have revocation, if you're able to only reach tablet 100 and 103, that is not enough to guarantee safety. Because you would have tablet 101 and 102, which can accept rights with 101 being the primary. But if you're able to reach three tablets, 100, 102 and 103, that is enough because there's only one tablet which is unreachable, the 101 tablet and it can't accept rights on its own. If you're able to reach all the tablets, that is enough too, and one is not. So in our example, we have four tablets, one of which is the primary. If we go ahead and shut that primary down, we expect that VTORC will be able to make forward progress, promote someone else because it is safe to do so. There. In that much time, VTORC promotes a different tablet, which is zone 102 as the primary and the previous one get remotes itself to a replica, which is no longer in a serving state. But in this case, if we go ahead and delete one more primary failure, let's say in this case, our cluster had another primary failure. This time VTORC won't be able to make any progress. The reason is that there are two failures now, and these two tablets had they been network partitioned, they could have accepted rights. So VTORC can't reach them. It's not going to be able to make forward progress, which is what the flexibility is what VTORC provides, because you're able to configure the amount of semizing acts you require. It is up to you to define how much of a durability you want. If you set the number of semizing acts requirement to something higher, let's say five semizing acts and you have 10 tablets running, you can handle three failures, four failures. So it's up to the operators to configure the policies such that they define the performance that they want and the durability trade-offs that they're willing to make. The next example that we're going to look at is a cross-cell durability policy. This policy is similar to the semizing policy apart from one difference. So the way that we define a cell is a failure domain. It could be an Amazon region, it could even be your confidence in different providers. You could say that AWS is one zone and GCP is the other zone. However, you decide to do that. So once we have a cell, the cross-cell durability policy all is different in the semizing one is that the replica acts have to come from a tablet, which is in a different cell. So essentially when a primary accepts a right, the semizing act is coming from a different cell, so you're guaranteed that your right is persisted in two cells. So in this example, we're going to have three, we're going to have four tablets, three of which are going to be in zone two and one is going to be in zone one. And if you take a look at the yellow lines, those yellow lines signify who can send semizing acts to the other tablet. The tablet in zone one can send semizing acts to all the other three and can receive semizing acts from all the other three because it lives in a different zone, but not the other. Because zone one, 200 and zone two, 201 both are in the same cell, which is zone two, so they can't send semizing acts to each other, which is what the white line signifies there. So if you take a look at the corums for accepting transactions, this time the corums are much less than the previous example, because if 300 is the primary, it can get acts from any of the three tablets. But if anyone else is the primary, they always require acts from 300 because that's the only tablet available in a different cell. If you take a look for the corums of revocation, reaching 200 and 201 is not enough because you have tablet 202 which can accept rights with 300. 300, 202, 201 that is enough because there's only one replica that's left. 300 and 201 is also enough because if you reach 300, you're able to guarantee that none of them are actually able to make forward progress because 300 is part of all of those corum sets. Let's take a look at this key space now. So we have the cross cell key space and it's going to use the durability policy called cross cell over here. Initially, one of the tablets in the second zone has been promoted as a primary zone to 202. If you take that tablet down, okay, so VTRK is able to promote someone else as the primary zone. One 300 gets promoted as a primary in this case from the VT admin page. We can also go ahead and repair and our cluster to a different primary tablet. For example, if you go over here, okay. So now zone two 200 is the primary. If we go ahead and take this primary down as well, this time to VTR will be able to fix this failure. And the reasoning is again in the durability policies because 300 and 201 are enough. 200 and 202, even though there are two tablets, they can't send some icing acts to each other. So they can't accept rights between themselves. And this is where the difference between the semi sync policy and the cross cell policy comes in because the failures are in the same cell. Cross cell policy can make forward progress even though some icing could not. So in the case of semi sync policy, two failures was enough that VTR was not able to make forward progress. In this case, it can. It has promoted someone else as the primary zone to 201 and the things are resumed. But any more failures than this, even 201 tablet going down, that would again result in a scenario where VTR can't make progress because it won't be able to make forward progress. There's only one tablet available and you need one semi sync act to even accept any rights. And that concludes the demo for both of those key spaces. I would like to talk a little bit more about the custom durability policies. So the way that the durability policy works is that you only need to answer three questions when you implement your own custom durability policy. This is encoded as an interface. So first thing you need to answer is who all can be the primary? So you can say that off the tablets that you have, only some tablets are allowed to be the primaries, others aren't. They could be read only tablets that you only custom for maybe OLAP transactions and you don't want them to become primaries at all. The second question is how many semi sync acts does each primary require? And this can be customized for each tablet that can be the primary. You could say that you have too much confidence in one of the primaries, let's say primary tablet A. It requires three semi sync acts, but you want tablet B to only require one semi sync act. That is also possible. And the final question is the number of semi sync acts that are defined, who all tablets can send these acts based on who the primary is? With all of these three questions, you can actually implement your own custom durability policy based on the constraints that you have and the trade-offs that you're willing to make. Apart from the primary failures, VTRG also handles many other failure scenarios that MySQL instances generally run into. So it maintains the cluster's desired state. If the primary goes into a read only state or the replica's replication is stopped and so on, the list of failures are listed here and many more, these are all the things that VTRG is able to handle. So if you have VTRG running, it's kind of an automated scenario where you just don't need to look at anything until something drastic happens, something that you did not prepare for or you're not expecting according to your durability policies to handle. If that happens, then manual intervention is required. Otherwise, VTRG is an automated process that will take care of your cluster and keep it healthy all the time. Thank you. And we're going to move on to the question and answer round. Before we do that, there are some resources that we have. Tomorrow, there is another VITES talk, which is going to talk about sharding and new features in VITES at 11.55. And the blog post series is linked here. And the VTR documentation. Please leave feedback. You can use the QR code for that. We would love to hear from you as to how the talk was and how we could improve. Thank you. Any questions? We also have a booth in the solution showcase for VITES. Please feel free to stop by to talk to us. Any questions from the audience? Yes. And the second question is, I noticed you were careful not to say M stands for majority of the... I noticed that you said like M, the primary M, doesn't stand for majority, you know, for tablets. Right. Like for scenarios where, you know, M is let's say only two replicas and we can have a potentially split brain scenario, like when it's less than a majority. How can one, you know, recover from those scenarios? How can we reconcile in the very scenarios where split brain can happen when M is less than majority? Let me repeat the question. We'll take the second question first and then I'll answer the first question. So the second question was about majority. The number of required replicas M does not have to be a majority. Yes. The way that M is written is that it can actually even be variable based on the failures that you have. In the cross-sell policy, if you actually have a failure of the zone one, zone 300 tablet, the one which is in the other zone, the only tablet there, that is enough because you only have one tablet running in that zone. In that case, none of the other tablets can make progress. So if we go back to that slide, in this case, if this tablet goes down, there's actually enough to bring down the entire cluster because you'll have only one tablet in a different zone. But that also means that you can handle multiple failures from this zone. Two tablets going down from here is what we saw in the example. It's not even a constant based on the durability policy. It could be one, it could be two. It's all dependent on the kind of failures you have. And the end of the question that you had as part of the second question was what happens and how you reconcile if you end up in a split brain scenario. The way that VTR works is that it will not allow you to get into a split brain scenario. It will stop writes at that point. In the example, in the situation that I described over here that if you were network partition like so, and you had one of the primaries running in this cluster, it went down. In this case, VTR won't promote anything else because it's not safe to proceed. It'll actually wait for manual intervention to come in, in which case the operator can decide how he wants to proceed in this scenario. He can actually take down all of these three tablets and just promote one from here. So it's up to the operator to decide how they want to take things forward. So the way that VTR works, it will not let the cluster go into a split brain scenario. I hope that answers your question. So in a semi-sync scenario where you only require acts from two other participants, why can't we have a split brain scenario here? Let me answer that question. So the basic principle that is preventing that from happening is quorum intersection. So what we are saying is that if you have, let's say, five tablets altogether and you require two acknowledgments for the primary to accept a right, then when you try to revoke the leadership from the current primary, you need to form a quorum that includes at least one of those replicas that is able to acknowledge. So in that example of five tablets with two acts, you need at least three replicas other than the primary to agree that this current primary is going to step down. So the quorum for normal operation is different from the quorum for leadership election and they have to intersect. And that's the same principle as has been published in the literature quorum intersection. Thank you. And the first question, which was about the API server outages. Yes, so the question was about what happens if the Kubernetes API server is unavailable. So VTR needs to be able to communicate with the topology server where we store state that doesn't necessarily depend on the Kubernetes API server. So as long as the networking in the Kubernetes cluster is functional and the topology server is reachable, we will still be able to perform an election. Any other questions? All right. If there are no other questions, we will end here. Thank you all for coming out.


Live from New York, it's the queue. Covering AWS Global Summit 2019. Brought to you by Amazon Web Services. Welcome back, I'm Stu Miniman, my co-host Corey Quinn and we're here at the AWS Summit in New York City where I'm really happy to welcome to the program a first time guest but somebody that has an app that's on my phone, so Andy Fang who's the CTO of DoorDash, give a great presentation this morning, thanks so much for joining us. Absolutely happy to be here guys.  Absolutely, yeah, I mean when we started in 2013, we started out of a dorm on Stanford campus and like you said, we were doing the first couple hundred deliveries ourselves but fast forwarding to today, we're obviously at a much, much different level of scale and I think the one thing that I mentioned about in my keynote is just we've been trying to keep up pace and more than doubling as a business every year and it's a really fascinating industry that we're in in the on demand delivery space in particular, I mean Dara, the CEO of Uber himself said in May, which is a month and a half ago, he said that the food delivery industry may become bigger than the ride hailing industry someday. So just one quick question on kind of food delivery because like I think back when I was in college, I worked at a food truck, it was really well known on campus and there are people that 20 years later, they're like, Stu, I remember you serving me these sandwiches and I loved it and the community and we gather and we talk. Today on campus, nobody goes to that place anymore because maybe I know my delivery person more than I know the person that's making it. So I'm just curious about the relationship between the local businesses and the people. How that dynamic is changing, the gig economy, I mean you guys are right in the thick of it. No, it's a great question. I think for merchants, a lot of the things that we talk to them about is you're actually getting access to customers who wouldn't even have walked by your store in the first place and I think that's something that they find to be very captivating and it shows in the store sales data when they start partnering with Adore-Dash. But we've also started building our products to really get customers to interact with the physical neighborhoods they're in. The most concrete example of that is we launched a product called Instore, an Instore pickup product where you can order online, skip the line and pick up the order yourself in the store and I think the way we can build the app experience around that, you can actually start building kind of a geospatial browse experience for customers with the Adore-Dash app, which means that they can get a little bit more familiarity with what's around them as opposed to just kind of looking at it on their phone themselves. All right, so the logistics of this are not trivial. You talked about 325% order growth. Your database is billions of rows, just the massive scale, massive transaction. Therefore, as a, you're an app and at the scale you're at, technology's pretty critical to your environment, so you've got to bring us inside that a little bit. Yeah, I mean, we're fortunate enough, and you and I were talking before the show, I mean, we're kind of born on the cloud, right? And we started off actually on Heroku back in 2013. We adopted AWS back in 2015 and there's just so many different services that Amazon Web Services has been able to provide us and they've added more over time. I think the one that I talked about was one that actually came out only in early 2018, which is the Aurora Postgres product. And we've been able to scale our databases, scale up our analytics infrastructure. We've also used AWS for things like, you know, real-time data streaming. They have the cloud watch product where it gives us a lot of insight into kind of how our servers are behaving and so the AWS ecosystem in of itself is kind of evolving and we feel like we've grown with them and they're growing with us and so it's been a great synergy over the past couple of years for sure. As you take a look at where you started and where you've wound up, can you use that to extrapolate a little bit further as far as what shortcomings are you seeing today that ideally would be better met by a cloud provider or at this point, is it such a simpatico relationship as you just alluded to where you just see effectively you're continuing to grow in similar directions just out of, I guess, happenstance? Yeah, it's a good question. I think there are some shortcomings. For example, AWS just recently launched MKS which is their in-house confidence solution. We're looking for something that's kind of a lot more vetted so we're considering do we adopt the AWS version or do we try to do it in-house or do we go with a third-party vendor that's- Confluence hard to say no to these days. Yeah, exactly and I think we want to make sure that we are building our infrastructure in a way that we feel confident in, can scale. With Aurora Postgres, it's done wonders for us but we've also kind of been one of the pioneers for AWS for scaling that product and I think we got kind of lucky in some ways there in terms of how it's been able to pan out but we want to make sure the stakes are a lot higher for us now and so when we have issues, millions of people face issues and so we want to make sure that we're being more thoughtful about it. AWS certainly has matured a lot over the past couple of years but we're keeping our options open and we want to do what's best for our customers and AWS more often than not has a solution but sometimes we have to consider other solutions and consider the fact that AWS may or may not solve some of the future problems we're facing.  Then I had a child and when she wasn't going to sleep when she was a baby and I only had one hand how do I feed myself? There's an accessibility story if people aren't able to easily leave the house so it's not just people aren't able to get their wings at the right time this starts becoming impacting for people it's an important need. Yeah and I think it's been awesome to see just how quickly it's been adopted and I think another thing about food delivery that people don't necessarily remember about today is it was primarily just a very dense urban area phenomenon, right? Like obviously in Manhattan where we are today food deliveries exist forever but the suburbs is where the vast vast majority of the growth of the industry has been and it's just awesome to see how this use case has flourished with all different kinds of people. Yeah I have to imagine there's a lot of analytics that are going on for some of these as you said in the rural areas, the suburban areas you've got, it's not as dense and how do you make sure you optimize for the people that are doing so what are some of the challenges you're facing there and how is technology helping? Exactly yeah I mean with our kind of a business it's really important for us to get into the lowest level of the detail, right? Just because we're growing 325% year on year in 2019 maybe we're growing faster in certain parts of the United States and growing slower in others and that's definitely the case and so one of the awesome things that we've been able to leverage from our cloud infrastructure is just the ability to support real-time data access and our business operators across Canada and the United States, they're constantly trying to figure out hey how are we performing relative to the market in our particular locality meaning not just the state of New York but Manhattan, which district in Manhattan, all that matters with a business like ours where it's just a hyper-local economy and so I think the real-time infrastructure particularly with things like with Aurora the fast replicas, we're able to actually get a lot of read hits to these replicas because it's not affecting our right volume so that's been really powerful and it's allowed our business operators to just really run and sprint. So Andy, I have to imagine just data is one of the most important things of your business. How do you look at that as an asset? Is there new things, new services that you can be putting out there both for the merches as well for the customers? Absolutely, I think one of the biggest ones we try to do is we never give merchant direct access to the customer data because we want to protect the customer's information but we do give them insights into how they can increase their sales and target customers that haven't used them before. So one of the biggest programs we launched over the past few years is what we call Try Me Free so merchants can actually target customers who've never placed an order from their store before and offer them a free delivery for their order from that store and so that's a great way for merchants to acquire new customers and it's a simple concept for them to understand and over time we definitely want to be able to personalize the ability to target these terms of promotions and so we have a lot of data to do that and we also have data in terms of what customers like and what they don't like in terms of their order behavior in terms of how they're rating the food, the restaurants so that kind of dynamic is something that is pretty interesting data set for us to have. You look at other local companies out there like Yelp and Google Maps they don't actually have verified transaction information whereas we do so I think it's really powerful for merchants to actually have that to make decisions off of. It's a terrific customer experience and it almost seems to some extent to be aligned with Amazon's professed customer obsession leadership principle to some extent and the reason I bring that up is you mentioned you started on Heroku and then in 2015 migrated off to AWS was it a difficult decision for you to decide first to effectively go all in on a single provider and secondly to pick AWS as that provider? It wasn't a hard decision for us to go to a cloud provider that was ready to do show time. I'd say Heroku is more of a student project kind of scale at that time, I don't know what they're doing today. But I think AWS at that time was still very, very dominant. I think we're considering Azure and GCP I think was kind of becoming a thing back then. AWS was always the most mature and they've done a great job of keeping their lead in this space. Google and Azure, I've propped up obviously Oracle Cloud's coming up too. And we're considering, I mean we've considered the capabilities of something like Google Cloud, their machine learning services are really powerful. They actually have really sophisticated probably more so than AWS. Kubernetes service is actually more sophisticated. I guess it's built in-house at Google so that makes sense. But we've considered the landscape out there but AWS has served a lot of our needs up to this point. And I think it's going to be a very dynamic industry with the cloud space and there's so much at stake for all these different companies and it's fascinating to just be a part of it and kind of leverage it.  You know, how do you look at that balance? You said in your keynote this morning, you have less than a handful of engineers working on the data infrastructure. So that line item of cloud, I'm guessing is non-trivial from your standpoint. So how do you look at that internally? How do you make sure you keep control and keep flexibility in your options yet focus on your core business and not the infrastructure piece of it? That is such a great question because it's something that we get, we think about that trade off a lot. Obviously in the early days, what really mattered ultimately is do we have product market fit and do we have something that people care about, right? So optimizing around costs obviously was not prudent earlier on. Now we're at a such large scale and obviously the bill is very big that optimizing the cost is this very real thing. And part of what keeps you satisfied with staying on one provider is kind of the ease of the setup and what you've already have configured there. And we've done optimizations over the years. We have folks on our finance team now who's basically looking at, hey, where are areas that we're being extremely inefficient? Where are areas that we can do bulk spend? And this is not just on AWS, but this is on all our vendors. Obviously AWS is one of our biggest and not the biggest line item there. And we just kind of take it from there and there's always trade offs you have to make, but I know there's companies out there that are trying to sell the value proposition of being able to optimize your cloud spend. And that is definitely something that there's a lot of, I'm sure there's a lot of places to cut costs in that we don't know about. And so yeah, I think that's something that we're being mindful of, I'd say. Yeah, the challenge too you see across the board is that there's a lot of things you can do programmatically with a blind assessment of the bill, but without business insight, it becomes increasingly challenging. And you spoke to it yourself, where you're not going to succeed or fail as a business because the bill winds up getting too high unless you're doing something egregious. It's a question of growth, it's about ramping, and you're not going to be able to cost optimize your way to your next milestone unless something is very strange with your business. So focusing on it and do course is almost always the right answer. Yeah, I mean when I think about increasing revenue or decreasing costs nine times out of 10, we're trying to provide more value, right? And so increasing revenue is usually the go-to option for us, but there are some times where it's obvious, hey, there's a low hanging fruit and cutting costs and if it's relatively straightforward to do, then let's do it. And I think with all the cloud infrastructure that we've been able to build on top of, we've been able to focus a lot of our energy and efforts on innovating, building new things, cementing our industry position, and yeah, I think it's been awesome to flourish on top of it. What, want to give you the final word? Any interesting insights in your business?  It's like, I think it was like five, six years ago, the first time I went to Hawaii and I got interested to poke. Everybody in California knows poke, but I live on the East Coast. Now I've got like three places within half an hour of me that I can get it. So, you know, those kind of things, what insights are you seeing? You know, what's changing in the marketplace? What's exciting you these days? Yeah, I mean, for us, we've definitely seen a phenomenon where different food trends kind of percolate across different areas and kind of start in one region and then spread out across the entire United States or even to Canada. I would say, I don't know, we don't, we try to have as much merchant selection on the platform as possible so that no matter what the new hottest trend is, that more likely than not, we're going to have what you want on the platform. And I think what's really exciting to us over the next couple of years is, you know, last year we actually started, we started satisfying grocery delivery fulfillment. So, in fact, we power a lot of grocery deliveries for Walmart today, which is exciting and a lot of other grocers lined up as well. We're going to see how far we can take our logistics capabilities from that standpoint. But really, we just want to have as many options as possible for our customers. Well, anything, thanks so much for joining us. Congratulations on the progress with Dora Dash. For Corey Quinn, I'm Stu Miniman. We'll be back here with more coverage from AWS Summit New York City 2019. Thanks as always for watching theCUBE.


What's up everyone it's your girl Kenzie here from late in sports cards, and I'm ripping a personal for Ryota t We've got a 22 23 Panini Revolution soccer hobby box Alright best of luck Ryota. Here we go Gabriel on the Sunburst to 50 Nice way to start that off Rookie fractal of Ben Pearson. We're sorry diamond diamond in revolution soccer rookie of Campbell Adam Armstrong infinite Richards futures Moises can say no Danny Wellbeck on the fractal odd guard rookie Christensen Chris me fam infinite shockwave KDB Kirian trip tripier fractal Odin's rookie James Garner Raphael Varanny on the infinite got supersonic Minson Rico Lewis rookie on the fractal nice one there man city Mitchell last pack here for you Ryota. Oh, let's switch on the back Julian Alvarez rookie nice Man City Ricky's coming out rookie of Brennan Johnson on the infinite And pull a switch. All righty Ryota that will do it for your box. Congrats on all those different parallels coming out of there Nice looking cards. They'll come right out to you


Namaskar. I am Professor Devdeep Prakash from IT Bombay. Welcome to my course, Business Fundamental for Entrepreneurs, Part 2, External Operations. In the next few minutes in the short video, I will introduce myself and I'll give you a little bit of overview about the course as to what is this course all about, who should take this course, why should you take this course, what is the structure of the course and what can you do to follow up on the course. Starting with my own introduction, I have had the privilege of serving in corporate companies in some of the leading companies of the world like Procter & Gamble and DHL for over 30 years. In the past seven years, I am in academia with IT Bombay at the School of Entrepreneurship teaching and mentoring engineering students who want to be entrepreneur. Apart from industry and academia, I have also led a global NGO for India for a few years impacting a lot of lives positively. So with that brief introduction, let's get into the course. This course is being offered to all of you watching by some of the best platforms and institute in the world is being offered by IT Bombay, which is probably India's best institute. It's being offered on the platform NPTEL, which is probably one of the most popular online educational platforms in the world. And the course is being offered within IT Bombay by the DS School of Entrepreneurship. And we have been offering this course to IT Bombay students in the campus for over four years. And we are now very happy to bring this course to you online in this platform. Why should anybody take this course? And what are the course objectives? As background, businesses today are extremely complex. Companies are very complex entities and have many aspects. Starting with the vision, goal, then going through the purpose, values, manufacturing, quality control, finance, accounting. Then you get into HR and people management. Make sure that you're responsible, well-governed business. And then you move into all the external dimensions of marketing and supply chain and retail, etc. So whether you work for a big company already, or you're thinking of starting up a business, or you're an aspiring entrepreneur, or a student who is trying to make a career choice, through this course, I'll try and help you give a broader perspective of business so you can make informed choices about how you want to go forward in your career or in your academic next course. I'd also ask you to look at the study by the World Economic Forum, which is one of the world's leading think tanks in terms of what are the skills required over the next few years. And 50% of the current workforce have to reskill themselves, upskill themselves in the coming years.  So you do require to acquire new skills. And through this course, I'll try to give you some leads into what kind of skills then you can acquire. So who should take this course? First, students. Students who are trying to decide on what to do next after graduation. Do they want to do MBA? If MBA, which kind of MBA or a technical course or a humanitarian course, or maybe just a functional course. If you're already working, and if you're working in a function, you may want to broaden your perspective for other functions in the company. And that will help you speed it up your career. And if you want to start up your business, you may get a few pointers in this course about should you start your business? Do you have enough skills and knowledge to start? And or when should you start? So these are pointers I'll try and offer you. How is the course structured? So business fundamental for entrepreneurship is actually a two-part course. Part one was run in the previous semester and covers the internal operations of a company like finance, like accounting, like manufacturing, like quality, like purpose and values and vision and mission. Part two, which is this course, focuses on the external operations of a company. How do you work with customers? How do you study markets and competitors? How do you distribute a product? What does the supply chain look like? How do you sell B2B or B2C? So this is what we'll cover in this course, which is business fundamental for entrepreneurs, part two external operations. And what are some of the discussion topics? So the next four weeks, I will take you through module by module in terms of how do you study markets, industries, competitors, players, products already that is existing. So if you want to start up, how do you find a niche in the market? How do you find a gap in the market? I'll then talk to you about customers and customer segments and how do you win with customers? How do you create great value proposition for customers? After that, I'll take you through value based marketing. How do you create value for your customers? And how do you capture value for yourself? And then how do you communicate? I'll talk about branding and advertising and market positioning.  I will then take you through some aspects of selling, sales channels. How do you distribute your products? What is the essence of selling B2B, which means selling to businesses or selling to customers? And then I'll talk you through how do you, how do you do customer service and how to build customer loyalty? And then I'll talk to you about supply chain. How do you manage a supply chain to distribute the products, supplier products across India and someday across the world? So these are the some of the topics that we'll discuss. And then what can you do after this course? So if you haven't done the first part of this course, business fundamental for entrepreneurs part one, internal operations, you can do that. You can do other NPTEL courses, which are more specialized. You can do courses in your own college or of course you can go and start your own business. So I look forward to many of you are watching these videos to enroll into this course, participate in the discussion forums, give us feedback, engage with us and then add value to yourselves and to your careers. And with that, I wish you best of luck and I look forward to having you in my course.


Hi, I'm Matthew coast head dating coach and founder of commitment connection calm and today we're gonna be talking about a Question from someone in our community who's asking will I ever find love? Now that's a hard question for me to answer But I can actually give you a question that you can answer that will Make it easier for you to know whether you're gonna find love or not and so the question that you need to answer is How smart are you going about?   Your chance of finding love is really low if what you've done up until now has hasn't worked out and You plan on continue continuing Doing what you've done up until now so if you keep doing what you've always done you'll Continue to always get what you've always gotten and so If you're just allowing chance and luck to determine whether or not you find love You're gonna have a really difficult time finding love if it hasn't happened already and You know the the other way to use to be dumb about dating and relationships is using bad dating advice a lot of Dating and relationship advice out there is just horrible Advice and if you're spending a lot of time using bad dating advice and getting bad dating advice from people that don't know what they're talking about then You have a really low chance of finding a love. However, you have a high chance of finding love if You find out what isn't working in what you're doing and you stop doing What isn't working right? That's step number one is find out. What's not working and what you're doing and and Stop doing it and number two is getting around other people who have found love already you actually have a statistically you have a much higher chance of Falling in love and getting married and you know finding love and doing all that if The people around you have done it and you have a much lower chance of finding love if the people Around you have not done it already so get around people that have and The third thing that you need to do is you need to start reading and start learning smart dating and relationship advice techniques and tactics and strategies and Use stuff that's smart use stuff that works use stuff. That's helped other people Get to where they want to be in regards to love Finding love doesn't have to be based on luck or chance You can take control of whether or not you find love in your life But you have to take control. You can't just let it happen on its own You know go out there and find information So that's it for this video if you want more information on how to attract a quality man into a committed Lasting relationship make sure you go to my website at commitment connection calm and take my quiz I'm Matthew coast and I'll speak with you again soon