Fawr gynny興 A The Tothi Tv. I enjoyed I like a monthly chat now with the corresponding fans for remember Chicago Heat. It's Tony Sampson. Rhyw bryd yn irgrifio. It's a really good time to hear blue isn't it? I keep saying because we haven't kicked the ball yet, at the moment no one can disprove or not the best team in the land at the minute. Mae'r ffordd maen i ymgyrch ar gwaith. Mae'r amlwg eu cyfnodd a'r byddwch i mi ddod i'r cyfnoddddu. Roedd gennym yn ei wneud, ond yn byw, mae'n gweithio'n holleg yi'n iawn, oherwydd mae'n clywbeth arbennig. Mae'n gwybod olaf o phobl, ond yn ymgyrch yn ei ddweud y flaenau gwyrddai yn ystafell. Mae'n gweithio я nesaf chi, ddweud o moedd yn trofnodi, a'r adnoddwch cyrnau. ..a blaenau dan jolŷnodd. Cymru gyda'n ddifrithio'n ddifrithio hwmddiwn hefyd. Ond rwy'n creu'n rhwng ond yma'r rhwng hwyl... ..a'i'r rhwng honno yn ddifrithio bydd y byddai y bydd. Mae ble yw'r llyfr yw'r arigau yn gwri. Dwi'n credu'r bwysig am ychydigad. Ond mae'n ganddofog hefydau'r rhwng hwn ar gyfer ymyniad... .. wrth gwrs, mae'r diogel â fan-gubill... ..yn ychydigad. The big thing that I'm kind of boosted by is that, the man is just seeing, we all seeing to start that midfield needs a changing. He's gone out and got what look like two excellent players for us to go in the hearts of that midfield then, do you? Ychydig i gyd, ac mae'n llywi'n meddwl i gael fitfynod, mae'n gilydd yn blaen. Mae'n gilydd fel amddangos bydder i capacity o'r ddiwedde â'r rhaglen gwnaeth hithi. Mae'n meddwl, mae'n meddwl ei bod yn cysylltiad â lŵr o phosbeithio ymdwyllpridd yn Gwyrraedd a chynnwys. Yn oedd yn llawer, mae'n tynnu amddangos o Gymraeg o hyn o'r gweld coreened o'r Llyfrgell Hain. Yn oedd ychydig yn yr oedd am ddarparu. Ond nid gallwn ni'n bywyd i'ch gilydd o'i rhoi cysylltu. Rydyn ni'n cymhwyl â'r cymhwyl i'n gymyn hynny, y gymchwil yng Ngharlach. Ond yna'n wyeb i'n ffordd ar gyflawn ei gofyn o bwyl i'r team. Yna'n gweithio dyna, ond rwy'n wedi cael ei fod yn arddangos i'r lle. Dwi'n credu bod ganddyddiaeth ymdd Encwyrn yn ei wneud am yr hyn yn ymwysig ac mae ech rhaid i gael yn hyn yn ôl i ymddalfydd ymddangos i gael. Llyfr yn edrych yn fwy ei chyfbio gwneud ar hynny bod dwi'n fwy o bwysig i ddweud cramigol sydd yn ei gael, ond mae'r sgwrd yn fy mwy o'r cyffredin wedi hyffordd â'r cyllidau yn hyn yn y past. Byddai'n gilydd yn gwybod i gwn i'ch gwirio i'r llwy i'r lleion. Gwybod ceddieb i gyd yn cael ei rhanio. Felly, yw'r byd-wch. A ffordd yw'r bydd i ddeliadol, ac yna rwy'n ychydig yn 40 yn anhygoel pethau a'r gwn siaraddau o'r ddechrau, a'r dweud yn meddwl, a oes amdano ym môl i'n gweithio. Tw li wedi'i hefyd yn ymddangos. Mae oes yn ymddangos, bydd ychydig yn ein himfodol y tro, gwyddo i fod oedd yn arfer. byddai'n hyn yw'n ei wneud o'r cyffredin. Rydym ni'n bod y byddwn ni'n eifft Constiwyr ddrŵr ac mae'n amlwg mins That Ball when a sy'n gyfraeg a yn ymwneud but felly peirio'n cael ei ddarllen amlwg mor i drwydd ym mwyn iawn, a'n bwysig eu gofeydd. Mae'r unig iddyn nhw'n ei ddechrau'n ganddalfol â Llyfrgell canllide ein lleig, ac mae'n dweud i'n meddwl, ond yn dyma'r cleif. Ond, mae'n rhaid i'w ddim yn merthynu bod yn awr i'r gwaith beirio. Mae'n gwahodd angen i'r gwasanaeth a fyddio'n gwahanol i gaelol a'r gwasanaeth i'r ddeimlo. Ond mae'n efo nhw'n meddwl i'r gwaith, ac fel yw'r adeiladio ac yn y ffraeg, mae'n ei ddweud i'n gwneud i'r gwasanaeth a'r adeiladio ar gyfer y cyfnodd gyda'r gwasanaeth. Mae'n gwneud i'n gwneud i'n gwneud i'r gwasanaeth i'r gwasanaeth, Fast, os y gallwn gynnwys da, gwnaeth yn ei rôl o'r fideo ar ddigon yma yma. Fy oedd uwch, Llyfrid gennym gynhygr yn fwy ystod yn staff gyda 9 sgol â lwyg am gynhyrch. Mae clwydwyd hynny i ddweud 500 o 5 o 6 o ddweud o ddweud. Felly, bydd efallai ar y ddweud o'r cyfrmelaeth. Felly, bod yna gofyn hon, ar un o ddweud o ddweud o ddweud o tro rôl i'r sgol, ac i ddim yn credu peirwyr bod hynny i ddweud. Roedd ei sgol yn y cethaol. felly mae'n byw i'n gwael, mae'n rhoi'n goll i ddim yn ôl. Felly, rwy'n ei gweithio, a mae'n oes yn defnyddio bod yma'r holl yn y pewr ystyried. Mae'n rhaid i'n cael ei ff��idog. Rwy'n credu ym mwyn yna'r ymddangos o'i eu bydd eu bod yn gweithio. Mae'n gweithio i'r ffordd o'r blaen. Felly, mae'n grwp i'n cael ei dweud y ffordd o'i tyfn o'r cyfnod, ond mae'n golygu o'ch cyfnod. Rhaid o'r bwysig o'r gwaith. Caelwyddech chi'n falch i'r ysgrif yn y strategiefynd, ac y ffaith bod rwy'n deud ymlaen i ddechrau... ychydig ein bodai'n ffli polaidd yn ystod yn cael ei ysgolion.  Er hwnnw, o gennym ei cyfnod. Fynig oedd swydd, a rhywbeth a'r hyn yn dweud y pethau hyn yw'r gwneud hynny, ond rôl fan o pholwyr a chno'r cymryd yw'r cy effeithi. Bydd y rhaid o'n ffóie o fewn yw'r cyfan ni o ran bryd i'r llwythau. Efo chyrnod o wneud â'r cyffredin a'r cyffredin. A'i'r wneud hynny o'r cychwyn, oherwydd dweud ei hynny yn gwrando'r hefyd. The third member there of the signing club this week, and obviously the biggest and the one that's caught the world's imagination, it seems like, is Hamas Rodriguez. I think just on a purely footballing basis, first and foremost, probably the biggest name ever to sign for Everton, and that should have mattered certainly with his global reach when Rooney was massive when he came back, but we'd made him anyway. He was asked to start with, and obviously Hamas Rodriguez, for me, and has been a well-class player in Everton, probably haven't had a well-class player really since maybe Andre Cinceltis. Llew gapi was an absolutely fantastic centre forward, and probably in that bracket, but coming through Everton, that well-class ability, we know he's had injury problems, we know his career hasn't gone probably the way he hoped, which is why he's coming to Everton. But nonetheless, that left foot, there's some talent in it, isn't it? Completely. We've seen all the footage of the ability that he's got, so again, hopefully this is a bit of a start for him to kick on from there, and I don't think that you sign and play for teams like he has, if you haven't obviously got that talent, so it's great. And also, there's clearly a trust and a respect there with Carlo as well, and I think that's important for some players to know that they've got somebody that can bring out the best and then put them in the best system and help them develop on that. So hopefully all those things click for us, and hopefully the players continue with the buzz of what's gone round as well. That will be a few new faces and stuff, hopefully it'll lift, as you say, some of those other players that maybe haven't been playing so well in their last season or two. So, he definitely brings, we know it's there, we just now hope it's pieces together with the rest of the new signings, but they're exciting. As you say, the prospect of somebody with his reach, first and foremost, we need to see what he does on the pitch, that's the most important thing, but all the other stuff and the reach that he's got as well just adds to the mystery and the intrigue as well, doesn't it? It does, let's move on to that then, let's leave the football to one side a little bit now and move on to the other stuff and we saw, you know, there was the buzz and excitement about it all over the weekend, there was people at the hotel and pitties with him and worrying and stories and everything else, but it eventually came to Everton revealing him as an Everton player. I think, personally, the club done an absolutely amazing job with it, being critical of the club, not doing things like this at the time, I don't think the club done enough when we had Wayne Rooney, I'm not going to lie, four weeks later, after he'd come, it made it very difficult to market somebody in the opening month, we had a great opportunity and we almost done it apologetically, did we do enough for Tim Kale and Tim Howard? No, we didn't, but it's about moving forward, isn't it? We've got a global super stand, I think the club reacted accordingly and we saw, we saw the Lime Street, you know, in Lime Street, the thing going across with Hammers, we saw building in Bogota, it's all it's building, you know, in Bogota lit up with the 19 and we saw obviously Miami and then the big one I think, the one that everyone kind of went all the way, there was obviously Times Square in New York seeing it there as well and I just think the club have done a very amazing job. I just think the club have done a very good job with it and it's about building on it, but I mean you're in America so, you know, was it there for you to see in Chicago, was it news in Chicago or was it still a little bit underplayed or what, cos here it's huge? No, I think the impact was just as big and I agree with you, I think the way that the club managed that and got out ahead of the signing was really impressive and you're right, I think there's been, you know, rightfully sort of criticism in the past that maybe has not taken advantage of the opportunities that we've had with those players that you've mentioned, you know, it's a constant sort of issue here, you know, when people talk about Tim Howard and McBride and all the other players that we've talked about. So, you know, we can't, you know, that's gone now and I just say I think we have got to look forward and I don't think anybody can criticise the club in the way they've managed the signing cos I thought it was really impressive and it shows the ambition for me as well, you know, it shows the front.  It has a massive impact and, you know, people definitely noticed it. I mean, my phone was buzzing. In fact, I was in touch with a guy who runs the Vice City of Atonians in Miami, you know, and we were just talking about how things would go and he was made up, you know, we've signed hammers and then he says, I'm going, I've just had a text to say and he was on Miami Beach at the time and he said I just had a text to say, look out onto the water because there's a boat with a big billboard of our new sign and he's like, I can't see it, I can't see it, but again, that's, you know, that's, that's built, you know, built the excitement for, you know, for him. Same with him. I was speaking to Michael Setterberg who runs the New York Atonians and he was the same, you know, he sent me, you know, he said, I think there's something in Times Square, so he sent someone down to go and have a look from the club as well. So, you know, he was sending pictures around, but yeah, it is. It's created, you know, a real sense of excitement and we've talked before, you know, there's a, not just in the US, but everywhere else.  So now they're seeing the, you know, maybe after some of the words and some of the things that have happened in the past that, you know, the club series about, you know, sort of investing in the international market, which is brilliant. You know, it just gives everybody a lift apart from the football side and give them something to believe in. And, you know, obviously what I want to do now is make sure that the supporters clubs are involved in, you know, these plans because I think what it does is it just gives them a chance to the club to sort of accelerate some of the stuff that they've been doing.  But now I think it just takes it to, you know, a different level. And I suppose the challenge now mate is, you know, after all the razzmatazz of, you know, the unveiling and everything is how do they maintain that, you know, and really sort of seize the opportunity. So, you know, fingers crossed that, you know, they're going to be doing it.  So, yeah, you know, let's hope that now, you know, this is the start of that sort of, you know, global evidence brand. Well, we have got a build on it's important. It's difficult. It's difficult. I mean, in some respects, it's over to you now Hamas, isn't it? You know, he starts knocking a couple in with that left foot wonder vision. But even if it just takes a little bit of time, the interest is there. We've had unbelievable numbers on our videos of an unbelievable amount of Colombians come on and, you know. Just wait till they see this one. Exactly. They see us on it. They see us on it, mate. That's it. It's gone through the roof. You know, I'm writing replies in Spanish and everything, trying to go, trying to put the titles and all that, you know. So just even that, but it is about building that because it's about spreading our brand yet. We did Reddle for a while in L4 and it's all us and it's only us and we don't care about, you know, we all were from the city and we live a mile away and two and three miles away from the city. That was great for a while. Football is, you know, we have to catch up. We have to catch up. But playing, you know, everybody else is jogging along nicely and we've been walking and we've got a sprint now to try and close that gap because the others are. We've seen Manchester City opening a, you know, New York City in a fair and a big presence in the US. Chelsea have been present in the US for years.  Evan have got to try to spread it far and wide and this is the club I've done really well and obviously Hammers will help it. If he does, and we have some of those big moments that he's produced, I'm not talking about this and if we win something incredible, but I'm just talking about if he's success and a positive influence on the team and we have those moments when he gets winners and, you know, he's creative and I think Evan will continue to grow and what the club have to do and they have done it this week to be fair. They haven't let it, they haven't let it die down. They've doubled down on the content. Even yesterday there was a joint press conference with Roderick and Anciolotti, you know, I thought that was clever. So there's all little tidbits coming off it. We need him to deliver and if he delivers we need the club to make sure they're ready to hammer home everything. So far it seems like they are and with the help of yourself and other clubs over there as well, how can we keep the conversation going? I guess that's the challenge for them, isn't it? No, I agree and I think you're right. I think if you look at some of those clubs that have established themselves in different markets, you're right. I think the number one ingredient to that is success on the pitch. That's a thing and, you know, we haven't been in that position obviously for a long time now. But again, you know, the hope there is with Carlo and, you know, with these few players coming in that we can move to that level on the playing field. So, you know, so you're right. I think the other ingredient for, you know, for sort of, you know, expansion globally, probably in any setting, you know, supported by the right commercial structure is, have you got something that people want to see here by or, you know, get interested in? And clearly with the hammers thing, you know, we've got that now. And it isn't just in South America, you know, it's, you know, it's beyond there as well. Obviously South America and Latin America is the focus. So, you know, those things are now sort of moving, you know, in the right place. And I think that's why people are excited.  We know that people have stuck with us, you know, through thin and through thick and thin. So to your point, it's now really important that sort of all of those different, those three different elements now sort of come together and keep building that momentum. You know, so, you know, we're really looking forward to that. You know, the supporters clubs, you know, I think I've told you before, certainly in the U.S. You know, now we've got a network of supporters group, group leads that interact and regularly, you know, on sort of all the socials and sort of WhatsApp groups and sort of dropping in ideas and things and wanting to know how they can expand. This obviously, I think moves things a little bit to it, you know, to a different level potentially. So, you know, what, what I, what I myself and Joe O'Reilly will be saying to the club and I've been is, you know, well, how can we now integrate this expansion strategy with the supporters clubs as well and make sure that, you know, they continue to, you know, to be involved because, you know, some of the issues that we've been talking about for a long time, like, you know, can you get a shirt? Can you get merchandise? How easy is it to do that? You know, those things now are, you know, top, top of mind. So, you know, again, I know the club has, has, you know, made some, made an announcement this week around sort of trying to maximize their distribution channels through fanatics so that everyone can get access to this shirt, you know, as much as they can. So, they're things I hope now that we can, you know, we can, you know, we can get a little bit of grit in and move forward. But the opportunities are there and I agree the club is, the club is, you know, in this first phase has done, has done a good job. It's now, as you say, we've got to keep that momentum, got to keep, you know, the positivity.  But, you know, there's, there's, there's thousands of blues in every corner of the world, you know, they've been chosen by Everton. And then, you know, as you say, like the hardy glory hunters mates are the, and they've stuck with it, you know, and there's something about Everton that they've wanted to connect to, they've stayed connected to. And as I say, they've stuck through with us. So, you know, now we've got to embrace that sort of loyalty and that passion for our club with the opportunities that this all brings. So it's exciting. It's really exciting. Right. I mean, last time you were on, the survey had been done and we've gone through that, the international survey and we've had all kinds of responses. Where have you up to? Have you had any more on that? Yeah, yeah. So that's what's been really great is that that's like an ongoing dialogue now between first of all Joe and I with the different clubs around, you know, around the world, but also, you know, with the club itself. So I think we told you that, you know, we've made some recommendations around based on the survey findings, based on a number of issues like retail, like how the clubs engage and connect and sort of build that profile and presence, how they can sort of help engage and find evertonians of the future in their localities, how do we grow those, as well as things like sort of, you know, tickets and even sort of connecting with them in the community as well. They were some of their findings. So, you know, we sat down with the club. In fact, we've had a few meetings and how to go through those. The club has taken those on board, listened to their, they've actually, over the last number of weeks and months, you know, they've been reaching out to the supporters clubs to get there. And put as well.  We're coming up to the new season. You know what? What are the things that are important to you? Which is again a really good signal. So they've been asking for that and using that then with the survey to inform some of their plans.  But, you know, for example, you know, they're looking to make sure that, you know, there's a number of states in the U.S. still that haven't got official affiliated supporters clubs. So I know that, you know, they're keen to close that gap, which is great because we can all help sort of spread the word to make sure that there's a blue supporters club in every state. The process to sort of become an official supporters club as well. They had a bit of feedback that some of it was a little bit clunky and cumbersome, so they're refining that and they're working on that, which actually is important to some of the clubs. They've got ideas as well around, you know, how can they support the existing supporters clubs with, you know, starter packs and also with, you know, sort of running events and how they can keep their own members engaged. So they're going to be working on that. I think they're keen to sort of highlight a little bit more of a spotlight on some of the supporters clubs to build that connection. You know, and so everybody gets to hear a little bit more about that.  But I think they want to delve into a little bit more detail so we all get to hear those events and stories and share them. So that'll be good. They did a number of Zoom meetings with some of the ambassadors and others with supporters clubs overseas and in the UK actually last season, obviously with the pandemic. So I think they'll want to continue with that. And I don't know what it does is it just creates that sense of community, I think. You know, when people want to throw it on social media, they're talking about it. I mean, I see it, you know, I see the reaction to, you know, to some of those things and they might seem small. But they're not, you know, knowing that the club is engaging and wants to engage, you know, it gets people talking, you know, in between the different supporters club. So that's all moving forward and, you know, we'll sort of, you know, we'll continue to talk to them. They've been, you know, very open to the feedback that we've given them. And, you know, they were obviously already working on a number of things, you know, before the season. So what we're trying to do now is to sort of complement them and then move forward. Brilliant. And last time we, again, last time we chatted, you talked about possibly having a meeting with Hummel. So has that taken place or are you still waiting? No, we're actually, it was, it was, it was this week, I think. So yeah, we met him. So the forum has got a number of sorts of different sort of working groups. I think I've explained this before. So we've got one that looks at sort of stadium atmosphere ones on catering. We've got obviously the international group. We've got one to the events. And then we've also got one for retail specifically. And that, you know, that sort of meets with sorts of the various different partners on the club.  So, you know, they were, they're the types of things that, you know, we've taken them through there. So, yeah. So, but we met with a guy called Philip Troulson, who's the chief brand officer at Hummel. It was largely an introductory meeting, but we were able to talk about some of the things that we've. We've raised with you before. And, you know, what was quite interesting with him. He's a swede, actually. He's a swede that's working for the Danish company. So that was an interesting dynamic itself. But he's actually worked for some other sort of fairly big brands as well in the US. So he understands the dynamics of certainly the US market, which I thought was quite encouraging. So, you know, he was quite alive to some of the issues we've raised in terms of distribution and availability. And shipping and those things. You know, he talked very positively about sort of the initial stages of the partnership with the club, which was called, and I think we've all, you know, we've all read about that. But from an international perspective, you know, he was very clear in letting us know that, you know, this is a significant part of what they, you know, what they want to be focusing on over the course. They've got, you know, they've obviously got bases in different parts of the world that, you know, I think they're going to try and sort of use the stuff. We've just been talking about, obviously, whilst that's largely an issue for fanatics in terms of distribution. Humble have obviously got an interest in that. So, you know, the whole hammers thing is going to be important. But, you know, we raised a couple of things like some of the data that we got from the survey around this. You know, he wanted to know about that to sort of inform the stuff that they've already got. So again, that was a good signal. We raised with them. So we've had a lot of feedback around the fact that in store presence, particularly in some countries, Ireland is one specific example where you used to be able to get, you know, walk into the shop and actually get the share to have you. That's changed has gone away. So we were able to flag that with him again, open and receptive. He's asked for more information around what might be the opportunities to do that. You know, I think they've got, you know, a sort of twin strategy, obviously, of online as well as sort of in store retail. And they've obviously got to balance it with demand. But again, he was like, look, if you've got ideas or if you think that there's things that were missing, then do that. So again, we know we provided that. So it was a good sort of introduction to, you know, to the conversation. The other thing as well is they've got a history humble of getting fan input into, you know, some of their product lines and that sort of stuff. So again, the fact that they've done it before, I think, is encouraging. So again, now, you know, we want to make sure that, you know, they continue to do that for future product lines and what have you. So, yeah, it was a good sort of healthy exchange. And, you know, we'll obviously follow that through now with the club officials and hopefully see them again as well. Yeah. I mean, that's really, really important, isn't it? That they are, you've got that relationship. They are listening to the fans or add loads of people when we've been talking about obviously the hammers thing and saying, can we get a shirt? Or we were saying, if you can't get a shirt, get a T-shirt, that's like the replica of the Everton kit, all the most. But it's amazing with his name on it. Because, you know, especially if you think Columbia, you know, sort of come up with Columbia, people were on saying a shirt like three weeks away. These are sort of whatever. That's right. But if you could get a T-shirt for, I don't know, $15, but it's an editing thing with hammers 19 on the back, you know, it's an opportunity. Is there enough for that going on? But we've also had Irish fans on then saying, I can't even get a shirt in Ireland. And it's like without going online. And that, I mean, that isn't good, is it? It's not good to, you walk into a sport store and you can get every kit and every man represented. It doesn't send off the right message, I don't think. No, it doesn't. And again, hopefully now we've got the opportunity. And I think you're right, having that sort of understanding of how things play in those different markets is going to be critical as well. The point you just made around sort of the cost of things is a real issue. We've all seen the black market opportunities there for people, their rife. So that's obviously got to be part of what the club thinks about. But it's funny, actually, all the Twitter exchanges and social media stuff. When we tweeted something that was a Columbian fan, it sort of said, you know, oh, this is great hammers, it's Jordan Everton.  And then we've got a follow up actually from a couple of Columbians straight away. And they were actually based in Chicago. So we've been in touch with them and now they're going to come to the game on Sunday. They're Evertonians instantly. So again, you know, that's just a very small example of sort of, you know, the impact of some of this stuff. So hopefully on the commercial side as well, we can match that, you know, that interest and attraction to everything with, you know, with the retail and stuff. But it feels good to be able to, doesn't it, at the moment? It is. We've got a, I think I've seen you saying something or you might have just said it in that. I think if only we could bottle this feeling, you know, when we're all buzzing and positive. You know, again, we can only do as much as we can on the team off the pitch, can only do as much as we can on it. It does just boil down to Carlo and the boys now to go on and start delivering. And we know we're old enough to have seen it last time. So when it was incredible, but, you know, Everton are waiting to be ignited at the end. If we could just get, I don't know, a trophy or a team in a Champions League that it would go through the roof because we've got a lot of fans under 25, 30, even under 30 now who might just remember us winning the Cup in 95, but probably not who go and, you know, fanatical fans over in America getting up like you stupid hours in the morning and watching us for basically not. We haven't even been able to put two seasons consistently together. So if we could get a bit of it, right, the club, I think it'd explode even further. And I think, you know, that's what we've all got to be aiming for. Because you mentioned it just before. The ambition is there to start and to demonstrate that ambition. I think for the first time in far-ad-mashiri rain and whoever else is involved in them with them for the first time and mentioning no names in Israel. He's got the world-class manager he wants it. He's got the man who's been there, done it, won it, but he plays respect for getting people in on another level to what we've had. And hopefully that will just continue to develop. If fans can get behind it and if the players can deliver and the reach gets bigger, then we can move forward and go up a couple of levels because that's how most of the elite club started. Manchester City, as we well know. We know when they did this big ten years ago. Good example. And that was a little bit different because they could spend what they wanted, but they still hadn't maintained that success. Chelsea had another club. You know, when I haven't made great Chelsea, you're just looking at them now with another club where they're looking at us. It can be done. I look at them across the park between a huge club. Where they were four years ago to where they are now is bear differences. And it can be done. Let's hope we start to make those strides, but it all sounds like things are moving forward. Is there anything I've missed off there, Tom? That's the confidence that our last meeting? No, I think that's it from international. I think that's probably enough, isn't it, mate, as well? I think, as you say now, it's all set now. It's all in place. Let's hope that on a football side, primarily, that we see the progress that we need to, because I think that's what we all want, and that'll drive them a mentor more than anything else. Fingers crossed, but now it is exciting, the buzz amongst the supporters club leads at the moment. Not just in America, but I've been working with some of the South American groups as well is amazing for obvious reasons. So, we want to try and connect that into other parts of the world as well now. And again, I want to make sure that these fans that are stuck with us through largely thin are able to be part of the next phase. So, that's what I'm going to continue doing with the rest of the forum and with Joe and the other international members to keep it going. So, look, we need to keep spreading the word, don't we mate? We do, we do keep spreading toffy TV, where there's well talent, that's where you get it. But three big games now in six days for Everton. So, Sunday's a big game and a tough game, but we've got Salford City then in a cup, the Carabao Cup on Wednesday, that's a big game. And then obviously West Brom, early kick-off next day, very early for you, next Saturday morning, isn't it? So, a big weekend out and guessing the interest will be there as well. Hopefully, hopefully we have a great weekend. That would be lovely. So, just have three good results over the next week or so. I think will be incredible for us and get us right on the proper footing for the rest of the season. Fingers crossed. Very good. You mentioned it before, hopefully we get a grip of this pandemic and we can get back in stadiums as well and really show the new lads what it's like to play for Evertonians when we're behind you. Build everything else as much as we can, but keep fighting the good fight. You're doing a great job. And look, if anyone in any part of the world wants to learn more about how they can be part of what we're doing, then obviously I know you're in touch with people, but they can get in touch with us at the fans forum. If there's things that we need to point them towards the club on, we'll do that with the engagement team that are building stuff as well. People should feel free to get all of us. Most definitely. If you're watching this from anywhere and you want to speak to Tony, you can do as a Chicago ever Tony, but like you said, the fans forum is there as well. Get in touch with them if you want to become a supporters club or you just want information about your local supporters club. There's the avenues there. Now you can have conversations with people about what to do next and get on board the Everton train because it might just be going a little bit quicker than it has been for the few years fingers crossed. Let's see what happens. Big thanks to Tony for getting up at the Crachydorne in Chicago and recording this. He told me before. It's just before his kids made loads of noise and he'd be able to speak. So there you go. Natto. Big pleasure, mate, speaking to you. Thanks very much for getting up and I guess I'll speak to you again in 46 weeks and see how we're going with it. Sounds great yet. Happy to speak any time and thanks for having me on again. Good to see you mate. Top man, top man. Big thanks there to Tony Samson joining us all away from Chicago. Make sure you check out the fans forum like I said if that's what you want to get involved in any of the supporters clubs. Otherwise give this video a thumbs up. Subscribe if you haven't and if you want more videos join us on Patreon. See you later.


Man, I feel really bad about that cleric video. Like the more I think on it. So you know what? I'm gonna play some Smash to make myself feel better. Before I do Smash though, I wanna do Mii's. Ah, where's the- is there no music? I know what music to put on. It's the gamer national anthem. Whoa, it doesn't have Insta preview. Look at that! I can scroll through the faces and I actually press them. I can swap between two things quickly. CCC, switch me- Well, this means I can do the Mii now. The Mii creator.  That's a lot. This is a lot. This is a crazy amount of hairstyles. Wow. It's always a little bit jarring the fact that the line is like above the nose a little bit. It looks kinda like I've got a mustache. I think I have brown eyes. Oh no. No. Okay, that's better. Oh! Sorry, I'll get to Smash eventually. I'm just- I like character creators. Oh yes! There we go. Hell yeah. Uh, this is Smash Ultimate. It's not actually what they advertised. It's just a remake of Smash 64. This is all you get. Oh, Diddy fights with me! Neat! Bah! Buh! All right? Uh! Buh! Neh! Buh! Donkey Punch! Uh! Buh! Neh! Neh! Donkey Punch! I did it! I did the smashing! Banana! Bomchoo! Buh! Buh! Buh! Eh, all right. Is Heather Smac talking me? Well, it's warranted.  Eh, ow! What a me! Buh! Buh! I can't- I can't read that. I'm too busy beating up little children right now. No, Diddy, don't get that. That's bad. That's bad. Stop. You're bad. Lucas, that's bad. Stop it. Stop, Lucas. It's your bedtime now. Give me the old Clapperoo! Oh, Diddy's dead. That's OK.  Yeah, it's all... Buh! Buh! We tech those. Aha! Take that. Take this. And those. And some of these. And not that. I don't like that. Diddy-O! Diddy-Y! Boosh! Bozer! Bozer! Aha! The spike wins. And then this. Buh! This minigame, which I'm already tired of. Well, it's Silver. Silver the Hedgehog. He's so cool. And edgy. But a different kind of edgy from Shadow. Sanic, come here. Fight me. There we go. The Nerf Challenger bots? No, no, no, no, no, no. This is just the first one. Just wait. Let's see. Where's Ganondorf? Oh! This boy. And that. And this. And some of these. Some of those. I'm unstoppable. He can't do anything to me. There's nothing he can do. He just can't. Man, Samus should just bring Yoshi on our missions now. There's nothing this boy can do. He's too big. Look, Waluigi's in Smash. He's so useful. Look at him go. He's doing his best. And Knuckles. Don't rush your video. Don't tell me what to do. Yeah, because there was very little risk to. Oh, it's boy. I'm a light bow gun. Light bow gun. Light bow gun. Normal shots. I'm all poisoned. Just like in the game. Wait. Now let's carve him. Luke. I am your fursona. Ouch, ouch. Stop. Stop. Oh, never mind. Thank you. Tipper, I barely knew her. Whoa. Now it's an even fight. Well, remember that time in Fire Emblem when Marth turned 50 feet tall and fought Evil Dragon? It's Ridley. He's too big. Well, he actually is too big. I should counter more. I say, is I missed my counter? All right. Thanks, Alucard. You helped. Huh, huh. All right, so this is a pit trap. Throw it down somewhere, right? Like there. OK. Come here, Wrath. Come here, Wrathalos. Mirror. Yeah, it works.  God, I'm so good at this game. Stepping on the pitfall. Yeah. Dude, that's so rad. Yeah. Hey, look at Link's pretty face. I would kiss him. I wonder who it could be. It's Mr. Tekken. There we go. It's like forward down diagonal down or something like that. Yeah, forward, forward. Something diagonal down. Diagonal down, down, forward. Or forward, down, diagonal, down. Forward, forward, down, forward, forward, down, down, diagonal. Easy.  Ken no Ken I will avenge you maybe Sure, you can wow I actually did it look at that Yeah, talk is cheap.  I know all your tricks I'm so excited for my boy Look at him. Let's go five Not even not messing around sword Yeah, Luigi's cowering in fear.  Oh, yeah, I forgot. Oh, yeah, look at that sword Big and large and range II. I don't even need to do anything else Just Sword be the villain. I was always meant to be my sword's bigger than yours Come on sword Sword my backstory is sword. My motivation is sword Unipalitena your shield is too small for my sword link.   There's someone in here Teddy.  Oh geez Okay, I'm so dead. Oh, yeah, okay One fear Wow, what is it?  I can bring it back. I've got rage now.  You got deleted out of the game Oh Yoshi. Oh, I have trouble with Yoshi, too. I have trouble with a lot of characters. Oh, no He knows how to grab. I'm screwed Stomp sword a good air dodge The king of evil is too strong Okay, well he's defeatable though Don't you taunt at me?  I wanted that disrespect. Oh Well sword God that was okay. That's questionable range That is questionable range. I don't know about that one. This is a stage Heard oh Good tech. I'm sorry. I get super I get hyper competitive. I'm sorry if I if I get very uh assholish It's just friendly competition, you know. Oh bye Kirby. Yeah, you guys have just let me win to be nice All right, okay, my controls are right now. Ah good start Oh That's a move That's an attack that happened what? The edge guarding Mirror see what happens. Oh Which whoa, no, no, no, no, sir. I know what you were doing. I know that move No, what oh Why did I let him do that to me?    So if Teddy runs out the clock Could win by default. No, but he's going deep. He's going in It's like nah, I want a real win here.  Oh toasty. That was your chance that air dodge Whoa, oh, I really thought he would have made that. Oh Good game Teddy Well done Ridley needs to work on his core Max Andre getting real aggressive very aggressive Whoa, what was that move?  They're so precise too. So I'm impressed that you're able to consistently land those Teddy wants it. He wants it so bad. Who can stop this monster? Oh His own proximity mine Yeah It's over Raining champ. All right freshman. It's up to you now. You know Making sure to establish dominance. Oh god.  No freshman Freshman why he wants that counter? He knows he's aggressive.  You can't touch them. They've got too many spikes All right, Teddy. This is where your reign of terror ends. You may be able to defeat crocodile But can you defeat sword? Oh? Why'd you stop? Oh good air dodge. Oh, what happened? I Guess there's a delay on your air dodge. Oh The up tilt to side tilt Yeah, I'm not making that oh No, not spiking me I'm the king of sword and shield mmm Nope, not today. Oh Oh Teddy What happened? Oh, I mean I'm supposed to be in your face. Oh it delays. Okay. Well sit down There's a new king in town. Oh god. Oh, no All right, dude. All right, bro All right, bro He's like it's my safest option It is a safe option. It's an obnoxious one too. No, you don't sword The range is crazy No, I rolled into that. No, oh toasty Toasty, no, I almost feel bad See if we could do this again. Nope. Yeah Not on my watch It's a good fight. Good fight. Let's see big sword. You need to babby sword. Oh Oh, it's little babby sword look you want to look pretty today.  I don't know what I'm ever going to do This king He's got a fast sword I got a slow sword. Oh I'm so sorry. He's short. It's too fast for me Whatever shall I do? Oh Whatever shall I do? He's so it is too fast. Oh Zeno oh I Feel bad because I looked brutal. He's dead. He's actually dead. I Killed him through the game Goes girthy hits. Oh, I saw do hope. He doesn't grab me and throw me off of the edge and suicide That would be the worst thing to have to happen. Oh Should have expected that stomp Stomp I should do that stomp Stomp no sword Oh, I love this cannon Okay, well I deserve that nope Nope wow Okay, he's pulling the sword strap, but with his kicks. Oh It's close one that would have been very very bad that was very very bad two heavy weights No Sword No, let that happen Oh Dennis GG the forward smashes are too strong and too thick weeds The return of the teddy oh He wanted to he wanted to stomp so bad he stomped himself off the stage With all the down tilts and I did it again too busy. No My boy my guy Well, he was too busy worrying that he could Didn't stop to think if he should Suicide is badass And this is a walk-off stage too, so it's very dangerous for both of them Just a single attack from one of them can completely destroy the other like that. Oh the forward tilt Sparta kicking him off the stage could very well still be his game like on a walk-off you never know Just one bad move Nice going kid. Don't get cocky. It's time for me Make like Thanos and do it myself. I brought you down before I'll bring you down again. I need to stop going so deep I say that as I go deep bull Wanted it. I wanted it. I wanted it Okay, yeah, that's gonna do it Nope the king is back No, I meant to all right well if I didn't press the right button, then I'm the worst player congratulations Teddy you beat everybody praise. Teddy praise. Teddy. Hmm. Teddy. Good guy, Teddy Gonna be spectating because he doesn't want to destroy everyone. Oh Dennis was like I know the spacing The super armor Oh God this game is so hype you guys like I don't I don't like scream a lot This game is super hype I don't get hype about any fighting games either because I don't play other fighting games But this is the only one that I understand somewhat Immediately goes for the sword No Why do you have to do them like that?   Yeah, that's what you get retorting Go on deep. Nope Ah, oh I was actually very stressed there time for the revenge when I played Marth. Oh, okay We're gonna have swords. Oh, oh, it's the reverse now. I have the big sword. No, you don't Yeah Never use Ganon against a Ganon main. I know all of your secrets. Oh Never mind Unless you're like the top top tears to players Tearless don't matter like like at our level. We're just kind of whatever your list don't matter for us Oh, what is this map? It's the Mario Brothers.  What what what to the sides? All right? We're supposed to take those Joseph We're supposed to take those we're supposed to take those Don't you stop that God you can go around. Oh, no, he's after me save me help help somebody Get out of here with my eye holes. What come back here you I'll catch you eventually This map I'm gonna get you. I'm gonna get you There we go.  There we go Gorsh Okay, all right, I'm still in the game Golly gee willikers Batman This goddess has got some things.  Whoa Sorry, I was quiet. I was focusing God. That was rough timber. You gave me a you made me work for that Samus is like my worst matchup. Oh Man All right, I'm down three stocks. It's because I have a puny sword. That's why It's not because I'm bad.  You're just like yeah, I'm just gonna shoot another one casually It'll hit him. I know it will wow gg. Oh, no, it's Isabelle She's come to vanquish to their darkness. Oh, yeah, there's the there's the fishing lure No, Isabelle. No, it clips zinging when they should have zagged.  All right timber. It's all up to you now. Oh, it's peach you. Oh It's that that's the team skull Thing. Oh, that's adorable. I love it Dark Samus doesn't know what to do. It's like this crazy little rat thing shoot like oh That was a good that was a good effort though Good one for timber You did very well. You got very close Get out of here. No, I'll take it. I'll take it I'll take it. My thumb was not the adrenaline's getting to me and my thumb was like on the top part of the Controller stop giving me bitch. It's distracting That grab is very strong range Out of here with my eyeholes. Yeah Ba da da da da da da da da da da da da da da da da da da da the edge guarding oh all right man those that felt good


A doctor has been curing incurable cancer patients for 50 years, while being fought by Big Pharma the entire time. Since the discovery of antineoplastins in 1977, a series of astonishing events have unfolded. The doctor has endured threats, multiple raids on the clinic, resulting in the confiscation of patient records, and the dissemination of false propaganda to mislead those attempting to research him. Big Pharma has even gone so far as to convene six grand juries in a futile attempt to indict him, despite being unable to sway a jury to support the charges. The legal battles have taken a heavy toll, costing the doctor millions of dollars, a financial burden that would have crushed most individuals in his position. Not only has this battle been personally costly, but it has also drained millions from taxpayers as the FDA channels funds into campaigns against him. The pharmaceutical giants have attempted to patent drugs already patented by the doctor, and have engaged in sabotage, trying to exclude him from his own clinical trials. An unprecedented situation, given that he is the sole financier of his trials, independent of large pharmaceutical corporations. If approved, the doctor's anti-neoplastons could revolutionize cancer treatment, surpassing traditional, perilous methods, such as radiation and chemotherapy. In addition, there's a hidden truth that Big Pharma doesn't want you to discover. The remarkable effectiveness of the Chicoil PEMF therapy system. With Chicoils and quantum frequencies, you might be just one frequency away from overcoming your limitations.


Hi everyone, Joe for Jaspy's casebreaks.com, coming at you with a random number block for a quick hit mixer number three. Just the Colts. Just the Colts. Remember, random number block, not part of the promo, but big thanks to Logan, Brian, and Jason for getting all the spots, appreciate all of you, the three of you. All there are the numbers right there. Let's roll it, randomize names and numbers three times, one, two, and three. Down to two, three times for the numbers, one, two, and three. We got five down to eight. All right, so Jason's got a lot of numbers here. So Jason, you got five, nine, four, three, seven, and eight. Brian, you got zero, six, and one, Logan, with two. All right, we'll see you in the next video for the break, Jaspy's casebreaks.com.


Crow Wing County Sheriff's Todd Doll is retiring this year and the race to take his place is now on. The election consists of three candidates who are campaigning to make it past the August 14th primary. Reporter Rachel Johnson has more. Eric Kling, Scott Goddard and Pat Picard are going head-to-head in a race to be the next Sheriff of Crow Wing County. Scott Goddard is running for the position after 20-plus years of serving. I started with the Breezy Point Police Department shortly thereafter went to the Sheriff's Office, short stint back at Breezy Point and then back to the Sheriff's Office. Pat Picard is a Brainerd High School graduate who went on to join the military in the Minnesota Army National Guard before joining the police force. I've been with the Sheriff's Office for over 20 years, 22 total years of law enforcement. I've worked for the Crosby Police Department and I also currently work for the Pequot Lakes Police Department and Cayuna Police Department where I'm the Deputy Chief. Eric Kling is running for his old position. He previously served as Sheriff of Crow Wing County from 2003 to 2007. You know I'm the Police Chief up in Pequot Lakes right now and I've helped that department become a better department and now I want to go back to the Sheriff's Office. The candidates will be narrowed down to two on the August 14th primary and then voted on in the general election November 6th. All candidates have many years of experience and have similar goals for the office but their focus is very. It's just not about a sheriff being a big public figure. Let's try to get our whole team at the Sheriff's Office engaged and inspired to serve. You know we're very fortunate and to have the relationships that we have with our community right now and we have to really make sure we're trying to strengthen those relate relationships within our community. It's one of the things that the Sheriff's Office doesn't do very well is that community policing piece. They take a call up in Jenkins and then run all the way down to Garrison so they can't build relationships with people and that's one of the things I want to make sure that we're doing is building relationships with people so that they trust us.  My focus as a sheriff of Crowing County is continue our collaboration that we have with all of our entities. Social services, our courts, our health department, really trying to drive home the point that this is not just a one-person show or a one department show. Though the race has been tight we will have to wait until the August 14th primary to see who will make it on the ballot November 6th. Reporting from Brainerd, Rachel Johnson, Lakeland News. You can vote by mail or in person through of the August 13th for the primary. If you enjoyed this segment of Lakeland News please consider making a tax deductible contribution to Lakeland PBS.


But I hope that you're here to listen to me talk about Kafka, because that's the room that you are in. So yeah, first things first, my name is Stella Cotton. I am an engineer at Heroku, and like I said, I'm going to talk to you today about Kafka. You might have heard that Heroku offers Kafka as a service.  We have like an engineering team that's strictly dedicated to doing cool stuff to get Kafka running on Heroku in like super high capacity. I am not on that team. If you were here to see that talk, this is the wrong talk. I don't actually know anything about running a Kafka cluster or tuning Kafka to handle like super high load. So who am I? I am a super regular Rails engineer, like many of you. I wasn't actually familiar with Kafka at all when I joined Heroku. I was like this mysterious technology that suddenly was like everywhere. And like all these hosted Kafka solutions, not just on Heroku, but at other providers.  And it seemed important, but I wasn't sure why. And then when I joined Heroku, I'm suddenly in this world where like not only is like Heroku an important part of our product offering, but it's actually like a really integral part of our system architecture overall. So today I'd like to talk about three areas that I hope will help other Rails engineers become more familiar with Kafka. We're going to start with like what is Kafka? We'll talk about how Kafka can power your services. And a few, just like two practical considerations and challenges that were kind of unfamiliar to me when I started using event driven systems. So what is Kafka? The docs on Kafka.apache.org, that's actually like the docs are super good, by the way. They describe it as a distributed streaming platform. But that doesn't really mean a lot to me as a web developer. But one of the classic use cases that people talk about for Kafka is data flow. So if you're running like an e-commerce website, for example, you want to know more about what your users are doing like on that platform. You want to track each page they visit, each button they click. But if you have a lot of users, this can be a lot of data. And if we wanted to be able to send that data from our web applications to a data store that our analytics team uses, how could we record and stream that high volume of data? One way is to use Kafka. And the basic data structure that powers Kafka is this idea of an append only log. And when you think about logs, people here, like what do you think about? For most web developers, that's going to be an application log. When something notable happens in our web applications, we're going to log it in chronological order. We're going to append each record to the record prior. And then once that record is persisted in this application log, it's going to be there indefinitely until we truncate earlier versions of our logs. So in a similar fashion, Kafka is also an append only log. Kafka has an idea of producers, and those are going to be applications that produce log events. You can have one producer of events, or you can have multiple producers of events. But unlike an application log, which is typically written so that you as a human can consume the log later on using your eyeballs. In the Kafka world, applications are going to be the consumers of these events. Like with producers, you can have one consumer, you can have a bunch of consumers, and a big question for web developers is often like, what's different about Kafka than something like Sidekick or Rescue? And in Sidekick and Rescue, events are typically going to be added to a queue. But once something picks it off to actually do the work, that disappears. In Kafka, it doesn't matter how many consumers are reading these events. Those events are going to continue to persist for other consumers to consume them until a specific retention period is over. So let's go back to our original example, our e-commerce app. We want this e-commerce application to create an event each time a user does something on the platform. We write each of these events or records, which Kafka is what Kafka calls events. And you want to do that to a user event log. And Kafka is going to call a log a topic, basically. And if you have multiple services, they can all write events to this user event topic. And each of these Kafka records that we write, it's going to have a key and a value, like a hash and a timestamp. And Kafka's not going to do any validation on this data. It's just going to pass along binary data no matter what kind of format it's in. So in this scenario, we're using JSON, but you can use a lot of different kinds of data formats. And the communication that happens between these clients that are writing to Kafka and reading off of Kafka is going to happen over a persisted TCP socket connection. So it's not going to have a TCP handshake for every single event. So how can our Rails app specifically interact with the Kafka cluster? We can use one of a few Ruby libraries. Ruby Kafka is a lower level library for producing and consuming events. It's going to give you a lot of flexibility, but it also has a lot more configuration. So if you want to use a simpler interface without a lot of boiler plate setup, there's Delivery Boy and Race Car, which are also maintained by Zendesk. And also Phobos. And these are going to be wrappers around Ruby Kafka to kind of abstract away a lot of that configuration. You've also got Karafka, which is a different standalone library. And similarly to Ruby Kafka, it has a wrapper called Waterdrop. And it's based on the same implementation that we saw before with Delivery Boy. So my team, we actually use a custom gem that predates Ruby Kafka. So I haven't actually used these in production, but Ruby Kafka is going to be the gem that Heroku is going to recommend that you use if you look at our Dev Center documentation. So, a brief look at how you can use Delivery Boy. We're going to use the simple version. Like I mentioned earlier, built on top of Ruby Kafka. And we can use it to publish events to our Kafka topic. First, we're going to install the gem, the usual, run a generator, and it's going to generate this config file, which you're probably pretty familiar if you use databases. And Delivery Boy is meant for getting things up and running very, very quickly. So you don't have to do any other configuration, except the brokers. Like, give them the address in the port, which might be localhost if you're running it locally. And the Delivery Boy docs will tell you how you can configure more things, but this is like the MVP. And using Delivery Boy, we can write an event outside the thread of our web execution to a user event topic. You can see we passed in user event as the topic. And each of these topics can be made of one or more partitions. And in general, you want two or more partitions. Partitions are a way to partition the data that you're sending in an event in a topic. And that allows you to scale your topic up as you have more and more events being written to that topic. And you can have multiple services that are writing to the same partitions. And it's the producer's job to say which partition you're going to send those events to. Delivery Boy is going to help you balance events across those partitions. You can let it just assign your event randomly to a partition, or you can actually give it a specific key. And why would you want to give a partition key? It's so that specific kinds of events go inside a single partition. Because Kafka only guarantees that events are delivered in order, like in our application log, inside a partition, not inside a whole topic. So for example, if you want to make sure that your user events related to a specific user all goes to the same partition, you pass any user ID there. And that way you could make sure that every event related to a user shows up in order, so it doesn't look like they're clicking all around on the website out of order because it's going to different partitions. And under the hood, Ruby Kafka is using a hashing function. So it's going to convert this into an integer and do a mod to divide by the number of partitions. So as long as your partition count stays the same, you can guarantee that it always goes to the same place. It's a little tricky if you start to increase your partitions. So now we're writing events to our user topic. That's really the only thing we really need to do. If you have a Kafka cluster running, you can also use another gem called racecar. Same thing, wrapper around Ruby Kafka maintained by Zendesk. And a same very little upfront configuration, just this generator. This config file will look familiar because it's pretty much the same. But this will also create a folder called consumers in your application too. And an event consumer subscribes to our user event topic with that subscribe to method at the top. And this is just going to print out any data that it returns. So we're going to run that consumer code inside of its own process. So it's going to be running separately from the process that runs our web application. And in order to consume events, racecar is going to create a group of consumers. It's going to be a collection of one or more Kafka consumers. And it's going to read off of that user event topic. And each consumer inside that consumer group is going to be assigned one or more partitions. And each of these are going to keep track of where they are in these partitions using an offset, which is like a bookmark, a digital bookmark. And the best part is that when one consumer goes away, if it fails, those topics are going to get reassigned to other consumers. So as long as you've got at least one consumer process running, you've got a good availability story. So we talked a little bit about what is Kafka under the hood. And let's talk more about the technical features that make it valuable. So one is that Kafka can handle extremely high throughput. One of the key performance characteristics that I thought was pretty interesting is that Kafka has the message broker, rather Kafka does not use the message broker, like the Kafka cluster, to track where all the consumers are. Like a traditional enterprise queueing system, like AMQP, is going to actually have the event infrastructure itself keep track of all those consumers. And so as your number of consumers scales up, your event infrastructure is actually going to have more load on it. Because it's going to have to track larger and larger state. And another thing is that consumer agreement is actually not trivial. It's not easy for the broker itself to know where the consumers are. Because like do you mark that message has been processed as soon as it gets sent over the network? Well, if you do and the consumer is down and it can't process it, how does the consumer say, hey, event infrastructure, actually can you resend that? You could try a multi-acknowledgement process like with TCP, but it's going to add performance overhead. So how does Kafka get around this? It just pushes all of that work out to the consumer itself. The consumer service is in charge of telling like where am I, what bookmark am I at in that ordered commit log. And so this is kind of cool because it means that reading and writing event data is constant time, O of 1. So the consumer either knows that it has an offset. It says, give me this specific place in the log. Or I want to start at the very beginning and read all the events. Or I want to start at the very end. And so there's no scanning over large sets of data to figure out where it needs to be. And so the more data that exists, it doesn't matter. It doesn't change the amount of time to look up.  And it also runs as a cluster on one or more servers. It could be scaled out horizontally by adding more machines, extremely reliable. And data is written to disk and then replicated across multiple brokers. So it has this scalable and fault tolerant profile. So if you'd like to know more about actual data distribution and replication side of Kafka, this is a pretty good blog post. And by the way, the slides will be on the website. And I'll tweet them out at the end. So don't bother trying to write down these links, because that would be a little complicated. And so to give you a more concrete number around what scalable looks like, Netflix, LinkedIn, and Microsoft are literally sending over a trillion messages per day through their Kafka clusters. So Kafka is cool. It's awesome. It can get data from one place to another. But we're not in a data science track. We're a track about services. So why do you care about this technology in the context of services? So some of the properties that make Kafka valuable for event pipeline systems are also going to make it a pretty interesting fault tolerant replacement for RPC between services. If you aren't familiar with the term RPC, there's a lot of different arguments about what it means. But it means remote procedure call. And TLDR, it's a shorthand for one service talking to another service using a request like an API call. So what does this mean in practice? Let's go back to our example of the e-commerce site. User is going to place an order. It's going to hit this Create API in our order service. And when that happens, you want to create an order record, charge the credit card, send out a confirmation email. And so in a monolithic system, this is going to usually be like this method call. It's going to have blocking execution. You might be using Sidekick or something to handle sending the email. But as your system grows more and more complex, you might start extracting these out to their own service. And you can use RPC remote procedure calls to talk between these services. So what's some of the challenges that you might find with using RPC? And so one is that the upstream service is responsible for the downstream services availability. If the email system is having a really bad day, the upstream service is responsible for knowing whether or not that email service is available, and if not retrying any failing requests or failing altogether. So how might an event stream help in this situation? So in this event-oriented world, an upstream service, our order as API, is going to write an event to Kafka, saying that an order was created. Because Kafka has this at least once guarantee, it means that that event is going to be written to Kafka at least once, and will be available for a downstream consumer to consume. So if our email service is down, that event is still there. That request is still there. And when the downstream consumer comes back online, it can pick back up. It can use its bookmark and say, I need to pick back up from XYZ and continue to process those events in order. So another challenge that larger and larger organizations find is coordination. In increasingly complex systems, integrating a new downstream service means a change to an upstream service. So if you'd like to integrate a new fulfillment provider, for example, it's going to kick off a fulfillment process when an order is created. In an RPC world, you need to change that upstream service to make an API call out to your new fulfillment service. In an event-oriented world, you would add a new consumer inside the fulfillment service that's going to consume the order created event topic. So there are some upsides. What's the big downside? In our first example, the dependency between those services is super clear. Like you look at that method and you see, oh, this, this, and this. The upstream service knows exactly which downstream services depend on knowing that the order was created. By abstracting away that connection, you gain speed, you gain independence, but you do sacrifice clarity. So you've got a Kafka. You're comfortable with the trade-offs. You understand what you're getting into. You'd like to start incorporating events into your service or in an architecture. So what might this look like from an architectural perspective? Martin Fowler discusses how, when people talk about event-driven applications, they can actually be talking about incredibly different kinds of applications. And I found this personally to be true even inside of Heroku. And it could be a big pain point when you're having a discussion about challenges, about trade-offs, in these kind of systems. So he's trying to bring a shared understanding to what an event-driven system is. And he started outlining a few architectural patterns that he sees most frequently. So I'm going to zoom through this to cover these. But you can learn more on his website or even better. He gave a keynote at GoToChicago that really covers this in depth. So the first pattern he talks about is an event notification pattern.  One service simply notifies the downstream services that an event happened. The event has very little information. It's just saying an order was created at this time. If the downstream service needs more information about what happens, it's going to need to make a network call back up to the order service to fill that information out. The second pattern he talks about is event-carried state transfer. And in this pattern, the upstream is actually going to augment that event with additional information so that your downstream consumer can keep a local copy of that data and not have to do that network call. And it can be actually super straightforward when everything that the downstream services needs is encapsulated inside that event generated by the upstream service, which is awesome. Except one of the challenges here is that you might need data from multiple systems. So for example, our order service, it's going to create an order, write the event. Fulfillment service is going to consume that event. And the fulfillment service is going to need certain details about the order, which is totally fine because we have that order information. And it's going to be passed along inside the event. But if it also needs to talk to a customer service, for example, to know who to send a package to, it's going to either need to make a network call or it's like to actually retrieve that information like we saw earlier, or it needs to find a way to persist a local copy of the data that it needs. And the idea is that you can also consider building that local copy off of events that the customer service is going to write. And so the fulfillment service is going to consume a separate set of events from your customer service that it can then persist locally and join it inside of its own database. A third pattern that Fowler talks about is event sourced architecture. This takes the idea of an event-driven system like even further. And it's saying that not only is each piece of communication between your services kicked off by an event, but it says that by storing every single event or storing a representation of every single event and replaying all of these events, you could drop all your databases, completely rebuild the state of your application as it exists in this moment just by replaying that event stream. So Fowler talks about an audit log being a good use for this scenario. He also talks about this really interesting high-performance trading system, which is not really something that's relevant to my interest, but might be relevant to yours. But having an audit log of everything that happens and actually relying on it to rebuild your application state is two very different levels of technical commitment, like seriously different. There are going to be additional challenges that come into play when you're looking to be able to recapture this state of the world. So one is code changes. So I worked on a payment system in the past and a big challenge that we had was if you tried to recalculate prior financial statements, they depended on business logic that lived inside the code, hard-coded, in the past, and that had changed. And so if you tried to recalculate all that money that you needed to send out to users based on the state of the world that day, you might actually get different values, and that's a problem. And that was not an event-driven system, so this is an issue even in regular systems, but it's something that you really need to understand when you're relying on the ability to rebuild your state of the world from events. And in a similar fashion and other challenge is that that state of the world might not be the same for third-party integrations. That might have changed, and an API call out to a third-party provider might return a different set of data or even an internal provider. Fowler talks about some more strategies for handling these issues. It's not an insurmountable task, but it is a big deal. And the final pattern that Fowler talks about is command query responsibility segregation, which if you've ever talked to anybody about event-driven architectures, you might, I would say 50% of the time, they think you're talking about this, and you may or may not be talking about this. So you might be familiar with CRUD, and that's a way of encapsulating logic for creating, reading, updating, deleting a record in a database inside your service. And it's at the heart of Rails controllers, like, this is very Rails-y. But the idea of CQRS is that instead of thinking about all those things as existing in the same domain, that you can actually split them out. So the service that writes to your system and the service that reads from your system are actually split. And at its simplest, one service is responsible for writing orders, so any method or API call that feels like an order.create, an order.update taxes, whatever, that's gonna go into your order updater service. It's gonna go one direction. And reading methods, or API calls, getOrderById, those are gonna live in another service. And it's not just an event-oriented architecture thing, you can do this with API calls. But you'll often see event-oriented architectures. You'll see event systems nestled in the diagrams, usually at the place where commands are actually written. The writer service, this command handler, is gonna read off of the event stream, process these commands, store them to a write database, and then any queries are gonna happen to a read-only database. When you wanna use it, crud is much simpler. Separating out read and write logic into two different services really does add a lot of overhead. The biggest reason I think people use it is performance. So if you're in a system where you have a large difference between reads and writes, or a system where your writes are super, super slow compared to your reads, you can optimize performance separately for those systems. But it's an increase in complexity, so you really need to understand the trade-offs. I found this blog post to be pretty good, succinct, like the title says, when to use and not use CQRS. And I would also, if you're thinking about implementing any of these patterns in your system, take a look at Fowler's blog post or and watch his keynote to get a really deep dive into the trade-offs and considerations for these. So we talked about what Kafka is, talk about how this technology can change the way your services communicate with each other. So next let's talk about two practical considerations that you might run into when integrating events into your Rails applications. It's definitely not a comprehensive list, but it was like two things that really surprised me when I got started. So the first thing to consider are slow consumers. Like the most important thing to keep in mind in an event-driven system is that your service needs to be able to process events as quickly as the upstream service produces them. Otherwise you are gonna drift slowly and more slowly and slowly behind, and you may not be realizing it because you're not like seeing timeouts, you're not seeing API calls fail. You're just slower. You're just at a different state of the world than everybody upstream. And also you might start to see timeouts, like it's the one place where you will see timeouts are gonna be on your socket connection with the Kafka brokers. If you're not like processing events fast enough and like telling and completing that round trip, your socket connection can timeout and then re-establishing that actually has a time cost. Like it's expensive to create those sockets so that can add latency to an already sourced system making things worse. So if you're consumer slow, how do you speed it up? So there's gonna be a lot of talks at RailsConf today and RailsConf prior about performance in Rails. But a more Kafka specific example is that you can increase the number of consumers in your consumer group so that you can process more events in parallel. So what does that look like in practice? So you remember in race car you run a consumer process by passing in a class name like user event consumer. If you're using a proc file for something like Foreman or on Heroku, you can actually start race car with the same class multiple times and it's gonna automatically have each of those processes have it be an individual consumer that's gonna join the same consumer group. And so you want at least two of these consumer processes running so if one goes down you're gonna have the other failed partitions be reassigned. But it also means that you can parallelize work across as many consumers as you have topic partitions. So of course with any scaling issue you can't just add consumers forever. Eventually you're gonna hit scaling limits on shared resources like databases. So you just can't scale forever but it will give you a little bit of wiggle room. And if you don't actually care about the strict ordering inside those topic partitions you can use a queuing system like Sidekick to help manage work in parallel and take a little bit of pressure off of the system. And it's extremely valuable in this case to have metrics and alerting like paging around how far behind you are from when an event was added to the queue. So Ruby Kafka is instrumented with active support notifications but it also has a stats and data dog reporters that are automatically included. And you wanna know if you're drifting a certain amount behind when the events are added. And the Ruby Kafka documentation which is also super good has a lot of suggestions for what you should be monitoring in your rail systems. And going one step further on my team before we put a new service into production because we use Kafka for a lot of our services I will run game day failure scenarios on staging but consuming off the production stream where we'll move our offset back by a certain amount to pretend like our service has been down for a day or two and see how long it takes us to catch up because if you have a serious outage on your downstream service you're gonna wanna know how much will room do you have and talk about what failure modes are acceptable for your service because if you're running an order service for example like you might wanna optimize for finishing those orders no matter what. It might take you four hours it might take you a day but you want it to be done but if you're running a chat bot service users are gonna be extremely confused if four hours later they start seeing things appear inside of their chat. So you'll wanna talk about what that means to process data at a delay. And they're also, so a big thing in Kafka to talk about is this exactly once versus at least once you can actually design a Kafka system to have an exactly once guarantee with newer versions of Kafka. So it means that consumers could assume that a message in a Kafka queue has only been sent once there's never a chance that messages will be not sent at all or that it'll be sent more than once and Confluent has a blog that talks a little bit more about this but the reality is with Ruby Kafka you should assume that your messages will be delivered at least once so it's gonna be there but you might see it more than once. So that's really important and one thing that this means is that you need to design consumers to expect duplicated events. So you can either rely on your database and use like Upsert for item potency or. Yes, thank you so much. Got the dance in too. All right, so design your consumers for failure. Rely on Upsert to lean on your database or you can include a unique identifier in each event and you can just skip events that you've already seen before but either of those things are gonna make your application more resilient in the face of failure because you can move back an offset and replay events and not be worried that you're gonna duplicate the same work twice. And the second thing that was really surprising to me was Kafka's very permissive attitude towards data. You can send anything in bytes and it's gonna send it back out. It's not gonna do any verification. This feature makes it extremely flexible because you don't need to adopt a specific format like a serialization format to get started. Like we talked about before, freedom isn't free, freedom is a blessing and a curse. What happens when a service upstream decides to change an event that it produces? If you just change that event payload, there's a really good chance that one of your downstream consumers is gonna break and your colleagues are gonna be really upset and they're gonna start seeing exceptions, could take down their service but you have no idea because you didn't really know that anybody was using that data. So before you start using events in your architecture, choose a data format, preferably one, not multiple ones, and evaluate how that data format can help you register schemas and evolve them over time. It's an issue in RPC systems as well but the explicitness of those calls means that somebody changing an upstream service has like a built-in method for being like, oh wait, somebody might actually be using this information especially when that's like an outgoing event. Schema registries can provide a centralized view of schemas that are in use in your system. This is also, it's just like much easier to think about validation, about evolution of schemas before you actually do all of this event-driven architecture than afterwards. And there are a lot of different data formats but I'm gonna talk about two JSON which most people in this room are probably familiar with. It's the format of the web and Avro which might be new to some of you and I know there are probably at least two Australians in the audience. There's like a 75% chance I'm gonna slip up on the next two slides and call it arvo but I do not mean afternoon, I mean Avro. So just ignore me. So JSON's a pretty common data format. Pros, human readable, super nice as a human, I really appreciate that. And there's also JSON support in basically every language. But there are a couple of cons. The payloads, like the actual size of JSON payloads can be really large. It requires you to send keys along with the values which is nice because it's flexible so it doesn't matter what the order is in. But it's also the same for every payload. So when you send them over it can mean that those payloads are larger than other formats. So if size is a big concern for you, JSON could be a bad fit. And there's also no built in documentation inside that payload. So you just see a value but you don't actually know what it means. And schema evolution is challenging. There's no built in support for A-listing one key to another if you want to rename a field or setting a default key value so that you can evolve over time. So Confluent, they're the team that built Apache Kafka and they now have a hosted Kafka product. They recommend using Avro like many other protocol formats. It's not human readable over the wire. You have to serialize and deserialize it because it's set in binary. But the upside is that there is super robust schema support. A full Avro object is sent over and it includes like this idea of the schema and the data. So it has support for types. It's got primitive ones like ints, complex ones like dates. And it includes embedded documentation so you can actually say what each of those fields actually do or mean in your system. And it has some built in tools that help you evolve your schemas in backwards compatible ways over time. So that's pretty cool. Avro Builder is a gem created by Salsify and that actually creates a very Ruby-ish DSL that helps you create these schemas. So if you're curious to learn more about Avro, the Salsify engineering blog here has a really great write up on Avro and Avro Builder. So that is it for my talk today. I have a couple more slides though so don't start leaving because I always feel really weird with people like, and thank you, and then they have a couple more slides. So if you're curious to learn more actually about Heroku and how we run our hosted Kafka products or how we use it internally, we do have two talks that my coworkers, Jeff and Paolo, have given that you can watch. And if you're interested in Postgres related to Kafka but different, my coworker Gabe is giving a talk like literally in the next talk spot in room 306 about Postgres 10 performance and you. And then finally, I will be at the Heroku booth today. After this and like during lunch, if you wanna come by and say hi, you can ask me questions, you can get swag, we've got t-shirts and socks, and we also have some jobs, you know, the use. So yeah, thank you so much.


పితా పికి పినాంమానిందినెది దా఍పెగినే సతావ్ది గార్గ్ ధార్. వారఆతించ్పెనం న్విబ లోవితంహిని. आगता अनेक जगाय दखाते लिए वी मन भिलूर शीएम सीते दारगकिशना डूः बहंगोलु। बूविधि आर औनेक चिष देखाते पनून जगर ते ख़ूँम आर्चों लिए पाएनि आमस आने ग़दी मनुश एजिन लोए एजे साफ ची। ये जगस भर पर आमक ढद साते तेखा वहाँ नम भबददाड तर भमश़र सआट्टेप ये तो उग्तिव तर फर तिनी आमाधे बले... नाट हँस्पिरे ये अनेक जगय तेखाई सो तर लिता लेन वूई पाले चालो ఇం్మార్లిస్మకిదిల్ననిం్ప్మితసి అంత్తిల్ల్. ఆ఻సర్లురేమా్లిక పసర్నిల్. సంత్మారిల్ల్. గార్మనికది నిద్మలికింది. , ఎరూయా నౚANA, ఫ్లంభ్మ్డిద్త్త్లుంనినరాతై, వ్వకిర్స్ుడి. అ౑కూకర్ neighboursies andarity & hospitality firm against- ప్ఌయళి అదరి చు�食 కెలైలాను�げచల Train. ఆస్రిసణతో� some people were కు Twenty and severe. ని തి స్త్స్న్న్లు. మారిపినినాద్పికెై పిధరన్నో. తరికుమి పిమేీఎ నారికేలు మానిక్నిస్లికొ మేనూటిని ప్రిమీనాము. మేవాప్నోది 천 only , 37%,  accordion school 100% సిలటిన ఆటిరం వంపు、 కూపచ౉ఠ్రవిమావర ంపచౢపికౚర pests� అఘలపిల౟కబ diffic Emperor సడిలల బరి యరరాన� Legver kern ఌాయటి మర౦ాగ౿ మాటికలడదరి spent Crunch సపేక నేపునియ�  Rover Hospital. Moni Bhala Hospital is the best hospital. కలోం కాటోంత్రరతిం. He was at 21 years old gentleman from Bangladesh who came to me with bilateral hip pain. He had been to few other centers in south India where he was told that he needed both his hips to be replaced. He was the case of a few step which we also called as enclosing spondylitis. He had a bad hip in the sense both the hips were near fused and he had deformities as well. He also had some limb length discrepancies or inequalities what we call. I offered him a bilateral hip replacement at one stage. It is one of a kind surgery as it is not frequently done. I operated him about five days back, both hips in a single setting. Post-op he is doing well, he was immobilized the very next day after surgery. His limb length correction has been made to absolutely equal on both sides. He has no deformities and he is walking absolutely straight. He is being discharged on Day 6 of surgery. These kind of cases which need a bilateral replacement needs a good technical expertise as well as good anesthetic and post-op backup in the form of physiotherapy and nursing. So we at Manipal are very well equipped both surgically and in other departments to handle these kind of bilateral joint replacements. Thank you.


Hello, and welcome to this presentation of the STM32Cube firmware drivers, including the hardware abstraction layer drivers. While this presentation is specifically about the STM32H7, the STM32Cube comprehensive software tool offers STM32Cube MX graphical software configuration tool used to generate initialization code based on user choices. A complete embedded software package for each STM32 series, such as our STM32Cube H7 with hardware abstraction layer or HAL and low layer or LLAPIs. A consistent set of middleware components, RTOS, USB, TCPIP, graphics, etc. The embedded software package is a layered approach. Low level, hardware abstraction layer or HAL with libraries and examples. Middleware level, set of libraries with examples including RTOS, USB, TCPIP, etc. And application level, demonstrations for use on ST boards. Embedded software is delivered by series, STM32H7, STM32F7, STM32F4, etc. And common modules are covered with fully portable APIs. Embedded software initialization code can be generated through STM32Cube MX, allowing the customer to remain focused on the core application code. The STM32Cube package is a complete embedded software offer that ensures maximum portability between all STM32 series through three software layers, HAL, middleware, and applications. The HAL layer is providing an API for the STM32 embedded peripherals from analog to connectivity and cryptography to graphical categories. A rich set of examples is available to help developers start using the HAL and the product. The middleware layer contains a full USB host and device stack supporting many classes as shown. STMWIN, a professional graphical stack solution, is available in binary format and based on the MWIN solution from ST's partner, SEGAR, as well as LibJPEG, an open source implementation on STM32 for JPEG images and coding and decoding. There is also a CMSIS RTOS implementation with free RTOS, an open source solution, and a FAT file system based on an open source FAT FS solution. The TCPIP stack is based on an open source LWIP solution and the SSL TLS secure layer is based on open source Polar SSL. Advanced demos putting together all the embedded software components are also provided in the STM32 CUBE H7 package. There is a complete set of documents including release notes, readme files, or associated user manual. The packages come with free and user friendly license terms. Like all STM32 CUBE firmware packages, the STM32 CUBE H7 firmware solution comes in a single zip file having the structure shown in this slide. It's organized in several main folders. The documentation folder contains the STM32 CUBE H7 getting started document helping developers to quickly become familiar with the firmware package and its contents. The drivers folder contains all the ST developed drivers. CMSIS contains the files defining STM32 H7xx supported devices, peripheral registers declarations, their associated bit definitions, and address mapping. The STM32 H7xx HAL driver folder contains the drivers for all the peripherals. The drivers for all supported boards are found in the BSP folder. Middleware contains the supported middleware libraries and stacks provided either by ST or third parties. The projects folder contains templates, examples, applications, and demonstrations for supported boards and with pre-configured projects and specific readme files that provide all necessary information for a quick and easy execution. The utilities folder contains miscellaneous utility drivers that are used by the provided projects. The release note lists the contents of all the packages, tracks the main changes, and provides information on the supported devices and boards and any known limitations. Through its generic architecture, STM32 CUBE offers a highly portable hardware abstraction layer or HAL. It allows developers to implement application functions by building on layers such as the middleware layer without requiring any in-depth knowledge of the MCU. This improves the reusability of the library code and guarantees an easy portability to other devices. In addition, thanks to its layered architecture, STM32 CUBE H7 offers full support of all STM32 H7 microcontrollers and the development boards designed by ST. The user has only to define the correct macro in the STM32 H7xx.h file and get in touch with BSP drivers and example or application projects specific to each board provided within the firmware package. For each board, a set of examples is provided with pre-configured products for e-warm, MDK arm, and SW4STM32 tool chains. The right-side figure shows the project structure for the STM32H743IEVAL board, which is identical for all the other boards. The examples are classified depending on the STM32 CUBE level they apply to and are named as follows. Examples in level 0 are called examples and use HAL drivers without any middleware component. Examples in level 1 are called applications and provide typical use cases of each middleware component. And examples in level 2 are called demonstration and implement all the HAL, BSP, and middleware components. The template project is provided to quickly build any firmware application for all supported boards. The STM32 CUBE project list file allows a quick access and search for a given example within the firmware package. All examples have the same structure. The slash INC folder contains all header files. The slash SRC folder contains the source code. The slash E-warm slash MDK arm and slash SW4STM32 folders contain the pre-configured project for each tool chain. A README text file describes the example behavior and environment needed to make it work. Rich documentation is associated with the STM32 CUBE H7 firmware package. Some documents are generic to all STM32 series and others are specific to the STM32 H7 series. The getting started with the STM32 CUBE F7 firmware package user manual is the document that you need to read first when you start using the STM32 CUBE firmware package. The STM32 CUBE H7 firmware can be downloaded from ST's website at www.st.com slash STM32 CUBE FW. Thank you.