Hello, everyone. Welcome to Options with Doug, streaming live daily on Bookmap Discord and the Bookmap YouTube channel at 1.30 p.m. Eastern Time. Before I get started, I need to go through the general disclosures. All bookmap, the minimum materials, information, and presentations are for educational purposes only and should not be considered specific investment advice nor recommendations. Risk Disclosure. Trading futures, equities, and options involves substantial risk of loss and is not suitable for all investors. Past performance is not necessarily indicative of future results. Here's my contact information. The best way to get in touch with me is through Discord. My name on Discord is Doug P. Also in Bookmap Discord, there's an Options-Doug Chat channel that's a great place to post questions, comments, and content related to the topics of my presentation and the topics of the channel which I'll go through in just a moment. I'm also on X, formerly known as Twitter, and my name there is at Doug Plass. The focus of my presentation today and the focus of the Options-Doug Chat channel is options, order flow, the impact of options markets on stocks and futures, and the influence of market maker hedging flow on price action. I have a two-step process for trading and the first is planning, and I use positional analysis. I look at how traders and market makers are positioned in the options market and how those positions change from day to day to develop a thesis regarding the expected trading range and volatility for the day as well as the directional bias. And the second step in my process is execution. I look at real-time order flow in Bookmap and real-time market maker hedging flow in SpotGamma Hero to confirm my thesis and for setups for entries and exits. And when I talk about setups today, setups can be taken any number of ways. For example, the S&P 500 setups can be taken with futures, with ES futures, spy shares, spy options, SPX options, or even futures options. Questions and comments are welcome, and I will be watching both the Options-Doug Chat channel and Discord as well as the Chat and YouTube for your questions and comments. Please feel free to post and I'll do my best to answer your questions. Here's my agenda for today, Monday, November 13th. First of all, I want to go over news items, upcoming for the week, economic data events. They are not any earnings that I'm watching this week. Then I'll go through my positional analysis, then I'll review some setups from earlier today, and then I'll take a look at the live market. And when I get to the live market, if anyone has any stocks they want me to take a look at, please let me know and I'll be glad to do that. Alright, let's start with news items. First of all, there were a couple of bond auctions this morning, six month and three month, 11.30 a.m. Eastern time, non-event. Then tomorrow the events really get started with the CPI data at 8.30 a.m. Eastern time. That could definitely be a market mover. Then on Wednesday at 8.30 a.m., PPI data and retail sales come out. Again that's 8.30 a.m. Eastern time. And then tomorrow morning is the VIX monthly options expiration. Thursday, 8.30 a.m. jobless claims. And then on Friday there is some data out, not really anticipated to be a market mover, building permits, 8.30 a.m. Eastern time. And the big thing on Friday is the options expiration. That is the November monthly options expiration. And as the week goes on we'll take a look at that expiration to see whether puts or calls are dominating. And that will give us a clue as to how the market may respond after expiration. Alright, that is the upcoming economic data. Alright, let's start with the positional analysis for the SOB 500. This is the ES Futures and Book Map. Before I take a closer look at this chart, I want to take a look at a larger time frame. And good afternoon Don. Welcome. Glad you're here. Alright, let's take a look at a larger time frame. I'm going to go to an SPX chart. This is a 30-day one-hour chart. Let me point out the key turning points on this chart. I have them shaded in these small rectangles. First of all, that is the September jobs report that came out Friday, October 6th. October 6th, Gamma Squeeze. Price found resistance right around $43.90. Move lower. Interest rates were increasing. There was the incursion of Hamas into Israel. And then this is the October 20th options expiration. Very put dominated, negative Gamma. The expectation was for a put-vanna rally. That really only lasted for a couple days. The market continued lower. Traders were buying puts before the weekend. And then there was a huge implied volatility collapse put-vanna rally after that was on, began on October 30th, Monday, October 30th. Again, huge IV collapse. Looks like there was some consolidation. And then last Friday, traders decided the magnificent seven stocks had dipped enough. And they were aggressively buying calls for most of the day. And that drove a huge rally on Friday. And note at the beginning of the day on Friday, Gamma Notional was negative for the S&P 500 and NASDAQ and now has shifted to quite positive after that huge rally. So there was certainly a put-vanna component to the rally last Friday as well as the call buyers and the magnificent seven stocks. We'll take a look at and see what traders are doing today in those stocks. All right, so that is the, those are the key turning points. Now let's take a look at the levels on the chart. First of all, the dash purple lines are showing the lower and upper weekly expected move. This is based on the options market. That's for the week. It's updated once a week. Then the dash blue lines are showing the lower and upper daily expected move. I update that once a day. Again, that's based on the options market. There are also some spot gamma levels on this chart. I'm going to point out the key daily levels. These are provided to spot gamma subscribers in a variety of trading platforms. This is thinkorswim. Again, I'm going to point out the key daily levels. First of all, this is the put wall. That's the strike with the largest net negative gamma that can be expected to act as support. Note that level did move higher from 4,000 on Friday to 4,200 today. So a bullish shift higher and the potential floor for price for SPX. The next level up is that the 4,395 volatility trigger and that is spot gamma's proprietary volatility flip level. Below that level, market makers position on the gamma curve is negative. In a negative gamma environment, market makers have to trade with price to hedge their delta exposure and that tends to enhance or increase volatility. On the other hand, above that level, like SPX is trading now, market makers position on the gamma curve is positive and a positive gamma environment, market makers have to trade against price and that tends to subdue or decrease volatility and leads to smaller trading ranges, more range days, mean reverting range days. Just above that is the absolute gamma strike at 4,400. That's the strike with the largest absolute positive and negative gamma. And that is where most of the gamma weighted open interest is concentrated in a positive gamma environment. That highest level of gamma weighted open interest can often act as a pin. So price, there's a good potential that price may be focused on that level. As the wheat goes on towards expiration. Then the next level up is the call wall at 4,450 and that is the strike with the largest net positive gamma that can be expected to act as resistance. And that level did move up from 4,400 on Friday to 4,450 today. That's also bullish. The volatility trigger also shifted higher. So 3, a hat trick for SPX, volatility trigger put wall, call wall all moving higher. That is bullish. Let's take a look at a one day chart for SPX now. So there's this, that was Friday I highlighted that. Showed that on the larger timeframe chart. I'm going to zoom just a little bit. This is SPX for today in this dark shaded portion to the right. This is the volatility trigger 4,395 acted as support and that was the great launching point for along today. Price moved up a little bit more than I thought. Passed the spy 4,40 level almost to this combo L3 level at 4,424. That was noted as resistance in the spot gamma AM founders note. All right. So those are the SPX levels in play for today. Now let's take a look at book map and book map. I have my own cloud notes. So I can show SPX levels. Most important today. There's the 4,395 volatility trigger that did act as support. Great launching point entry point for along today. Here's the spy 4,40 absolute gamma strike. So I have SPX levels, spy levels. There's the spy 4,41 level. That's not a spot gamma level. That's just a round number level that did act as resistance. And then there's this combo level up above that I mentioned. And this is how I frame movement in the SMB 500. I'm looking at SPX and spy levels as the key levels for movement within the SMB 500. We'll talk more about setups in a few minutes. All right. Note there is a difference in price between ES and SPX. And today it is, earlier it was a little bit lower than 14. And today it is somewhere between between 14 and 15 this afternoon. So I'm using 14. So ES minus SPX is 14. That's what I'm using. So I'm showing the SPX 4,400 level at ES 4,415. All right. So so far today those are the levels in play with the again the key level being the 4,395 volatility trigger acting as support. All right. For spy there were several shifts in levels. The volatility trigger call wall and absolute gamma strike all shifted higher. So bullish shifts higher. A hat trick for spy as well. And the put wall did move lower. And I really consider the shift higher and the shifts higher and the volatility trigger call wall and absolute gamma strike as more important. All right. So my thesis for the day based on the shifts in levels for the SP 500 was definitely bullish. All right. Let's take a look at NASDAQ now. This is the NQ futures and book map. And again I'm going to take a look at first of all one isolate QQQ levels. So we can see the QQQ levels in play for today. Note the sharp fee reversal that was not really at any key level but then just a very mechanical uptrend up to around the 378 level. Let's just zoom this chart a little bit so we can see the spot gamma levels in play for today. So QQQ trading above its volatility trigger and note above the 380 level. You really can't see the label there but that is the call wall. The call wall has remained at QQQ at 380 for QQQ for some time. So earlier today the 377 level act has been acting as support. All right. So that's QQQ and there's that 377 level acting as support. Let's take a look at NDX this 15,500 level definitely in play for today in DX. There's the 15,500 level and that is a large gamma two level. All right for QQQ the volatility trigger and absolute gamma strike shifted higher. Put wall shifted lower and for NDX also a hat trick. Volatility trigger, put wall, call wall all shifted higher. Let's go back to NQ now. Lunchtime consolidation between 377 and that 15,500 level. Now it looks like NASDAQ wants to break out above that 15,500 level. All right. So thesis for the day for NASDAQ was also bullish based on the shifts higher in levels and one of the key levels for today was right around the lower day they expected move for NASDAQ that was not really tested just above that level earlier this morning. All right. Let's take a look at gamma notional to see how market makers were positioned on the gamma curve at the beginning of the day or positioned on the gamma curve. Alex asked do I consider icebergs? Yes I do. Very important information for creating futures. And I'll talk when I talk about setups today the icebergs were a key in that long at the 43.95 level. All right. Let's take a look gamma notional for today. This is how market makers were positioned on the gamma curve at the beginning of the day for the S&P 500, NASDAQ and Russell 2000. Note all these. The numbers for S&P 500, S&P X and Spy very positive and it's been quite a while since I've seen a positive number for Spy. So this is a very positive, positive notional gamma in this position. Traders are short calls. Market makers are long calls. That's the assumption that spot gamma makes. So market makers have to trade against price to hedge their delta exposure in this positive gamma environment. As price goes up those calls start to increase in value and they have to sell futures to hedge their delta exposure. And as price drops those calls lose value and market makers can buy back their shorts. So market makers are trading against price. All right. So for QQQ the numbers also positive. These numbers shifted pretty strongly from Friday. So on Friday gamma notional was negative for S&P X by QQQ and shifted quite positive today. Still negative for the Russell 2000. Let's take a look at the Vantemodel now to get an idea of what this means. I'm going to start with S&P X. Earlier today the low of the day for S&P X was again that 43.95 volatility trigger. Let's zoom in on this chart. So first of all let me explain what this chart is showing. This is the Vantemodel delta notional. This is market makers delta notional on the vertical axis and price on the horizontal axis. There are two curves on this chart. First the light gray curve shows how market makers delta notional changes with changes in price only. And then the purple curve this is what we focus on shows how market makers delta notional changes with changes in price and implied volatility. And that change in delta notional with the change in implied volatility is the Vant effect. Vant is the second order Greek. All right. First of all let's locate 43.95 on this chart. Somewhere around here between these two lines. So what this is indicating is this morning as price was increasing there was a very, very slight Vantetail one. Really not much. S&P X trading pretty close to the bottom of the curve. Let's see where S&P X is trading now. So right around 44.18 somewhere just right at the bottom of this curve. So there's no Vantetail left at all. And if price continues to increase market makers delta notional will start to increase and they'll have to sell futures to hedge their delta exposure. And that is typical of a positive gamma environment. So we know gamma notional was positive at the beginning of the day and S&P X is trading above its volatility trigger. Let's take a look at spy. Spy low of the day. Right around 4.38 and a half. Somewhere around here. So very again a very slight Vantetail one to the morning. Right now spy is trading right around 4.41 close to the high of the day. Right on the bottom of the curve. And finally QQQ QQQ low of the day. Let's see where that 3.75. So again a very slight Vantetail wind QQQ actually still negative for the day trading right around 3.78 toward the bottom of the curve. So no no more Vantetail wind enterprise starts to increase. Market makers will have to start selling futures. They will sell NQ futures for QQQ. All right so Vantetail not that much of a component in trade today. Like it was in that huge rally that I talked about from October 30th that IV collapse put Vantetail rally. All right let's take a look at some setups now. So first of all my thesis as I mentioned before bullish on the S&P 500 and NASDAQ and based on the positive gamma notional looking for lower trading range more subdued price action today. Now that's all dependent on other factors as well. You know of course both the NASDAQ and S&P 500 are index of stocks and there are seven stocks at least that are huge drivers of price action in the both the NASDAQ and the S&P 500 and it certainly pays to watch those every day. All right so let's take a look at some setups now. First of all I'm going to take a look at what options traders have been doing today. I'm going to start with the S&P 500. This is the hero signal hedging impact real time options. What this chart is showing is price for SPX and the hero signal for a combined signal of SPX by XSP and ES futures that showing what options traders are doing and all those instruments and market maker hedging activity. A rising line indicates traders are taking positive delta positions and market makers are hedging that by buying futures. On the other hand with the falling line indicates traders are taking negative delta positions. Market makers taking the opposite side so they have to sell futures to hedge their delta exposure. I'm going to zoom in on this chart and I'm going to focus on first of all the morning and this was not a very clear signal so focus on the I'm focusing on the long setup the reversal higher at the hedge wall the volatility trigger 43.95 and really took a while for options traders to get going. Let me zoom in this chart so we just see the so there's the signal in the morning looking for a long entry you know if you were just looking right around this time like I was so what I saw is price moving down to a potential support level 43.95 volatility trigger traders start taking positive delta positions and then looking for a long entry. Alright so let's go take a look at book map take a look at the clues and book map. Let's go back to the ES I'm going to zoom in. Alright so I'm looking at this level to act as support potential support. Alright so first clue just looking at a very short time frame I saw that traders were taking positive delta positions with a rising hero line. I have a potential support level large traders coming in with iceberg orders so Alex there you go yes I do consider iceberg orders that shown by this on-chart indicator as well as the rising light blue line and around that level also notice cumulative volume delta rising you can see this final shift and volume dots the volume dots are showing market buy minus sell but magenta dots indicate more sellers than buyers green dots indicate more buyers than sellers and note that price was making a series of higher lows so I knew that at least in the very short term traders were taking positive delta positions aggressive buyers were coming in right at that 43.95 level large traders with iceberg orders and then as price starts moving higher buy stop orders help to feel the move higher that shown by the yellow line there and again remember my thesis for the day was bullish so there were a number of ways to take this as I mentioned in my introduction by futures you could buy a call in futures spy call SPX call so a number of ways to take this trade or call spread typically not the best trade skewed is not favor call spread buying call spread typically. Alright so the initial target for this setup was at 440 the 440 absolute gamma strike some consolidation at that level but price continued on higher after a little bit of consolidation up to 441 and note that buy stop orders help to continue to fuel the move higher up until about 12 o'clock. Alright so that was the long setup in the SB 500 the hero signal for SB 500 did did not provide the most clear signal let's go back and take a look at hero again zoom out so it took a while for that options traders they were up and down but hero started moving higher until around 1050 11 o'clock and let's go back go back to book map and that's when price was approaching this 440 level absolute gamma strike that was the call wall last week. Alright let's go back to hero now alright that's the SB 500 come back and look at the entire day so so far for today hero is trending negative now and that's pretty negative minus 2 billion so traders are buying puts today and that activity has been pretty steady since about 1045 buying puts and then right around 1150 they stopped buying calls they started selling calls sorry about that nothing I did alright so note right now both lines are moving down that's typically a pretty strong signal and notice the price responded up until about 130 when traders started buying calls again alright let's take a look at NASDAQ so NASDAQ this is the combined signal for NDX QQQ not very clear today not really providing much of a clue so in that case I like to look at this combined signal for the Magnificent 7 and there you go this is what has was certainly driving both the SB 500 and NASDAQ on Friday and again today so this is a combined signal for the second stocks known as the Magnificent 7 Apple, Amazon, Google, Meta, Microsoft, NVIDIA, Tesla very very good leading indicator of price action very good confirmation let's zoom in on this so this is when price started to move higher just before 10 a.m. traders started taking positive delta positions and note very typical behavior right around noon just before noon traders take their foot off the gas stop taking positive delta positions and price moves lower consolidates alright let's go take a look at NASDAQ so we see this turnaround point just before 10 a.m. take a look at the NASDAQ chart so here's that turning point just before 10 a.m. just above the lower daily expected move let's zoom in on this just a bit and you can see the shift in order flow aggressive sellers on the way down falling yellow line indicates sell stop orders fueling that move lower then aggressive buyers start to come in and price starts to make higher lows as traders were taking positive delta positions in the mag 7 so the reversal point in the NASDAQ not quite as precise and this lower daily expected move upper daily expected move not as precise as the spot gamma levels and the round number levels let's go back to hero let's take a closer look and see what traders are doing and they were buying calls primarily also selling puts calls shown by the rising orange line sorry about that try this one more time very quickly rising orange line traders are buying calls rising blue line traders are selling puts when traders buy calls and a stock market makers sell the calls and they have to buy stock to hedge their delta exposure all right so this is the the signal I think probably the primary signal you certainly want if you're a spot gamma subscriber definitely want to bookmark bookmark this chart chart magnificent seven and take a close look at it every day all right so bullish setups in SUV 500 and NASDAQ driving price higher magnificent seven driving price higher just like they did Friday traders took a small break this morning and also Friday afternoon and now they're back at it all right let's take a look at some stocks so one thing I did today looking for a bullish day as I ranked my watch list down here below the chart by hero signal so this is showing comparing the hero signal to the last 30 days that shown by the entire length of the slider here and the dot is showing the hero signal today and comparison to the last 30 days again shown by the entire length of the slider and also the last five days shown by this colored portion here so you can see the hero signal for Tesla is the strongest that it's been the last 30 days and stronger than it has been in the last five days and that's understandable Tesla has been pretty beat up recently and traders are coming in and buying the dip in Tesla so let's take a look at the hero signal for Tesla this is really the stock of the day zoom in traders buying calls and selling puts call buyers more aggressive taking advantage of the low price and note the spot gamma levels in play 21250 hedge wall acting as support 217 call wall not much resistance and also now Tesla trading above the 220 key gamma strike let's go take a look at book man remember 21250 was the hedge wall Tesla traded down a little bit lower to the 212 level very clear shift in order flow magenta volume dots down to that level shift to green volume dots and aggressive buyers in all the way up to 225 passing right through the key gamma strike in the call wall note the liquidity target shown here in book map and the typically for a higher price stock like like Tesla the liquidity comes in mostly concentrated at the zeros and the fives and these are limit sell orders that come in in the book order book most of them at the at the cash open for a stock they'll typically stay in the order book until they're filled and those levels of higher liquidity act as targets for price very bullish day in Tesla let's take a look at a couple of other stocks want to go back to my hero watch list all right the next Amazon no spot gamma levels in play for today but a very bullish day timely flow alert traders are buying calls in Amazon this is the typical pattern traders take their foot off the gas and price consolidates Friday was not typical that there's really no pause at lunchtime the pause didn't come until late in the afternoon sorry about that zoom back out very sharp contrast traders taking positive delta positions take the foot off gas price consolidates let's go take a look at the book map go to Amazon and for Amazon the shift in order flow was not quite as clear mostly aggressive buyers on the way down and the way up but nice sharp V reversal pullback entries then options traders take the foot off the gas price consolidating right around 143 that liquidity in the order book at 143 the primary target above 143 50 kind of unusual to see that liquidity not at a round number but the price continues higher that would be the next next target let's just zoom out a little bit so above that note the liquidity stacked up at the round number levels especially 145 and then when you zoom out like this that liquidity at 143 50 becomes a lot less significant alright so that's Amazon let's go back to hero any questions IWM bullish day and IWM I don't have it on book map on this computer I haven't on running out on another computer but let me just check one thing right so so far today IWM just very slightly positive QQQ slightly negative I know Tom Sosnoff has been talking about a pairs trade with the Russell 2000 and Nasdaq buying the Russell 2000 selling Nasdaq so far he's not done well with that trade today but for the for the year but it looked like it is working today so traders are buying calls and buying puts call buyers more aggressive call shown with the orange line put shown with the blue line alright Caesar asked could we take a look at Tesla please already took already looked at Tesla that was the first stock that I looked at sorry I don't want to go back over it for everyone who saw it before please just take a look at the recording I guess starting around 210 maybe something like that I think that's probably when I got to Tesla so Caesar sorry you missed that but I did take a look at Tesla alright Shane I'll get to a few two in just a minute it may not be in hero I will see I certainly don't have I don't have that stock in in book map right so there's IWM and when I was looking this morning the next stock on this ranking list was Meta strong day in Meta note the 330 level key gamma strike call wall now it looks like prices consolidating right around that level typical pattern actually would just stick with this will pull back in the morning reversal hire is options traders start taking positive delta positions and they take the foot off the gas and price consolidates or move slower this pattern repeats over and over and over again let's go take a first one see what traders are doing so call buyers early in the morning call buyers and put sellers driving price hire wrong tool sorry and they stop selling puts and then stop buying calls and price consolidates let's go to book map take a look at Meta very bullish day in Meta Meta let's zoom in on remember the 330 key gamma strike call wall call wall breach earlier today so there's that pattern down this case down to the 326 level pretty close to the opening print aggressive buyers start to come in price moves higher to the liquidity targets above also again 330 being the key gamma strike and also the call wall price moves up a couple levels to the resting limit sell orders in the order book attracting price reversals at those levels so Meta doing a very good job today of moving from round number level to round number level now back down to 330 level note the all the aggressive sellers coming in you can see the accumulation of magenta volume dots couple of tests of VWAP there this is the blue line there like blue line showing VWAP let's go back to hero see what options traders are doing all right let's see if a few to use in here so sorry that stock is not available in hero heroes not available for every stock so not not available for that stock sorry all right any Z1 halts have any stocks they want me to take a look at meanwhile we'll go back to the go back to the SB 500 here looks like the hero signal options flow has somewhat leveled off still up and down in the range today kind of chopping around let's just take a look at shorter time frame see if that gives any clarity so in the shorter time frame it looks like just looking at the last 30 minutes of data that hero continues to oscillate up and down but now looks like it may be making a series of higher lows let's see what zero DTE traders are doing first of all for the day so making up a pretty large component of the notional value today that is minus 1.23 billion versus a total all expirations one point right now a little bit under 1.8 billion so around two thirds of the notional value today for options trades are in options that expire at the end of the day today zero DTE options trades and that is I guess really somewhat understandable considering CPI data comes out tomorrow morning traders are just trading not worrying about tomorrow when they're trading zero DTE options let's go back and take a look at the magnificent seven and starting to trend higher again let's go back to book map go to ES ES making its way back up to the 441 level high of the day check Nasdaq so Nasdaq broke out of this lunchtime consolidation range between 377 and 15,000 did one final retest around around two now trying to get above the 378 level let's see what Nvidia is doing today let's see what options traders are doing in Nvidia and Nvidia they're actually selling puts and selling calls so they're selling premium and Nvidia today but overall the notional value for options trades is positive right now around positive 88 million let me just check one thing I know Nvidia earnings are coming up so I think Nvidia earnings maybe maybe next week alright I'll check that I'll talk about that one that comes up alright last call anybody have any stocks they want me to take a look at Nvidia no gamma levels and play for today back the SP 500 book map Nasdaq let's see what Tesla is doing alright Tesla back to the 225 level let's check CVD so the move higher and Tesla definitely driven by not only options traders but aggressive buyers in the morning CVD levels off price consolidates on and around 225 below 225 looks like CVD is starting to tick up again you can see the green volume dots coming in aggressive buyers are back in Tesla alright Don says a whole new language I'm learning thanks Don I guess there is a lot of jargon and trading so yeah it just takes time if you have any questions about what I'm talking about both book map and spot gamma have great websites book map has a fantastic knowledge base you can search for anything in there a number of great articles and then also spot gamma has a great support center that is free and available to everyone so both book map and spot gamma free resources free help centers available whether you're a subscriber or not alright my time is up I want to thank everyone for watching thank you very much for your questions and comments remember CPI data comes out tomorrow morning could be a market mover and I'll talk about it tomorrow afternoon alright thanks again bye


This study aimed to develop algorithms for spatial interpolation of daily rainfall data on 1 km and LTE, SUP and GT, 2 and LTE slash SUP and GT, regular grids in the Arda and Amblev catchments in Belgium. The authors compared the results of geostatistical and deterministic approaches using seven semivariogram models, including Gaussian, logarithmic, power, exponential, rational quadratic, spherical, and pentaspherical. They found that the Gaussian model was the most frequently best fit for daily rainfall data. The negative estimates of cryging were observed for convective more than stratiform rain. Spatial interpolation with geostatistical and inverse distance weighting, IDW, algorithms outperformed the Thiessen polygon method, while integrating elevation into cryging with an external drift, KED, and ordinary co-croaging, OCK, did not improve the interpolation accuracy for daily rainfall. The authors recommended using ordinary cryging, ORK, UNK, and KED when interpolating daily rainfall with very few neighboring sample points. This article was authored by S. Ly, C. Charles, and A. Degra. We are article.tv, links in the description below.


Right. So this is this is Mark Smith. I don't think Mark needs an introduction. He's he's working for MongoDB. He's gonna tell us lots of things that you probably don't know about MongoDB.  Thank you. Hi, everybody. I'm known as GD2K online generally for reasons that aren't that interesting. And I joined MongoDB last December. So I've been there around seven or eight months and I'm reasonably experienced. In the past I've built systems on top of MySQL and Postgres, lots of stuff on SQLite, Redis, CouchDB, Solar, but I'd never actually used MongoDB before. So I've been learning a lot over the last seven to eight months. And there were two primary things that I really learned. One is that MongoDB is really powerful and kind of fun. And the other is that almost everything that anyone says about MongoDB online is wrong. So I'm going to spend the next 20 to 25 minutes trying to bust a few myths and give you an idea of what MongoDB is, what it is and how it works. So primarily this talk is aimed at people who don't currently use MongoDB and might be interested in what it is and hopefully sort of working their way through some of the misinformation that's online. If you use MongoDB regularly, you probably know what it does, but it is a big and complex product. So hopefully you might learn something new anyway. So next slide please. So before I really get started in the real myths, there's this video on YouTube and it involves two dogs kind of having an argument. And one uses a lot of technical jargon and a lot of slogans to describe how amazing MongoDB is. And the other dog is actually a bit more down to earth and increasingly gets frustrated with the first dog and how unrealistic it is. And when I announced that I was going to work at MongoDB, a friend of mine sent me a link to this video immediately just in case I hadn't seen it. And the thing is, this video was published in 2010. It's 10 years old and you all think that no one at MongoDB has seen it and nothing could be further from the truth. Next slide please. This is my colleague Max and like me and everyone else at MongoDB, he has seen the video on YouTube. He has also bought the t-shirt. He's wearing his MongoDB is web scale t-shirt. If you were to walk around our head office in New York, you would see this sticker on about half the laptops in the office. So the next time you're tempted to send this 10 year old video to somebody who works for MongoDB, maybe if you could think twice, I'd really appreciate it because it was funny at the time, but it's almost all incorrect now. And I'm going to counteract a lot of the misinformation that it's been so easily spreading for about 10 years. So next slide please. So now that I've got that out of the way, I'm just going to give a very high level overview of what MongoDB is in case you really haven't touched it at all. Next slide please. So MongoDB is a clustered database. The minimum number of machines you can have in a cluster is three. If you want to have high availability and you don't want to lose any data, you need an odd number of machines in your cluster so they can have a little conversation among themselves and elect a primary. Now the primary is the machine that essentially handles all the connections to the cluster. So once a primary is elected, all the clients, whether it's your Python client or any of the other language clients that can be used to connect to MongoDB will connect to the primary. And it's the primary's responsibility to stream data down to the secondary. So they all store the same data but the secondaries can be slightly out of date. So this obviously is for redundancy. It's for data resilience rather than scalability because all those, the primary essentially acts as a bottleneck to the cluster. You can force your client to connect to one of the secondaries to do, say, analytics queries on a machine that's on the slightly less read load and that's kind of an interesting model but you have to understand that you will be working with stale data if you're talking to the secondary because the data comes in through the primary first. Next slide please. I have to keep moving backwards and forwards between my notes and what's on the screen. So what do we store in this database cluster? Well MongoDB is a document database so we store collections of documents. Now a collection is like a table in a relational database and a document looks a bit like this on the right. It's a map of keys and values. This document in particular is from our sample movies database. It's for a movie called Blacksmith's scene that was filmed in 1893 and it's one minute long and it involves a blacksmith hammering at an anvil and then taking a break, wiping his brow, opening a beer and passing it around and then getting back to hammering on the anvil again. It's like a TikTok video from 1893 which I think is kind of cool given I didn't even realize they had movie cameras in 1893. But I'd like to highlight a couple of things about this piece of data that I think are kind of interesting. So the first, next slide please. So the first is that it's hierarchical and kind of multi-dimensional. So the cast value here is a sub-array and you can update individual parts of this document individually. So you don't have to update the entire document each time. So I can append items to this array if I want to or I can insert or delete items from the array. The other thing is the IMDB value is what we call in MongoDB a sub-document but in Python you would call a dictory. In JSON you might call it an object. Next slide please. And the other thing is that there's some values here that are of types that aren't available in JSON. And I'll talk about that a little bit more in a moment. The ID is an object ID type which is a special type we use for generated IDs in the cluster and released is displayed here as a native Python datetime object. It's not actually stored in the database as a Python datetime object but it is a native MongoDB datetime object and a Python driver converts that into something that's useful for you as a Python developer when it's retrieved from the database. So next slide please. And I'll be covering why this is important in a later slide. So the first myth about MongoDB is that it's on version 2.4. You won't see people kind of promoting that fact online but if you install a relatively recent version of Debby and Jesse and run apt install MongoDB you will get version 2.4. The problem is that version 2.4 was released in 2013 so it's getting on for eight years old and there have been seven or eight major releases since then each of them fixing bugs and adding features and increasing improving performance. In fact the entire storage engine has been rewritten since then. So MongoDB 4.4, next slide please, is almost a completely different database to 2.4. And if you're interested in actually installing an up-to-date version of MongoDB, Google MongoDB community, follow the first link that goes to the MongoDB website and follow the instructions for installing it on your favorite Linux, Mac or Windows distribution. Next slide please. So the first myth, the second myth sorry that I've already alluded to is that MongoDB is a JSON database. You will see this quite a lot. It's a very pervasive myth. Next slide please. In fact at the moment it's on the MongoDB homepage that we store Richard JSON documents. But this isn't actually true. Next slide please. MongoDB is a Beeson database and this may sound like a sort of minor technicality because a Beeson is a binary, actually I don't know what the S stands for. Anyway it's a binary object notation. It's not just a sort of binary version of JSON. It's much more efficient to store and traverse than JSON which you would kind of expect from the fact that it's binary but it also includes extra data types like the ones that I showed you before and the ones you'd really care about as a developer are the ability to efficiently store binary blob data. It stores date times natively so you can query against different aspects of a date timestamp that's stored in the database and it also includes various different numeric types like decimal numbers that are good for storing currency. This is important because Beeson is totally fundamental to MongoDB. It's the format of the protocol that's used to talk to the server. It's not a rest query that you use to talk to MongoDB. There's a binary streaming protocol built on Beeson. Database queries are actually Beeson structs. Database results are Beeson. MongoDB is fundamentally a Beeson database. Next slide please. Another thing you will hear about MongoDB everywhere is that it doesn't support transactions. That it's a I forget what base stands for. Basic availability, soft state, eventual consistency database. Two of those have never been true. There's a reason for this myth existing. It's that essentially two years ago we didn't support transactions. Next slide please. Two years ago we added transactions to MongoDB in version 4.0 and then last year transactions were extended to support sharded clusters. Now whatever type of cluster you have for MongoDB will support transactions. Despite this, it's not so necessary to use transactions in MongoDB as it is in traditional relational databases. Because we have a rich document format that allows you to store nested related data together in a document, you don't need to do so many joins across collections or tables to update data. You don't need a transaction to ensure that those data updates are done atomically. Updates within a single document are atomic by themselves. If you have a good database design and you're storing related data together, then you can update all of that data in one atomic operation. Having said that, now that MongoDB supports transactions, for all those times where you do need to do updates across different collections or across different documents, that facility is available too. But if you're doing it too much, you probably need to look at your data design, your model design and try to factor that out as much as possible. Next slide, please. Another thing that goes hand in hand with the transactions thing is that MongoDB doesn't support relationships, that you can retrieve multiple documents, but you can't join across collections. This hasn't been true for quite some time. We support joins, left outer joins, and have done for quite some time using a type of query called an aggregation pipeline. Next slide, please. That doesn't say a lot. Aggregation pipelines are, yes, it's been supported since 2.2. Next slide, please. I'll show you just quickly what an aggregation pipeline actually looks like. It's a set of operations you can conduct on a collection. They're optimized so that they can be reordered or filtered out based on what will work most optimally with the data and the type of query that you're doing. One of these operations is called a lookup operation. Here I'm conducting a single aggregation operation on the orders collection starting at the top. This is doing a left outer join with the inventory collection where orders.item equals inventory.sku. It will embed the resulting documents in a sub-document called an inventory docs. Next slide, please. It becomes a bit clearer, and one more slide, please. This becomes a bit clearer when you can actually see the kind of data that's returned. Here it's looked up some documents matching that relationship in inventory, and then it's embedded them in the resulting order document. Here, this happens to only have one embedded document, but because this is a one-to-many relationship, it's an array of documents that comes back, so you could have multiple documents in here. I quite like this because when you do this kind of query in a relational database, it flattens it down into duplicated rows in the resulting, in the result set. Whereas MongoDB actually takes advantage of the fact it's a hierarchical document format and embeds it in there. Not only does MongoDB support relationships and joins, I think it actually does it quite intuitively. Next slide, please. Another thing people will talk about quite early on if you're discussing the pros and cons of MongoDB is sharding, and there's a reason for this. Sharding is a pretty cool feature. Sharding is when you take your entire dataset and you divide it into separate pieces. So you take all of your data, you maybe divide it down the middle, and then you have what are called two shards. So they're two separate datasets that are related, and then you take one of those datasets and you put it on a cluster, and then you put the other dataset and put it on another cluster. So you now have two shards. And when you do queries, you ideally send the queries to the cluster that holds the data that you want to get back. Next slide, please. The problem with this is that I said you need a minimum of three machines in a cluster. As soon as you have two shards, as soon as you have sharding, you need three machines per cluster. So you're looking at a minimum of six database servers. And because you need to send the queries and the data updates to the correct shards, you actually need some servers to negotiate that in front of them. So you need a shard server. And because you want redundancy, in case one of the machines goes down, you actually need a minimum of two of these machines. So you've gone from a minimum of three machines, which is a significant cost in a production environment, to a minimum of eight machines. Next slide, please. So what we recommend generally is if you're working with large data that isn't currently performant on your cluster or won't currently fit on your current machine, we recommend you look at upgrading your machine first. As soon as you start adding shards, you start to limit the types of queries you can do. You add a huge amount of complexity to your operations cost in terms of actually managing the cluster. So buy more RAM. For example, if your data isn't fitting in memory, buy more RAM. It's probably cheaper than buying another five servers or a faster processor. If that's your bottleneck, essentially look at the thing that's limiting your scaling and attempt to upgrade that first. Look at the cost of that first. Having said that, sharding is there for you if those aren't solutions at the current time. Another really interesting thing that sharding can do is if you shard on the location of the users who are accessing the data, you can move that shard cluster to be geographically closer to those users so they get less latency when they're doing queries against your database, which I think is kind of cool. Next slide, please. But if you are looking at upgrading your cluster, I recommend you look at MongoDB Atlas, which is the database hosting service that MongoDB run. So they'll run your database for you. They will handle scaling your cluster up and down as required. So you'll only be paying for the kind of usage you require. And it still supports sharding and things like that if you need them at a later date. Also, it will take huge amounts of operation spend away in terms of doing backups and handling redundancy and things. Next slide, please. So the reason people talk about sharding is because micro sharding used to be a big thing. So back in 2.4, if I remember correctly, MongoDB had a lock in the storage engine that meant that it could only efficiently use one core on a machine. So it was a bit like the global interpreter lock in Python to that respect. Actually, I apologize. It was before MongoDB 3.2. So some enterprising DBAs discovered that if they sharded their data and ran multiple shards on a single machine, they could make use of all the cores on that machine, which was quite clever, but a bit of a hack. And this got known as micro sharding. Since 2015, MongoDB has a non-blocking storage engine called WiredTiger, which doesn't require this anymore. So it makes full use of the cores on your machine. So people used to talk about sharding because it was required to optimally work on multi-core machines, but this is another historical thing. Next slide, please. Oops, that wasn't meant to come up. These are my slides that were actually disabled and somehow it's exported to them to PDF anyway. Could we move to the next? I'll keep on saying next until we get to next, next, next, next, next. That stopped. It was the last slide, please. So myth number six, MongoDB is insecure. So there have certainly been data breaches with MongoDB and it has developed a bit of a reputation for it, which I think is slightly unfair. Next slide, please. So the cause of this is that MongoDB in most distributions with the older versions automatically binds to the network and it automatically starts up with no authentication. So hopefully when you're hosting a production server or anything on the internet, you have a firewall either on your machine or in front of your machine or both. It's the default on Amazon web services to have a firewall that only exposes your SSH port. Unfortunately, some less experienced developers, I would say, would usually develop their services as a separate app server and database server and when they found that they couldn't connect to the database server, they would log into all the firewalls that were available and essentially open up the MongoDB port and at no point think about adding authentication to their database. And what this means when you expose that port to the internet is that a bot will find your instance of MongoDB and essentially steal your data or these days what it does is it encrypts all your data within your database and adds a document telling you where to send Bitcoin to get your data unlocked. I would argue that if as a DBA you put an unsecured database on the internet and somebody steals your data, then it's more your fault than anything else, but modern versions of MongoDB also don't follow this behavior anymore. So nowadays, MongoDB won't bind to the network. It will only be accessed from local host until you've added some authentication. You can use an override flag to override that security feature if you want to. You still can stick unsecured instances of MongoDB on the internet if you really want to, but I strongly recommend that you don't do that. On top of this, MongoDB uses industry standard security. It uses TLS for connections by default. It uses Scramshare 256 for authentication. There's no reinventing the wheel here. MongoDB is no less secure than any other database you might use. Next slide, please. Another quite persistent myth about MongoDB is that it loses data, and I will try to explain where this myth comes from. Next slide, please. First, I would just say it's difficult to prove a negative. MongoDB is used and trusted by some big banks like Barclays and Morgan Stanley. If it lost data, then I think that would be unlikely. It's also used in a bunch of other industries that really care about not losing their data. Next slide, please. The reason people lose data in MongoDB is because MongoDB actually allows you to trade off between the robustness of your data and performance, and the default is perhaps not ideal. So by default, when you send an update to your MongoDB cluster, it uses a configuration option called a right concern, which by default is set to one. This means that as soon as the data has been accepted by one of the databases, one of the servers in your cluster, which will be the primary, you get an acknowledgement back that the data has been accepted. Unfortunately, this means that if you get your acceptance back and then the primary goes down with a catastrophic disk failure, then you've lost your data. So that's not ideal from a perspective of caring about not losing your data. So almost every time, unless you really, really care about squeezing out all performance and you don't mind losing some data from time to time, you should use a right concern of majority, which means in a cluster of three machines, it will be accepted by two of those machines and written to disk before you get an acknowledgement back that the data has been accepted.  Again, this kind of stems from people not quite knowing what MongoDB is or how to use it, but I would say that the default is unhelpful in that case. Next slide, please. So this really sums up all of the other myths that I've covered. People will talk about MongoDB being really easy, and I've certainly found it very easy to get started. Storing data in the database is really easy. If you have some JSON data that you can just, or just some data structures in Python, you can just start storing them in MongoDB without really knowing how to efficiently use the features that are in there, how you might lose data, how you might squeeze some extra performance out of it. You don't even need to know relational theory like you do with a relational database. You can just get started. And this is kind of a problem, I would say, overall in terms of generating image, because you've got a lot of inexperienced users. So its strength is also maybe one of its biggest disadvantages from a marketing perspective. So what you really need to do is learn how to use MongoDB properly from an operations and a development perspective. And MongoDB themselves provide kind of two paths to this. The documentation is really comprehensive and is always being expanded and revised. But less known is that MongoDB run this thing called MongoDB University, which is a bunch of online courses that you can do in many cases for free that will dive into different topics around MongoDB in terms of hosting or indexing or complex aggregation pipeline queries and really help you become an expert in using the product. So if you do decide to take up MongoDB and actually use it in production, I recommend doing a few of these courses to make sure that you're really using it properly and that you know all the features that are available to you. Next slide, please. I can't remember quite what time I had until. Is it quarter to? So we have two minutes left officially, but we have a longer break after this. So maybe you can overrun me by a minute or two. I think I only have two minutes anyway. So while I have an audience, I'd just like to pitch something that I personally have been working on recently. So my team are taking the John Hopkins University COVID-19 dataset, which is stored as a bunch of CSV files that every so often change format or get updated to GitHub incorrectly. And we've turned it into a queryable MongoDB database cluster. It has username password of read only, read only. If it sounds interesting, the bit.ly link here will take you to all the documentation on how to connect to it and use it from lots of different platforms. So if you just kind of want to have a play with MongoDB and with an interesting dataset that might teach you something useful, this is a good place for that. If you decide to build something either with it or without it that's based around COVID-19 and in some way, good for humanity, we're offering free credits for anybody doing that. So if that sounds interesting as well, please do get in touch with me on the Discord. Next slide, please. So this slide had a lovely build up while I was talking, but you know, just go straight to the end. So now, unlike most of the people on the internet, you will hopefully be right about MongoDB at least some of the time. Thank you very much. Thank you very much for the excellent talk. That was just in time.


The authors investigate marine heat waves on the ocean bottom in the shallow waters surrounding North America. Relative to their surface counterparts, bottom marine heat waves are often more intense, more persistent, and can occur independently.


You know, you can be deep and light. You can be happy and sad. You can be funny and serious. You can be calm but not cool. You can be weird and goofy and smart and wise. You can be confident and yet fearful. You can be beautiful but feel ugly.  It's all good.


What's good, Josh Boros back again with another video. So we're gonna check out 10 WWE teases that disappointingly went nowhere. We've seen it a few times in WWE where they tease something. And it's, you know, there's a little bit of excitement, potentially of a future matchup. And then something happens and it doesn't go nowhere. Like maybe, you know, the talent depending on the booking situation. It doesn't go anywhere. Like it's, it's things happen, you know? So maybe someone's schedule doesn't align or maybe someone wants more money and they feel like they're not getting paid enough or maybe, and we've seen this a few times, Vince McMahon decides to do something else and completely abandoned the whole idea of what potentially could happen. It's happened before. So we're going to check out some of them instances where we thought we were going to maybe get something special. And then it ultimately turned out to be nothing. Appreciate all of the support you guys have shown on the channel. Let's get right into this one, man. From when practice for WWE to tease future storylines and characters on Raw or SmackDown, this is done to wet the appetite of fans and give him a subtle hint of what's to come in the future months. Over the years, WWE has been prone to deliver a tease and that tease ends up leading to absolutely nowhere. While the tease itself can be quickly erased from the memory of the fans. Often the tease is for something truly epic and WWE are called out for failing to deliver any type of meaningful follow up. This isn't always WWE's fault as the nature of pro wrestling means that things can change in a moment's notice. And WWE can be forced to go back to the drawing board and cancel what was going to be an exciting and compelling creative direction. Join us now as WrestleMania 10 WWE Teases that went absolutely nowhere. Be sure to subscribe and hit that notification bell for daily wrestling videos and follow us on Facebook for exclusive lists. Also, check out our new website, Number 10, Triple H versus Bray Wyatt. Teasing a heel vs heel rivalry is at least risky as the fans may be confused who they're exactly supposed to be rooting for. However, when WWE teased Triple H versus Bray Wyatt in early 2016, the reaction from fans was a clear indication that this was a match and a feud that they wanted to see. Oh my God, that dog. They had so many options that year. They have more options than what they wanted to emit. Roman Reigns wasn't the only option, by the way. He wasn't, but, you know, that he's itself took place on March 7th, 2016, the addition of rule about family had annihilated Ambrose, reigning WWE Champion Triple H's theme song would hit before Wyatt exited the ring as stay down between he and the game and sued and the crowd came alive. Wyatt even stroked Triple H's WWE title, potentially hinting that he was coming for the game's gold. Unfortunately, WWE never had any plans to follow up the tease, and the two decorated stars never even got a featured feud in WWE. Number nine, an intergender wrestling return. One of Dean Ambrose final storylines in WWE was supposed to be a feud with Nia Jax. This would have seen WWE bring back intergender wrestling, and it was supposed to lead to a match between the two at a live event. WWE would heavily tease the match up on Roy, yet it was apparent that both looked uncomfortable with what WWE had booked them to do. According to Jax in an interview with Renee Paquette, the scripted teases led to utter confusion both from herself and Ambrose, and Ambrose was fully aware that WWE were trying to punish him just before he left the company. Yeah, you can tell. They were trying to just ruin his credibility and anything that any momentum he had, they were trying to destroy it, which I don't like, I think that's messed up, and I think that's part of the reason why he's probably going to be an AEW for life.  But I just, I think what Vince did here was just not cool, bro. It wasn't. I remember getting the script, and they were just like, yeah, you're going to come out. And I was like, so wait, am I going to start wrestling the guys? Like, and I'm like, what's going on here? And they're just like, yeah, you know, we think this is kind of cool. I was like, I don't know. And then I go to Dean, Dean, John. And I was just like, dude, I don't feel comfortable with this. Like, are you, how are you? And he was like, it's all right.  It's like, he said he's like, yeah, whatever. They're just trying to get me. And to me, I'm not the kind of person to where like, in a wrestling thing, like, I just don't think I should be able to hit somebody and they don't get to hit me back. Do you know what I mean? Especially because it's an inter- I can respect. I can respect Nia on that one, bro. I can respect that. I can. I can respect that. She says she doesn't really feel comfortable hitting someone and she know they can't hit them back. Equal rights, equal fights. I respect that from Nia. I do. I really do. Entertainment thing. I thought it was so weird. And I know John didn't feel comfortable. He's like, I don't want to, I don't want to hit you. Yeah. Jax continued on saying. They had like advertised us on a live event. Yes. Having him. And I was like, what the heck is going on here? I was like, are we doing this? And I thought at first I was like, it's kind of cool to the inter-gender matches. Like that would be actually super cool if we can go that route. And if anybody who's amazing and it has like incredible resume, it's John, but I'm like, does he want to do this? Is this what is this where we're going? And then I don't know what happened. Somebody said like the state that we were supposed to be working in didn't allow inter-gender matches or some crap like that. I don't know. And then it just went away. Number eight, AJ Styles. That was just all Vince just trying to stick it to John Moxley. Well, you know, Dean Ambrose at the time, that's really what it was. It was pointless. It's no no need for it.  Goes rogue in late 2018. I remember this segment, which led to speculation that WWE were going to build towards a rivalry between AJ Styles and Vince McMahon. Yeah. In the segment, AJ and McMahon met backstage and McMahon would pretend to be unaware of who exactly AJ was before claiming that he and AJ have similar traits. McMahon would declare that he wanted to see AJ's inner animal. And then in a dramatic moment, he would slap the former WWE champion across the face. AJ would then respond by definitely in the neck. He didn't even hit his face.  Bode, I remember watching that and I was like, okay, we're going to get something here. And they didn't do nothing, bro. I really thought that we're going to do something there because he laid out Vince, bro. Ultimately, the segment and the tease of the fear between the two was quickly erased from the history books. The WWE failed to mention the segment ever again. Number seven, Batista vs Brock Lesnar. Batista vs Brock Lesnar is surely a matchup program that WWE would have booked at some point in time. Yet surprisingly, the two have never had an extended rivalry. This appeared like it was about to change in 2014 when WWE would tease a future rivalry between the two during a segment on four. I vaguely remember this. The response to the tease was overwhelmingly positive. During a promo exchange between Batista and Randy Orton, Lesnar, along with Paul Heyman, would interrupt and chaos would ensue. Heyman would inform authority figure Brad Maddox that Lesnar either wants a match with Orton or Batista. When the idea was thrown out that the fans may see Batista vs Lesnar, the mood changed in the arena and there was a tangible excitement. Sadly, the match never took place and where Batista officially retiring in 2019, there's now no chance that the match will ever take place in a WWE ring. Yeah, you know, that was a missed opportunity for sure. Number six, CM Punk vs Stone Cold Steve Austin. This was cool too. One of the dream matches that fans always wanted to see is CM Punk vs Stone Cold Steve Austin. The two characters are vastly different and this in turn would make for one compelling money-making feud. WWE successfully teased the dream match on two separate occasions. The first time was in 2011 during a memorable backstage segment on Raw and the two had a rather comedic interaction. The segment, as expected, received a noteworthy response from the crowd. The teases for an eventual feud between the two continued when the two took part in a sit-down interview with Jim Ross to promote WWE 13. This interview was intense and raw and it looked like both men were trying to sell a match rather than simply promote a video game. The interview received widespread praise and now there was even more buzz to see the match take place. Ultimately, the match never happened and the promotional interview was a final time that the two legends would share the spotlight together. They were supposed to be selling a game and it looked like they were selling a match. And I was for it. I was all for it, bros. Number five, who cost Finn Balor the universal title? It was common during the old era of WWE for the company to make bold booking decisions and figure out the fallout at a later date. When WWE booked Demon Finn Balor versus Roman Reigns for the Extreme Rules pay-per-view in 2021, they needed a way to protect Balor whilst keeping Reigns as a universal champion. WWE's idea was to have Balor about to perform his trademark coup de gras only for the rope to magically snap out of nowhere. This was a unique finish and it was heavily teased that somebody was behind cutting the rope and fans hoped that this would be explored in the coming weeks and months. But WWE never had any plans to explore the tease and the rope breaking was only implemented as a match finished to protect Balor's demon persona.  Which was just dumb. That was dumb. You know who did it? The man upstairs. That's the only thing I can think of because it just made no sense. It's one of the few blunders of Roman Reigns title defenses. That match was fun but then it started getting really comical and goofy very quickly. But as from the fans and attendants made it clear that it was a production team member who cut the rope and of course it was only fitting that WWE received backlash for failing to follow up on what could have been a strong storyline for Balor's character. Stupid. Number four times up for Roman Reigns. Upon recent. Yep, they didn't do nothing here. Now they're trying to bring it back. Triple H is trying to bring it back. But when he kind of they redebuted him, I'm like, I like this. What they're going to do with this? They're teasing something and then they just dropped it. And now they're trying to bring it back but I don't think people care right now. So. Dining with WWE in 2022, Karrion Kross was instantly presented as a foil for Roman Reigns. Kross made his debut attacking Drew McIntyre before placing an hourglass in the ring and then the ring just so happened to be the Reigns and the bloodline. Kross would then point to his wrist, signalling that time is up for Reigns and his historic title reign. It goes without saying that this was an incredible return and it made Kross look threatening within a few short minutes. The obvious teaser was that WWE were going to book Kross vs. Reigns yet this never transpired. It's never been explained why WWE failed to book the match and it's entirely possible that it's due to Kross's difficulty in connecting with the audience since returning to the company. Number three, legends collide. As mentioned at the beginning of this. There is a thing. I think they could have did it. I just don't know. He has to win feuds. He wasn't winning anything. He hasn't really won anything, but he's taken the claim of corrupting people and turning them rogue, but he hasn't really won anything. So it doesn't matter if you're causing people to go rogue after they face you, you can't beat him. So it doesn't matter. He has to win stuff. Win noticeable matches, noticeable feuds. It can be the case that WWE has every intention of following up on a tease only for real life events to get in the way of their creative plans. WWE would heavily tease the Rock vs. Triple H on a number of different occasions, including a memorable seven on Smackdown in 2014, as well as an acclaimed segment at WrestleMania 31, which also included Ronda Rousey. These teases were intended to build towards WrestleMania 32 as WrestleMania in Dallas was going to see the two legends face off for one final time. During an interview with Talksport, the game revealed that the match was canceled due to the scheduling conflicts with The Rock. I don't remember the details of it, but it was one of those things that The Rock and I talked about to the point where we did the backstage promo. Let's throw a scene out there and see what happens. It blew up, so we talked about it some more than scheduling just got in the way. At that point, we were over a year away from that WrestleMania. It wasn't until maybe four months of the following year we got to that and Rock goes, it's just not going to work. I just can't. All of my stuff, my movies and everything has changed. I just can't make it work anymore. It was what it was. I would love to have done it. It would have been a blast to step in there within one more time and tear it up. I would have preferred that than what we got. So I definitely would have preferred Triple H in The Rock one more time. I would have preferred that. Preferred that than what we end up getting that year. So to Seth Rollins' baby face turn, the 2022 Royal Rumble saw former Shield Brothers collide as Roman Reigns defended the Universal title against Seth Rollins. Outside of a lackluster DQ finish, the match was excellent as the chemistry between the two was incredible and the post-match angle led to an exciting tease for future storylines. This is so good. Once the match was over, Reigns brutalized Rollins with a steel chair to the shock and horror of 40,000 plus fans in attendance. That's worth noting that Rollins was still firmly a heel at this point and this was seemingly supposed to tease a baby face turn and tease the idea of Rollins coming after Reigns for revenge. Although Rollins has been absolutely annihilated, his character brushed it aside the next time he appeared on WWE TV. It was disappointed to see that there was no baby face turn and there was no desire from Rollins to exact revenge. Yeah, and that's the only thing about that. I would say they should probably turn them baby face sooner. Eventually, it ended up happening in the long run, but they should have did that. That would have been a nice catalyst to turn him baby face. And number one, Hulk Hogan versus Stone Cold Steve Austin. Yeah, WWE had numerous chances to hook Hulk Hogan versus Stone Cold Steve Austin in 2002. Yet due to a variety of reasons, the match never took place. It appeared like all hope was lost in seeing the two icons of WWE collide. But that was until 2005 when the teases for a match between the two began to surface. The first tease was at the Royal Homecoming Show in 2005 when during a promo from Hogan, out of nowhere, Hogan would call out Austin and outright challenge him to a dream match. This received a gigantic response and logic would assume that Hogan wouldn't tease the match in such a direct manner if WWE weren't actually going to deliver it. The next tease came at the Hall of Fame Ceremony in 2006. Austin was inducting Bret Hart and Austin would briefly divert away from focusing on Hart to addressing Hogan on the stage by stating, you know, it's funny. I was going through my bag in the back. I couldn't find something. I lost something. I went into the back looking through my bag and I found a can of whoop-ass and it had Hulk Hogan's name on it. Although the teases created significant buzz, they ended up leading to nothing. And the two never had a one-v-all matchup in WWE. But they have it, folks. 10-w- I still think that would have been the biggest match of all time, bro. And it was supposed to potentially happen, but creative differences. People couldn't decide who goes over. If I'm Hulk, I do the job for Stone Cold. I did a job for Stone Cold. Simple as that. That's just me. I know egos get involved. I do the job for Stone Cold. Because he carried the torch after Hulk Hogan left. After Hulk Hogan, you know, before he went to WCW and stuff like that, after he went to WCW, he carried the torch. He put WWE on his back, him and obviously the Rock and everybody else. But Stone Cold was the guy. So comment down below. Let me know some other potential dream matches and potential dope storylines that could have could have been if you know, WWE would have went through or plans would have failed through if they weren't on this list. There's a few that could have, you know, that possibly could have been on this list or should have been on this list.  I would have loved to have seen that, bro. That could have been possibly cool. But I appreciate all love support. Road to 150K and I'm still here to speak to you to rest and jump. We're appreciating you and me. See y'all on the next one. Peace.