All right, can everybody hear me? Thank you. All right, let's get started. So, hey everyone, this is the Sigoth deep dive for KubeCon NA 2023. So this year, we're gonna focus pretty heavily on cell and our usage of it in Sigoth. So I'm Mo from Microsoft. I'm one of the leads for Sigoth. I'm Jordan Liggett, also lead for Sigoth from Google. All right, so we're gonna mix it up this year. So normally we wait till the end to do this, but this year we're gonna do it at the beginning. So I see Anish, I see you in the audience there. Thank you very much for all your contributions this year. To hear, I know you're not here. Hopefully you're watching this. Thank you also. I don't think I saw James, maybe if he's here, but also thank you for your contributions. Nalek, I know you're not here, but hopefully you'll watch this and say yeah. So, Nebruun, I hope you were here. I know you're here at the conference, but thank you also for all the work you did. Rita, I know you're hopefully gonna watch this afterwards, and thank you for all your hard work. And Ting, I know you're not here, but we very much appreciate your contributions. I'm gonna go over some of the stuff we did generically in 129 before we sort of deep dives more into the cell stuff. So there was like six high level things we worked on. KMSV2 went GA and 129, so yay, it's over. It's over. Cluster trust bundle just landed in alpha, so I know I see some cert manager folks here. I hope that they will adopt it at some point. We made some great improvements to balance service account tokens that contain node references as alpha NV129. James helped with that. We've made a bunch of improvements to Authent and OCD that we'll talk about in detail, and we are continuing possibly the longest journey of any single thing, which is the reduction of secret space service account tokens. All right, so you've heard probably people in various sessions talking about cell. What is it? If you're unfamiliar with it, it stands for Common Expression Language. It's a non-touring complete language, and it's designed to be pretty intuitive to read and write with a heavy focus on being able to bound execution time, run quickly, run in performance critical paths, and be able to limit the amount of memory and CPU that's used. Here's just an example of what it might look like. It's pretty natural syntax. You sort of have dot accessors to fields. There's the ability to have macros or functions that the integrator provides to the expression so that the person who's writing the expression can make use of, but doesn't actually have the ability to define and do crazy dangerous things. So why did we settle on cell? We started this exploration a couple years ago on the CIG API machinery side, and we'd looked at a lot of different sort of extensibility languages, things like Rego and JavaScript and Lua and Wasm, and none of them really hit all the points that we needed. It had to be really, really lightweight. Some of those were not lightweight. We had to be able to ensure that the expressions had a bounded cost. So cell does that by limiting the complexity, but also allowing us to compute the cost at compile time, so we can just not allow expressions that would be too expensive. This was especially important for cell use in areas that were API facing, where sort of end users or maybe less trusted users were the ones providing the expressions. Because that was the first place where we were using cell in Kubernetes, it was critical to get that right. Another benefit of cell, we can do really, really deep type checking integration. So rather than just sort of accepting a blob and then at runtime, maybe it works, maybe it doesn't, we can actually do that checking at the beginning and tell you when you're starting up or loading the expressions, this is gonna work well, this isn't gonna work well. And then as we've used cell in more and more places in Kubernetes, we have the ability to customize what the expressions have access to in terms of variables and functions and macros and helpers for each specific use. So here's just some of the places that outside of sigott cell is being used. We won't go into them too deeply because these have been covered in the API machine or deep dive and I think at least one other talk from CC covered these. But I just wanna highlight one thing, which is all of these use cases are either directly or indirectly related to the usage of cell in REST APIs. Whereas the next two things we're gonna talk about are usage of cell in a file-based config that's past the API server. So this went alpha and v129. There's a lot of improvements that we made overall to how OIDC can be configured in this cap. But I wanna really narrow our focus on the aspects of this that are related to cell and how cell improve this. So there's a lot of advanced uses that you can imagine where you want a full-blown authentication webhook. But there can be significant problems when your webhook is down and just the maintenance costs of having such an integration point. So we wanted to see how far we could let people get by just having static configuration on the API server. That kind of means you have to make some hard choices. So you have to sort of define what kind of tokens you're gonna accept and what they mean. So if you had an opaque token, there's really nothing you could do with something like cell because there's no way to interpret that without making a database query or something. We're not gonna hand you network access in the cell environment. That kind of goes against what we wanna be able to do there. But if you limit yourself to something like JOTS, that means you have a mechanism for understanding how you can verify a payload, you have a mechanism for key distribution, which is basically OIDC style discovery. Now you've constrained the input in a way that cell can really help you. So let's walk through an example. So on the top left there, you can see the exploded payload from a JSON web token, right? It's just a JSON object. And you can kind of see the claims that are available. So as we talked about earlier, you can define a custom environment, right? So where you see the cell expression that claims variable maps to that object at the top that you can see, right? And now you can kind of start seeing what things you can do, right? So it just so happens that this user's IDP emits a string that happens to be a concatenation of basically their group membership. Previously, you would have to write some kind of authentication webbook to sort of explode this information out. Now you can just use cell functions, split that out. And in this example, we've purposely injected a static group into the list as well. You can imagine how you would use that, for example, if you want every user from your IDP to belong to a particular group, so that way you can assign policy to them, right? Another one of the things that the authentication config will let you do is just have as many of these authenticators as you want, right? So you can kind of mix and match how all these configs work out for you. So as we kind of walk through, the username is gonna just be statically suffixed with this external user. And we're also going to take the audience from the token and put it in an extra field, right? Now this means that if you had an admission webhook or admission cell policy, you can make decisions based off of that if you wanted to, right? So for example, if your IDP encodes in the token that the user logged in with 2FA, you can make decisions based off of that, right? You might not allow any action in CubeSystem from a user that didn't log in with 2FA or something like that, right? And we can keep going and take this further. It is unlikely that your corporate IDP has a concept of like Kubernetes system users, right? It probably does not have any concept of a Kubernetes service account or a Kubernetes KubeLit. And so a user info validation cell expression basically lets you say, I never expect that to happen. And you can sort of constrain that down, right? So this one is basically saying, hey, if for any reason I ever see a user that has a system colon prefix in their name, just flat out reject the authentication. This example doesn't cover it, but you can actually do the same exact thing with the claim payload as well. So you can say that, hey, if the user is not in like a particular group, they can't authenticate at all, right? So in Kubernetes, if you authenticate, you get a baseline level of access. Like for example, you can hit discovery and get all the metadata about the cluster, right? That's not great if you know that that user has no business being in that environment, right? So sometimes your IDP lets you configure these things. Other times the IDP could configure it, but you don't happen to have access to that. That's a different team. And you just wanna manage your Kubernetes environment. Now you can do that, no web books necessary. So that was the set of authentication configuration that we've added more flexibility to. In 129, we also worked on expanding what you could do with authorization config. So again, previously, the way you would configure authorization, you would just pass command line flags and say, here are the modes I want. I want node authorization and RBAC authorization and maybe webhook authorization. And then if you said you wanted a webhook authorizer, you had to give it a kube config file to tell it where to talk to the webhook authorizer. It's a lot of flags, not super intuitive. And a lot of people came to us and said, I've got one webhook authorization integration off to some IAM system. But I actually have a second one I wanna run locally to maybe do some deny rules or something. I wanna run two webhooks. And the system we had only lets you configure one. You start trying to add multiple versions of webhooks via command line flags. It just kind of becomes a mess. And so we added the ability in 129 to have a config file that lays out exactly what authorizers you want. And you can have more than one webhook authorizer. You can order them the way you want. When you do that, some questions come up, right? Webhooks tend to be slow. They tend to be less reliable than the authorizers that are built in. And so as soon as we start talking about running more than one of these, we have some questions, some goals. Can we limit the blaster radius of these webhooks? Can we, if we know that the local one we're gonna run that has some deny opinions, if we know that it only cares about requests shaped a certain way, can we avoid sending other requests to that webhook? Avoid paying the latency cost. Avoid paying the reliability cost. And then finally, some users want to host authorization webhooks on the cluster. And so right away, you've got a cycle problem. If the authorization webhook is gonna maybe make certain requests not be able to be authorized, what about the requests to make the pods to run the webhook that's making the authorization decisions, right? It's easy to get into cycles and problems like that. So in addition to just being able to express having multiple webhooks, we added the ability to exclude certain requests from going to webhooks based on something called match conditions. For those of you who have seen match conditions on admission webhooks that API machinery did, this is a very similar concept. We followed the same approach, but this is in a file-based config. So we're gonna demo that now. Let's see if the demo works. And while Jordan gets that going, just as a reminder, admission webhooks run on mutating requests, authorization webhooks run on every request. So it's an excellent way to break your cluster if you do it wrong. All right. So what I have here, I've got a little status dashboard showing three types of clients. On the top here, I've got a load balancer that's poking at my healthy endpoint. This thing may or may not be authenticated. It just wants to know, is this server good so I can include it in the load balancer? Then I've got a system controller. This is a CUBE system service account. It does really important things. If we disrupt it, bad things are gonna happen. This is sort of a stand-in for every system controller that exists in Kubernetes. And then down here, I've got my demo client. This is the thing that maybe I want to authorize in a different way or put some safeguards around. And so this is what the authorization configuration looks like in 129. So to start, I just have the node authorizer and the RBAC authorizer. Pretty standard setup. If I enable a webhook authorizer at the end, first of all, dynamic reload. Not in 129, but coming in 130. So that's pretty great. You can change your config without restarting your API server. Now I've got a webhook at the end. And so you notice a few things. First of all, it is now authorizing my demo client. So that's cool. You'll notice the latency is higher for the demo client, right? But not for the system client. So it's because these are being authorized by the RBAC rules. And so they don't even make it to the webhook. But I am paying a little bit of a latency cost on my demo client. That's okay. So other things that you see here, you can actually customize the timeout and customize the failure policy. Like if I hit an error with this webhook, what should happen? Previously, the timeout defaulted to 30 seconds, which is really bad. And the failure policy just continued on in the authorizer chain, which might not be so bad. But if you're wanting to put deny rules in, you actually probably want it to hard fail. All right, so now we've got a setup where, I've got my webhook at the end. That's fine. But what if we wanted to have some deny stuff? Maybe we don't want anything outside the system controllers messing with CubeSystem namespace. Well to do that, we have to put maybe another webhook, a local webhook that knows about deny stuff up at the top. So let's do that real quick. So I'm just gonna do this part to start. All right, so now I've got a deny webhook up at the top and you see right away, like I'm paying latency cost on everything now, okay? I'm actually double paying it on my demo client. So everything just got slower across the system. So that's not ideal. But that's not even the worst thing that could happen, like this is when the webhook is working well. If it's, what if I get errors from it, right? Okay, my deny webhook just went down and I've just completely toasted my cluster. The load balancer thinks it's unhealthy, the system controllers are broken, everything is broken. So what we really wanna do is scope down this webhook to only requests that we know we might want to deny. And so we're gonna add a few match conditions. So the first thing we're gonna do, we're only gonna pay attention to resource requests. We don't care about, this deny webhook doesn't care about non-resource requests like discovery or health Z or metrics, okay? So we made that decision. So right away, our load balancer isn't impacted at all if this webhook goes away. The second thing we wanna do, this is only, in our use case, we're only caring about protecting cube system, okay? So we're only gonna pay attention to requests inside cube system. Everything else doesn't even touch this webhook, okay? So now my system controllers are happy in other namespaces, that's good. We're not paying latency costs there, that's good. But we still have cube system broken, so that's obviously not good. And so the last thing we're gonna do is we're going to exempt system service accounts from even being intercepted by this webhook. And so once we do that, my load balancer is happy, my system service accounts are happy, my non-system service accounts are totally fine in other namespaces, right? The only thing that would be impacted by an error if this webhook was completely unavailable is the clients I was trying to deny anyway inside the namespace I was trying to deny anyway. And so that one's still hitting an error, but when we fix the webhook, and that is actually working properly, now it can get the forbidden error we want. But we've really, really scoped down the worst case scenario. That makes me so happy. When people say, I wanna run multiple webhooks, and I say, why would you put yourself in that position? With this, we actually have a tool to make that a reasonable thing to do. All right, thank you, demo gods. A couple notes on that. Automatic reload is not in 129. For 129, you just start up your server and just config you start with, that's what you get. But automatic reload will be in 130 before it goes to beta. All right. If you have questions about any of the cell stuff or any of the other stuff that we talked about or did this release or stuff that's coming up, I wanna let you know how to get in touch with us. That's a link to the community page for SIGAuth. We have bi-weekly meetings, we have mailing lists, we have Slack channel. We're very friendly, we promise. If you have questions or have ideas or want to help with progression of some of these things, please come join us, participate, give your feedback, give your thoughts. Yeah, so with that, we have some time. I wanted to open it up for questions about this or any of the other stuff we talked about. There's a microphone there, I think, if you wanna line up if you have questions. Thank you. Also, a lot of the stuff we talked about is alpha, so please go play with it and give us feedback because we can still fix it. Once it's beta, then we can fix it with permanent tech. The question was about what's the motivation for the restrictions on cell execution and resource consumption? It wasn't nearly as specific as specific hardware, it's just the knowledge that the person operating the Cube API server, providing the hardware, the resources for that, is not always the same person that's populating cell expressions via the API. And so, we needed to be able to prevent abuse, essentially. For something like what we talked about here, where it's actually config files for the API server, abuse is not really as much of a concern, but it is still a critical path execution. And so, where it might be acceptable to pay milliseconds of latency going out to a webhook, when you're talking about the conditions that are gonna be evaluated to avoid going down that path, we really want nanoseconds to microseconds. And so, that's where cell fits, for authenticating out to an authorization webhook. We don't have that planned right now, but we structured the config file so that there's a spot for it if we get there. So, the initial connection type, there are actually two connection types. There's run in cluster, so this is if you're running inside a pod and you're delegating back to the main Cube API server for people running extension API servers, the second connection type is here's my cube config file. So, the first goal was really to get parity with what we already had from the command lines, but we have a spot for additional connection information styles in the future. Yeah, I really wanted what you asked for, but there was a separate cap that had tried to do it a couple years back that didn't really make progress. And it was probably gonna prevent this cap from progressing if we tried to solve that problem at the same time. So, I listened to Jordan basically and said just... You try to be incremental and actually deliver some things and then build those out, yeah. Yes, whether you use HTTP one or HTTP two is not currently under the control of this config. The client that it builds will actually try to use HTTP two. So, it will try to keep connections open to it, but that's not part of the control there. Yeah, it? No, not at all. Yeah, the client that's constructed, when you load the config and say, I'm gonna be talking out to a webhook, it creates a client, that same client gets reused. This is just sort of putting conditions in front, so sometimes we don't even call the client.  Yeah. But that doesn't happen. Thank you for going to the mic. I've got kind of a beginner cell question for you. Can you talk a little bit about how you guys like bind, it seems like cell fields are sort of dynamically generated on the context in which the cell is running. Can you talk a little bit about how you bind or like validate that like the field that you're operating on actually exists and like, or just maybe give me a guide on where to find resources for that. One, let me take the start of that. So I'm gonna back up, right? So it's situational specific, right? So if you look at, for example, the username expression where it's doing claims.username, we have absolutely no idea what's in your claims because your jot has no known schema to Kubernetes and there's no way for you to tell us what the schema is. So that is a runtime check and the runtime check will basically make sure that that cell expression returns a string, right? And if it doesn't, it's gonna error out. So if for some reason returned an integer or the claims.username wasn't there, it's gonna fail. But for example, in the user info validation on the right side, that user info object is a Kubernetes internal well-known schema object. So if you tried to type in user info.foo, your API server is not gonna start because it's like there's no foo field on that. So we basically try to do the absolute best we can with the schema that we know, but on things like arbitrary payloads, we can't help you there. Now, cell does have the question mark operator, so it has like optionals. So you can write cell expressions that can optionally pull in information depending on if you think it's gonna be there or not. So you can be as restrictive or as open as you want in those expressions, but go ahead, sorry. No, no, I was gonna say, thank you. There's two steps to using cell internally. There's a compile step, type checking step, and then there's an evaluation step. And so for things where we know the schema, the compile step will actually catch any errors where you're using a string where it's actually an end to using a field that doesn't exist. For dynamic things like the claims, like Mo mentioned, it's all run time. Thanks. Ready to go? Yes, yeah, that's correct. So the things that you have access to are the token, if you're doing token authentication, and then request attributes. So source IP is not included in request attributes yet, but if it's included in the token itself, then you could map that into extra information, and that would be visible to the authorizer. Yeah, so what you might want to do instead of saying that I'm gonna encode source IP into the token, you could instead encode the concept of internal network, or as I mentioned, something like Tuofay. Some claim that gives you the sense of okay, I trust this client in a different way than I normally do, so when they're gonna do, maybe they're gonna exec into a production pod. Sometimes you have to do that, but you still might want to, I see you laughing Jordan, sometimes you do. And so you could constrain it that way, but yes, that is totally possible. I saw a hand over here, yeah. No, no, no, no. Cell just evaluates expressions, and the variables that the expression has access to are entirely up to the integrator. So in this case, for the claim mappings, the inputs, we provide it a map of string to anything based on the claims in the token. For the validation rules, the input variable is a user object that has really well-known fields. So it's entirely up to us as we integrate cell into different aspects of the server what the variables are that it has access to, what the schema of those variables are. And we try really hard to make the schema match the same types you would be dealing with if you were using a webhook. So for the authorization rules, the object that you have access to is a subject access review schema. It's the same object you would be dealing with if we actually sent it out to your webhook for admission webhook conditions. The object that the cell expressions have access to is an admission review object. So it's the same object your webhook would see if we ended up sending it out to your webhook. We tried to make the schemas sort of a line between the cell expressions and the integration of that area. APM machinery has the ability to run cell expressions in validating a commission. So this is the 3488, and it's very generic. It basically is running the cell on an admission review. So you can do anything you want to do from the information in an admission object. So if you wanna talk meta, so cell for admission control has access to a function which lets you invoke the authorizer. And that authorizer you can ask it any question you want which then might flow into your webhook that we just configured, right? So yes, you can go as far as you want. Turtles all the way down. Yeah, just be careful, right? If you end up making like seven authorization calls. You can't, we don't let you. So this goes back to the cost. All right, right, right. The cost aspect. One of the great things about cell is we can be very specific in attributing cost to different parts of the expression. So when you're working with data, the cost is based on the function you're calling or the macro you're calling and the size of the data for something like the authorizer function that we make available to admissions cell expressions. We actually give that a really high cost. So you, I think you can basically only do two calls. Just because that could be going out into webhooks, like it's a pretty expensive call. So the cost is actually done at compile time.  Yeah, so it'll just fail before you can create it. And then there are additional protections at runtime. So if something unexpected happens, we thought you fit within the cost parameters, but then at runtime you're actually going along. There's also like a context cancellation mechanism so we can keep the server from running away with cost. All right, thank you for coming. We'll hang out here for a few minutes. Appreciate it.


AP editor said she can't imagine a US intelligence official being wrong. The Associated Press journalist who reported a US intelligence official's false claim that Russia had launched missiles at Poland last week has been fired. As we discussed previously, AP's anonymously sourced report which said, A senior US intelligence official says Russian missiles crossed into NATO member Poland killing two people. Went viral because of the massive implications of direct hot warfare erupting between Russia and the NATO alliance. AP subsequently retracted its story as the mainstream political media class came to accept that it was in fact a Ukrainian missile that had struck Poland. AP's firing of reporter James Laporta looks at this time to be the end point of any accountability for the circulation of this extremely dangerous falsehood.  And to this day the public has been kept in the dark about the identity of the US official who fed such extremely egregious misinformation slash disinformation to the public through the mainstream press. It is absolutely inexcusable for AP to continue to protect the anonymity of a government official who fed them such a profoundly significant falsehood. This didn't just affect AP staff, it affected the whole world. We deserve to know what happened and who was responsible, and AP has no business obstructing that knowledge from us. Laporta's firing looks like this is yet another instance where the least powerful person involved in a debacle is being made to take the fall for it. A powerful intelligence official will suffer no consequences for feeding false information to the press, thereby ensuring that it will happen again. And no disciplinary action will be taken against Laporta's superiors despite the buffoonery that subsequent reporting has revealed on their part. In an article titled associated press reporter fired over erroneous story on Russian attack, the Washington Post reports the following. Quote, Internal AP communications viewed by the Post show some confusion and misunderstanding during the preparations of the erroneous report. Laporta shared the US official's tip in an electronic message around 1.30pm Eastern time. An editor immediately asked if AP should issue an alert on his tip, or would we need confirmation from another source and or Poland? After further discussion, a second editor said she would vote for publishing an alert adding, I can't imagine a US intelligence official would be wrong on this. I can't imagine a US intelligence official would be wrong on this. Can you imagine not being able to imagine a US intelligence official being wrong? This would be an unacceptable position for any educated adult to hold, much less a journalist, still less an editor, and still less an editor of one of the most influential news agencies on earth. These are the people who publish the news reports we read to find out what's happening in the world. This is the baby-brained level of thinking these people are serving the public interest with. Anti-war commentator Daniel Larison writes the following of the AP editor's shocking quote. This is a quote from him. Skepticism about official claims should always be the watchword for journalists and analysts. These are claims that need more scrutiny than usual rather than less. If you can't imagine that an intelligence official could get something important wrong, whether by accident or on purpose, you are taking far too many things for granted that need to be questioned and checked out first. Intelligence officials of many governments feed information to journalists and have done so practically ever since there was a popular press to feed information too. And that information certainly should not be trusted just because an official's source hands it over. It is also always possible for intelligence officials to just get things wrong whether it is because they are relying on faulty information or because they were too hasty in reaching conclusions about what they think they know. Whether the AP's source was feeding them a line or was simply mistaken, a claim as provocative and serious as this one should have been checked out much more thoroughly before it got anywhere near publication. The AP report in this case seems to have been a combination of a story that was too good to check and a culture of deference to official sources in which the editors didn't feel compelled to make the effort to check. Indeed, the only reason the press receives such explicit protections in the US Constitution is because they are supposed to hold the powerful to account. If the editors of a wildly influential news agency will just unquestioningly parrot whatever they are fed by government officials while simultaneously protecting those officials with anonymity, they are not holding the powerful to account and are in fact not meaningfully different from state propagandists. They are state propagandists. Which is probably why they are sipping lattes in the AP newsroom while Julian Assange languishes in prison. As Jacobin's Branko-Marcetic observed, this is far from the first time AP has given the cover of anonymity to US government officials circulating bogus claims of potentially dangerous consequence. Like the time it reported an official's evidence-free assertion which later proved false that Iran had carried out an attack on four oil tankers off the coast of the United Arab Emirates or the time it led another one anonymously claimed that Iran may try to take advantage of America's troop withdrawals from Iraq and Afghanistan. So to recap, powerful government official who fed AP a false story, zero accountability. AP editor who asked if a report should immediately be published upon receipt of the story, zero accountability. Second AP editor who says she can't imagine a US intelligence official would be wrong, zero accountability. Journalist who wrote the story, singular accountability. In Assange society, power and responsibility would go hand in hand. A disaster would be blamed on the most powerful people involved in its occurrence. In our society it's generally the exact opposite, with the rank and file taking all of the responsibility and none of the power.  We cannot allow them to continue holding all of the power and none of the responsibility. This is backwards and must end.


So, every time Nintendo does a financial briefing, a quarterly update, a meeting with their investors, they generally update the schedule of primary Nintendo products by region. Essentially, what this is, is the release slate of video games coming to their two major platforms for the next six months to a year or so. The list is updated with only currently announced games, and these are obviously games that Nintendo is publishing and or partnered with in some way. Now, it is important to mention this because this is different than the graphs that Nintendo throws out on social media. Like when they throw up a timeline show and look at all these games coming out, that's very different from this because this is what they tell investors, look this is the games we have coming that we are going to make money from that will hopefully turn into profits into their pockets, which happens when they get dividend payments on their stock. Now, normally these are pretty standard. There usually isn't any new announcements found in these. They give either exact release dates for games that have release dates, like as an example Snipperclips plus Cut It Together coming out on November 10th. The Elis Super Mario Odyssey on here, even though it already released at the time, you know, coming out on the 27th, but sometimes you get an update and the update can go mostly unnoticed because it depends on what you mean by it. And Nintendo did something with this update schedule that I have never seen them do before. So we all know that Pokemon and Metroid have been announced for Switch, literally just announced to be made. That's it. No release dates, no nothing. And Metroid Prime 4 in all major territories, which apparently is a temporary name, is still TBA, which means to be announced, to be determined when they're going to release that game. That's typical. That's to be expected. And that's what I expected it to say for the Pokemon, as we're listening, a Pokemon RPG for Nintendo Switch. Well no, they're actually listing Pokemon for Switch for 2018 or later. So they're not committing to it coming in 2018, but they're saying there's a chance. What was that that Jim Carrey said, you're saying there's a chance. So unlike that situation in Dumb and Dumber when it was like 1 in a million, this is not a 1 in a million chance. This is almost a 50-50 shot. Here Nintendo is putting up that 2018 date. They would not be saying that if there wasn't an internal goal to have Pokemon for Switch done and ready to go in 2018. Now if that's the case, that would obviously be their major holiday title at the end of the year. Not only because that's the best time to sell a bunch of Pokemon games, but because that gives them the entirety of 2018 practically to continue to develop the game. Now this could be multiple things. You could say maybe the rushing the game, maybe it's not going to be as impressive. But we also don't know when the game was started on. Potentially they could have started on this game before even Sun and Moon came out. Or they could have been working on it since Sun and Moon came out, which would be 2 years of development. You figure they would need more than that for their very first game ever on Switch. Maybe they don't. Maybe the development of what they want to do on Switch is just really, really easy because the hardware massively overshoots their current ambitions for their first attempt at a Nintendo Switch full version Pokemon RPG. But again, it's just, you know, it might as well say TBA, but the fact that it says 2018 or later, which again, I've never seen this. I have looked at these reports over the past 20 years, especially when I was coming to Zelda. I always look for updates if there was an update to Zelda's release date they haven't announced yet. You know, Breath of the Wild says 2016. When's it going to, is it going to switch on here before they announce it and say it's coming out a different day or a different year? And that, it's just very interesting to see it announced kind of in this way. But again, it's very noncommittal. 2018 or later is very noncommittal. They're not saying it's going to come in 2018, but they're saying it might come in 2018. Here is Metroid Prime 4 being TBA. Well, Pokemon RPG says 2018 or later tells me that Metroid Prime 4 is for sure not landing in 2018. We might see it in 2018. We could see a teaser trailer for it at E3 or the Game Awards or something. But even in Nintendo Direct, of course, but I have a feeling that that's like one of those for sure is a 2019 game. It could be a spring 2019 game. I don't know. But this is just exciting because we've talked a lot at this channel about the lineup for next year and how it obviously does not seem as prominent as the lineup from this year, especially just from Nintendo's. Let's forget their parties because we honestly don't know what their party games are going to be there beyond the beginning of the year. We don't know, you know, Nintendo's lineup, you know, I'm just looking at it right now for next year. They have Kirby Star Allies, which is that Kirby game coming out in spring and then they have Fire Emblem for Nintendo Switch coming out at some point in 2018. Yoshi for Nintendo Switch coming out at some point in 2018. And then Project Octopath Traveler. I'll count that because it's an exclusive game, even though it's their party that's coming out sometime in 2018. And Dragon Quest Builders, I guess, is coming out in spring as well. That's about it. That's all we know for sure for 2018. There is nothing else announced except for Pokemon and Metroid. So Pokemon could definitely be even a bigger deal than Mario Odyssey if it lands next holiday. And I don't know when Fire Emblem is going to land. That could be a big deal for Switch. That, to me, could be their summer game, like their Splatoon 2 of the summer. Right? I think Fire Emblem is on that Splatoon 2 level now that it's jumped up in popularity since the release of Fire Emblem Awakening, Fire Emblem Fades, Fire Emblem Warriors. I think if they can get Fire Emblem for Switch out shortly after E3, or even before E3, that would do wonders for them. But they also don't have that massive spring title, right? Like, is Kirby and Dragon Quest Builders going to be enough in spring to be those sales drivers? I don't know. And obviously, Wolfenstein 2 is probably coming in, hopefully, early 2018. They just said 2018. I'm hoping it's spring, if not sooner than spring. I wouldn't mind if it hits winter at January 2018. But yeah, this is just exciting to me that Pokemon could be their capper next year. And I said could be, as I said, Nintendo 2018 or later. I got the screenshot up. It's going to be an interesting fun ride. And I can't wait to see where it takes us in the future. Interestingly enough for those that are curious, the 3DS lineup for next year has two games listed from Nintendo. And that's Kirby Battle Royale coming out in January. And then Sushi Striker, the way of Shishito. I remember seeing that game at E3. That game also comes out in 2018. There's a couple other games you look at. In Japan, they had the Dead Heatbreakers. Mario Party Top 100 releases in Europe in January, whereas it releases this year in the United States on November 10th, the same day as Snipperclips. So yeah, it's just a very interesting thing to see how Nintendo is going to handle it. I'm just, Pokemon, I just want it. It'll be my first time playing a Pokemon game in almost 15, 16 years. Like, I don't know what to say about, OK, take that back. Not my first time playing a Pokemon game in that long, but my first time investing in a Pokemon game. Like when someone said the other day, we're talking about badges and how they removed them. And this and that. I wasn't even aware of the badges got removed. That's how far gone I am from the Pokemon series, really since the gold and silver days. It just baffles my mind to even think, wait, there's no badges in some of the most recent games or something? I don't know. I don't know what's going on. So a lot of my, the reason I fell out of the series because of bad experiences, a lot of these experiences that didn't feel exciting to me after gold and silver. For all the criticism I might have for the Pokemon series since then, I haven't fully invested enough in a single Pokemon game to actually even call my criticisms legit. I can only talk about why I stopped playing Pokemon rather than why I haven't been able to get back into it because it's just baffling to me all these different decisions and all these different mechanics going on that are hard for me to understand on the outside looking in at this point. But whatever, I'm fully investing in Pokemon on Switch. For all I know, I'm going to love it. I'm going to be so invested in the game that Nintendo Prime is going to basically become Pokemon Prime. I don't know. Anyways, folks, I'm Nathan and Robert Jets from Nintendo Prime. Let me know what you think about this news down in the comments below. If you liked this video, you know what to do. And if you disliked the video, hit that dislike button. Subscribe for more content just like this. And I'll catch you in the next one.


two identical terrariums, and in each of these terrariums, you have the rare and beautiful GSI daisy that is so endangered, and it's such a great thing to have, and all the people come from around to look at them. The difference is, in the upper terrarium, it is divided into two by an unbreachable purple glass wall. Now, what's going to happen? Well, as you might imagine, things are not perfect in terrarium land, and the blight comes, and the blight kills off one of your GSI daisies in each of the terrariums, but if you're down here, you're not worried, because you can grow this beautiful daisy, and it will grow back, and it has its posy, and it just gets grown back when, oh my goodness, the rust comes, and it wipes out one of the daisies in each of the terrariums, and if you're down below, you're still not worried, because it can grow back, and pretty soon you have a beautiful display, but if you're up above, you're really worried, because now you're extinct. Now, suppose that instead of this being worried about GSI daisies in our terrariums, that we were worried about Glacier National Park seen in a map, and Yellowstone National Park seen in a map down here, and at the present time, Glacier and Yellowstone are connected by corridors that are essentially wilderness running down the Rocky Mountains. What is going to happen if we lose those corridors of wilderness that connect the two and turn them into islands? And the simple answer is that you don't lose everything, but you probably do lose some of the things that live in both of the parks, just as for the terrariums you get extinction.


What's going on, everyone? Sam here with latent sports cards. We've been 22 at Penini National Treasures football hobby, four box, full case break, number 63. Pick your team style. Andrew A with the Falcons, Andrew W Cowboys, Enmar G, Texan Saints, Bradley R Steelers, Chad R with the Bucks, Corey S Cardinals, Daniel S Eagles, Gary S Ravens Broncos, Greg M, Jets Hanobi Patriots, Jake S Browns, James L Rams, Jeffrey H Bill's Dolphins and Seahawks, Joe N Giants, Justin C Raiders, Kyle S Vikings, Mark R with the Commanders, Oren W Panthers, Rory C Lyons, Packers, Ryan B with the Chiefs, Sean M Niners, Simon S Titans, Tom B Bears Colts, Tai Chi Bengals and Yahweh T with the Chargers and Jaguars. Chase with another spot. Chase. What does that mean? Five to go, everybody. What does that mean? I know I always do pull my Ravens, that's true. 101 for Chris, I'll never forget the Chris, what's it called? The 101, Kyle Hamilton. Ravens would be sweet, dude. I love the Ravens. Love pulling the Ravens. Ray Lewis and Ed Reid have a really cool one. And you know that, like the Zach Thomas and that Duelado, the same one Ray Lewis and Terrell Suggs have a card? That's one that I haven't pulled it yet, but hey, what up, Stark? We're down to five to go on Star Wars Sig series, everybody. Five to go, thank you all. Three. Three to go, three to go, everybody. Wow, incredible. I mean, somebody else took a spot or two. Must have gotten deleted before I could say thank you. Must have been Chase again. Thank you, Chase.  All right, Super Bowl or Treasured Moments is at Cooper Cup 299, Rams. And Josh Allen at 25 for the bills. Usually we don't unless there's a damaged one, Gunnet. That's the only thing. To 49 is Curtis Samuel. Is that Gary? Assume that might be Gary. 18 to 49 is Kavon Tibidou. Yeah, usually unless there's a damaged card just because it costs a lot more in shipping, that's the only thing. We've got Framed Fabric of Layton Vandoresh. Game worn, nice one there for the Cowboys. That's a 49. Oh, G, duh, G-unit.  Gosh, nice one here is gonna be a Bailey Zappy to 49. Yeah, if you have something damaged on one of yours, we will send an empty box and wrapper. But yeah, 22 of 49, John Riggins. Notable nicknames, Diesel. Nice one there, congrats on that to commanders. That's cool. Eric with a spot. Jay Taylor with a spot. I think we're down to like one to go here, Sean. One spot left in Star Wars Six series. We've got Ron Jaworski, three of 99. Nice one there. Joseph S with a spot. I believe we're actually down to two. I think there was a refund that came in. I think there was a refund that came in. Yeah, two to go. Two to go, everybody. That is TJ Watt, 18 of 99. Steelers. Shaq still has nicknames from Riggins. I guess technically, yeah. I can make this last one. Going to the Packers. 81 of 99, Christian Watson. Nice one there, congrats on that. Packers. No refunds, all sales final. It must have been an auto refund. Every now and then it'll do that. Every now and then Shopify. If it flags like a fraudulent purchase, it'll come through as a, it'll come through and say like automatic refund, whatever, so it must have happened on that one. Or if it doesn't recognize a card or something, it'll do that. So it must have been the case. So still two remaining on Star Wars Six series, everybody, thanks again. We are almost there. Almost there. A, Treasured Rookies, Garrett Wilson, the 99. Empty top there. Got a Dak Prescott to 35. There is, that is messed up right there. There's like a tire track through that. Empty Boxing Rapper coming to the Cowboys. Sorry about that, Dallas. Is David Bell, nine of 25 for the Browns. How is something on there, man? There was something on there. Erica Zucanmuts, 28 of 49 for the Dolphins. Going to the Colts, Matt Ryan, 14 of 25. That's on that Colts. Got Duel, Jerseys, Matt Stafford, Cooper Cup. That'll be going to the Rams. Greg, I'm selling us out. Thank you, Greg. We're sold out for the night, everybody. Sold out on the night. Yo, Greg. Thank you all. Appreciate that very much. Jordan Davis, 57 of 99. Going to the Eagles. Nice one there, Billy. Oh, cool one here. 35 of 49, Antonio Freeman. That'll be going to the Packers. Nice one there, Green Bay. Well, throwback hit there. Got eight of 18. Jersey number parallel, Jalen Tolbert. Nice one there for the Cowboys. Congrats, Dallas. Eight of 18. 65 of 99, three-color patch in ball RPA. Ryan Robinson, Jr. Nice one there for the Commanders. And empty. Not a bad box there, a couple of RPAs. No, we gotta get it. We have definitely gotta be a banger somewhere in here. Still two boxes. There's gotta be something big. Gotta be something big. Oh, that one's fine. Such a salesman. Oh, you know, man. That's why I went to school for her. Got a, to 99, Tyreekill. But I do love cards also. I've been obsessed with cards since I was like six years old. Seven of nine, that is gonna be a Matt Stafford. That's one's so sick. So sick. Gary, this one's awesome. 15 of 25, game gear, game use patch, and Juan Bolden. That's awesome. That's my guy right there, dude. One of my Ravens jerseys I currently own. Game worn, as you can see on the bottom. Three colored patch, awesome. Six of 25, Devin Duvernay. Tremendous treasures going to the Ravens as well. Here we go again, Gary. Back to back hits there, buddy. Got 43 of 49, TJ Hawkinson for the Vikings. Doesn't make up for the 2x shield T-Law. 32 of 99 is gonna be a Tyreek Wholen. Nice one there for the Seahawks. Magnus next one. Let's be going to the Commanders. The future on card auto, Johan Dotson, seven of 25. Nice one there, the future. Johan Dotson, J.Dot. Going to the Rams again. We've got a Tyler Higby, 81 of 99. Grats, Los Angeles. 21, NT. That is gonna be a Jacob Harris, five of 25. Again, 2021. I'm known for picking the Commanders as my dark horse team every year. I'll stick with it for a while. I'm just gonna stick with it until it works. So I could say, hey, I told you so, five years later. I like Magnus. This one's mine, I like Magnus, last one. 43 of 49, Sausgardner. Crossover, RPA. Going to the Jets. How many times do you think you've gotten somewhat excited that a bear's coming but it's actually a Ravens patch card? Probably a lot, AJ. Probably a lot. Very true, AJ. Very true. I hope nothing put the worst for them. Fair for the Commanders. Fair, Gary, fair. Fox, good luck. All right, CMC at 99. Hey, what up from Germany? That's awesome, what up? What up, what up? One of the Niners, got to A. Mike Evans, 33 of 35 for the Bucks. This will be a Derek Henry, Century Materials, four of 49. He's at home. Yeah, he's off today, stuck with me. 18 of 49 for the Bengals, that is a Jamar Chase. Nice one there. That guy brings me luck sometimes. Nice one here, Tremendous Treasures, two-color patch, 15 of 25, Tyrion Davis Price. Tyrion Davis Price, 31 of 99. That is gonna be a Micah Parsons Century Materials for the Cowboys.  Got to A, Devontae Wyatt, 18 of 95, Jersey Number Parallel for the Packers. A, 91 of 99, Jason Seahorn, going to the Giants. Nice one there. Nice one here, the Magnum X2. Got to A, true RPA, 92 of 99, four-color Peer Strong Jr. What up, CJ? Yeah, it's been a minute, how you doing, buddy? Peer Strong Jr. And going to the Falcons, 23 of 99, Desmond Ritter. Congrats on that, I believe that is Andrew. There you go, Andrew, nice one there, buddy. Desmond Ritter, 23 of 99, that's awesome. Get that into a mag for ya, empty, empty. They come in on like the same, we have like the software we use, it's the same, you can see them both at the same time. All right, we've got jerseys, Micah Parsons, Tyrann Davis Price, Jamar Chase, Derek Henry, Tariq Wollin, TJ Hawkinson, Devin DuBernay, Anquan Bolden, Chukar Duel of Stafford and Cup, got an Eric Azucanma, Matt Ryan, David Bell, Bailey Zappi, Leighton Van Der Ash Gameworn, that is Kevon Tibido and Curtis Samuel, non-magdottos, we've got a Jason Seahorn, Devontae Wyatt, Jacob Harris, Tyler Higby, Jordan Davis, Brian Robinson Jr., Jalen Tolbert, Antonio Freeman, TJ Watt, Ron Jaworski and John Riggins. Hey, have a good one, Gary. Thanks again, buddy, appreciate you selling us out on this break. Have a good one, my man. All right, we've got Johan Dotson, seven to 25, that one should be okay. Christian Watson, 81 of 99, true RPA. Pierre Strong Jr., 92 of 99, true RPA, that one should be fine as well. Sauce Gardner, 43 of 49 for the Jets, crossover and a Desmond Ritter, 23 of 99, RPA for the Falcons. I'll do it for the break, guys. Thanks again for the field. Coming up next is NT Divisional.


from theCUBE Studios in Palo Alto in Boston, bringing you data-driven insights from theCUBE and ETR. This is Breaking Analysis with Dave Vellante. Earnings season has shown a conflicting mix of signals for software companies. Well, virtually all firms are expressing caution over so-called macro headwinds. We're talking about Ukraine, inflation, interest rates, Europe, FX headwinds, supply chain, just overall IT spend. MongoDB along with a few other names appeared more sanguine thanks to a beat in the recent quarter and a cautious but upbeat outlook for the near term. Hello and welcome to this week's Wikibon Cube Insights powered by ETR. In this Breaking Analysis ahead of MongoDB World 2022, we drill into Mongo's business and what ETR survey data tells us in the context of overall demand and the patterns that we're seeing from other software companies. And we're seeing some distinctly different results from major firms these days. We'll talk more about Mongo in this session which beat EPS by 30 cents in revenue by more than $18 million. Salesforce had a great quarter and its diversified portfolio is paying off as seen by the stock's noticeable uptick post earnings. UiPath, which had been really beaten down prior to this quarter, it's brought in a new co-CEO and its business is showing a nice rebound with a small three cent EPS beat and a nearly $20 million top line beat. CrowdStrike is showing strength as well. Meanwhile, management said Microsoft Workday and Snowflake expressed greater caution about the macroeconomic climate and especially on investors minds is concerned about consumption pricing models. Snowflake in particular which had a small top line beat cited softness and effects from reduced consumption especially from certain consumer facing customers which has analysts digging more deeply into the predictability of their models. In fact, Barclay's analyst, Ramo Lenshaw published an especially thoughtful piece on this topic concluding that Mongo was less susceptible to consumption headwinds than for example, Snowflake. Essentially for a few reasons. One, because Atlas, Mongo's cloud managed service which is the consumption model comprises only about 60% of Mongo's revenue. Second is a premise that Mongo was supporting core operational applications that can't be easily dialed down or turned off and three that Snowflake customers and Snowflake has a more concentrated customer base and due to that fact, there's a preponderance of its revenue is consumption driven and would be more sensitive to swings in these consumption patterns. Now I'll say this first, consumption pricing models are here to stay and the much preferred model for customers is consumption. The appeal of consumption is I can actually dial down turn off if I need to and stop spending for a while which happened or at least happened to a certain extent this quarter for certain companies but to the point about Mongo supporting core applications, I do believe that over time you're going to see the increased emergence of data products that will become core monetization drivers and Snowflake along with other data platforms is going to feed those data products and services and it become over time maybe less susceptible and less sensitive to these consumption patterns it'll always be there but I think increasingly it's going to be tied to operational revenue. Last two points here in the slide software valuations have reverted to their historical mean which is a good thing in our view we've taken some air out of the bubble and returned to more normalized valuations was really predicted and look forward to look we're still in a lousy market for stocks it's really a bear market for tech the market tends to be at least six months ahead of the economy and often not always but often as a good predictor we've had some tough compares relative to the pandemic days in tech and we'll be watching next quarter very closely because the macro headwinds have now been firmly inserted into the guidance of software companies. Okay, let's have a look at how certain names have performed relative to a software index benchmark so far this year here's a year to date chart comparing Microsoft Salesforce Mongo and Snowflake to the IGV software heavy ETF which is shown in the darker blue line by the way it does not own the CTF does not own Snowflake or Mongo. You can see that these big super caps have fared pretty well whereas Mongo and especially Snowflake those higher growth companies have been much more negatively impacted year to date from a stock price standpoint. Now let's move on let's take a financial snapshot of Mongo and put it next to Snowflake so we can compare these two higher growth names. What we've done here in this chart is taken the most recent quarters revenue and multiplied it by 4x to get a revenue run rate and we've parenthetically added a projection for the full year revenue. Mongo as you see will do north of a billion dollars in revenue while Snowflake will begin to approach $3 billion 2.7 and run right through that four quarter run rate that they just had last quarter and you can see Snowflake is growing faster than Mongo at 85% this past quarter and we took now these most of these profit of these next profitability ratios off the current quarter with one exception both companies have high gross margins of course you'd expect that but as we've discussed not as high as some traditional software companies in part because of their cloud costs but also their maturity or lack thereof both Mongo and Snowflake because they are in high growth mode have been operating margins they spend nearly half or more than half of their revenue on growth that's the SG&A line mostly the sales and marketing is really where they're spending money and they're specialist so they spend a fair amount of their revenue on R&D but maybe not as high as you might think but a pretty hefty percentage the free cash flow as a percentage of revenue line we calculated off the full year projections because there was a kind of an anomaly this quarter in the Snowflake numbers and you can see Snowflake's free cash flow which again was an abnormally high this quarter is going to settle in around 16% this year versus Mongo's 6% so strong focus by Snowflake on free cash flow and its management Snowflake is about $4 billion in cash and marketable securities on its balance sheet with little or no debt whereas Mongo has about $2 billion on its balance sheet with a little bit of longer term debt and you can see Snowflake's market cap is about double that of Mongo's so you're paying for higher growth with Snowflake you're paying for the Slutman, Scarpelli, execution engine, the expectation there stronger balance sheet, et cetera but Snowflake is well off it's roughly $100 billion valuation which it touched during the peak days of tech during the pandemic and just as an aside Mongo has around 33,000 customers about five times the number of customer Snowflake has so a bit of a different customer mix and concentration but both companies in our view have no lack of market in terms of TAM okay now let's dig a little deeper into Mongo's business and bring in some ETR data this colorful chart shows the breakdown of Mongo's net score net score is ETR's proprietary methodology that measures the percent of customers in the ETR survey that are adding the platform new that's the lime green at 9% existing customers that are spending 6% or more on the platform that's the forest green at 37% spending flat that's the gray at 46% decreasing spend that's the pinkish at around 5% and churning that's only 3% that's the bright red for Mongo subtract the red from the greens and you net out to a 38% which is a very solid net score figure note this is a survey of 1500 or so organizations and it includes 150 Mongo DB customers which includes by the way 68 global 2000 customers and they show a spending velocity or net score of 44% so notably higher among the larger clients and while it's a smaller sample only 27 in Mia's net score for Mongo's 33% now that's down from 60% last quarter note that Mongo cited softness in its European business on its earning call so that aligns to the ETR data okay now let's plot Mongo relative to some other data platforms these don't all necessarily compete head to head with Mongo but they are in data in database platforms in the ETR dataset and that's what this chart shows it's an XY graph with net score or as we say spending momentum on the vertical axis and overlap or presence or pervasiveness in the dataset on the horizontal axis see that red dotted line there at 40% that indicates an elevated level of spending anything above that is highly elevated we've highlighted Mongo in that red box which is very close to that 40% line it has a pretty strong presence on the X axis right there with GCP snowflake as we've reported has come down to earth but still well elevated again that aligns with the earnings releases AWS and Microsoft they have many data platforms especially AWS so their plot position reflects their broad portfolio massive size in the X axis that's the presence and very impressive on the vertical axis so despite that size they have strong spending momentum and you can see the pack of others including cockroach small on the vertical on the horizontal but elevated on the vertical couch basis creeping up since this IPO Redis MariaDB which was launched the day that Oracle bought Sun and got my sequel and some legacy platforms including the leader in database Oracle as well as IBM and Teradata's both cloud and on-prem platforms. Now one interesting side note here is on Mongo's earning call it clearly cited the advantages of its increasingly all-in-one approach relative to others that offer a portfolio of bespoke or what we sometimes call horses for courses databases. Mongo cited the advantages of its simplicity and lower costs as it adds more and more functionality this is an argument often made by Oracle and they often target AWS as the company with too many databases and of course Mongo makes that argument as well but they also make the argument that Oracle they don't necessarily call them out but they talk about traditional relational databases of course they're talking about Oracle and others they say that's more complex, less flexible and less appealing to developers than is Mongo. Now Oracle of course would return we retort saying hey we now support a Mongo DB API so why go anywhere else? We're the most robust and the best for mission critical but this gives credence to the fact that if Oracle is trying to capture business by offering a Mongo API for example that Mongo must be doing something right. Okay, let's look at why they buy Mongo. Here's an ETR chart that addresses that question. It's Mongo's feature breadth is the number one reason lower cost or better ROI is number two integrations and stack alignment is third and Mongo's technology lead is fourth. Those four kind of stand out with notice on the right hand side security and vision much lower there on the right that doesn't necessarily mean that Mongo doesn't have good security and good vision although it has been cited security concerns and so we keep an eye on that but look Mongo has a document database it's become a viable alternative to traditional relational databases meaning you have much more flexibility over your schema and in fact it's kind of scheme unless you can pretty much put anything into a document database developers seem to love it. Generally it's fair to say Mongo's architecture would favor consistency over availability because it uses a single master architecture as a primary and you can create secondary nodes in the event of a primary failure but you got to think about that and how to architect availability into the platform and got to consider recovery more carefully. Now no schema means it's not a tables and rows structure and you can again shove anything you want into the database but you got to think about how to optimize performance on queries. Now Mongo has been hard at work evolving the platform from the early days when you go back and look at its roadmap it's been started as a document database purely it added graph processing, time series it's made search much, much easier and more fundamental it's added Atlas that fully managed cloud database service which we said now comprises 60% of its revenue it's Kubernetes integrations and it's kind of the modern microservices stack in dozens and dozens and dozens of other features Mongo's done a really fine job we think of creating a leading database platform today that is loved by customers, loved by developers and is highly functional and next week, the cube will be at MongoDB world and we'll be looking for some of these items that we're showing here in this chart this always going to be main focus on developers Mongo prides itself on being a developer friendly platform we're going to look for new features especially around security and governance and simplification of configurations and cluster management Mongo's likely going to continue to advance its all in one appeal and add more capabilities that reduce the need to spin up bespoke platforms and we would expect enhancements to Atlas further enhancements there is Atlas really is the future maybe adding more cloud native features and integrations and perhaps simplified ways to migrate to the cloud to Atlas and improve access to data sources generally making the lives of developers and data analysts easier that's going to be, we take a big theme at the event so these are the main things that we'll be scoping out at the event so please stop by if you're in New York City at MongoDB world or tune in to the cube.net Okay, that's it for today. Thanks to my colleagues, Stephanie Chan who helps research breaking analysis from time to time Alex Meyerson is on production as today is Andrew Frick Sarah Kenny, Steve Conti, Anderson Hill and the entire team in Palo Alto, thank you Kristen Martin and Cheryl Knight help get the word out and Rob Hoth is our editor in chief over there at Silicon Angle remember all these episodes are available as podcasts wherever you listen just search breaking analysis podcasts we do publish each week on wikibon.com and siliconangle.com you want to reach me email me david.valante and siliconangle.com or DM me at Dvalante or a comment on my LinkedIn post and please do check out ETR.AI for the best survey data in the enterprise tech business this is Dave Vellante for theCUBE insights powered by ETR, thanks for watching, see you next time.


Welcome to the course on great ideas that have shaped the world. This is a course dedicated to ethical, political and scientific ideas that are shaping our contemporary world, from Socrates, Plato, Confucius, Buddha, to the contemporary digital revolution. Now, this is a course that is global in nature, in a sense that it deals with ideas from different parts of the world, from China, from Africa, from Latin America, from the West. Furthermore, this is a course that is focused on the contemporary. So to give an example, if you are going to read Darwin or Confucius, you are going to read these authors from the perspective of our contemporary world. The question is not what was the relevance and what are the debates on Darwin, for instance, in the 19th century, but the question is how has Darwin impacted our world? You don't need a background for this course. This is going to be a course that is interdisciplinary and introductory to a certain extent. I'm looking forward to developing debates with you, to discussing with you, and to listen to your intuitions.


So what are you doing? Do my introduction for my vlog do my introduction for my vlog Friday, but you know how many people comment Friday Friday Friday Friday Friday Friday Friday your hair looks nice Thank you unlike unlike signers hair. What what's wrong with my hair? I don't like this parting on you I just thought that it's a bit greasy. So I need to do something so just this also guys She's wearing my earrings in my top just saying hi guys. Welcome back to my channel. If you're new here. My name is seppy I'm sorry. I sound so stuffy. I am suffering from hay fever season Symptoms and that's why I just sound like this, but I'm not ill. Thank God at least I don't think I'm ill Anyway, it's Sunday, and we're going out for a final family lunch before soul goes back to Sheffield someone say hi and Sine goes back to Latvia. So Sine say hi Yeah, so obviously You guys are coming along because that's what we do. So I was just packing and Picking our shoes on Sine has more time than so so she's gonna pack later. I've already packed I have you yeah, okay, and where are we going for lunch for brunch lunch? Mom, why should we go to eat? Yeah, why should we go to eat? Stay home. Hello everyone. You look so beautiful.  Thank you very much. You're so cute packing for girls I could so she made food for them to take how cute is she look at this? So she's just made loads of food for them and like all of the meat pre-packed into like portions and How cute is that? So we've come back to where we went last week for breakfast for brunch It's a place called Midi's and it's in Southgate and just got my latte. We've all got lattes Latte gang Latte gang Sauce hungry. She has no energy to say latte gang right now. Say latte gang Latte gang So yeah, we're gonna have our little lattes. I had I have ordered the chicken Milanese with Henne We'll see you'll see So catch us up on your life because you weren't here last week People need to know what's going on in Sheffield Absolutely enough So and I've got my eyelashes redone by the way, I get them done at a place called beauty rehab And the girl who did it for me this time so be we did classics mixed with like a few russians And I am obsessed so I'm finally telling me they've never seen my lashes look nice. So Absolutely love them Is that a smile I see as soon as her food is appeared and she was trying to tell us she wasn't hungry Is that a smile? Oh? Oh, she's done it angry now. Oh, I gotta move the camera Thank you Okay So we are gonna perform a very typical Iranian tradition soul Okay, so basically in Iran Or Iranians in general around the world. I don't know if you guys do this So maybe I'm making this up, but I know I'm not making it up We put eggs under the tires and then we drive over them I don't know And We're gonna do that for you guys now. I don't know why My dad's saying I haven't seen this ever happen in Iran only in England. Okay, we don't know We drive over eggs as to be honest We kill the sheep We think is bad teams is going evil eye and then when you kill the sheep, what do you do and we give it to poor people? Yeah, they cook it and they give it all to poor people. No, they don't cook. Oh, they give them meat Just meat. They give it to poor people because if they are blessed with something we want to share all the That's so cute. Thank you. Where are we going? We're going for an ice cream wrenchy and she's lost her voice and she's still on ice cream No, I'm not having my mom and I have this looking. I don't need we had this last week. Look Maybe I lied so that we can have one Look at this Oh my god, what do you think? I knew you would like it We're on like a mini food tour because we've now picked up some hot dogs from the hamster butcher Oh Cool as that Food tour continues. We've come for lunch at Royal China in Baker Street This place has so many awards for all the food. I love the food here. Look at my hair, the wind What are you doing? You choose, for example, half a kilo of this prawn For the menu. Cookies look like this. We like the Chinese food. I love Chinese food So was really mean before because she was hungry I feel like this is becoming repressive in all my vlogs. In all my vlogs. So is hungry So she's mean No, you are mean at all Not my dad's room out his trip to China So if you want to commentate on the food So this is like aubergine, this one's like lemongrass Soldiers tried that amazing Another sort of buns Happy mom having soup He is always on the phone Chusha them I'm gonna make up a honey We're in South Bridges I go this is the department store our family likes the most we like it more than her It has everything and it's very close to transport link.  We need a name for you guys Tell us what you think in the comments This is the time where I hold his hand When I'm gonna walk him to Count as I'm again, this is the time when I hold your hand when I want to walk In the direction of everywhere I want to shop one makeup counter down She She beg all please just say She's gonna hit me if I put this They go just say what you just said I'm not So scared to say I Every time Sol talks my mom My dad only comes to my room because the hairdryer is here they're gonna name you So my dad feels awkward because he's treating his Favorite Turkish restaurant doodle if you're watching this he is sorry this is his first time coming here though and Me and my mom if you guys have watched other blogs, then you'd have seen we've come here before this place is called Using Yeah, and we always come here for like the breakfast, but it's currently almost one o'clock because we're gonna have it as brunch And it's like a Turkish breakfast, but I'll record it properly and show you guys what they have If you're in London, and you want to try good Turkish breakfast here does it this is in north London They have those chains and another face that does really good Turkish breakfast in central London It's for the amabache and James Street behind What is Iranian breakfast No, no sign guy. Oh, yeah, I can't approach it. I can't believe I said that I'm gonna scrap them There is really good Iranian breakfast. We need it in London and we have Jams everything that's very true traditional The food Oh So more of the story she thinks it's oily and it's not healthy But she's still here and she comes with China every single time Mom I love me these it's not Turkish Say again what do you like I love No, wait, what else do you like? between Turkish You like some such out and Hacker San and you like Noriko Vitalian he hasn't had the pizza But the pizza Yeah, definitely He likes to see food The table behind us is Iranian, by the way, but that way Okay, guys, if you guys are watching any other table, yeah, if you have a table behind us shout out to you guys Basically, we live in north London and north London is so densely populated with Iranians so many walking if you just hear it Wait Saina Saina said she's not coming home next week, so I sent her this meme I Have in my hand now you never want to hold my hand. I'm not holding my hand.  There was nothing that prompted it live and it's so hot You went to Istanbul Made them work very cold Really? but I came out very cold I'll back to hotel.  You like it? I like it You're happy that you cheated on the wrong? No You're about to have breakfast Yeah technically he didn't cheat Telling you the way I like it How I want it This is Milan, Zeppi in the dome I forget the name Duomo This is it This reminds me of Milan and Zeppi If there was one talent I wish I had It would be to be able to sing I feel like if I could sing I could use it like a mermaid So I could make booze pool and love it Would you sing it boy? I just sing the love song with my speaking voice I don't know about that guys I feel like Zeppi stop it I like this I wish we were in the city This one's so like Parents, due to you they gas up your confidence with that terrible I don't know what to say Literally with parents like this Who knew like Confidence from anywhere else Pada Kojain I want to sing in the city If you wanna be Me I swear No one's gonna watch my vlogs anymore They're gonna be like Suck it, it won't be Baby, there's a prize to pay Ah I'm gonna have a bite You guys like always do this Look So Dad Tell us something interesting about life About life Oh actually tell me the best book you've read My dad has a whole library in our house Maybe one day we'll show you Any books at least worth it to read it once Some books worth it to read it every day Which books do you read every day? Your life That was proper philosophical I'm reading a new book now guys It's called Think and Grow Rich It's very good, it's not like What it sounds like in the name It's pretty much like a I don't know how to explain it It's just a book about How to change your mindset And how changing your mindset will Get you everything you want in life And books like these is a bit similar to the secret It's similar to The power of positive thinking It's similar to that Which one? That makes your positive Yeah that's what I'm telling you This one's called Think and Grow Rich It's really good The power of positive thinking is written by a priest In the 60s that's also very good And the secret is like a fast track version of all these books The secret is new But it's not as good as these ones Because these ones like They go into it, like the secret Copied all of these ones in my opinion More into depth, the secret kind of just Took the best bits of all of these And kind of put it into an easier format into a book But it's really good to start you off On positive thinking books So If you want to be with me There's a price to pay Okay so we are going to end today's Well this weekend's vlog Right here I hope that you guys enjoyed it If you did then please give us a Thumbs up to Subscribe guys I want you to subscribe Can we have more subscribers just for me Please We would love you to subscribe We have so many YouTube family People that we love Can we just say a big thank you for The people who watch Nice comments Thank you guys And I want to give a shout out to all you people who Message me and send me cute videos I'm so sorry can we just give a shout out She really doesn't know how Instagram Works the other day She replied back to her own message Don't, she gets upset when you take The link out of her Don't know She loves you guys and she does And then I read some of her messages When I come over the weekends and then I tell her And then she starts And one of My youngest Followers I love you sweetie so much She always sends me videos of her on Instagram So thank you all so much for watching I think I should start doing a little shout out thing At the end of my video It's like whoever wants the shout out Let me know because I know some people might just Want to have a little private chat with me Which is why I keep it private but If you want a little shout out in the next video Let me know So Love you guys so so much Don't forget to check out my socials My Instagram is Persian Bunny Always link down below Ciao


We talk about the introduction of this course and in this module I will be talking about the topics covered, the books, the web resources, why this course, what is the approach of this course and about the instructor. So as you can see on your screen right now that there are quite a few topics over here and I will be covering the intro of all those topics in the subsequent modules and of course you are welcome to ask questions also. So you see that this is the division of all those topics and we have the search engine optimization over here. We also have the Amazon web services and I will also cover how and when to make the process of small businesses e-commerce websites on the internet. And you see now this is the breakdown of this course and you can see that quite a few modules are there on the introduction to the course. Then of course there are modules on the rapid application development, there are modules on the Amazon web services and when you have made all those wonderful things which is your web based database application, how to bring the visitors, how to bring the traffic to your web application source so that for this we need the search engine optimization. So I will cover this, how to bring the traffic to your website, how to bring customers so that those customers are converted into profit. Now these are the main textbooks which I will be covering in this course. The thing is that it is a very diverse course and it is a multi dimensional course, it is multi technology course and therefore it is very difficult to find a single book which covers all the topics which are translated into the modules. So these are some of the books, actually all of the books which I will be covering and within these books I will be covering some of the topics which are relevant for that particular book and you will be able to find most of these books on the internet. You can get those books and start reading and those topics which are covered. Now this is the list of the URLs, the web resources which are there which I will be covering and of course you can download these material, you can go through it, some of this is in PDF, some may not be in the PDF but in the course outline which is with you it is listed that which part of the material will be covering or will be coming from which part of the resource. So these are the reference materials which we will be showing. Now I just want to assure you that you are in safe hands and your instructor is quite qualified professionally and academically also and your instructor as a matter of fact have done lot of work in this area and the job portal of your instructor was regarded and which was ranked as the number one nationally competing against professional software houses. So I have the requisite academic background and I have the requisite professional background to add to your professional life, to add value to your career so you are in safe hands. Now why this course? The reason being that the world has evolved tremendously during the last couple of decades and there has been a large proliferation of the web based applications which are on the desktop and on the mobile phones also and web is global, web is everywhere and that global nature of the web makes you marketable globally, that's your market, your market is everywhere, it's not in a certain country, it's global market. Now when you are global it is not only e-commerce, there is information also, the products also, there are services also and you yourself is a product. So the approach of this course is to make yourself, to make your product, to make your service marketable globally so that you have the potential customers which are all along. Now let's look at some numbers, if you look at these numbers over here, there is a huge market of let's look at food in the UAE is 82% increase, is a tremendous increase. Now this is not about the companies which are making food items but the companies who are delivering food items, is a tremendous market. Now the thing is that you need to have web applications which have a backend database so that a customer can come to your web application to your website and make an order, make a selection and the more convenient it is for the customer, the more potential you have as a professional IT professional. The approach of this course, now the approach of this course is a hands on approach, the approach is not to look at dashboards and look at results but to get open the hood and get your hands dirty and use the tools to fix the things, to develop the things and of course as you make things, as you develop things, you will make some mistakes. That is fine because every mistake is a lesson so we as we proceed in this course I will tell you how to do things and you will make mistakes and we will do the coding also and you will see the results and it's a tremendous happiness when you see the results of your work coming in front of you. The approach of this course is a problem solving approach so I will identify the problem in front of you, I will tell you about the problem and then I will give you the background about the problem that what goes behind and what will come front and then I will give you a solution about the problem, we will discuss the solution, we will work on the solution and of course then you will know that this course has added value to your professional career and what will be coming in the subsequent modules is a brief introduction about the different topics which will be covered and that's about it.


Some residents of Delta State have charged Governor Sharif Aburavari to focus on infrastructural development, security, and to create more job opportunities across the 25 local government areas of the state. The residents have spoke with our correspondent, Akwema Jiro Friday, at the 60th birthday celebration of the governor in Assaba, the state capital, noted that a more important agenda for Governor Aburavari is to make an impact in Delta State. Infrastructural developments, let's be specific, human capital and security, these are the most important areas to mention. Pay attention to this, to the state, that the state will enjoy God's favor, God's grace, the way they never enjoyed before. All right, he's back. And if we look at the agenda, they are in general, it means not a great job, we are looking forward, they are looking forward for him to look great job. Why are you looking forward to him to impart his background on Delta State? Two of your beautiful kids, they are believing in him that working with him knows that he has the capacity and he has the fear of God to do the right thing for this state. He gave us a number of employees that we must employ, he gave us a number of capital and investment we must attract to this state, and as I speak, we are already looking at an investment giving him about $3 billion, $3 billion, we are going to talk to the African Development Bank, they are bringing some billions of dollars, the state is going to have a touch that they never had before.