So, what if I told you tomorrow morning you're going to wake up and the stock market is going to be down 50% from where you bought in?  What are you going to do in that particular time period?  What are you going to do? You guys saw in the title of today's video, I am ready to lose 50% on my principal, on my account value in the stock market. And this is actually the unfortunate reality for many people that we're investing in the stock markets in the early 2000s and towards the 2007-2008 period, which is also known as the Great Recession. So, in today's video, we're going to be talking about my mindset heading into the next recession. Like you guys saw, I'm ready to lose 50% of my money. We're also going to be breaking down some individual stocks performance throughout the last recession. We're also going to be looking at some indexes, the S&P, the Dow, and the NASDAQ, taking a look at how they did performance-wise, percentage-wise in terms of the last recession and how much they rebounded from the bottom that they saw the indexes throughout the recession from 07 to 09, also known again as the Great Recession. So, if you guys enjoy this video, go down below, hit that like button. It really supports me and supports the channel in general, and consider subscribing to the channel if you do enjoy the content here, and also hit that notification bell so you're notified every single time that I do make a video. So, it's no news here. It's not a surprise that we are heading towards the end of an economic cycle right now, guys. The bull market has been running now for about 10, 11 years, and we have a recession on average every five to 10 years. So, we're getting towards the end of this cycle. I'm not calling the recession this month, next year, in six months. I'm not going to be that guy, but I will be that guy that's preparing as the recession starts to creep up, because we all know that it's going to happen, but no one knows when it is going to happen. And it's always a good idea to be prepared by having cash set on the side, knowing what you're going to do and having that plan in place. So, let's take a look here at the S&P 500. We'll see how much it rebounded, how much it fell in the year of 2007 through 2008. And you guys can see the previous recession in 2000, how it did as well. So, the market here dropped to a low of $666, all the way down to about $666.79 from a peak of about $1,550. And you guys can see that is over a 50% drop. So, the people that were buying at the peak of the markets here, they were down 50% to 60% on their money if they were investing in the index. And let's say in some individual stocks cases, they were down maybe 70%, 80% and some of these stocks that got hit the hardest. And you guys can see back in the 2000 recession, we were at the same price roughly at about $1,550 and we sold off all the way down to $800. So, the unfortunate reality here guys is if you were to invest in the S&P 500 at the peak in 2000 at about $1,500, you would not have made a single dime in profit until 10 years down the line as the second recession recovered and the bull market started to hit. Because think about it, you invested here, we sold off, we rebounded, but we didn't even get past the previous spot on the S&P 500 that we were at 7, 8 years prior in terms of this peak here. And we dumped, we lost about half of our value and this is the kicker here guys. If you were to panic out of the S&P 500, if you were to panic sell, let's say at like $7,800, you know, you were in the index, you would have missed out on forexing your money because you guys can see the S&P went all the way up to $3,000 nearly, which you know from $6,700, you know, do the math, do 600 times 4, what is that guys? That's about $2,400, so you would have forexed plus your money if you were to buy at the bottom and hold all the way till now, which kind of solidifies my long-term philosophy in the stock market guys and me viewing all of these recession dips as buying points for the long-term, just think about it, you know, if you had a long-term vision here, you know, although we were in a time period where the markets haven't been growing much, you know, over the past 10 years, this would still be a juicy opportunity to hop into some long-term plays, some businesses that have a good economic moat that are going to be here for years to come and you know, history proved itself after that as a lot of stocks did so well from this period guys, a lot of stocks did so, so well, so you guys see 50% drop followed by a 4x on the S&P 500 going over here to the NASDAQ guys, NASDAQ went from 2256 all the way down to about $1,1100 roughly, which is another 50% drop, 50% drop in the NQ and from there guys, it went literally from $1,000 all the way up to $8,000, nearly $8,000 for the NASDAQ and I don't know about you guys, but my math is telling me that that is nearly a 7 to 8%, not 8%, 7 to 8x return on the NASDAQ, so you know, initially, yeah, you're down 50%, you're down 50%, you may be panicking a bit, but if you have that long-term perspective, if you're like, okay, we're seeing this dip right now, you know, stocks are on sale, the amount of cash, the amount of value this business holds is way higher than what the stock price is, hence why the stock is undervalued, okay, maybe this is an opportunity to hop in for the long term and if you were that, you know, using that mindset back in this time period, you would have done a ridiculously good job, you know, on your returns and obviously the NASDAQ is a tech heavy index, tech stocks, you know, from this crash have rebounded ridiculously, just think of Apple, Amazon, Google, Facebook, these stocks have done so well, you know, Facebook actually wasn't around, but you know, the Google's, the Amazon's, the Facebook's or rather the Apple's, they have done so ridiculously well, you know, after the recession, it's not even cool, guys. So how I'm viewing this, guys, is short term, yeah, a recession, it's going to tank the stock market, stocks could be down 30%, 40%, 50%, but long term, that is the beautiful buying opportunities that open up so many doors for building wealth long term, and that's kind of how I'm viewing things, guys, you know, short term, yeah, there's going to be a lot of pain, markets are going to be down, but if you have that long term vision, a lot of these value companies, they're going to be at such discounts, it's not even, it's going to be ridiculous, right, they're going to be at discounts where if you buy in at these dips, the wealth you're going to build through compounding, especially in some of these dividend stocks where the starting yield is going to be a lot higher when the stock is going down and compounding that yield over time, you know, continuously buying more shares, reinvesting, the wealth you're going to build long term is going to be unbelievable, right, which is why I love when the markets drop, I love it, I absolutely love getting in at cheaper valuations, at cheaper prices to build wealth for the long term, so taking a look at the Dow Jones performance, here you guys can see it went from 13,000, 14,000, all the way down to about $65,000 to about $7,000, so that was another 50% drop and from there we rebounded from $6,500 all the way up to about $27,000, which is roughly a 3-4X in the Dow Jones as well, so that's another prime example, markets drop 50%, you know, are you willing to withstand a 50% drop to get a 400% return over the next 10 years? Me personally, I am willing to do that, so you guys can see, you know, the major markets, they got hit pretty hard, but they rebounded very nicely, building a ton of wealth for people in America and across the world and this is kind of how I'm viewing the next recession, guys, you know, if we drop, let's say from $26,000 on the Dow, maybe down to about, you know, $15,000, $16,000 again, maybe $18,000, you know, if we drop from the NASDAQ, you know, upwards of $7,800 here, if we drop down to, let's say, you know, $4,000, $4,500, if the S&P goes from $2950, if it gets back to like, you know, $2,000 flat or like $1,800 or whatever it may be, I'm viewing these as very, very good dip buys to buy individual stocks and ETFs for the long term, guys. There's a bunch of different things that are going through my head, you know, that would be going through my head when the market crashes, right? I'll be looking at some small cap, you know, value stocks and ETFs, small cap growth because for those of you all that don't know, during a recession, during a crash, typically the dividend aristocrats, they don't get hit the hardest, but what does get hit the hardest are the small cap stocks and what rebounds the hardest after the recession is the small cap stocks. So, I will be, you know, investing in some small cap stock funds, small cap ETFs because I am a younger guy, I'm willing to take on more risk and my horizon in the stock market is much longer than some of these other, you know, older people's horizons might be. So, I'm willing to invest in some smaller cap ETFs for that growth potential after the rebound, you know, after the recession. So, very quickly now, now that we saw the overall markets, how much they dropped and how much they rebounded and kind of my thoughts and philosophies behind this, viewing this as a buying opportunity, you know, let's take a look at some individual stocks. We'll take a look at some value stocks and some growth stocks and see how they did after the recession. So, Apple, we love talking about Apple on this channel. Let's take a look. APL 2008 and went from $96. Actually, no, that's not 2008. This is 2008. It went from $28 per share all the way down to about $11 per share, guys. That is more than a 50% drop. That's like an 80, 70, 80% drop or like maybe like a 60, 70% drop in the stock's price. And you guys can tell the rest is history, right? From $12 all the way up to $233. I couldn't even tell you how many doubles that is. The stock has literally gone up like 20 times, 20X from that period. So, if you were able to withstand the initial 60% drop, well, you would have made long term if you had the vision on Apple, you would have made 2000%, right? Pretty, pretty amazing, right? So, Amazon AMZN, this was literally a stock that did amazing as well. Take a look at this. From $92 and an 07, it went all the way down to about $40 in 08. So, from $40, guys, all the way up to $2,000, what is the math on that? What is the math? $40 up to $2,000. Is that literally a 50X in Amazon stock? Yes, you heard me right. You would have been down 50, 60% in 08. If you held, you would have made 5,000% if my math is right, which is ridiculous, absolutely ridiculous. You know, Facebook wasn't around then like we already mentioned. Google, we can see Google went from 350 all the way down to about 130. That's another 50% drop and from 130 all the way up to 1300, which is roughly a 10X in Google stock over the span of 10 years. Think about that, guys. You're literally doubling every year pretty much if we're going 1,000% in 10 years. That's about 100% every single year. So, you guys can see how some of these tech stocks rallied. If we're going into some, I guess you can say more stable stocks, maybe starting out with Disney. You know, Disney went from 34 down to 16 and you guys can see how much it rebounded from there. If you want to see an even more stable, stable stock, you know, Coca-Cola, even Coca-Cola got hit in their recession, right? It went from 31 to about $20. You guys can see, it wasn't roughly, it wasn't really a 50% drop. It was more of like a 30% drop and from there, from $20 all the way to $52, you know, that was a nice little double and ensum since that point in time. You know, PG is another one. Procter and Gamble, that's a pretty safe stock from $72 down to about $46. You guys can see that is not a 50% drop. It was more of, you know, a 30-40% drop and you guys can notice, you know, over some of these more safe value stocks, they don't drop as much during a recession as some of these growth stocks like we saw, you know, Apple, Amazon, Google and, you know, those type of stocks, right? And of course, the small cap stocks get hit very hard as well. You guys can see Procter and Gamble went from $45 to about $111. What are some other ones? You know, Pepsi is a safer stock, I guess you can say, you know, from $77 all the way down to about $47, then all the way up to $134. And you may be asking yourself, you know, are there stocks that didn't go down in their recession? Yes, there are a couple that come off the top of my head. McDonald's being one of them, guys. This was a very good play in the previous recession. And literally, if we zoom in on these years, you know, it went from like $47 and it actually appreciated in value in 2009. It was up to about $65 per share. Chipotle Mexican Grill is another one that went up during their recession. And it went up a lot during their recession, guys. You guys can see, you know, it was at $73. It peaked at about $150, sold off to about $36. And then it started to ramp up all the way back to the hundreds, you know, after that dip to $36, which is really, really awesome. So those are just two stocks that I can personally think of that did quite well during their recession. And guys, I advise you to just take a look at a bunch of these stocks and see which stocks did well, which stocks did poorly, which stocks did very, very well. You know, these are all great things to know when we're investing close to the next recession, right? So the gist of this video, the whole basis of this video is to not be scared about investing during the recession and to be prepared to lose 50% or more of your portfolio, because that's what history is telling us has happened in the prior to recession. So in my opinion, dipping in the markets, 50% drops in the market, 50% dips, you know, these are buying opportunities for the long term. Because think about it, guys, the previous two times we've seen dips like this, it's made us generational wealth if you were to hold 10, 15 years, you know, after the dips, right? If you were to buy even after the 2008 dip, if you were to buy heavily and hold all the way up till now, just think about how much money you would have, right? And let's say we dip 50% now by the year of 2030, in my opinion, in 10 years from now, the markets will be even higher and we will regret not buying if we were to see a recession this year and the markets were cut 30, 40, 50%. We would definitely regret, in my opinion, not loading up and holding for the long term. So I hope you guys enjoyed this video. If you made it this far into the video, I'm currently in Mexico right now, which is why there is no Market Update video today, but expect a Market Update video for tomorrow on Wednesday. It should be coming out. And if you enjoyed this video, go down below, hit that like button and really supports me and supports the channel in general. Feel free to subscribe to the channel if you haven't done so already and you want to see further content from me as well as drop a comment. Let me know down below in the comment section, what do you guys think about this video, this topic?  I would love to know. So I'll see you all in tomorrow's video. Expect a couple of vlogs coming in Mexico, how to trade while traveling, stuff like that, showing you guys the resort, all that type of stuff. I'll see you all there. Have a great one. Peace out.


Uh, so anyway, we have these bunch of shared notes and they're great because they do update like on everybody's phones in real time. But there was something where it was like, who put that on there? You know, I like, I don't remember having the conversation, but I remember putting it on there. And my son went and found the shared note history so that we knew who put it on there and when, uh, and you can get to shared note history by going to a shared note and then, uh, and then you, there's the, there's the shared people in the upper right. And if you tap on that, you can say show all activity and it will show you, you know, on December 19th, it says I made edits on August 7th for this particular note. My daughter made edits, uh, so, you know, it's, um, it's handy. You can see, and then you can, if you tap on that, then you can see which edits it'll highlight, which things that person either added or removed or changed. I don't think I've ever done a shared note. How do you make a shared note, my excellent question. So you, uh, let's say I want to share this note that I have that's not shared. So I would go in notes and, uh, open V note and then at least on my phone and the upper right, I tap the three little dots in a circle and from there, there's an option share note and you can, um, I send it via messages and that way I can choose, you know, how people are sharing it, but, uh, but you could send it via mail or anything like that. But yeah, I send it via messages and then, uh, and then the share options are people that you're sending it to, you can set their permission to be view only or that they can make changes and you can also choose whether the people you're sharing it with couldn't share it with new people. So I could share with you and say, but John's not allowed to share with others. Like it just, you know, I want to be in control or whatever, you know.  Um, so.


day. I'm making Chris a quick lunch. He was out on the water this morning and his boat broke down so he's had a long ordeal trying to get back and he's finally almost back to his truck so I thought I'd surprise him with something good to eat when he got here because we have to drive to Yule after he has a shower and get stressed to take the boat in to get it fixed. So I just happened to have some ready rocks. Now you probably think I can't believe you're using something like that. It's great to have stuff like this on hand for lunches, okay? So I've got beans, pinto beans, I've got rice, I've got burrito shells, fresh chicken that we're going to fry up and slice and put in. I'm making a burrito. I've got some tomato, onion, fajita seasoning which is my favorite and I've got some cilantro paste. I've never used it. This would be my first time using it because I thought it would be easier to keep in the refrigerator than the fresh cilantro because it don't last long and we're going to get started. I'm going to show you what I'm going to do right quick. First thing we're going to do is let me try to get the same term so that y'all can see better. The first thing we're going to do is open the ready rice, put it in our pot. This is just Uncle Ben's or Ben's ready rice jasmine. You can buy any kind, but it makes cooking a snap when you're wanting something quick. Now we're going to pop open these beans and pour them in there with the rice, okay? And that's going to help fill our burrito shell up with something besides kicking. Now I'm going to add a little bit of this in there just because I don't know what it's going to taste like but I think it will be good. So we'll put a little bit of that in there. This is a cilantro paste.  We're going to put in some of my favorite fajita seasoning. I love fajita seasoning more than I like. Let me take this off and grab more. More than I like taco seasoning. My seasonings because of the humidity down here in Georgia always want to clump up and stick together.  I'm going to chop up half this tomato and put it in there. We're using a right enough tomato knife and we're finally getting a little okra out of our garden. I'm super excited to finally have some fresh okra. I don't have quite enough to fry yet but in the next couple of days I will and so that's exciting. I'm just going to put this in there for flavor and for some juice because that rice is not real juicy and you know why it wouldn't hurt for the onion and I would it. What's doing? While we're at it I keep this in a bunch of foil in the refrigerator so that it doesn't smell up the refrigerator and it works good. Come here onion. Lord can't get it out. Chris wrapped it the last time and buddy he wrapped it. Okay I just need a little bit. Here we go with this. It always wants to lift it on the knife. I'll just chop it the best I can. Somebody said one day that they wouldn't gonna watch me anymore after they've seen my knife skills and I thought Lord well I'm not a chef. I'm just a home cook and I think I do pretty good considering. So what I'll probably do is save a little bit of this fresh for the burrito and then put some of this in our beans just let it simmer in there a little bit with that rest of those ingredients I'm thinking it'd be good don't you. It's gonna be delicious and it's so simple and easy. Now the next thing we're gonna do is we're gonna take our chicken and I am going to butterfly it so that it cooks quicker.  Now I'll wash I'm gonna use my other hand and move this camera and bring y'all over here with me and talk about what I watched last night on TV. I watched something on Netflix last night I don't know if y'all seen it or not but it says poisoned or something like that and it talks about our food and it talks about salmonella and food board diseases and oh my goodness I was shocked at what I saw so if you have Netflix I suggest you watch it today or the next time you can. It was really good and I enjoyed it and I learned a few things on it. I learned that I'm not buying romaine lettuce anymore I could tell you that okay but let's get over here and start cooking. So what we're gonna do let's see where I'm gonna put y'all is I gotta turn my light on so y'all can see and we're going to put this back here in the back let's turn it on. You see only I didn't turn on and get preheated this one back here okay this one is preheated just for the burrito shells on a super low and then this one over here is hot and ready for our chicken. So we'll do our chicken right quick let's get y'all all the way back. So all I'm gonna do is put a little olive oil in here use my meat hook grab my chicken I'm gonna season it once it's in here get a little lid over it right quick and we're gonna reach down here and get me some seasoning that I want to put on there because I want something besides just not the easiest seasoning. I want it to be really good. So I think I'm gonna use my chili lime okay I like it a lot. No it's not gonna take that this long. That long to cook. It's twelve oh one. That little water in it and you hear it. Once you calm down a little bit. So there's some of that. We're gonna cook this chicken sorry y'all we're gonna cook this chicken a couple minutes and then we'll flip it. But now if we cover it it's gonna get done quicker on the inside. So I think what I'll do is change locations with it and let's keep this up right quick. I'm gonna put that chicken on the back eye and put a lid on it and it's not that interesting on the back eye for the lid on it. So let's get something stirred this up. We could put a little chili lime in this too. I don't know if I've got it. I bet I do have a lemon or a lime in the refrigerator. I bet I do. But you want it to taste good. So add a lot of stuff to it. This is not a taco seasoning fan. I don't know I guess because I grew up eating it so it's just boring to me. So I like to use these other seasonings in my food. It's a little different than what mama did. So this is gonna be on the inside of the burrito.  It's smoking hot. Y'all look how pretty it is. So let me put this around so y'all can see it good. I'm looking y'all. Here it is right here. Look how pretty it is. So pretty. Okay so now I'm gonna put the lid on it again. Now with that seasoning on that side it's gonna get a lot browner but we want it to be brown and I don't even care if it's a little bit blackened. We're gonna hop over here and get our other stuff ready. Well that's finishing up. So we'll have a burrito shell. Let me put my onion up. Chris has that wrapped in heavy duty foil. He was serious. Alright we got us an avocado. We're gonna open it up real quick. If it's good and ripe and it's at the perfect right unless you should be able to just squeeze it and that middle part just fall right out. Like that. Because lots of times if you try to put a knife in it and twist it then it's kind of hard to get the knife out of it and to me it's a little bit dangerous. I can't help but think that. Okay. I've got some of this fresco crumbling cheese and it's about to go out of date so we're using it today too. Since it's going out of date I'm just gonna slice through it with my tomato knife. And we're gonna put this on our burrito. Okay. So let's slice these up and get them ready while our chicken cooks. Y'all tell me how your day's going. Chris did not have a good day. His boat's torn up. He's on his way home. I'm sure he's sad. That means he will be with me for a few days because he won't be able to get out of my boat. So I will have company, my husband's company. I bet he goes to Savannah and does another video for y'all while he's out of a boat. Alright there's our avocado. We got onion. Let's chop up the tomato. We need to go flip our chicken before I mess something up. Let's get our tails over there and get it done.  I cook my fish on high. I cook a lot of stuff on high. That's how I like food. This chicken should be done. But I'll leave it on that side for just a minute. I'm gonna turn off the eye. I'm gonna turn off the back eye. And so the only eye that's gonna be on now is this front eye. We're gonna let this chicken rest about five minutes before we slice it for our burritos. So while we're doing that, I'm gonna finish chopping up my tomato and then chop up some of this cheese. It says it's crumbling cheese. I bought this the other day because I was gonna make that. I don't know if y'all seen it or not, but I made that Mexican corn. And I couldn't find the right cheese. Well then I found the right cheese and so I had this left in the refrigerator. It's something I don't ever buy. It says it crumbles. I don't know. Let's see if it does really. Yeah, it does. So we'll use this crumbling cheese on it. There you have it, crumbling cheese. You can use this on that corn, too, if you're making the Mexican corn. And that's probably enough cheese for me and Chris. He's not a big cheese eater. Alright, so there's our extras. I guess you'd call them. Let me wash my hands, y'all.  It's done. I'm gonna chop it right here. Let's get it and let it rest right there for a minute. But it has been in the pan for a little bit resting and I think we could go ahead and start slicing into it.  But I think I'm gonna get a different knife to slice it with and throw away some of my mess while I'm at it. Grabbing what's handy or I'll slice it with this one. So I'm just gonna slice it out of diagonal. And remember we had the lid on this chicken so it's definitely done. It's probably a little over cooked to tell you the truth. But that's alright. It's gonna be good in our burrito. Now that's not on that show. They had the main companies that sell chicken. And I'm gonna tell you my favorite ones. And then y'all can let me know if you haven't tried them and then if you turn around and try them, what you think about them. So let me get this sliced up though. It's a hard thing if you let it sit out and rest. It also continues to cook a little bit because it's so dog on hot. Now let me show y'all this. There's our beans back there and our rice. Well that was easy, wasn't it? And then here's our preheated skillet. And I have a sign. Where did I put it? It was hanging right here. Where did I put that little sign? Anyway, poultry's supposed to get cooked. Let me turn this around and tell y'all. Poultry's supposed to cook to 165 degrees. When I started this show I didn't have a clue. I just cooked the hound out of it like mom and dad. But anyway now I try to cook it a little bit less just so it's a little bit juicier. But you still gotta make sure you cook it enough. So most of my recipes I tell you how thick it needs to be and how long you need to cook it first side. And this rice is sticking to the bottom. I gotta get it off the... Let me take it over here for Prius. We'll go ahead and make me one, y'all. We need to get out some sour cream, but we'll go ahead and make me a burrito. And then he should be here any second. So I'm gonna take a burrito shell out of this. Oh, there it comes. There it comes, y'all. Give him some cheer because he's had a really hard day, haven't you, Prius? No. I'm gonna say hello. I'm making you a burrito. I told them I was making you something special since your day was so long. Let me give y'all a kiss. Yeah, kiss. What? Oh, I was looking for sour cream. I'm just standing here wondering what in the world I'm doing. Alright, so we're gonna make a burrito right quick. Y'all ready? Here we go. I got everything over here. I guess I'm gonna have to bring my burrito shell over here and make it. That's alright. Let's make a swan. Here's my burrito shell. Beans and rice. Some chicken. This'll be a big one. A few onions, some crumbling cheese, some fresh avocado. And I'm gonna go ahead and put the sour cream on it. Why not? Where's my sour cream? I'm making a mess. Here, here it is. We're gonna go over here. Let it get warm and wrap it up. I just move y'all around everywhere. So, it's already pretty warm. So when you wrap a burrito, it's pretty warm.  I can't hardly get it in the burrito shell, but you try to flip the bottom up, grab it, push it together and turn it. Okay, let's get it on a plate. Oh, you know what? I've got some enchilada sauce in here in the pantry. Let's go look at my crazy pantry. It's not in the best of state. But let's see if we can find some sauce to go on the top. Now, I know I got some salsa, but what we're looking for is sauce. You can tell how I got all my meat over here. There's some red enchilada sauce right there. Refried beans. I keep my beans on this side. I'm running low on mixed vegetables, carrots. I can tell when I'm running low on the way I've got my pantry done. And there's my broths. You can see I've only got one chicken because I make my own chicken most of the time. So I don't keep a lot in here. Of course, I got me some Eagles, Table Syrup, mayonnaise, my beans. And then here you'll see my sauces and condiments. Somebody's saying I forgot the tomatoes. Okay, I'll put them on there. I'll put them on the top. You want some of this on there? On your burrito? No. You want salsa medium? It's got a lot of stuff in it already. Yes. Some of the green pepper. All right. So let's put it down on a plate, put your tomato on it, and then you can sprinkle it with this and try it for them. All right, y'all. Y'all are just going to watch Chris eat. How's that? He's going to sit right here at the bowl. Just come on over here. You want a can of Coke or something? See what we got. Yeah. There you go. Flip it upside down, but other way. There you go. All right, y'all. Chris likes this hot sauce. I don't think this is. All right.  They want you to put tomatoes on it. What about avocados? I got avocados in it. I got sour cream in it. I got onions in it. I just forgot to put the tomatoes in it. There's rice and beans in it. There's lots of spice in it.  No, I got chicken in there. I made you some chicken. So we're going to let him try it, y'all. See what he thinks about our concoction today. So you can tell if you get a bag of this rice that's already ready, how quick you can throw a lunch together. What do you think? Does it have plenty of flavor? I put a lot of fajita seasoning in it and I put a lot of chili lime. Has it got too much? No? All right. It's got a lot of flavor. It's delicious, ain't it? Delicious. Delicious. Y'all, it's delicious. So don't feel embarrassed to go to the grocery store and pick up some canned beans. After talking to the guy, I'm serious. Y'all need to go watch that show I was telling you about. About the food administrations and what they regulate. And to tell you the truth, eating canned vegetables is really safer than eating fresh vegetables from the grocery store. Okay? And then I got this ready-made rice because they do have to adhere to certain things. They don't have a lot of regulations, truly, for salmonella with chicken. So they sell chicken with salmonella. Period. That's why you gotta cook it. That's why you have to cook it. And they say it's up to the people that buy it to know how to cook it, okay? So that you don't get it. As long as you bring it to the right temperature, especially hamburger meat. And that cheap hamburger meat that you can buy, those pre-paggies and stuff out of the freezer. They can have up to, it's said, they can have a lot of different animals. Meat in them. So you gotta be careful what you buy. And make sure you cook it all the way, okay? Now steak and stuff like that, it's typically on the outside of the meat. And that's why ground beef is so dangerous. Because the ground beef, it's the outside that gets ground with all the inside. So then everything gets it. But with a steak or a roast, it's on the outside. So if you sear it and you get a good brown on it, it kills it, okay? That's why they serve steak burgers in restaurants. They don't serve ground beef. That's why they have the ground steak in a restaurant. And you can get it at a medium or a medium well or whatever. You know what I'm talking about. Anyway, y'all go watch that show on Netflix. It was really informative. I can guarantee you one thing. I won't be buying any more romaine lettuce. It seems to be one of the scariest ones. Spinach can be too. So that's it. Y'all have a wonderful day and we thank you for watching Collard Valley Cooks. Where we cook, like our mama's did. My mama didn't have a lot of this stuff, I'll be honest. She didn't have no crumbling cheese. She didn't have no... She would buy minute rice. My mama would buy minute rice. And we didn't grow up eating sour cream and avocados. We're so blessed today y'all. We have so much more that we're used to eating that we never got to have eating growing up. So y'all have a wonderful day. And come back and see us. Bye y'all, love ya.


Hey, this is Brett and this, 2020 Ford F350 Crew Cab Long Box XL STX is stock number 13634Z. I'm here at Summit Automotive in Fond du Lac, Wisconsin, you're new and used heavy duty truck headquarters. This 2020 Ford F350 has the 6.7 liter power stroke diesel engine. It puts out 475 horsepower, 1,050 foot-pounds of torque. It's paired up with the 10-speed automatic transmission. This truck has been fully-safetyed and inspected by our service shop, has a fresh oil and filter change. All the fluids have been checked and topped off and it is 100% ready to go. I'm going to go all the way around in this video inside, underneath, start it up and take a look under the hood to give you the most accurate representation possible. Black agate metallic is the color and I shoot all my videos in 4K. So if you have HD capabilities on your computer, tablet, smartphone, or television, recommend turning those on right now because it is your best way to check out the quality condition options and cleanliness of the truck before seeing it in person. As you go down the driver's side here, the duly tub and box are in fantastic condition. Driver's side doors and cab are in really nice shape as well. Didn't see any dents, didn't see any dings, paint is very shiny and reflective, front fender is in great shape. If you like the video, you can subscribe to my YouTube channel, which is youtube.com slash Summit Auto. Click the bell notifications and you'll get updates on the videos I do each and every day here at Summit Automotive. And you'll also have access to one of the largest catalogs of vehicle walk-arounds on YouTube so that's pretty sweet as well. This one has the polished aluminum wheels and these are 17-inch wheels and it has Michelin LTX AT tires. These are LT245, 75R17s and I'd say they have probably about 70 to 80% of the tread left on them. Frame and underbody is exceptionally clean on this truck, which you'd expect on a 2020. I wanted to show you that black gate. It's got just a little bit of metal flake to it and a little bit of gold flake to it, one of my favorite blacks that are out there. Headlight lenses are nice and clear, front bumper and lower valance are in excellent shape. I didn't see any dents or dings on there, looks really good. I really like the new grills that come on the Superduties, they look really good. The hood is in fantastic condition as well, didn't see any dents or dings in there and it does have cab lights up top, those are LED cab lights. Passengers side front fender, no major dents or dings on there and the passenger side front wheel, no major scuffs or scrapes. As you go down this side of this 2020 Ford F350, take note of how clean that body is, how reflective and mirror like that paint is. I take these HD videos so if you are far away or even if you're close by, just cannot make the trip down but you're still interested in purchasing the truck, you can see the truck, hear the truck and have confidence in the vehicle that you're looking at. Before you even get here, so when you do get here, there's absolutely no surprises and you can make a smart and informed buying decision from wherever you're at and if this video helps you make that buying decision, let your salesman know that you saw the video that it was helpful and that Brett sent you. Back wheel is in excellent condition as well and the back tires have just as much tread as the front tires. The front and underbody back here looks good. It does have the camper package with the anti-sway bars and of this one of course has all the remaining factory exhaust so it hasn't been altered in any way and the underbody looks really good on this truck. Dualy tub is in nice shape, I didn't see any major rock chips or cracks in it. Coming around to the back, the rear bumper is in great condition. It does have of course the full towing package which includes a receiver hitch for pin and seven pin wiring and the tailgate is in really nice condition as well. Has the truck's port soft tonneau cover, I didn't see any rips or tears on there that looks really good and it comes with a linex spray and bed liner. Get these side box tie downs and the bed is in very nice shape on this truck. That spray and bed liner goes onto the tailgate linex. I consider them to be the best bed liner out there, I got it on my truck, love it. Back wheel is in excellent condition as well and once again down this side of the dualy tub looks really good. This one does have the telescopic tow mirrors, they're heated and have built in directional signals that telescope out like so and fold in like that. Inside the XL package gives you the grey cloth interior, 40-20-40 split bench seating in the front, no rips or tears on these seats, they are in fantastic condition. I don't think this truck's ever been smoked in, you do get a lumbar right there. LED rubber floors, auto headlamps, tilt telescopic steering wheel, power windows, locks, and mirrors. Take a quick look at the back seats, they are just as clean as the front seats, no rips or tears back here and it does have the latch child safety system for any child car seats, you may want to put it back here. Fixed glass rear window, these seats fold up for extra storage and you get the nice flat floor back here. Jack tools, pull that strap, get those down. Side curtain airbags, child safety locks on the back doors and of course the inside and bottoms of the doors all look really good on this truck. We'll hop inside, check out the miles, the radio, and everything that this truck has to offer on the interior. You can see that this one has 16,975 miles, you do get a compass and miles to empty display. Instrument cluster is very nice and clean. Comes with the multi-function steering wheel, cruise controls and information center controls on the left. Steering wheel is in nice condition, I didn't see any major wear on there. Bluetooth and audio controls on the right, there's your shifter for your 10 speed automatic transmission. This one does have AM FM capabilities on here, you can also hook up your Bluetooth cell phone on there as well. And I think you got to have the truck on for that to work. Has the factory exhaust, brake stability control, hazard lights, volume and tune controls, turned out four wheel drive, factory brake controller and climate controls down here. You do get a USB jack and 12 volt power point as well as two more 12 volt power points right there. Passenger side glove boxes, floor and seat are an excellent condition, no rips or tears on there. And the headliner is in really nice condition as well. You do get the six upfitter switches right there and map lights. We'll start it up and take a look under the hood. That's right up, no check engine lights or anything like that. Did want to show you the tire and loading information sticker as well as the VIN sticker real quick. Turn those lights on too. I would personally like to thank you for checking out the video today and hopefully from this HD video you've been able to verify the quality condition options and of course cleanliness of this truck all the way around inside. Now under the hood we have the 6.7 liter power stroke diesel engine bay, is very clean runs, very smooth. Once again this truck has been fully safe and inspected by our service shop, has a fresh oil and filter change, all the fluids have been checked and topped off and this truck is 100% ready to go, there's the emissions sticker. And I would highly recommend this truck to make quality and condition standpoint. I don't think you'd be disappointed in this one and the Seymour pictures of this truck are one of our other 550 new new cars, trucks, SUVs, minivans, Wranglers, half tons, three quarter tons, one tons, you name it, we've got to go to that website right there, summitauto.com. Full pictures and descriptions of every single vehicle, all at summitauto.com. If you'd like to check out more HD videos you can go to youtube.com slash summitauto. Click the bell notifications to get updates on the videos I do each and every day, as well as access to one of the largest catalogs of vehicle walk-arounds on YouTube, so check that out there. In fact in a second you'll see a link to subscribe to my YouTube channel in the upper left. Link to more F350 videos that I've done in the upper right, a link to this vehicle on our website in the lower left and a link to one of our latest YouTube videos in the lower right. So check us out. We're super excited to help you with this ultra clean 2020 Ford F350 Crew Cab Long Box Dually XL STX in black agate metallic. Thanks again for checking out the video. Remember to like, subscribe, and share on the YouTube channel. I really appreciate it. Thanks again.


Hello, my name is Sergio Svedra and I'm a technical marketing manager here at GitLab. In this short video, I'm going to show you a new feature introduced in GitLab 13.3, which is Edit Feature Flag User List from the UI. Here's the sample project. It's called DemoFFUL. This is a public project that you can access and clone. And it comes with its own instructions on how to set it up and run it if you want to clone it and replicate it in your own environment, GitLab environment. The back end is using a Kubernetes cluster that is running on GKE. And it has auto DevOps enabled. It also uses three environments. You will see that later. It uses a QA environment, a staging environment, and a production environment to be able to also show you the different capabilities of Feature Flags. So Feature Flags is a way to control the audience that will be getting new functionality that you're introducing in your application. And so let's go to the Feature Flags console. So here's where you configure Feature Flags. The configure information is you need the API URL and the instance ID of the Unleash capabilities. We're using Unleash, which is an open source project, to implement Feature Flags. This is installed on GitLab and it's a server. And you need the instance ID and the API URL to be able to call it from your application. So this information you need to include in your project variables. There's more information about how to set these up in the instructions and the written file. But here, for example, you see this is the Unleash URL and the instance ID, which is these are the values that were shown in the previous screen. You also need a PIMP file. You can follow the instructions again to go through the steps on how to get that. I've chosen to disable call quality in this project to make the pipeline faster. And I will also enable staging so that we can have that extra environment. Let's go back to the Feature Flags dashboard. So the new capability introduced in GitLab 13.3 is the ability to create new lists of users. So here we're going to create a new list. We can call it the FF for Feature Flags, user list two, create this new list. And then we can add users. And here we add user IDs or emails, in this case, let's add Pluto at gmail.com. And then we can also add a magic at cfl.com. There you go. So now we have these two users in this user list. And now once we have this user list, we can create a new Feature Flag to use this user list. We can call this FF test two. And then we need to add the strategies to the Feature Flag. So for QA, let's actually use our user list. And here we select the number two that we just created. And then we can add another strategy as part of this Feature Flag. And for this one we'll use staging. And for this strategy, we'll do it for all users. So let's just leave it like that. And then one more strategy for production. And for this one, we can do a percent of users. And we can do 80%. And then we create the Feature Flag. Good. So now we have FF test two.  And here this is how the Feature Flag is being unleashed or used within your application. So let's add, let's actually edit it. And we created a new Feature Flag called FF test two. So what this is going to do is going to check that if this Feature Flag is on for the specific users that we've designated, they will be the only ones seeing that new Feature. And if they are not part of that Feature Flag, then they will just see Hello World. Obviously, this is simple functionality. The idea is here that you will have a lot of logic here that is a modification to your application. So let's just commit to master. And this is going to fire up a new pipeline. So in this case, we're using auto DevOps and we've added a QA environment and also a manual stage and job here that will be deploying a running application within QA. We'll also deploy it to staging. And finally, we'll do a manual deployed to production. And as part of the project, we have a client that will be running. Here it is from the terminal, from my local laptop here. That is going to, it's basically a for loop and is going to loop over the different environments. So this one is going to be QA. The next loop around is going to be for staging. And the last one is going to be the production environment. And for each of the environments, what it's going to do is going to basically log in, register and log in the user. And the users are here. So these are the list of users, Pluto, Magic, Pluto at gmail.com, Magic at CFLR.com, Mickey at Disney.com and Hulk at Universal.com. And remember these first two were part of our feature flag for the user list that we created contained only these two usernames in there. So and in one of our strategies, we are targeting these two users only for the new feature. So you'll see when the script is executed that for part of the strategy, if I remember correctly that we did was for QA, so for QA we will see that only these two emails or users will get the new feature. And these two will not. They will get the old feature or the old application without any modification. And then it'll loop around again and it'll do the same thing for staging. For staging, we define that all users will get the new feature. So we should see that every one of these users, Pluto, Magic, Mickey and Hulk, will get the feature, the new feature. And for production, we define that only 80% of the users should get the new feature. And since it's four and it's 25%, so we should see the three of these folks, three of these users will get the new feature and one will not. Very well now that the pipeline has completed, you can see that the application has been deployed to QA staging and I manually deployed it to production and everything is green. So now let's execute the client. But before we go there, let's go back to the feature flag. The feature flag we're about to execute is this, FF test two. So let's execute the script and let's see for QA, according to the strategy, only the users in list two should get the new feature. So that should be Pluto and Magic and indeed Pluto and Magic got the new feature and not Mickey or Hulk. For staging, we had a strategy that all users would get the new features and new feature and they all did here, all four of them. For production, we had defined that 80% should only get it. So 80% of four should be three individuals. So and Pluto, Magic and Hulk got it and not Mickey. So what we've seen in this video is we were able to use the brand new feature of user lists and the ability to define them via the GitLab UI. In this case, we define a new user list called user list, FF user list two with two usernames in there to emails. From this screen, you can manage the lists, you can edit them or delete them. We were also able to create a new feature flag that made use of that user list called FF user list two and we were able to apply that to a strategy for QA. Very good. So I hope you enjoyed this video and we'll see you next time. Thank you.


Everyone, welcome back to theCUBE's coverage of .com, Splunks.com virtual event, their annual summit. I'm John Furrier, host of theCUBE. We've been covering .com since 2012, usually a physical event in person this year. It's virtual. I'm here at Claire Hawken who's the CMO of Splunks. She's been here three and a half years, your first year as CMO. And you got to go virtual from physical. Welcome to theCUBE. Good to see you. Thank you very much, John. Great. So I got to ask you, I mean, this has been the most impressive virtual event. You've taken over the hotel here in Silicon Valley, your entire, the entire teams here. It feels like there's a dynamic of like the teamwork. You can kind of feel the vibes.  Tell us what's happening. It's been, I think for everyone a year where we really hope to be back to having a hybrid event, so having a big virtual component, but running .com as we had before from Las Vegas, which wasn't possible. So what we thought in the last six weeks is that we would actually bring the Splunks studio to a physical location. So we've been live all of this week from California where we're sitting today and really thought through bringing the best of that programming to our amazing audience of 26,000 people. So we're sitting here in the studio. We have a whole live stage and we've activated the best of .com to bring as many Splunkers as we can and as many external guests to make it feel as real and as vibrant as possible. So I have to say, I'm very impressed that since 2012 and watching the culture evolve, Splunk has always been that next big thing and then the next big thing again. It seems to be the theme as data becomes so bigger and more important even than ever. There's a new Splunk emerging. Another kind of next big thing. This kind of says the pattern Splunk, do something big, that's new, operationalize it, do something new again. This is a theme, big part of this culture. Can you share more about how you see this evolving? Sure, and I think that's what makes Splunk such a great place to be. And I think it attracts people who like to continually challenge, reinvent. And I think we've spent a lot of time this year building out our portfolio, going through this cloud transformation. It just gives you a whole new landscape of how you unlock that power of data and how our customers use it. So we've had a lot of fun always building on top of that, building our partnerships, what customers do and really having fun with it. I think one of the best things about Splunkers, we do have this incredibly fun and playful brand and as data just becomes something that is more and more powerful, it's really relatable and we have fun with activating that and storytelling. And you have new manager, Teresa Carlson came in from Amazon Web Services. You have a lot more messaging, kind of building on previous messaging. How are you handling and looking at the aperture of that's growing from a messaging standpoint? You have a partner verse, which is rebranded of your solution, of your ecosystem. Kind of a lot of action going on in your world. What's the update? It keeps us busy and I think at one end, the number of people that are using Splunk inside any customer base is just growing. So you have different kinds of users and this year we're really working hard on how to partner and position Splunk with developers. But at the top end of that, the value of data and the idea of having a data foundation is something that's incredibly compelling for CTOs. So working really hard about looking at Splunk and data from that perspective as well as the individual uses across some areas like security and observability. You know, one of the things I wanted to ask you is I was thinking about this when I was driving in this morning. Splunk has a lot of customers and you keep your customers and you have a lot of customers that organically came into the Splunk through the product leadership and just great product. And then as security became more important, Splunk kind of takes that territory down. Now mainstream enterprise with the platform are leaning into Splunk solutions and now you got an ecosystem. So it's just becoming bigger and bigger. It just seems that the scale of the Splunk is growing radically bigger than it was. Is that happening? And what's your take on that? I think that's definitely a thing, John. So I think that the power of the ecosystem is amazing. We have customers, partners as you've seen and everything just joins up. So we're seeing more and more dot joining through data and we're just seeing this incredible velocity in terms of what's possible and how we can co-build with our partners and do more and more with our customers. So Splunk moves incredibly quickly. And I think if anything, we're just gaining velocity which is fun and also really challenging. Cloud scale and certainly during the pandemic you guys had a tailwind on the business side. Talk about the journey that you've had with Splunk as in your career and also for the customers. How are they reacting and what can they expect as Splunk continues to evolve? I think we're working really hard to make sure that Splunk is easier to use. Everything gets every more integrated. And I think our goal and our vision is you just, you just capture your data and you can apply it to any use case using Splunk and to make it sort of easier to see that data in action. And one of the things I love from today was the dashboard studio. They're just these beautiful visualizations that really are inspiring around how data is working in your organization. And for me I've been a Splunker for three and a half years and I just think there is just so much to do and there's so much of our story ahead of us and so much potential. So just really enjoying working with customers on the next data frontier really. You have the Jedi Knight from Star Wars speaking. We do. You had the F1 car racing, Lando was here. Kind of the young Jedi, the old Jedi. Kind of the generations are coming together. You're seeing kind of that old IT world which relied on Splunk and now you have this new developer, real time shifting left with security, DevOps now going mainstream. You kind of have the confluences of these cultures coming together. It's not really clashing. How are you handling that? How do you see that and what Splunk kind of doing? Because I can see the themes. Am I right or am I going to? No, no. One of the stories from this morning that really struck me is we have Cal Poly and we work with Cal Poly on their security and they actually have their students using Splunk and they run their whole security environment. And at the very top end, you have Walmart, the Fortune one just using Splunk at a massive incredible scale. And I think that's the power of data. I mean data is something that everyone should and can be able to use and that's what we're really seeing is unlocking the ability to bring all of your data in service of what you're trying to do, which is fun and it just keeps growing. We had Zach Brown on the CEO of F1, McLaren team, racing team here on theCUBE earlier. And it was interesting because I was like, driving the advantage with data, kind of cliche, but they're using data very specifically, highly competitive. It almost kind of feels like a cloud kind of scale model because they've got thousands of people working on the team, they're on the track, they're competing, they're using data, they've got to be agile, they've got to be fast, real time, kind of sounds like the current enterprises these days. Absolutely, and I think what's interesting about McLaren that the thing I love is they have hundreds of terabytes of data, moving it just at incredible speed through Splunk Enterprise, but it all goes back to their mission control in the UK and there are 32 people that look at all that data and I think it's got a half second delay and they make all the decisions for the car on the track. And that I think is a great lesson to any enterprise is you have to bring all that data together and you have to look at it and take decisions centrally for the benefit of your whole team. And I think McLaren is a really good example of when you do that, it pays dividends and the team has had a really, really great season. Well, I want to say congratulations for pulling off a great virtual event. I know you had your physical event on track and literally canceled in the last minute because of the pandemic, the Delta virus, but it was amazing, made for digital TV kind of event. Absolutely. And this is the future of media. Absolutely, and it's a lot of fun and I think I'm really proud. We have done all of this with our in-house team, the brand, the experiences that you see, which is really fantastic and it's given us a lot of ideas for sort of, digital media and how we storytell and really connect our 20,000 customers, our 230,000 community members and keep everyone connected through digital. So this has been a lot of fun and a really nice moment for us this week. You know, it's interesting. I was saying to the team here on one of our breaks is that when you have this kind of agility with media to tell your own story directly, you're almost telling more stories there before and there's a lot to tell. You have a lot of successful customers, the new partners. What's the coolest story that you've seen? What would you share that you think is your favorite if you could pick one or a few of them? What are your top stories that you see happening? So I've talked about Cal Poly, which I love because it's students and the scale of Walmart, but there are so many stories and I think the ones that I love most are the data heroes. We talk about the data heroes a lot at Splunk and the people that are able to harness that data and to take action on that data and make something amazing happen and we just see that time and time again across all kinds of organizations where data heroes are surfacing those insights, those red flags if you like and helping organizations stay one step ahead and Conf is really a celebration of that. I think that's why we do this every year and we really celebrate those data heroes. So across the program, probably too many to mention, but in every industry and at every scale, people are making things happen with data and that's an incredibly exciting place to be. You've got a lot of great customers to use as references, but I have to ask you as you go forward this year in marketing, what are your plans to take on this new dynamic? You've got hybrid events, you've got the community is always popular and thriving with Splunk, large-scale enterprises, global system integrators, doing business deals with you guys. As you guys are continuing to grow and grow and grow, what's the strategy? How do you keep the Splunk coolness going? Because you guys are growing so fast, that's your job is to keep things on track. What's your strategy? I think I look at that and just we put the customer at the heart of that and we think who are the personas? Who are the people that use Splunk? What's their experience? What are they trying to do? What are those challenges? And we design those moments to help them move forward faster and so that I think is just a really good North Star. It's really unifying and our partners and customers and every Splunker gets really behind that. So stay focused on that. Well, Cliff, thanks for coming on theCUBE. Really appreciate it. Congratulations for a great event and thanks for having theCUBE. We love coming and sharing our media partnership with you. Thank you for coming. Thank you so much. And next year is your 10th year, John. So we look forward to celebrating that as well. Thank you very much. Thanks for coming on. Okay, there's theCUBE coverage here, live in the Splunk Studios. We're a virtual event, but it's turning it to be a hybrid event. It's like a VIP event. A lot of great stories. Check them out online. They'll be recycling through so much digital content. This is truly a great digital event. I'm John Furrier, host of theCUBE. Thanks for watching.


We're going to look at an acid-base reaction between HCl gas and ammonia gas. There's still a transfer of a hydrogen ion from the acid HCl to the base ammonia. It will produce ammonium chloride, which is a solid, which we'll see as smoke coming out of the tube. I'm going to add some concentrated aqueous ammonia to one of the flask. We're going to add some concentrated hydrochloric acid to the other flask. Most of our studies with acids and bases are going to be in solution, but you do not need to have an aqueous solution to have an acid-base reaction.


thank you to Hugh for making such a nice introduction of me, so there's no need for me to talk too much about myself at this point. But one thing I think for sure is that I'm just very passionate and I love coming to, you know, being an advocate, I travel to conferences and meeting people, understanding what your needs are, and then of course I'm advocating too. And these days I'm doing more about event streaming, things in that space. So that's why to even today, let me kind of look for my clicker. Where's the clicker? Oh, right. Sorry. So I'll be talking about really examining about, you know, a bit deeper about terminology. Is it just semantics? Is it reactive or eventful? Or are they actually the same? And so, yeah, so with that, let me start. So, so just to give you a background, I when I joined IBM, like three years or actually, I should say 2018, so before COVID, way before COVID. So I kind of got asked, there was a, at the time, IBM had a partnership with LightBand. So that's how I started working with some ACA integration and then advocating for that. And that's how I met Hugh and LightBand, all the great folks there. And there's just been such a great, you know, friendship and reactive has always been dear to my heart. And it's just something about it, right? And just working with events, you know, in that space, although in the reactive though, I'm noticing that the word events has never been really like formally kind of put to the forefront somehow. So I kind of get into, that's why I want to get into this topic. Now I'm working with the event streaming specifically Apache Pulsar, which I actually will have a talk this afternoon too. So with that, let me kind of, let's go back to some basic first. So what is reactive, right? I started looking into some basics. So reactive basically refers to distributed applications that meet, you know, the kind of respect that for core principles, attendance of reactive manifesto, responsiveness, elasticity, resiliency, and message driven. So I don't need to explain too much. Everybody in here already expert on that field. And, but then the thing is too, it's interesting, as Hugh has mentioned too, initially the reactive manifesto came out and that's what I was going by. But then I actually visited the site reactive manifesto and realized there's reactive principles and that's been like added to that, which is kind of nice because I think it's now kind of bringing the manifesto, but okay, again, manifesto is a bit more in my mind, right? Thinking more of an abstract kind of conceptual thing that we need to achieve. We need to have systems that are all those four like kind of principles, but how do we actually make it happen? So it gets into reactive principles in our design, which, you know, it's kind of nice that saying that I think we need to stay responsive. However, that's, I think that's where I feel that maybe the word responsive, if you go deeper, right, is beyond just the word itself, it can also mean is it responsive for data that's in at rest? Is it data in motion or in transit or is it data in use, right? So there are different state of data too that we need to be worrying about responsiveness.  So I think with reactive systems too is basically dealing with, you know, data in all states and being very responsive is my understanding. Anyway, then of course too, we need to accept uncertainty and then with reactive way of doing things is asynchronous by nature. That's very much like decoupling the space and time, right? So very, you know, so there can be things uncertain too. There could be network failures that we cannot assume network is always up that type of stuff. And, you know, uncertainty failure and then assert the autonomy and tailor consistency of these things that are still kind of high level. But I kind of like the fact that we really are decoupling the space and the time too. So you make, you know, your style of programming or design, everything is very asynchronous in nature and also handle dynamics. So over there too, as we know, it's kind of like the diagram that we describe the manifesto in there. So, okay, so that's reactive. Now the thing is too, as I'm kind of working more with events streaming these days and nobody talked about reactive, but I kind of tried to draw some comparison between, you know, these two camps of thoughts, right? So I call it like the alphabet soup of event computing. As we know these days, events, you know, and, you know, it's been kind of overloaded in the marketplace. The marketing team like to use that as a way of attracting attention. And certainly it has a track a lot of attention too. And I go to speak at conferences, a lot of people may be curious, but the actual number of people actually using event driven systems or using, you know, asynchronous style of messaging are not that many for some reason. People are probably more curious than they are actually doing things. But anyway, so I kind of decided to look into all the terms, right? So they're like, you know, essentially too, there's event, if you talk about events, you know, I kind of not highlighting those in here, event sourcing, event driven architecture, event processing, event streaming, event messaging, all of these, and essentially too for events, right? And if I look into like the basic definition of an event, you know, breaking it down like an atom too, it's basically an occurrence in space and also time. So think of like XYZ coordinate, if you need to represent an event, right? And then, and it also has a time component to it. But the difference is that we don't like use one, one way of capturing the state, state changes. Essentially, we want to capture each, well, okay, so that way, that way, events basically are kind of finite too. So an event occur so you cannot change it. It's kind of immutable at that point. And then you are changing the state changes of that event, as the data kind of travels through time. So the thing is too, at the core of it too, is that event messaging, event streaming, processing, all of these are dealing with data. And especially in today's world, this massive amount of data too, can be, you know, mostly too, are kind of events are data, mostly like in motion or in use, rather than at rest, like, you know, maybe reactive systems, maybe also working with data at rest, because you need to be doing some sort of processing to data that's in a database or storage like that. But anyway, so that's just, at least in my mind, that's what I'm looking at it too. And also too, I've highlighted a couple of things too that I feel reactive systems are already kind of employing this react event driven kind of way of doing things. You know, it doesn't say it out loud, but it is actually using event driven way of doing things asynchronous, perhaps like messaging can be using pops up way of doing things, right, and doing message queuing, depending on your, you know, your, your usages of these things. But ultimately too, they are also talking about building data pipelines too that are, you know, highly, you know, you can kind of stream data, like ongoing delivery of data, really fast and everything like that. So that's reactive systems. And then of course too, it gets into serverless applications to serverless to by nature too, it's already using kind of an event driven type of approach and, and can also be kind of applied to like reactive systems as well for serverless type of applications or at least this is how it's being defined in the field. And then there's also like microservices too as Hugh also brought up, right, these days we're all talking about microservices and then the nature of microservices so decoupled in nature and also like ideal for cloud native environment stateless is the way to go. But you can also support like stateful microservices as well. So all of these two are kind of, you know, all, all these are really about event computing reactive is also so, but I think that if reactive definition is kind of higher level of abstraction, that is kind of not just about the event event may be kind of working more with, you know, the mechanism of messaging of streaming processing all of these, whereas reactive is probably like a higher level that you have all these goals you need to achieve as it's more abstracting out what is needed. Okay, so basically too, if I kind of look through all of these, I find that, you know, these are like just some of the goals, right, where we're talking about apps that needs to be responsive, right, it can be, it also should be real time too, especially in event streaming cases. The real time is actually the goal of such to everything, you know, not quite exactly real time, but it, you know, strictly speaking is basically near real time is what we're looking at. And then also too, they are both to event streaming in today's world event messaging all of these and reactive, they also are, you know, targeting targeted in this cloud native environment that that is like so, you know, kind of so important too, because in any any kind of cloud native environment, you are being charged, you know, by the by your usage. So you want to make sure that it is very efficient is what it is. So and also the aspect of recoverability from failure as well. So it's kind of their resiliency should also be built in. And then also to very asynchronous, the messaging and processing part, there's no time that we can, you know, allow it to be wasted, basically. And also to one aspect of using event streaming or event way of doing things are essentially and with reactive systems is that you can actually enable your, you know, your data to be built as data pipelines to our system. So you have data that flow flows through different systems and then you can use different languages to implement your flow of your system of your data through the system as well. So ultimately too, I think it is what it is, is that event streaming event computing reactive systems are basically we want to make a system that's resemble how the human brains work. How do we interact with people? We don't, you know, when we do things, right, we, we, we would be always doing things in asynchronous manner. Nobody is doing things like synchronous, right? If you're talking on the phone nowadays, you want to talk and both can be talking at the same time. All of these is a way of kind of, you know, kind of a resembling what real, real life should be like that. So, so that's how like we then even driven approach reactive systems are enabling us computers to work closer to how human beings think. But I guess unfortunately too, what I'm finding is because the way we've been taught, you know, in school, when I first started school, we're being taught to program in synchronous style blocking fashion. You're, you have a request, you send the request to your processor, it come, you have to wait for it. And then when it's done, then it sends back the response back to you. So that's, I think that's how our minds have been trained because that's probably the easier way to do when we first learn about computers rather than thinking of things asynchronously. But I think that's the thing is that we are trying to do systems that are more asynchronous these days. So, yeah. So ultimately too, having, you know, systems that are more resembling real, real human interactions is that you're bringing it, bringing it more like status satisfactory in, you know, customer experience and more effective applications too. Okay. Okay. So then this is just what I'm kind of thinking in my mind is that we have the event streaming all of these event kind of things and they kind of comes together essentially trying to wear what we're trying to do is build better systems that resemble how the human, human beings do things. So that's how this, okay. So, but I like to, before I go to just want to think of some challenges too, right? Right now, as I'm finding, right? I mentioned about, I go to talks and finding there are lots of people with lots of interests, but only usually to it, every conferences, you have a few people that know the systems very well and they come, come out with difficult questions. Those are really valid questions. But the majority of folks too are still kind of asking or learning about it. So I find that maybe, you know, because of this paradigm shift that's needed for us to learn, so perhaps too, we can think more about how can we make these systems to be more approachable by, you know, more folks if possible, right? And also too, because business too are not willing, they're usually impatient and, you know, with kind of anything that's more difficult, it takes more time to, you know, to be educated in order to know how to do things. So that type of stuff. So can we kind of make the tooling a little better? Maybe. And kind of make it easier for people to use. How can we design tooling to kind of serve people better? Basically. And also too, some of the other things I like to kind of think about is we want to kind of build in, you know, guaranteeing security of message delivery. That's also very important and also like easier to debugging and observability kind of aspect too. And then we can actually do some like education on the grass root level too. Maybe to schools to start teaching kids through to think, you know, asynchronously, maybe we can increase the adoption eventually. Like, so it makes it more mainstream thinking rather than people coming out and learn things the old way, then it's harder for you to switch to the new way. So that's that. Okay. So before I go to just thought I kind of share with you because I was at a couple of conferences was kind of talking with some folks and this one too. I think it's a prime example as to why we need to definitely advocate for event driven systems, event streaming and reactive systems. I was actually talking to an architect of a major pharmaceutical company here in the Midwest and he was describing to me this problem they are trying to solve. And I think, you know, he was talking about some of the problems about, you know, you don't want to be waking up in the middle of the night to fix things. If you can do things more event driven, it's actually easier for your life. But this particular example of the pharmaceutical company is that they are trying to do, okay, they're selling pharmacists or medicine, right, to end users, but or consumers. But the thing is too is that, you know, they are going to always going to, let's say, a CVS or a Walgreens kind of, you know, middleman. So they have been only doing B2B type of business, but now they want to get into B2C, so directly to the consumer. So take for example, if you're, you know, you get medicine for a diabetes patient. And the thing is we want to maybe have devices of measuring the blood level sugar of the patient that's taking the medicine and if it drops, right, you want to be able to have it notify somewhere that maybe, you know, your pharmaceutical company, they want to keep track of all of these use cases. And so if there's a drop in your, you know, blood sugar level, you want to notify, maybe you want to notify not only, well, the patient itself may not know himself or herself, but you want to notify maybe like their family, somebody close to their, you know, or some legal guardian or something to notify them. So then they can take action on, you know, kind of telling the patient, please take your medicine, you forgot about your medicine, something like that. So I think it's really exciting is that event-driven kind of approach can be applied to so many creative different ways that you can actually improve human life. And in this particular case with a diabetes patient or any kind of patient they're taking medicine, you use this kind of system of being able to measure somebody's health and then being able to notify anybody that are taking care of this person.  So anyway, so that's just an example of what I think this, you know, is just an exciting field that can be applied to so many creative ways that can enhance our lives and not only enhance, but really save lives too in some cases. So I think then with that, let me kind of go into here. I just want to say thank you again. If you want to stay in touch with me, these are my LinkedIn and Twitter handle. And also I have a Discord server too, where I actually answer questions, but I actually have a Twitch channel too. But if you come to my talk, I'll share that with you. But otherwise too, I've been doing a lot of different things in my Twitch, so you're welcome to join me. So with that, thank you so much. And everybody, please enjoy the conference. And thank you so much again to LightBand, to Hue, to everyone giving me this opportunity to share with you. Thanks.


Okay, I'm Hanok, I'm from Cisco System, and I'm going to present to you a small project that we created to test our routers and our feature on the router. It's called QX, and actually it was my first journey in the open source because my friend told me, try to open source it. Don't put it in your drawer, and this is the result. Okay, so I'm going to talk about traffic generation, how we are doing it in Cisco to test our routers, and it's all based on software. Okay, today there is a DPDK library and I will talk about that. So because I have very, very short time, I will talk about stateless and advanced stateful mode of the traffic generator. Let me start with the result. The result after we open source the traffic generator, it seems that many has the same problem. Many needed traffic generator to test their routers. So for example, many open source start to use T-Rex. Like OpenNV, DPDK if you want, FIDO, Cisco internally, and many things in Cisco and Intel and Melanox, and Red Hat and Small. This is from an analytic on our documentation. You can see that it's growing about 1,000 users actively. And this is the mode of operation because there are many types of modes that you need to test. There need to be modes of operation from the traffic generation. For example, you don't need realistic traffic to test a switch, right? Because there is only a switching of packet of simple lookup. But when you want to test snort that doing inspection and normalization or DPI environment, you need to create a realistic traffic, something that with Layer 7 that simulate client, servers, and application. If you want really to evaluate the performance of the gear that you want to test. So there are in general two modes of operation, stateless and stateful. One of them is I will talk about advanced stateful and I will talk about stateless. The problem that we try to solve again is to estimate the performance of stateful features on the router. Stateful feature on the router behaving in a weird way. You know, for every flow we open a context, we cache the clients, cache the server, try to normalize the traffic and so forth. And by bumping a UDP packet and short packet, we won't get any reasonable number, right? It won't give us anything. But because of that, we need to generate realistic traffic. The problem is that realistic traffic really cost, really expensive, like 500K for 50G or 100G. And it's not flexible and this is the reason that we open source this. So what is T-Rex? T-Rex is a software. It's an application, it's a Linux application. It sits on top of DPDK and it's exposed a free way of mode that I've already talked about. And using that, it can come with a container and it's scalable. Everything is about scale and virtualization. This is how, you know, I perceive it. It's really, really fast. Everything is from bottom up is scale. And this is the slide I'm using in Europe. There is another slide for the US. Okay, let's talk about Stateless. Stateless is a way to generate traffic to test switches. It's composed, the building block is a stream. We call it a stream. And you can add more stream, remove stream. And the API is JSON-RPC and we created a Python that simplified the way that you can work with it. So there is a server side, you install the T-Rex server, and then you interact with it with the client, with the Python. You add stream, remove stream, get statistics, start it, and everything else. There is a nice GUI that works on top of this API, on JSON-RPC API. And let's see what is stream. This is the traffic mix that we are using. So you can build a profile that builds from streams. In this example, there is three streams. The blue one, the green one, and the yellow one. So the blue one is a packet that I can generate using Scapi. Anyone knows Scapi? So you can build a packet, a template of a packet, and then you can build a program that changes the packet over time. For example, I want to create a range of source IP to destination IP. And then I can choose the mode. The blue one is continuous, just bump the packet in specific rate. The green one is a burst of packet. Let's say I want only three packets. And the yellow one is the multi-burst with inter-packet gap, inter-burst gap, and I can connect them. I can create a program that say when the green one finished, start the yellow one and then point to another stream, it's like a program that you can build on Python, using Python. Let's see how simple it is before that. So this is the architecture, the high-level architecture. There is a server. There is an RPC using JSON-RPC. There is a data path that I talk later on that is scalable with the number of scores. As you add more cores, you will get linear scale with the performance, which is really, really high. And then come the Python that encapsulates all the JSON RPC into a nice API. And there is a Java API for someone. Ericsson is supporting that. And there is a GUI. And there is a console. There is the API. We're just wrapping everything for the users. So we separated the definition of the profile from what to do with the profile. This is the definition of the profile. I define this as the low-word of a profile of stateless. We defined really a simple continuous stream with this definition. Ethernet over IP, over UDP, over 10Xs. Okay, this is the packet. There will be a different type of packet from different direction. From one direction it will be 16.001 to 48.001. And the other direction is the opposite. This way we can create B-directional traffic. So this is the profile. And then we can manipulate the profile, load it. So there is a console that you can start the profile, load the profile, get statistical about the profile, and so forth. And there is the API. This is the API impact on that we wrap everything. So in this way we are connecting to the server. And then reset everything, reset all the statistics, add a stream that I showed already. Clear the statistic, start the traffic. And here I can multiply and say that the traffic that I want is 5 megapacket per second for a duration of 10 seconds. And then I can wait. After I wait, I can get statistics, how much packet, how many drops, how many packets were sent, and so forth. So a really, really simple API. And T-Rex do the hard work to separate what you ask it, what you ask him to multiple core. It's by magic dunder. You don't need to separate the profile. So this is the thing that we do for you. This is the performance. This is on the XL710 on one core. You can see that we can reach to 30 megapacket per second in one core. And it's linear scale. So it's all about the performance. So let's talk about stateful. Stateful is more for features that inspect the traffic, like DPI, like SNOT, like firewalls, like NAT. They need to generate stateful traffic. In this example, T-Rex can act like a server or like a client and generate traffic on top of TCP stack that we wrote. The reason that we wrote the TCP stack is that if you will take TCP stack from Linux, it won't scale. It will scale to 1 million packet per second, and we needed much more. We needed 10 million, 40 million active flow generating 200 gig. And this is how we did it. We took a BSD, a native BSD stack, and we changed it in a way that it would be multi-core. Every instance of the... Every thread instance had its separate stack, and we did, through the API, through the control plane, separated the application to each core. And we managed that. From the perspective of the user, you see one box that do one thing. Okay, so there is a layer of emulation of application on top of TCP stack, on top of DPDK, and everything is event-driven. Every core has an event-driven loop. No thread, nothing. No locks, no interaction between them. Only a messaging between the core. And by that, we can reach really high-scale. This is an example for the emulation layer. Okay, the clients, for example, do a request, and then wait for a response, and then can do a delay of random, and then send another request, wait for response and close. The server side do the opposite. You wait for the request, send the response, and so forth. Okay? This is just the low-word of the lower-level microcode that we have in the emulation layer. Let me show you a real profile. Remember the profile of the stateless? It was Python. It's talk about streams. Here we are talking about application on top of TCP stack. So in this example, we have a utility that can take a pickup file, convert it to the instruction that the emulation layer understand, and then replay it on top of TCP stack from the client to the server, and so forth. And by that, reaching millions of servers, millions of clients talking to each other, and exercise the device under test with millions of flows. I will show a performance. Just to dive in what we are doing inside, so from simulation point of view, from the client side we are simulating, creating the socket, connect. Once we got the cincinac, we are writing a buffer to the TCP stack, and then reading. This is an example of write and then read. And then we close the flow. From the server side, we don't open all the servers ahead of time because we cannot do that, right? Let's say we have a millions server. We won't do the bind and socket because we might not need all of them. So we have a special API today because we rewrote the TCP stack from BSD.  Once we get a packet to a server, we dynamically simulate everything like it created the socket, bind, listen, and then start the program. But you don't need to do that, right? This is internal. You just need to define what you want to do to provide the pickup, and we will do it for you and get all the statistics. This is an example with two templates. There is a ton of statistics. Statistic is the God here, right? We cannot miss even one packet. So you can take a JSON of all the counters from the TCP stack, from the flow table stack, from UDP, and from other layers of the traffic generator. I want to touch really one point of the complexity in what we did. This is a real engine, by the way, of the car that I showed you before. So let's see what is the problem with scale with TCP. This is one flow of TCP. In the transmit side, you have a sliding window. Let's say 32K or 64K. This is how the Mbuff. Mbuff is a layer inside the kernel that manages the pointer inside the packet. This is how a packet looks like. It needs 32K. In the worst case, if we need 10 million flow, let's do the math. 10 million flow multiplied by 32K, it's about close to half a gig of memory. But we cannot have half a gig of memory for 10 million flow. It's about 40 million flows. So what we did is we changed the API of the stack. Instead of pushing the data to the stack, the stack is asking the data from us, from the upper layer. And by that, we are saving a lot of memory. We can use for 10 million flow only .1 gig of memory. And you don't need to do anything. You just need to write and you can use one of the profiles that already have and you change it a bit and we will do it for you. The same problem happened in the ARX side when there is a drop. There is a window that tries to accumulate everything. Okay? And just to show you the last comparison, we compare NGNX with T-Rex to T-Rex client and server. And the performance is factor 100 faster and from memory perspective is 3 orders of magnitude. That's it.


Howdy, so I'm going to share a couple of things before I get deep into my topic. This here, GoDogGo, which is actually a Dr. Seuss book, this was my favorite children's book. Now, I'm going to own up to this because I don't care. Not only was this my favorite children's book when I was a child, but it was my favorite children's book into my early teens. I don't know why it was just something about it, maybe because I like dogs, you know, all these dogs in here, but this was one of my favorite children's stories. This here is Reality Check by Guy Kawasaki. If you don't know who Guy Kawasaki is, you need to go and look it up. The guy's written tons of books. He was basically the guy who helped Apple become what it was because he knew marketing and all this other kind of stuff. Anyhow, this is a brilliant guy. I hold this up because, one, this is an autographed copy of it.  Anyway, I got an autographed copy of it and I'm in the book. It's hard to see, but I'm kind of, well I'm in one of these, somewhere here, because I helped to edit the book, which was really a lot of fun. Now, I'm talking about both of these because the first one I told you was a children's story. The second one wasn't really a story and yet it's told in story form.  In this book, this is exactly what he did. He had all these different stories. He had ideas of things that he came up with, trying to make illusions to one other thing. He said, you know, like this is something like this, or can you imagine that someone did this and whatever, but it's told in a story form. And you know, I have people always asking me about, you know, how I write and I've done, you know, previous video on writing tips a couple of years ago. Actually, I guess it's 2013, we'll say a few years ago. When I talk about writing all the time, and I like to talk about blogging, and I tell people in person and I write about it in the blog, but I don't necessarily talk about it in the videos, how every day I see everything as a story. When things are going good, I see it as a story. When things are going bad, I capture it as a story. Oddly enough, it keeps things from getting too tense when things are bad, and when they're good, it's even funnier. You know, so I like that idea of being able to tell stories. And I think that if more people could figure out how to be conversational in their blog writing, that they would probably do a lot better. People would certainly react to it a lot better, and they'd get better comments because there is a way of breaking things down in a story.  What's going on? People are telling stories. If you're meeting someone out for dinner and it's just the two of you, what are you doing? You're telling a story. You're always telling stories. Even in school, in between all that other stuff that you really didn't care about, sometimes you didn't care about, sometimes you did, there was a story. So we love to tell stories. We love to hear stories. Maybe there are some stories that we've heard way too often, like the stories my mother tells about me as a child that, okay, I've heard that story, mom. Do not tell the lady in the checkout the story about something I did at age two. It may be cute, but she doesn't care. At least I hope she doesn't because I'm standing right here. I don't need to have that story again. So I like to think that you can tell a story. Now, here's the thing about telling stories. A story is both as short or as long as it needs to be. So one of the things that I think of every once in a while is, like, I wrote this post a few weeks ago talking about 31 things people do wrong in blogging and social media. Not the exact title, but we'll just run with that for a while. And it was actually was 31 things. So I basically sat down and I wrote an outline for 31 things. 16 about blogging, 15 about social media. So I wrote this thing. And then I went in thinking that I was only gonna have a post about 1,000 words and ended up being over 4,600 words. Why? Because with each thing that I put down, I had a little story to tell. They weren't overly long stories because it had never been my intention to expound three or four pages worth on each one of these categories. But still, I thought of every single one of them as a story, as something personal, short personal because I just wanted to hit it and quit it. Okay, we just went James Brown, I don't know why. But I think of these things as stories and it makes it easier to tell. I did another video a long time ago where I was talking about speaking in public and how I never write speeches. And what I do instead is I write out an outline. I write up my points because I know what they are and then I can talk about them and I can expound on them because, in essence, I'm telling stories. Even if it's a teaching moment, if I'm talking about and this means nothing to most of y'all. If I'm talking about a healthcare finance thing, and I'm telling people how to research revenue codes and match them up with diagnosis codes so that they can get their bills paid. Well, there's a story in there. I mean, the way I'm telling it because this is something I've experienced. It's something that I've worked with other people in doing. So even though it's a teaching moment, like I said, it's also a story. So I think that a lot of writing has to do with mindset.  Everybody I know tells a story. Even people who are shy as anything, once you get them talking, they can tell stories. They may not be the best at it, but they can tell a story. And you can tell a story as well. That's why I say, you know what, you might as well do videos. If you're gonna do a video no matter what you're talking about, do the video as a story of some sort. Anyway, that's what I got for you today. Tell a story. Write a story. Think about it as a story. Let me know your thoughts. Tell me a story. Bye.