What's up football fans thank you for hanging with us you're watching Fandals Sportsbooks more ways to win I'm your host Lisa Kearney inviting you inside of the Fandals Sportsbook here at the Meadowlands one of my favorite places to be it is week 13 a team's are gearing up for the final few weeks of the season here and we've got some awesome matchups for us ahead right now and of course you know how we do we're betting them our NFL experts are breaking down the biggest games of the week handing out best bets and giving you our best value DFS plays of the week as well it is go time so make sure you download the Fandals Sportsbook app sign up for your new account and plug in the promo code more ways 1000 to get your risk-free bet up to 1000 bucks all right time to get things off with the eight and three Buccaneers headed to Atlanta to take on the five and six Falcons here we go guys let's get into this match I'm very excited about an NFC South show down here Falcons still surprisingly in the playoff on a win over Brady's Bucks of course would help that Tampa Bay came from behind a beat Indie last week thanks to a huge game from Leonard Fornette who had 131 total yards four touchdowns 44.1 fantasy points for me but no one cares about that including that game winner with 20 seconds to go meanwhile Falcons running back Cordero Patterson coming up a career high 16 attempts 108 rushing yards in Atlanta's win in Jacksonville Bucks are an 11 point road favorite right now Dave and Ed it's a big number Dave Weaver can Tampa Bay cover that number I love how you're trying to sell this as a good game this is not a good game Lisa this is gonna be an absolute blowout boy I mean Matt Ryan it's just not very good anymore Ed five interceptions the last three games with one touchdown I have no life so I researched let's find some streaks where Matt Ryan has had five interceptions over three games the last five times that's happened he's 0 and 5 against the spread in the next game the Falcons have beaten only last place in second last place team when they played division leaders they've lost by an average of 29 points this is an absolute blowout Tampa by 30 now let's talk about turnovers here for just a second because they are largely random one of the big reasons why the box for Matt Ryan well I mean they're not entirely random but they're random enough and I think they're random here when we talk about Tampa Bay they won over the Colts because of takeaways it wasn't necessarily because Tom Brady was having a phenomenal performance Leonard Fornette certainly padded the stats but this Bucks offense had a lot of short fields and a lot of additional possessions that's why they beat the Colts to me Atlanta is probably due for a cleaner game and Tampa Bay is still having some problems as far as protecting the ball and having longer fields and to me this spread is just too big offensively they have a lot of injuries you know that's going to be a problem as well so to me I think the spreads just too big I think Atlanta covers it I was waiting for a regression to the mean type situation thank you Ed but I did find this to be interesting and our betters I think I will appreciate this the Bucks own a league worst one in five against the spread record on the road this season Atlanta enters this game with a league worst oh and for home ATS record so I mean pick your poison Cole Wright our NFL expert joining us now from Chicago for the right take on this matchup Cole which team do you have winning and by how many points well some bragging rights on the line in the NFC South and I have decided with my guide Dave over there sorry about that Ed but Atlanta they're the NFL's version of iron pyrite because they've been fooling people all season long in the thing that they're a halfway decent team you know they have five wins of course but all five of those wins have come versus teams with a sub 500 record and then there's Tom Brady and the Tampa Bay Buccaneers now just six games left to play for the defending Super Bowl champions and just a one of those games is versus a team with a winning record and that's next week versus the Buffalo Bills so this week I see Tom Brady in the game going out there cross the T's dot and eyes on a Sunday as usual and to be honest with you I don't really see them lose the game for the entire rest of the season I think the box win easily in this one 34 to 13 guys I mean the win is not it's not the problem at all here guys if you roll with Brady and the box and give those points a winning $50 bet means they're going to collect more than $95 this is the Fandall sportsbook app you know how we roll all right you guys moving on now from the NFC South to the AFC North you're in a huge rivalry between the eight and three Ravens at Pittsburgh taking on those five five and one Steelers Pittsburgh coming off in that embarrassing 41 to 10 loss in Cincinnati where the defense gave up 198 rushing yards meanwhile the Ravens have the best record in the AFC they're coming off that ugly 16 10 win on Sunday night still a win quarterback Lamar Jackson threw four picks in that game and get this quarterbacks who threw four picks or more had lost 41 straight before Baltimore's win week 13 now the Steelers getting four and a half at home no respect pony you're in Pittsburgh and you follow both of these teams very closely which side are you backing pony I'm gonna go with the Steelers this is Pittsburgh Super Bowl this is a referendum on Mike Tomlin's team specifically like Tomlin's defense bruised and battered as you pointed out Lisa but historically they do a very good job against Lamar Jackson two games against the Steelers his passer rating in those games is a robust 56 he is terrible against this team so much on the line for the Steelers their season really at critical mass and for that reason Baltimore can win Dave but they very rarely win big it's usually a field goal or less that's why I'm riding with the Steelers it's surprising that Lamar Jackson has only started against the Steelers twice in his career last year he missed the game for COVID two years ago he was sat in week 17 when they were 14 and two so in those two games he's 32 for 56 that's 50 57 percent completion rate with five interceptions he has not been good against the Steelers and the Steelers have covered six straight as a home underdog these are the spots where they feel disrespected like you said there's a lot on the line here for Pittsburgh I'm with you pony all right guys let's get a bit deeper on these Ravens and Steelers for that we dig in on those next-gen stats to get an analytical perspective on this matchup as we know the NFL analyzes the location speed and acceleration of every player on every play then creates these various data sets that we get to tap into so got to get Ed in here your analytics guy Ed give us a next-gen staff that you're using to pick this Raven Steelers game well Lisa the most impactful connection by far for Ben Rathlisberger this season has been with tight end Wunderken Pat Friarmuth in all likelihood second place will have to step up though and that's Deontay Johnson here is his route chart from week 12 nine catches for 95 yards sounds good but an expected completion percentage over expected of negative 5.4 percent that's more of a concern here should have been more given all those yards and catches especially considering that his target share among all receivers was more than a third Bengals pressed him a lot more than 40 percent of the time knowing that's where Steelers want the ball to go to Johnson still amass 42 yards in those situations Ravens should have a good game plan to limit Johnson but Baltimore has its own offensive concerns simply put I think the spread is too big here I'm leaning Steelers so it's a clean sweep but the under for me is the play that I like the most pick whichever way you want to go thank you Ed awesome next level info from next-gen stats if you want to tell Ed hey do you like the Steelers to bounce back this week take those points a winning $50 bet means you're going to collect more than $95 and hey a reminder here you can make your first bet on the app risk-free just sign up now for a new Fandals fourth book account using promo code more ways 1000 you're going to get a risk-free bet up to $1000 again that promo code more ways 1000 time now for our DFS download of course that means a chance to win millions in prizes for free Fandals does it every single week I literally sit up here and say this every week Fandals hooked you up for free just head to Fandals dot com sign up for weekly DFS contest get your friends your fam your co-workers compete each week for free to sign up set your roster play and win of course our job here a more ways to win is to help you score as many points as possible so fandal editor in chief JJ Zachary's and joins us now in house with his best values for week 13 hey JJ hey Lisa if you look at this slate this week there's a lot of value at the running back position and all three of my values this week are running backs let's start with Antonio Gibson there aren't many games on this main slate that project to be high scoring but Vegas and Washington have an overunder of 49 and a half points that's not that bad Washington's been focused on running the ball more over their last three games and it's not that they've been winning because a positive game script that's a good thing for Antonio Gibson but over the team's last three Gibson's average 24 rush attempts per game and in week 12 he saw a 20.6% target share which is his highest mark by far since week one at $6,200 he's an insane value next there's Jamal Williams it sounds like Deandre Swift will be sidelined this week that means Jamal Williams is set to have a lot more work in that backfield without Swift for a lot of last week's game Williams saw 79% of Detroit's running back rushes and he had an impressive 20% target share if he comes close to hitting that in week 13 he should pay off against a Vikings defense that ranks 13th in adjusted fantasy points allowed to the running back position and then finally James Conner without Chase Edmonds over the last few weeks James Conner seen at least a 13% target share in every single game that he's played that's on top of a running back rush share that's hovered the 70% range we know he sees goal line work in that offense he scored 12 times in the ground this year yet he's still only $7,300 Chicago is not an easy matchup but we're buying volume in fantasy football and James Conner should see that there you have it head to Fandle.com and sign up for free DFS competitions right now and each week of this NFL season thank you JJ use JJ's information for a chance to win millions in prizes of course follow our guru as well at late round QB on Twitter and Insta hit up his podcast as well the late round podcast on Apple podcast. Let's get back to our game previews now because we have to talk Cardinals and Bears facing off in the Windy City this weekend at 9 and 2 Arizona has the best record in the NFC quarterback Kyla Murray by the way expected to be back for this game he has missed the last three with a sprained left ankle see how mobile he can be here as for the Bears sitting at four and seven quarterback Justin feels also dealing with an injury miss last week with the cracked ribs but he is also expected to start on Sunday the Bears are getting seven and a half points at home. Cole you're in Chicago so I definitely want to get your perspective here but pony I'm gonna start with you give me your pick for this game. Well I like the Bears because I know Cole this is a really this is the Cole Bowl this is his team where he lives and the team has been riding all year the Cardinals but look I like I like Chicago in this spot and here's why we don't know how Kyla Murray is going to respond from an injury you know he's never come back in season from an ailment and played his first two seasons he played all 16 games and if you track the Cardinals this year at least lately when they're supposed to lose and they're an underdog they win with Colt McCoy when they've been a big favorite they haven't brought the goods like when they lost that home and got blown out by Carolina so I'm gonna take Chicago to keep it close here the lines too big Bears plus seven and a half. Well pony I wish I could I like the Bears like you do but I really don't I do like the way your beard's coming in though looking pretty sharp and now they say all wins look the same in the books well that Thanksgiving Day win for the Bears not so much however it did give Bears fans just a little sliver of hope when it comes to Andy Dalton filling in for Justin Fields we know Justin Fields looks like he could get the start with those cracked ribs but either way if Andy Dalton is in there he gives the Bears somewhat of a chance to go out there and win a ball game and I spoke to David Montgomery a little bit earlier in the week and he told me that all he's trying to do right now is do all the little things that put the Bears in good position to win a ball game but that said despite the litany of injuries Kyler Murray he's coming back and even if Kyler Murray isn't all seems go the way Colt McCoy has gone out there and played at two in one he has Arizona out there balling and they're getting no respect right about now we'll talk about that a little bit later but I have to side with the Arizona Cardinals in this one twenty seven twenty one I see them getting their tenth one of the season I love the confidence there cool thank you now let's turn it up and get to prime time and we're starting with a Sunday night match up featuring two AFC West rivals here we got the six and five Broncos they're in Kansas City taken on my seven and four Chiefs Denver has one three of four and can move now into first place in the division if they can pull off this road win arrowhead of tough place to play the Broncos success has been largely because of their defense which is giving up only about eighteen points per game that is third best in the league of course this Chiefs offense will certainly test that unit especially coming in well rested off of the buy Kansas City has one four in a row features the number two total offense in the league Denver getting nine and a half points here in this game and which side are you backing well Lisa when you look at these two offenses I think it's important to sort of take away strip away the volatility and just look at overall skill set and I think when you do that you'll see that yes the Chiefs are the better football team here and certainly is a better offense but it's not that much better EPA per pass without turnovers when you strip away those yeah Kansas City's fourth best in football but Denver middle of the pack fifteenth of point two one you can also look at both quarterbacks both passers when they are not under pressure which is also a stable metric EPA per pass Kansas City is seventh best but Denver is fourteenth best to me these offenses yeah Kansas City is better but they're not that much better that's a really big spread to expect I think Denver can cover I think the problem for Denver is that nobody moves to change more than Patrick Mahomes and the Chiefs twenty five and a half first downs this year per game Lisa was talking about their defense being good but their offense actually this year as far as first downs is better than last year there were twenty four point eight actually the twenty five point five is the best since Peyton Manning Broncos back in 2013 so they're moving the ball and that's a problem for the Broncos because the Broncos are good when they can control the time of possession they're seventh in the league time of possession but when they don't control time of possession they're one in four and I think with the Chiefs moving the chains and staying on the field it's gonna be a long game for the Broncos also Lisa the Chiefs are coming off the buy the last three years Andy Reid has put up 38 points a game in those games after the buy so a lot of offense expected here from the Chiefs maybe take that over all right you guys despite that Broncos defense now to the bright lights on Monday night with first place in the AFC East on the line we got the eight and four Patriots headed to Buffalo to take on the seven and four bills New England right now the hottest team in the league winning six straight games their defense has been the key especially specifically winning the turnover battle you look here the pass force five at fumbles last week against the Titans they have 25 total takeaways that's second most in the league as for the bills they're coming off a blowout win over the Saints on Thanksgiving day but they're three and three and three in their last six games where they've been hot and cold alternating blowout wins with very bad losses despite that the bills are two and a half point home favorites in this matchup Dave I'm always saying which team are we going to get here this week from those bills it's an interesting match up which team do you like I like the Patriots you know they're undefeated on the road believe it or not they have not lost their five and oh the bills got smacked at home against the Steelers they got smacked at home against the Colts they have not been reliable at home and when you take a look at what's happening next week the Patriots are on a buy and the bills are going to be playing Tampa in Tampa on a short week I think this is a great spot for the Patriots to come in and get the way they're going to be playing again Pony the day after Christmas so with the win here the Patriots really positioned themselves nicely to win this division yeah I think Buffalo I was stunned by this line I thought New England deserved to be favored based on how the bills fared at home against the Colts and the way New England's play but then I thought about a little bit more I'm going to give this game to Bill's mafia I think the fans believe it or not are going to have a huge effect on this game why because it's Mac Jones really for the first time going into a hostile environment the Patriots road wins they've touched on them Lisa have come in place is like Houston lowest attendance in the league Carolina Atlanta the LA Chargers where opposing fans come in and take over their stadium every week that will not happen in Buffalo in prime time I think that's a unique situation for a rookie quarterback and because of that I give the edge to Buffalo all right let's see where Ed gives the edge here on these of matchups ahead and you use next instats to pick the Raven Steelers game earlier in the show now I want you to dig into your bag of tricks there give us three bets based on that next level data that you think are very good value on the Fandle Sportsbook app for week 13 what stands out to you here well Lisa let's picture this the Colts did not have a dynamite day from Jonathan Taylor they had to pass to keep up with Tampa Bay and yet Carson Wentz nearly pulled off the upset here's his past chart from week 12 here is where and when he was most effective on intermediate throws from 10 to 19 air yards total EPA was eight that's solid when the Bucks only employed a four man rush went to ZPA was 10 that's also good when Colts receivers ran out routes meaning they broke to the sideline went to ZPA was 4.9 that is good lastly when Wentz was in rhythm meaning he had two and a half to four seconds from snap to throw that EPA was 2.7 under those conditions and with an effective RPO game Wentz can be effective and I expect that he will be able to cover a large number against the Texans next Vikings running back Dalvin Cook is out so Alexander Madison is in taking over the starting reins just like he did the last time the Vikings face the Lions I'd say it worked out well for him that was his week five chart in that previous meeting 113 rushing yards and 25 carries but his dozen rushing yards over expected was one of the higher marks of the week Madison was also heady where he carried the rock going to the strong side more than 70% of the time and the Vikings were smart with when to employ him only having them run into a stack box of eight defenders or more just 8% of the time Detroit has actually had decent success containing other rushers but not Madison and I expect a repeat performance and the Vikings covering finally the Rams maybe loses three straight after starting the season 7 to 1 but Cooper Cup has been no less effective here is his route chart from week 12 against the Packers everyone knows LA wants to get Cup the ball Green Bay's defense has played well and yet Cup still finished with a positive 2.1% expected completion of Mark Cup was open 30% of the time well below his usual rate for the season but once he hauled in a pass his yards after catch over expected was 20 using his speed and shiftiness to finish with the 6th highest mark for the week the Rams are schedule dependent they can slaughter the seller dwellers of the league with Cup Odell Beckham and company and I am leading a lot of points against the Jaguars. I mean that team is so stacked they are so loaded at I'm with you awesome stuff as always take that information use it to place your bets right now on the Fandals sportsbook app you can place a wager on the bets that we just talked about the ones that Ed just highlighted or hundreds of others just keep scrolling it's all available for you right now time to speed things up and hit our betting markets rapid fire style it's one of my favorite segments guys I can't stand in efficiency we're shouting out your local teams as we rip through the rest of the week 13 slate and guys I give you the game you have 10 seconds or less to give me your pick Dave let's start with the four and seven giants at the five and seven dolphins in New York upset the Eagles last week at home the G men getting four and a half in Miami yeah how about those Giants forcing four turnovers to red zone interceptions able to win that game Miami has only given up 11 and a half points on average their last four games so my play in this game is the under I think the Giants keep it close so Giants to the ender Pony six and five Chargers in Cincinnati taken on the seven and four Bengals both teams would make the playoffs if the season ended today Bengals giving three last time the Bengals scored 41 points against a divisional team they came back the next week and lost to the Jets Lisa so for that reason I think the Chargers under the radar here take them to go to Cincinnati cover and went outright that's fair Cole Washington beat the Seahawks on money and I football to win their third straight the Raiders coming off the thrilling overtime win in Dallas on Thanksgiving Washington here a two and a half point road dog how do you play it well Lisa I wish I could tell you that the football team looks sharp versus Seattle but plain and simple they did and you they didn't look like a very solid team out there from front to back but they did get the win but in the other point you look at Las Vegas what are they doing right now well they're right in the mix when it comes to that division race just a game behind Kansas City and their knee deep in that playoff mix so you know what I'm gonna go with the Raiders in this one they're trying to move above 500 at the Roomba 28 to 14 that AFC West is a tight, tight division and the Jets ended a three game losing streak with a win in Houston last week this week New York is hot home here hosting the Eagles Jets are getting seven at MetLife I'm gonna borrow a line from my BFF Dave Weaver and say that the Eagles should not be seven point favorites to anybody even the Jets the past defense for Philadelphia is really suspect I think Zach Wilson can throw a lot of deep balls and keep this game close I think the Jets cover here I also didn't know we just became best friends awesome stuff guys all right I'll be joining you in LA next week hey the Jets will be right here at the Meadowlands on Sunday just across the parking lot from where I'm standing right now in the Fandals sportsbook that means the party is going down here at the Fandals sportsbook at the Meadowlands Fandals sportsbook opens seven days a week we're showing you the inside view here come watch wager win with your favorite teams your favorite players the sportsbook is located across the parking lot from MetLife Stadium and it is so easy to get to on game day just hop the free round trip shuttle from Lot G and if you don't have a parking pass it's all good head to Reds restaurant in Carl's set catch the $10 shuttle to MetLife and then head to Lot G for that free ride right here to the Fandals sportsbook as I always say mass transit of course available as well Sunday is going to be absolutely hot in so get your friends come out for an awesome time here at the Meadowlands in the Fandals sportsbook and wager win have fun with us NFL NBA whatever NHL whatever games you like to wager on we got him here for you time now to give some underdogs a little as we pivot here and bring Cole back in Cole you've been rocking these moneyline moneymakers all season including piggy picking the big moneyline upset of the Broncos beating the Chargers last week so fist bump yes here we are in week 13 give us a couple underdogs that you think will win outright this week what do you think hit that Denver point total right in the head last week as well Lisa don't forget about that one but either way how about the Dolphins there are 500 team at home and the New York Giants will they stake on the road but Danny Dimes he is expected to play is dealing with that next strain but either way if he's not ready Mike Glennon he'll be good to go and that just seems like too much to game plan for the Dolphins I see big blue winning this one 24 17 and remember that story about the guy who continuously bet against Bill Belichick and came out on top well that's because that never happened the Patriots they won sixth straight in the bills they've scuffled over their last few they dropped two of their last four and I'm plain and simple and not a Buffalo believer when you fall to Jacksonville and Andy like that sorry Bill's mafia I have to go into England here 21 to 14 they continue to roll 21 14 you know I'm writing my notes down Cole thank you hey go ahead and tail Cole's upset picks or make any other bet on the Fandals sportsbook app risk-free right now up to 1000 bucks all you got to do is sign up for a Fandals sportsbook account new users get a risk-free bet up to 1000 bucks just by using promo code right there on your screen it's more ways 1000 and of course on this show we like to hook you up our experts are giving you their risk-free bet of the week Dave I'm gonna start with you what is your risk-free bet for 1000 bucks here on week 13 this is called the blowout bonanza I'm taking two teams that are going by at least 20 points number one no team has lost by more than 20 than the Falcons this year I need to Tampa minus 19 and a half and the chiefs to beat the Broncos by 20 points or more three out of the last four so both of those teams chiefs and bucks to win by 20 I get almost 11,000 Wow my altered its spread is a little more modest than that the Seattle Seahawks broke my heart last week and I want them to break my heart again Seahawks minus two and a half thousand dollar risk-free bet for 2800 I feel like I've now got a pile of tickets that our futures plays here in this spot my latest risk-free bet is the Chargers to win the AFC West sorry Lisa at one point I thought Kansas City had the value now I think it's swung in the other direction they're only a game out and at plus 280 you get a great return I feel like they're doing it quiet and sneaky and that yeah I wouldn't be wouldn't be surprised if that happened Pony not mad at you gamblers make sure to sign up for a fan of sportsbook account right now to place your bet even if it's on the Chargers just do your thing remember use the promo code more ways 1000 to get your risk-free bet up to 1000 bucks it's easy it's legal it is live right now take your winnings if you hit and just get your money back in site credit if you don't you get to do it all over again on us all right we've hit some spread in total bets on this show but there are a bunch of other really fun bets on the fandals sportsbook app right now that feature a wide variety of wagers that you can make so guys let's focus on some of those right now I'm gonna give you the bet and then you give me your quick pick Dave you're up first which quarterback will have the most regular season passing yards Tom Brady the favorite at plus 200 Tom Brady is a favorite but he plays Panthers twice and also the bills very good passing defenses that's not a good matchup Herbert has some good games left I'm gonna go with him Pony Steelers over under seven and a half regular season wins sitting there at five five and one I think the over is very enticing at that plus 125 here's why three home games left Baltimore we've talked about the Browns and the Titans without Derek Henry they win those three games which I think they go over okay and Chargers to make the playoffs yes minus 128 no plus one one oh six my favorite quarterback metric EPA CpoE composite Justin Herbert is 12th which is good but that's the worst among all four starting quarterbacks in the division the fourth place team in the West is not making the playoffs I like no Cole which team will finish with the best regular season record you got the Cardinals there the favorite at plus 250 well you know I have to roll with the team that I've been rolling with all season long they're the best team in the league record wise undefeated on the road and I see that continuing versus the Chicago Bears and the world playing in simple they're like Rodney Danger filled the league because no one's talking about them they're getting no respect right about now so I'm gonna put all that respect on their name Arizona okay there it is finally great stuff by you guys and now I want to tell you about the Fandall Casino app and how you can win a share of a million-dollar prize pool just by playing with us how easy is that the Fandall Casino app is a secure online casino that has the best online gaming action out there Fandall has partnered with the top game developers to give players the most innovative online gaming experience including live dealers for some table games that Dave had fun playing he said he made some friends there are also a ton of promotions and bonuses that you can take advantage of including the one million-dollar holiday spectacular check this out we're very excited about this promotion all you have to do is opt in daily and place real money casino wagers of at least $50 on the opt-in date after that you'll have a chance to be one of the 100 winners selected each day play one day or every day for your chance to win Fandall Casino is available for players 21 or older in New Jersey Pennsylvania Michigan and West Virginia there it is one million dollar holiday spectacular with daily winners so download the Fandall Casino app right now and take advantage of the million dollar holiday spectacular promotion again it's my Fandall and you can find it there on the Fandall Casino app. Hey guys you know what we did hit the game picks the best bets futures and DFS we did cover it all here again check done week 13 is here and you can bet it right now check out all the bets that we talked about on the Fandall sportsbook app new users again be sure to plug in that promo code more ways 1000 to get your risk free bet up to 1000 bucks follow us on Twitter at more ways to win TV and hit me up at least the current on Twitter and Insta and enjoy the games this weekend good luck with your bets


Live from Denver, Colorado. It's theCUBE, covering Commvault Go 2019. Brought to you by Commvault. Welcome to theCUBE, Lisa Martin with Stu Miniman. Live on day one of Commvault Go 19, we're in Colorado this year and we're excited to welcome to theCUBE for the first time we have Matt Shia, VP of Strategic Pricing at Commvault. Matt, welcome. Thank you, thanks for having me here. So lots of news coming out yesterday and today. You know, in the last, because Stu and I have had a number of conversations today already about just how much evolution has happened with Commvault in this calendar year alone. Analysts came in, you know, when Sanjay took over and said Commvault, you've got to upgrade your sales force. We've seen the sales leadership changes. They said, in hands your marketing, we've seen new routes to market, partner focus, expansion into, you know, really expanding the TAM with a head big acquisition. Talk to us a little bit about from, you know, a pricing perspective, a strategic perspective. What are you guys doing? What's new this year that you guys are really saying, hey, we're listening to our customers. We're listening to our partners. So there's two parts to it. The first is really just making things simpler and easier for everybody. So we started that journey last year. Sanjay came in and said, keep it going. So we need to continue the go to market simplification, make it easier for people. So we've tried to do that as much as possible. We're going to continue to do that, whether it's packaging related, pricing related, make it quicker for customers and partners to get access to the software. The second part to that is when we release new products, like Activate, we've talked a lot about Activate over the last couple of days. We have new packaging for that, which is exciting, but we need to make sure that's accessible. So making that easy for our partners to get to it, cross selling and upselling, that kind of thing for everybody to have access to. So that's really the direction that we've gotten from Sanjay. And as we get into the future, it's continuing that with things like HeadVig and Metallic and all that. So anything particular about Activate, what differentiates how that's priced in package versus how Commvault might have done stuff in the back? It's the granularity of it is what it is. So Commvault, one of the great things that we can do here is we can be flexible. And Sanjay talked a lot about that in his main stage presentation this morning, and we can give a customer the ability to do what they want and when they want and how they want. So they've purchased from Commvault in the past likely, they have different routes that they've bought from and Activate gives them the ability to buy in that same manner. So it's granular, gives them the ability to get software when they need it, the type of software they need, but in the manner they want to buy it as well. So that's the exciting part of it. So we had a chat with Rob earlier talking about Metallic and how that SaaS product was put together. Well, customers have a lot of experience now with SaaS. So tell us from a pricing and packaging standpoint, your involvement and what customers are going to see when it comes to Metallic. Yes, we're directly involved with the pricing. We wanted to make sure that it aligns with everything we stand for as a pricing organization at Commvault. And I'm excited about it because we've never really had a straight SaaS product that's like, go to the website, get the price, download it, good to go. It's exciting, I can't wait to have it out there. I can't wait for customers to go get it and download it. The booth has been really, really slammed today from what I've heard. So I'm excited about the pricing. All right, and there's a couple of different pricing models depending on how they're doing. Maybe you could walk us through that. Yeah, sure. So you have three different options that you can buy, each one gives you a different use case. So you have backup endpoint, mailbox, all that, 0365. Different things you can buy. They all start at one particular price point. They're tiered, so the bigger you get, the more of a discount you get. The other cool thing that we can do here, because we do different use cases, which is sometimes different than competitors, is that you get a family discount with Commvault. So if you buy one and you get to a high enough level, you can go into another one and into another one and get that same discount. So we're really trying to get customers to use as much as they can, get them accessible, and we hope they like it. Where were customers in terms of when this was being conceived? Just not just metallic from a product and a technology perspective, but from a consumption, subscription perspective. Were they actively, I would imagine, certain customers, like maybe part of an advisory board, helping you guys determine, this is kind of a new direction for Commvault, where they talked to us about the influence that some of these key customers had, and really enabling this pricing to be so transparent. We had, it wasn't even just customers, there was a lot of people who had influence into this. So industry influencers, financial influence, a lot of people had a lot of influence and a lot of input into how we do it, because obviously everybody has a way that they like to buy. Customers had a big input, because as we started this, one of the first things we came through was, how do we make sure that the packaging looks good? And that was one of the first core deliverables, because everything sort of runs off that. Make sure that it looks right, make sure it's accessible to customers, and easy. So that was one of the first things we did was go out, surveys, customer surveys, input, data points, all that really started the process. All right, and metallic is 100% through the channel, so tell us a little bit about, how that works for SaaS offering. Yeah, so through the channel, for us it's going to be fantastic, because we want to make sure that our partners can sell it to folks. That was one of the biggest things our customers came back with was, we like to buy through our partner. We don't want to have to go do a whole bunch of different things. So great, you should go out and buy from your partner, they have access to it, it's easy to understand, it's easy to price, easy to package, and there really shouldn't be a whole lot of worrying about it from a customer standpoint. Quick and painless. Yeah, and the other thing, I understand if it's core, it's by capacity, if it's the 0365 or endpoint, it's based on your number of users, there's that piece in there that if I have my own cloud storage, I can leverage that. So is that just a different pricing? Because I didn't see that piece on the website, how does that impact things? Yeah, so it really, it's about flexibility. Like if you want to use ours, you can, and that's fine. If you have your own and you want to go use that, that's fine too. Like we're not really, we don't want to lock anybody into something that they may not need or want. So if you already have a contract with one of the cloud providers, you're free to go and use that, and we're not going to worry about it. If you want to go do it through us, and that's great. We'll work with you on that. So Metallic focused on the mid-market, but Commvault has a really good percentage of revenue that comes from large global enterprise accounts. You guys have made some leadership changes there, new initiatives on these large global enterprises, and some that are going to be fulfilled and delivered exclusively through, I think, global systems integrators. We do have a GSI program. So talk to us about that from a strategic perspective, knowing so much business comes through the channel for those really large enterprise accounts. What's that strategic pricing, conversation, concept all about? Yes, so that one's a little bit different. We have so many different things that we do. We have Metallic, we have the HeadVig, obviously, that we just acquired. We have Commvault Complete and all the different things we do. So from an enterprise standpoint, it's how do we get the right go-to-market for them, which is potentially a systems integrator. If they go that route, larger partners, potentially some of our alliance partners are key to that as well. And then there's the how do we make it easy for them to buy all of that technology in one so that they don't have to have five different things that they're buying from Commvault. So that is the roadmap discussion. So how do we get from here to there and make sure that they have easy access to that? So that's part of the conversation we're having now. But it's the first thing that's on my mind every morning and my team works on it every day. So as we integrate HeadVig, as Metallic comes into market, obviously we have appliances and different routes there. Those all have to be easy. So if you're a customer and you want to buy five of them, it's like quick and painless for you to buy all five and it's an easy model for an enterprise. So that's how we like that to go. How does it work? Say let's look at the HeadVig acquisition as an example. They came in bringing customers, they announced the acquisition in September, it's closed, they're already working on integrations. Talk to us a little bit about from a strategic perspective, when there's an acquisition, there's customers that are on certain, they've got certain contracts. How do you take all of that past experience from the incoming company and start kind of massaging those pricing the structure to now fit and be delivered through a Commvault? Yeah, it's a great question. It's one of the things that we're starting to work on now, which is how do we take all those different price points and packaging and work them in? We've done a little bit of it, so we've integrated what HeadVig has into our portfolio in terms of it's there through Commvault, so they're the same PS, the same support, the same maintenance, the same everything in that respect, which is great. They're going to align to Commvault in that way, but really the next step is going to be exactly what you said, which is how do we put those two together? So we don't want to keep them apart, we don't want to, you can buy HeadVig and then you can buy Commvault, we want them to be the same. And so the long-term vision for that will be to do that. We haven't gotten there yet. That's the next plan with HeadVig integration is to take those customers and say, how did you buy it, what did you like, what didn't you like? And then we can take that feedback and really use it to package up a solution. Yeah, Matt, I'm curious how the changes in the public cloud have been impacting your line of work. For example, we watched the AWS Marketplace and they have more and more customers buying through them. Last year they came out with the, I forget what they call it, it's like the private buying so that you can even, if you have a special arrangement, you can still buy it through the AWS Marketplace. Is that, are you seeing that as a trend or customers interest in that as Commvault looking down that path? Yeah, they're interested in it and certainly will enable people to go do it. It hasn't been a huge focus yet in terms of price, right? Because a lot of things that we have that are priced are already aligned how they should be in the cloud. So when we sell something like a VM, for example, it's kind of aligned to how they buy it anyway. So we haven't seen a huge change in how people would do that. It's more as we get more into the cloud and multi-cloud with Sanjay's vision, we'll start to see some more go-to-market perspectives that are like that and the routes to market will change a little bit but we're set up for it already from a pricing standpoint so it's not going to be a big change. So as we look at the momentum that Commvault carries into their fourth annual go with how much leadership change, we talked about that, the routes to market and things, what are some of, do you think the bar has been set like, all right, we've got to figure this out, for example, the simplification of the head-veg Commvault structure, is there kind of an expectation that as fast as they're now iterating and delivering on technology, you've got to be able to do the same from a pricing standpoint? Yep, everything you need to do on technology, I need to be just as fast on pricing. Yeah, there's definitely that expectation and that's a great expectation.  It has to be, it has to go at the same time so we're tight with all the folks that were doing the head-veg integration, making sure that we're aligned to it, there's absolutely that expectation, but I love that expectation because we have to get it out at the same time and that's great. It does, well it makes things interesting and exciting but customers are demanding this transparency because if we think about it in our consumer lives, we have transparency, I mean, think about buying a car these days, as the consumer, you're so empowered with whatever you want to buy and there's this expectation as an IT buyer that they have the same type of transparency and the same type of simplified pricing structure. So you've got to be able to deliver to meet that too, right? We do and there's no black box anymore. Like when I first started doing this a long time ago it was like, here's a product, here's a black box, here's, you'll buy it from your partner. That's gone, like they need to know exactly what goes into that. So transparency, we talk a lot about it from a pricing standpoint, it used to be like, don't talk about pricing, right? Because nobody should really know what happens in there, everybody knows what happens in there now and they should, I mean, it's their money so we need to make sure that they understand how they're spending it, why they should be spending it with one vendor versus another and then what's going to be good for them in the long term. So we talk a lot about that from a strategy standpoint. Well, that's actually something that could be a competitive differentiator for Commvault, right? Compare if there are others who are saying, you know, secret sauce, talk to sales, that can be, with how quickly things change and move these days, that transparency can be a real game changer in the customer's experience. It can be and one of the, so I came from a background of competitive intelligence when I did, I worked at a firm for a long time in CI and so I was told by my boss at the time, he said, don't be the department of rah-rah, be the department of facts, all right? And so as a pricing person, it's the department of facts. I'll tell you as a customer, this is good, this is coming, this is where we are now, all that stuff and it's up to you to make a decision. Like it's, you know, it's there, the facts are there, the pricing we think is structured in a way that helps you and supports you but you're free to make a decision. I don't want to force anything on you and so that's for me and my group, that's where our transparency kind of lives is we know customers have to buy, we know they have options, they're not always going to choose Commvault, we like them to, but they're not going to. And we just try to make that as easy as possible and make it a painless solution, all right? Easy and painless, I'll take it. Matt, thank you for joining Stu and me and talking to us about what you're doing and how quickly things are iterating all the way from the technologies to the pricing structure, we appreciate your time. Anytime, thanks for having me. All right, first Stu Miniman, I'm Lisa Martin and you're watching theCUBE from Commvault Go 19.


Now, having done the common emitter amplifier to some detail, let us have a quick comparison between common emitter amplifier and common base as well as common collector. Now, we will not have time to look into the detailed analysis of both common base and common collector. What I have shown here is a one typical circuit, which you would use for a discrete common base amplifier. So, what we have here is you have again you can see a potential divider here and you are given a biasing very similar and you have a resistance R e here and you have a resistance R c and R l. Now, the major there are two major differences here compared to what we saw in a common emitter. We see here the signal is now applied to the emitter. We said that in a common base amplifier, we said that the signal is applied between the emitter and ground. Now, since we are using a voltage divider network to bias get a certain value of V B E, we need to ensure that the base is at AC ground potential. This is done by connecting a capacitor from base to ground a fairly large value capacitor. Now, in this case, we will not analyze it, but just by looking at the circuit, we can see that the output side is very, very exactly almost exactly same as what we saw for the common emitter amplifier. Therefore, the output resistance is high. In a common emitter amplifier, the output resistance was typically R c and that is generally R c would be a few kilo ohms. So, the output resistance was quite high. Now, we know that the output resistance of a voltage amplifier should be ideally 0, but that is not satisfied by a common emitter amplifier. The same problem is here in a common base amplifier also. The output resistance is quite high. Now, here since you are applying the input signal to the emitter here, if you look at the equivalent circuit, you would see that the input side would have capital R e coming in parallel with small r e. We know that small r e is a very small resistance. Therefore, the input resistance will be small r e, which is an extremely small value. So, this is one of the major difference between a common emitter amplifier and a common base amplifier. In a common base amplifier, the input resistance is very, very low. Now, coming to the voltage gain, we see that the… In fact, you get the same expression for the voltage gain here, except that the sign, there would not be a negative sign in a common base amplifier. The expression for the voltage gain would have a positive sign. Now, this is because of the reason that if you look at the model, you will see that the way the signal is applied. In the previous case, the signal was applied to the base. Therefore, any increase in value of the base voltage resulted in an increase in collector current, which decreased the V c. In this case, it is the other way. That is why we see that there is no… The voltage gain would be… There is no negative sign. Now, what is the application of a common base amplifier? Now, common emitter amplifier, we said that even though its input resistance is not very high, output resistance is not low, still for simple modest application, you could use a common emitter amplifier. Now, common base amplifier, the input resistance being very low can be used as a current amplifier. If you remember, towards the beginning of today's lecture, I said that a current amplifier should have low input resistance. So, common base amplifier, you could think of as a current amplifier. Another interesting application of a common base amplifier is its high-frequency response. It has a very good high-frequency response. We would see some of this later in another lecture. Now, let us look at the common collector amplifier. This also has another name, which is called the emitter follower. Now, again looking at the circuit, what we have is you have the input connected through a capacitor, the circuit here. We see here that we are not using the standard potentiometer divider here. That is there for a very important reason. We will see that in a minute. So, we would choose R B, a fairly high value of R B you would choose and the output is taken from the emitter and you would have a coupling capacitor there and you would have the load R L here. Occasionally, you might use the R E, which is used for biasing itself as a load resistance. Now, in this case, this you would see that is very similar to what we did for the common emitter amplifier with no emitter bypass capacitor. So, you would see the input side is very similar to that and there we saw the input impedance or input resistance we saw was R B parallel beta plus 1 times small R E plus capital R E. Now, here also if you consider this as short circuit, instead of R E, you will have R E parallel R L, but you would see that the input resistance would be now quite high. So, here is a situation where your input resistance is very high. Now, the output resistance is quite low. This is because of the reason that you are taking the output from the emitter. Please recollect that both for the common emitter and the common base, the output was taken from the collector and the collector terminal was a current source. We had a control current source here and because of that, you had a high resistance there. Whereas, here you are taking the output from the emitter and we know that the emitter terminal and the impedance looking into the emitter is quite small. So, in this case, you would see that the resistance you have the output resistance is quite small. Now, here the voltage gain is approximately unity. So, here is an amplifier where your gain is unity, but this circuit has very high input resistance, very low output resistance. Therefore, this is a very useful circuit. This is used as a buffer and you can think of this similar to the voltage follower using an op-amp and that is why the name emitter follower is given here. The main difference being in a voltage follower, the impedance you get is almost infinite because in a voltage follower, since you have output directly connected to the negative terminal of the input of the op-amp, you have an extremely high value. The input resistance, open loop input resistance gets multiplied by extremely large value. This is almost infinite, but here the value is not that high. Again later, we would see in another lecture how we could increase the value of the input resistance. So, we see that in comparison the common emitter, the common base and the common collector. So, we see that from the impedance point of view, we see that the common base is extremely low input impedance, whereas common emitter has higher, whereas common collector has the highest. So, from the input impedance point of view, common collector is the best. Now, from the voltage gain point of view, we saw that both common base and common emitter gives you same gain, but common base cannot be amplifier, cannot be used directly as a voltage amplifier, since the input impedance is quite low. So, that is why most of the time, we would find that a common emitter amplifier is the most preferred choice. Now, we can have a quick look at the high frequency hybrid pi model. In the model which we use so far, we had only r pi, r naught and g m v pi. Now, in the high frequency model, what we have here? We have two more capacitors here. There is a capacitor here called C pi and you have a capacitor between the collector and this b dash terminal. Now, the output base terminal is the b here and this b dash terminal is the inside terminal and you can think of this r, this r, this resistance r here, the r b here as the, what is called the base spreading resistance, which is important in the, when you analyze the circuit for high frequencies. Now, in this particular model, we have the device capacitors here. Now, the just, we can have some insight into the performance of a common emitter amplifier without going into detail analysis. We can have a quick look at the model and try to have an idea about the high frequency response of the common emitter amplifier. Now, in a common emitter amplifier, so if we replace what we did earlier with this particular model. So, if you replace the mid band high high hybrid pi model with the high frequency hybrid pi model, what we would see is that, we would find this C pi, which is the capacitance between the base and the emitter and the C mu, which is a depletion capacitor. Now, here we would see that, when we do the analysis, we know that the collector terminal, we did earlier also from an analysis, we saw that in a common emitter amplifier, the output terminal is minus g m times r c parallel r l and the times the input voltage, say in this case v pi. So, think of a scenario, where one side of the capacitor, you have v pi and the other side of the capacitor, you have minus of g m v pi r c parallel r l. Now, what we would see that, equivalently this is equivalent to multiplication of this capacitor C mu by the gain. So, effectively when you analyze this particular circuit, we can represent this C mu as coming in parallel with this C pi multiplied by the approximately the gain of the common emitter amplifier. Now, the typical voltage gain of a common emitter amplifier, let us say would be about 100 or so. Now, the value of C mu is typically about a picofarad or so and the value of C pi would be about approximately 10 p f, 10 to 12 p f. So, we would see that, because of this negative voltage gain in a common emitter amplifier, the capacitor C mu gets multiplied by the voltage gain and the effectively you would have a huge capacitance sitting across the input side, which reduces the high frequency response. So, coming to the frequency response, we earlier talked about the low frequency side. We said the low frequency response we said is primarily due to the coupling capacitors and the high frequency response is due to these two capacitors, which we found here. When we do the analysis here, we would find that this high frequency response is like a low pass response and typically the kind of high frequency cutoff frequency you get for a common emitter amplifier would be the order of would be definitely less than megahertz. Now, for a general purpose transistor, if you use a general purpose transistor like BC 147 or 547, you would see that the for a gain of let us say 100 or so, you would see that the high frequency cutoff frequency cutoff does not exceed about 200 or 300 kilohertz. So, this is one of the major disadvantage of a another disadvantage of a common emitter amplifier. The high frequency response is not good. Now, here when we talked about common base amplifier, we said that the common base has very low input resistance. Another advantage of common base resistance is that the problem which we talked about here. Now, the multiplication of this capacitor C mu by the gain which is called the Miller effect is not there in a common base amplifier. This is because of the fact that we said in a common base amplifier, we apply the input between emitter and base. So, you would see that this capacitor we know C mu is appearing between collector and base and therefore, this C mu now would be appearing parallel and we know that value of C mu is quite small. So, therefore, in the case of a common base amplifier, intuitively we can see that the high frequency response is quite high. So, in later lecture, we will talk about how we can combine the common emitter and common base and get a very high frequency response, also very high voltage gain. So, we have come almost to the end of the lecture. Let us have a quick recap of all that we did today. Now, we talked about different types of amplifiers. We talked about amplifier being a controlled source and we also said that very often when we talk about amplifier, what we have in mind is a voltage amplifier. Therefore, we say that the input resistance should be very high, output resistance should be very low and we said actually there are four types of amplifiers, but the most commonly used amplifier is the voltage amplifier. Again coming back to the voltage amplifier, which is the most commonly used one, we said because we want to develop the entire signal voltage across the input resistance of the amplifier, we would like to have very high input resistance. So, ideally if we can keep r i infinite, then the entire signal voltage would appear across the input resistance. And the output resistance, this being a voltage amplifier, we have a Thevenin representation here and if you want to ensure that the entire voltage that is A V o times V i appears across V out or V naught across the R L here, then we need to have R naught very small or ideally 0. And this is why we always say, generally we say that the output resistance of a voltage amplifier should be low, but we must keep it in mind that we should apply this only for a voltage amplifier. We also talked about current amplifier and we said when we talk about a current amplifier, the scenario is very different. In a current amplifier, the input resistance should be as low as possible, ideally 0. If it is a short circuit here, then the input signal is a current signal and if your input is a short circuit, then the entire current would flow through the input of the amplifier. And the output, you have a Norton equivalent there. Therefore, in the ideal case, in a current amplifier, we should have high output resistance, so that the entire current I naught flows through the load. Then we talked about a public address system. We said a typical application, we can keep it in mind.  And an amplifier, generally in a public address system, you need a preamplifier. This is because of the reason that the microphone output is very small and the impedance of a, if you consider it as a voltage source, the impedance is very high. So, the preamplifier in a public address system ensures that you have a very high input resistance and also an extremely low noise preamplifier. So, in a public address system, you would have a preamplifier which is a low noise amplifier followed by a post amplifier. Now, if you have a discrete amplifier, that is where you can think of maybe using a common amplifier. So, we see that common amplifier because of its low input resistance cannot be directly used along with a sensor, especially with a microphone or so. You could use it in between stages. And finally, in a public address system, you need to develop the signal across a loudspeaker, which is extremely low impedance 8 ohms, 16 ohms or so. That is where we use a power amplifier. This is one of our lectures later on. Now, then we talked about op-amp being an ideal voltage amplifier. Interestingly, in an op-amp also, how did an op-amp achieve such an ideal, how did it become an ideal voltage amplifier? One thing we said is because of the negative feedback. Now, another thing to keep in mind in a op-amp is if you look at the inside of an op-amp, essentially you have three blocks inside an op-amp. The first block is a differential stage in a, when we talk about a 741. And that stage has the takes care of the common mode rejection ratio. And also has a gain of typically 741, typically a gain of 10 power 3, followed by a post amplifier, where another gain of 10 power 3. So, all together approximately 10 power 6 gain is picked up. And in a 741, you have a final stage, which is an output stage. So, you would see in most of the applications, you would find say these three blocks.  Now, there were a lot of questions on biasing and so on. And we said discrete amplifiers, even though they are not ideal, they have their place because you can build them. But the major minus point of the discrete amplifier is that because there are too many components, the reliability is low. And also you need to design it very carefully. And the gain and the other parameters can vary with time and also with different devices. Now, there were lot of questions on biasing. Now, what is the need for biasing? I hope it is clear. After today's lecture, things are very clear. Now, the purpose of biasing is to choose an appropriate point on the ICVC characteristics. And you need to choose this point such a way that you are far away from saturation as well as cut off. So, you would choose a point somewhere in the middle depending on the value of ICU 1. And you would choose for example, in the design example given to you, you are given a VCC value of 10 volts. So, you would choose a VCE value and IC value depending on the constraints given. So, biasing essentially is an exercise to choose a point an appropriate operating point. So, that you can get the desired gain and so on. Now, we also talked about good biasing circuits and bad biasing circuits. And we said that these two circuits which is said are bad because they cannot keep them from thermal runaway, any temperature variations. And the BJT being having a negative temperature coefficient for its VB, we said it will cause thermal runaway. And we said that this circuit is bad because this cannot prevent it. And we talked about the second circuit being bad saying that this particular circuit is designed for a particular value of I B. And that cannot be, if there is a variation in I B from one device to another device then this circuit fails. And we said that the most commonly used circuit is the one with two resistors at the base and a resistor at the emitter. And this is the circuit which you are going to use tomorrow. And what we did is, we said the kind of thumb rules or you would choose a VBB value for the base value and the VCE and the ICRC to be roughly one third VCC. So, in your design example you could take care of this. And we also said that you take care of the beta variations you would make sure that the current flowing through R 1 and R 2 is much higher than the base current. So, you ensure that by making sure the current through R 1 plus R 2 is approximately 10 percent of the emitter current. Then we talked about small signal approximation which is very very important. So, therefore, we said that in a common amplifier we assume that the input signal which you superimpose on the DC is much smaller than VT. So, typically we said the value we are talking about is about 10 millivolt or so. And if it is not you would have lot of distortion. Very often we also said very often you do not see this on an oscilloscope, but actually if you see it on a signal analyzer you would see distortion. And so depending on the application you need to take this in mind. Then we talked about hybrid pi model. We said this is an extremely good model and where we have two small signal parameters gm and r pi. And if you take it the early fact also into consideration we have small r naught. And with this we said a common emitter amplifier can be analyzed easily. And we got the parameters of the common emitter amplifiers. And what we found that was the input resistance was quite small r pi which is about a few kilo ohms. And whereas we found that the gain was quite high maybe about 100 or so. But the output resistance again was quite high. So, we said that common emitter amplifier is not a good candidate as a voltage amplifier. It is ideally suited as a kind of a post amplifier. And we also said we need to keep it in mind the overall voltage gain in an application where the the resistance the signal source resistance need to be much smaller than the input resistance. Now later we talked about T model. We said that is a very useful model when we talk about whenever we have a resistance in the emitter. We find that T model gives you much an easier way of to analyze the circuit. And we saw a common emitter amplifier with a series emitter resistance. And we found that in this case compared to the previous common emitter amplifier with a capacitor with the emitter the input resistance here was much higher. But the voltage gain was very low. And we said the output resistance was the same. And we said the both the amplifiers common emitter amplifiers were unilateral amplifiers where meaning the whatever you do at the input is not affected at the output. So, any variation in the in the load resistance does not change the input resistance or any variation in the signal source resistance does not change the output resistance. Then we compared the common emitter amplifiers with common emitter amplifier with the common base and common collector. And we said common base is a good candidate we said as a current amplifier and it is also very good high frequency response. It is a very low input resistance therefore it cannot be used as a voltage amplifier. We talked about common collector amplifier being as a very good choice as a buffer. And finally, we talked about the high frequency model. And we said that common emitter amplifier again has low high frequency response because of the billier effect. So, this brings us to the close of this lecture here. Thank you.


Welcome everybody to JSA's Virtual Roundtable series, new for 2021. We're really trying to connect you guys virtually as best as we can during these crazy times. So we're introducing for first in the industry unique virtual experience, the ability to network before and after our expert panel. So go ahead and join other attendees in the networking lounge at the table of your choice for virtual networking right before the roundtable begins. And feel free to table hop and don't worry about missing a beat. A countdown will count you in right before the virtual roundtable starts for a global screen takeover. And even our roundtables have been enhanced in 2021. We now offer live interactive Q&A with the audience. I just raised my virtual hand to ask the panelists a live question. Pretty cool, right? And once our roundtable concludes, you'll be returned back into the networking lounge at the very table that you were sitting at to continue that networking with other attendees and panelists. And as always, from our JSA family to yours, happy networking.


Hi, I'm here today to show you the new S-Max 10 from Salomon. This is a pure pieced range, so if you're going to choose this ski, you're going to want it to perform on the pieced, and that's where it's at home. In terms of the shape, check out the tip. Great shape here, early turn initiation, and the standout tech for me is the Edge Amp. This is the raised platform on the ski, and it gives you 30% better edge grip. It's easy for me to say that in front of the camera, but I've felt it on test. I've tested over a thousand pairs of skis in my time, so this Edge Amp really works. Look out for it, it really grips and holds the turn. Inside it, it's got wood core, so that's going to help you reduce dampening. The length that I've used is I use the 165. I'm 12 and a half stone on a good day, and about 5 foot 10, so that's aimed at intermediate, sporty intermediate skiers to advance skiers looking for sporty fun on the piece. So I was out this morning on Salomon's new S-Max ski. I took it right from the top of the mountain on the hard pack down to the softer snow at the bottom. I found it was really easy to initiate the turn at the top, and then with the Edge Amplifier, it really grips on those turns and allows you to finish them. As it got lower down, it was a more forgiving, easy ski through the choppier snow. After spending the money on the S-Max, I found that it's going to be an ideal ski for the intermediate advanced skier who's looking to progress their carving technique without wanting to go into an out and out race ski.


The European Commission for the control of foot-and-mouth disease, EUFMD, is continuously seeking for the new possibilities to contribute to early detection, surveillance and outbreak management of FMD and similar transboundary animal diseases. The use of drones in risk and affected areas is such a possibility. Drones allow to obtain real-time data and biological parameters in wider areas without disturbing animals and introduction of biosecurity risk. Drones can capture the farm structure and surrounding area, its borders, establishments, feeding and watering points of animals, and neighboring farms. Drones can get quite close to animals without upsetting them. In this way, clinical signs of infectious disease can be observed and recognized. Drones can be useful for inspection of multiple farms in a short time of animals on pasture and for control and verification of the measures during outbreak management. Drones can also be used to find animal carcasses, monitor movement of animals and wildlife, identify risk contacts with other herds and wildlife, and if equipped with a thermal camera, they can detect animals that have perexia. Overall, the use of drones could make surveillance and control activities much more efficient and fully achieve the goal of maintaining biosecurity to the highest professional level. This is an excellent example how new technologies can support field activities in practice.


From Rails to Phoenix, why Phoenix? When we hear about Phoenix, we hear about performance. This is what most people, when they first install Phoenix, they're blown away at the average response times that they're seeing. It's a common thing to see almost daily a new developer tweeting out their delight in sub-1 millisecond response times. Some have even never seen the U symbol in the logger before. So it's a great hook for those looking for something much faster than Rails. But we have to ask ourselves, is performance enough? Can you go to your boss and say, this other framework is much faster, so we need to rewrite everything in? Do people, your users, even care about the performance once you're past a certain threshold? Let's look at one guy's opinion. So recently, David was on a podcast talking about Rails performance, and he said, I see a lot of hello world benchmarks that respond in nanoseconds. Who gives a flying F? Have you ever met a customer who said, your page rendered in 100 milliseconds? That is not good enough. I need nanoseconds. No one ever asks for that. I think his DHH is right. He's absolutely right. None of our customers are complaining if our page renders in 100 milliseconds instead of 50 milliseconds, or 200 milliseconds instead of 100 milliseconds. So the question is, isn't who wants some 100 millisecond response times? Real question is, how difficult is it for your engineering team to achieve that performance on a consistent basis? How much effort is required to reach this threshold? Let's take a look at a real world example. So if you're unfamiliar with Bleacher Report, they are a sports news website, and they were running Rails for a very long time. They had, in the summer of 2014, they began a rewrite in Phoenix. They were probably one of the first large commercial websites to actually do so. And at that time, it could have been considered a legacy Rails app, pretty decent size, 50 models, 40 controllers. The characteristics of their production environment prior to the rewrite was 150 AWS instances. Their responses were log jamming, and by that, we mean their response times were taking so long that as new requests are coming in, the responses were not coming out fast enough, and so the application server would fall over. Multiple engineers per application, and multiple complex caching strategies were in place. Afterwards, the results of the rewrite after they went to production with Phoenix, one-fifteenth of the servers previously required, 10 to 30 millisecond response times on average, largest average spike 400 milliseconds, and there's been only one instance of a spike ever reaching up to 800 milliseconds. These applications are supported by about one engineer per application, and there's no caching in place. So you may be asking, how is this possible? Well, as Rails developers, we are told two things. Well, first of all, we're told that we should make a sacrifice of performance for productivity, but beyond that, we're also told that we should call the database as little as possible, and we should render from the cache as much as possible. Using the cord, the creator of Phoenix is seeing more and more reports coming in of applications that have made the switch from Rails to Phoenix and seeing as fast or faster response times without any caching in place. Others have seen the same and share the story. And it's not just Rails. There are many other languages and frameworks that suffer from cacheitis that Phoenix has been able to alleviate. How can this be? Why is Phoenix faster in some cases without caching than other solutions with caching? This doesn't make sense to most people, it doesn't compete. Elixir is a concurrent language. Instead of objects passing messages between each other, like you have in Ruby, you'll have many independent running processes running that are passing messages. Elixir runs the Erlang VM, also known as the Beam, which manages its own processes. So unlike operating system processes that start close to one megabyte in size, the processes in Elixir are far smaller, usually weighing in around one kilobyte.  So while the total number of objects to be collected may be similar to a Rails application, in a Phoenix app, any given garbage collection is limited to its own process instead of running on the entire world. This means the collection ends faster and it runs on much fewer objects. To facilitate all these processes, Erlang is a language that Elixir has built on top of. Erlang consumes as many cores as possible in the CPU, whereas Ruby was built and is still meant for a single core world. Elixir being a compiled language means that Phoenix can push a lot of the work to compile time that Rails has to do at runtime. An example of this is the Phoenix router. So in Phoenix you have a system called Plug, which is a base library, and Plug provides functionality similar to Rack in that you build out these middlewares. And during compile time, Phoenix will actually compile different paths that the middleware can take, whereas in Rails this has to be negotiated at runtime. Phoenix makes really smart use of the Erlang VM, let's see an example of this. In a blog post recently written by Evan Miller, in this post Evan describes certain tricks Phoenix uses to enable extremely fast template compilation. The TLDR of this is other languages will delete and create new strings all the time during template compilation, whereas Phoenix makes use of Erlang's IO data type that allows for memory reuse. And finally, the database is not as slow as we've been led to believe. The idea that the database is a bottleneck is all too common misconception. Here we see Chris warning that one shouldn't fall into that track. And Parker Selbert recently wrote a blog post talking about this. Back in February, he built two APIs, one in Rails and the other in Phoenix. The Rails API was built with Ruby 2.3, Rails 4.2, had Redis cache, and using active model serializers, had a warm cache built, warmed up the cache before the benchmarks ran. Tune the fetch to as little data as possible from the database, all associations are preloaded, all content is cached as strings, no marshling, so you get the highest performance. All data is generic, not customized to the current user. That means that they're benchmarking against different users in the application, and we don't want to get a custom one every single time that's going to bust the cache. Request is paginated to 100 primary records without a limit on side loads, and finally the payload for the Rails side of things weighed in at 160K. On the Phoenix side, latest, Lixar, and Phoenix, no entity cache. Fields are fetched from the database, so every request is hidden in the database. All JSON responses are serialized on the fly directly in views, includes customized data based on the current user, so unlike the Rails application, this is actually building out responses based upon user's customized data. The request isn't paginated at all, there are 250 primary records, so we're getting more data coming back, and the payload is 724K. The results of this is that the Phoenix application is serving up two and a half times more records with four and a half times more data in those records. Without any caching, the Phoenix API response times are on average one and a half to two and a half times faster. Why does this matter? To better understand that, let's take a look back at the Bleacher Report results. Phoenix doesn't ask you to compromise performance and productivity. In fact, because of its performance, you could argue engineers will be more productive. When it takes less people to support a similarly functioning application, those resources can be put to better use. Instead of putting out performance fires or having to manage a complex caching graph, the engineers can focus on features. No matter how you spin it, not working on caching is always going to be faster, it's always going to be less work than having to work on caching. So the question is, can Phoenix's performance benefits free engineers to work on bigger ideas? So to help us answer this question, I think we have to look back. And the question right now isn't why Phoenix, why Rails. And I don't mean to say this as a hit on Rails, just the opposite. I owe my career to Rails. I think a lot of people in this room owe their career to Rails, and Rails has changed many people's lives. Instead, this is more taking a look at what made Rails popular in the first place when it first came about. To me, the reason Rails did so well is because it had two very compelling stories. First, it allowed you to build something in half the time for half the cost. Second, it optimized for developer happiness. So the business people were happy that they're spending less time and less money to get their product out there. And the engineers were happy that they get to work in a language and a framework that they actually liked. I've spent some time already talking about how Phoenix can be more economical to build out, so let's focus on this. This is what we're taught from day one as Ruby developers. Ruby optimizes for developer happiness. In Rails, piggybacks on that. I want to challenge it. Does it actually do that? While the Ruby you write today feels good, what about the Ruby you wrote last year? Does that feel good?  About last month, about last week. Is the idea of going back and looking at code that you previously wrote make you happy? The true problem, sorry, this is a very common complaint in main languages. But it boils down to a comment on the language features rather than any syntax. The true problem is state. We spend all this time building up state in our heads. Having to construct this complex system in order to understand how even the most simple of code changes affect anything else. Imperative programming languages like Ruby that allow for the state of the entire application to be changed anywhere else requires more time to reason about it. So when you're making changes to code you've written in the past, you're dealing with having to recall from memory that application state. And how other methods in the system could affect that state. Reading other people's old code only completes the complexity and makes people more angry. Which could really explain why we hate reading other people's old code. Lixar has an antidote to this. It's called functional programming. Now, functional programming is not a magic wand. And many people still see the lambda and they get scared because math. But let's see how simple functional programming can actually be. Does everyone understand that the result of this would be three?  It's not that simple, though, in reality. Some traits of functional programming in Lixar are that functions are pure. By saying functions are pure, this is a big concept to understand. We mean that functions don't have any side effects. So in Ruby, you may be modifying instance variables or global variables or something else outside of the function itself. Whereas in Lixar, you have data coming in, you have data going out, and there's no other effects outside of that contract. Variables are immutable. So in a distributed system or we're learning concurrent processes, having to deal with what the values are in the variables that you previously read could lead to race conditions. And immutable data is just something that helps alleviate that from the get go. And finally, explicit is greater than implicit. This is kind of the, in Ruby and Rails, we say convention over configuration. And Phoenix definitely subscribes to convention over configuration. But in Lixar, you hear quite a bit of explicit is greater than implicit. An example that could be active record callbacks. So if you go back and read someone else's code that's calling save, you don't know what other 50 things could be happening. Whereas in Lixar, you're gonna have a very explicit code path that things are taking, it's not, you don't have to go code splonking. You don't have to find out where the effects are taking place. So all this results in a system that allows you to do more happy. Simpler systems are easier to hold in your head. Documentation is easier to find. You don't have to figure out, okay, what class is this instance part of? And code is much easier to test. When building Elixar, Joseph Villeen had the opportunity to learn from other languages. He took what he saw as some of the best features of other languages and put them in Elixar. He took the syntax from Ruby. He took the pipe operator from Fshark. If you're unfamiliar with the pipe operator, let me introduce it to you. So writing deeply nested function calls like this is not unheard of, but it's also very difficult to read. So you may break it up like this. Pipe operator simplifies it even further. So the idea here is that the previously, the result of the previous statement is now injected as the first argument in the corresponding function. So Baz takes QUX as its first argument. Result of Baz is now piped in as the first argument of bar and so on. The reason why this ends up being really nice is Elixar also cleans up a lot of Erlang code. So Erlang doesn't have the pipe operator. And what would be considered to be the primary argument is not really consistent in its arity, in this place within the function arity of the Erlang standard library. So Elixar had the opportunity to actually wrap all these Erlang functions and have a discussion over, okay, we expect perhaps this list to be the primary argument. And so we're going to always assume that it's going to be the first argument here, which plays in really nicely into the pipe operator. Pattern matching is something that was already in Erlang. But if you're unfamiliar with the concept, it's not regular expression pattern matching. Pattern matching has to do with function definition. So here we see three functions that are defined. They all have the same name. They all have the same arity. You can have different arity when it comes to pattern matching or rather function definitions in general in Elixar. But the difference here is the first argument. So for the first function, we see 0, 1, and x. And in this imaginary contrived example, we're going to pretend that multiplication is super slow. And we've optimized that quite a bit. So what ends up happening internally, if you call a function with 0 as the first argument, it will match back to this function. And it will give us whatever result we put in. If you have 2 as the first argument, it matches back to the bottom one because the bottom one has a greedy matcher in a variable name. Where this comes into play, it ends up being really nice, is a place, for example, in Phoenix controller actions. This is a simple action. The URL params are passed in as the last argument. But what if you had a query param that you wanted to work with? In other languages, you may have some ugly conditional statement inside the function. Or you may have some other way to parse it out at some point during the request cycle. In Elixar, we can pattern match directly up here. We can just grab it out. So now we can work directly with the query object. And we can still work with the original params object. So the value of whatever was assigned to the query. This is called a map that the second argument would be used to have called hashes and Ruby. But what's assigned to the Q key is now bound to the query variable. And then the entire map is bound to the params variable. It doesn't stop there. We can even match on specific values within the map. Top function will match if Q is equal to bar. And now we have a very specialized function to handle that parameter. By learning what has worked in other languages, by making the best use of Erlang to avoid having to write caching strategies until absolutely necessary, Elixar and Phoenix optimize for your long term happiness. But how different is it working with Phoenix from the perspective of a Rails developer? Let's compare the two frameworks on a very high level. Here's a Rails application structure. Phoenix application structure. Primary difference is going to be instead of app, things live in web. Rails router, Phoenix router, Rails controller, Phoenix controller, Rails migration, Phoenix migration, Rails generator, Phoenix generator. Elixar also implemented tooling that should be familiar to Ruby developers. Rake and Bundler are represented by the tool called Mix in Elixar. Mix is also a first class citizen. It's built into the language. Other tools like IRB, Ruby Debug, and Pry are also represented natively in Elixar. IEX, the Erlang debugger, and Pry is part of IEX. In fact, most other tools in services or libraries that you may go and use outside of Rails are built into Elixar. It's leveraging everything that's in Erlang. So Phoenix was inspired by Rails. And Elixar was inspired by Ruby. And you may be convinced of this, that Elixar is Ruby for Erlang, and that Phoenix is Rails for Elixar. But Elixar is not Ruby. Phoenix is not Rails. Chris wrote a blog post specifically on this. He acknowledged the similarities between the frameworks, which have been discussed as where the two diverge. And if you're interested in knowing that, suggest you go check it out, because it's on my company's blog. We'll do the marketing right there. This is evidenced by my feeling that the least interesting part of Phoenix is actually the performance story. That may seem strange considering all the performance numbers that I've already shown you. Now Rails changed the world. The past decade, in my opinion, would have been very different for startups and tech companies if Rails didn't exist. Most startups that they weren't using Rails, they were likely using something inspired by Rails. And every day we're met with another comment on how the sky is falling, on how startup investment is drying up. This quote is actually, I think from about two years ago, or three years ago, the CEO, former CEO of Yammer. He, after Yammer IPO'd, he pretty much just pieced out and said, that's it, that's the last idea. I just cashed in, see you guys later. And Mark Andreessen weighed in and said, that's nonsense. There are infinite number of great ideas out there. But how do we facilitate? How do we enable those ideas to come about? I believe that technology is the lens through which ideas are grown. How do we expect to find the next big thing if our lens hasn't changed in 10 years? Phoenix enables us to think about how we built software in a very different way than we built in Rails. OTP, you can think about that as a standard library for building distributed applications. It's part of Erlang. It's been there for, I think, close to 20 years at this point. And Phoenix itself is a distributed application. Some people may be confused about that. When you think about Rails, you think about the monolith. And it's at the top of the pyramid. But in reality, within the Elixir Erlang ecosystem, Phoenix, while it may seem like a big thing, it's actually just can play a much smaller role and a supportive role amongst a wider system of applications that are running alongside and next to one another. So by leveraging the best that OTP brings to the table, Phoenix is solving incredibly difficult problems. A little while ago, Chris decided to test how far he could push Phoenix by scaling up its WebSocket connections. After a few performance tweaks to the framework, he was able to get two million concurrent connections over WebSockets with a single Phoenix application instance. Now it was a very beefy box. Had a lot of RAM, had a lot of cores, but even still just one application instance was pushing this. There weren't any empty connections running. All the connections were simulating, chatting across the network. And a broadcast to all of the nodes took under two seconds. So Phoenix continuing to push the boundaries on what is possible was so little allows us to dream up a different class of applications that were only achievable under, by multi-billion dollar companies in the past. This is the same leap forward that Rails gave us when it first came about 10 years ago. Recently, Chris's focus has been on Phoenix 1.2, which will come with a new feature called Phoenix Presence. Presence allows it to solve a problem amongst connections that's supposed to be unique, but may be coming from different areas. So imagine a situation where you join the same chat channel under the same account, but from different devices. And what if that chat is being facilitated by multiple servers? So you may join, there may be a net split, and then you join server A, and on the other device you join server B, and then there's a conversation going on amongst the isolated between the two servers and when they join back up in the network, how do you resolve the differences at that point? This is an incredibly, insanely difficult distributed programming problem to solve. And Phoenix is going to give this to you out of the box for free. 1.2 I believe is due out in a few weeks or release candidate right now. So, how do you learn Phoenix? Nice thing is that as Rails developers, you already have a huge head start over everybody else. We went through this at Dockyard. We had a client application. We were actually rewriting it from there. And I was the lead developer on it, but we basically were running out of time so we wanted to put more engineers on it. All of our engineers had, were trained up on Rails. So I gave them, gave Thomas' programmatic programmers book, programming Elixir. And I said, read part one. Part one is about 200 pages. It goes over Elixir syntax, basic functional programming. And after about a week, they had enough knowledge that they can start making meaningful contributions back to a Phoenix application. Now that's not to say that they were expert Elixir developers. They weren't Elixir Phoenix developers. They weren't expert distributed application developers. But Phoenix is so similar on its face that if you are already familiar with an MVC framework like Rails, then you're going to have a much easier time transitioning to it. And this is a huge value proposition for companies that may be concerned about adopting Phoenix, right? So the concern is always, we agree it's really cool technology, but who's going to build it? Who's going to maintain it? Well, there you go. It takes about a week to retrain a Rails team in order to work with Phoenix. And this wasn't just our experience. We've seen a lot of other companies, a lot of other people mentioned similar experiences. So some reading material if you're interested. There's some really good books out there on Phoenix and Elixir. The middle one, Sasa Yurik, if you want a more advanced introduction to the books, Elixir and Action. Programming Phoenix just came out. It just reached publication with Chris McCord and Joseph Villeen and Bruce Tate writing it. And finally, Elixir for the Rubyist is not out yet, it's under development by Hal Fulton. So two of these names on the list may seem familiar. The economics and Hal Fulton, also known as the authors of the programming Ruby or Pickaxe book in the Ruby way. I think there's something here where the authors of two of the books that were most responsible for evangelizing Ruby are now evangelizing Elixir. In closing, let's go over how we've answered this question. Why Phoenix? You can offer an order of magnitude and performance. You can avoid having to wrap all your coding caching, implementing features costs less money, requires less engineering support, optimizes for long-term developer happiness, takes about a week to retrain existing real developers. And it's going to change the world. So thank you very much. My name is Brian Carderola. I'm the CEO of Dockyard. And if you're interested in working with Elixir and working with Phoenix, please come and chat with us. Chris McCord, the creator of the framework works for us. We hired him about five months ago to work on Phoenix full-time. So thank you guys very, very much.