Hi guys, yeah, I just went to this event in March. It's actually like three days conference, it's actually a two days conference and the last day is actually hackathon. So it's in Tokyo. It's actually the first time it has the hackathon. So they are giving like a lot of luxury prices like Nintendo Switch for the guys. And yeah, so I'm introducing myself. My name is Amy Xiong and I was software engineer in TigerSpike which is just around Tanjong Pagar. So yeah, so this is my contact and so just a brief introduction about TigerSpike. It's just we are actually a digital product company that we have user experience, user experience services and app and web company. So this is like emotion journey mapping for me throughout these three days. So you can see mostly it's actually a happy kind of emotions and so it's actually is a very fruitful experience for me. And the last time I'm sort of like brain dead because I've actually learned a lot of stuff. So yeah, and so actually before the two days conference, they actually have networking session. So they actually break, they actually like anyone can join to, they have an event that for you to walk to Observatory Tower for you to have like a networking session with all the developers. So you can actually use this chance to talk to everyone and like you know like different developers that are working of quite a lot of interesting kind of stuff. So this is the schedule mainly and you can see there's actually different talking duration. So if you can see there's a lightning, it usually is around five to 15 minutes of presentation. So and most and others around 20 to 40 minutes is a longest presentation. So that mostly all of them actually talking about their site projects and some SWIFT practices. And in this year I noticed there's quite that there are some machine learning VR and some object protection in the presentation which I find quite, it's like a different kind of thing that we normally do in a mobile environment or web kind of SWIFT stuff. So yeah, conference highlights, that's a disclaimer. I won't, I'm not going to repeat the whole presentation and I wouldn't, I didn't, I wouldn't be the best person to explain all of their awesome presentation. So I'm actually, I will only choose some presentation that I find interesting that I'm actually interested to know more that's why I do some research on it. And and that's for some, that's after this I will say I will actually show that there's some presentation that I also find it interesting but I doesn't have a chance to show it for today. So other than that I'll actually attach some Google's, some slides from them, the presenter's slide. So it's actually good for you guys to look at it, it's actually very, in very detailed information. So the first topic is cross-platform. So cross-platform, before this I thought cross-platform is more like a hybrid app which is, I don't really like to give, I mean before this I've had experience with all these Fungab, Fungab and some other platforms don't really work well with native. So, so I don't really have a pleasant experience with that. But so right now for cross-platform experience, there are two interesting presentation. One is actually Swift on Android which is, you try to plot the Swift into Android and build your own tools. It's actually about React Native. So Eric Wing is actually, he's not only an Android developer and also a Coco developer who actually, he has his own STK called Blur STK with another R. So he's giving a lot of opinions on how he actually developed his STK that must over some difficulty in porting the Swift to Android environment. So and Ota, he actually made the, he actually contributed a lot in Coco Ports for the previous five years. So he will actually talk about his experience on building React Native in React Native projects. So back to Swift on Android, main questions like, so do I, right now, do I, can I write Android in Swift? So sadly, it's actually, you know, it's, so to build Android in Swift we have to go through quite a lot of process on doing it. And so, and next slide is, so next slide is actually like, it's possible but it will be painfully inconvenient for you guys. So, so but the whole concept of Swift to build on and to use Swift on Android is the fundamental stuff that if you got a live, see, mix everything possible. So you have to kind of, by, by developing Swift on Android, you have to overcome some linkers, errors, which is, I'm not sure you can find a lot of people can answer you on Google or Stack Overflow. And you have to develop a method that interface the JNI, the Java interface. And in this case you have, you might need to resort to some hacks or code generation. So, so in this case, so I'll explain it on C. So, so you can imagine like C is like a building block for everything. So if on Swift can actually talk to C. So, and so if you got a library that you want to use it in Android, as long you actually must it, you can actually talk to it. So, and for the build system, libraries and language, you will see that you like, let's say UI kit is not really the like, it's actually considered the UI. It's not really like the language of the Swift. So mainly for Swift on Android, we're actually using Swift call for that. And build system, you will see like for like X code, build system, Android Studio and Visual Studio, which is actually way more different with each other. So language, the language will be the one that we use to standardize and to try to talk with each other. But I mean, because right now the platform vendors won't be actually, they won't really have an interest to build the platform that we can to let the language to communicate with each other. So, so yeah, you can try to use Swift package manager, Swift compiler, like X code, like how X code actually does and reproduce their commands. And from what Eric mentioned in his presentation, he actually mentioned like, actually quite pain and hard to scale as it's as you have to went through a lot of process to do them. So, so another, another way is a CMake, which I tried to know more about it to see. It's actually like a cross platform meta build system. So, so similar, like you need to list the file that you want to build in a text file. So, CMake will actually like create a native project for it like, like a Visual Studio and X code and make files. So in his blur SDK, he handle the build system and challenge using the CMake inside his SDK and provide like, provide convenience of deployment ready prebuilt libraries for, for, for us to use. So, so Eric actually, Eric Wing actually produced, he actually released his beta version of blur SDK and he actually demo his gaming, demo his flappy bird in iOS and Android by using his SDK and yeah. And for the, so for the libraries in writing in Android. So, so you can see right now there's a native and you can, you can actually, you can speed as three categories. So native Android only development or cross platform development like the non-native GUI, but it's usually common to be used in video games. And if it's actually C library against, again, you can use it in Swift and cross platform native GUI. So he actually suggested IUP, which is possible user interface that to help you to develop Swift on Android more easily. So, so move to react native, which is before this, like I said, I, I have, I heard about it. I know it's actually, it's actually a JavaScript, you write like JavaScript syntax, but I'm not, I don't really have the idea of playing with it for mobile development. So after hearing, after, after auto share his experience by moving away from Swift, and typically it's actually native code. So he, he decided to move away because he found like the effort for, for two hours and junior and not the effort of fixing and developing and not to be the same for one web engineer. So they are, they are team actually decided to give react native a shot. So, so he, he goes to explain quite a lot of the development pattern and they end up choosing react native at that stage because they find it, there's react native is still a development, is still on their development phase. So there's still quite a lot of improvement. So to explain what is react native, react, react is like, it's actually a Facebook project that they actually offer a single direction component model, which is you data can only flow, flow down. So that can replace the whole MVC set in front of, in front end application. So, so react native is like the implementation of react where instead of having abstract web page, so web page doms, it creates a native view hierarchy. And so do note that, do note that react native does not includes view controllers. So it's like a MVC model from Apple Coco framework that doesn't directly map into the react native. You need to write JavaScript, which is react native that interact with a view hierarchy. And it doesn't, and, and it's, it doesn't like transform your JavaScript into native code straight away. So, so to, so yeah, react native is a cross platform. And it, so you can actually build it in the Samsung TV, Windows 4, Android 4, or even a web page in react native. So I, I haven't really have a time. I mean, I'm actually going through some react, I'm actually trying to learn react native right now to know, to try to play around the ideas of doing some better project by using react native. I think I will show it up on GitHub later. So next topic, I'm home, I'm not, I hope I'm not too fast. Next topic is actually at transport security. So the presenter is actually a Japanese called, I mean, the hand is called Niwa Tako. So in, in Tricep Tokyo presenter can choose to present in Japanese or English. So when let's say if the presenter present presented their presentation in Japanese, we will have a live, a live translation. So a live translation. So you have to like listen to it. And it's not necessary 100% accurate, but it's actually good enough for us to understand what they mean. So at transport security is actually Apple implemented and forced it to improve the privacy and data integrity to ensure that your app network connection is following industrial, industry standard protocols. So it will, it will protect the user that the protect the user to trust your app that does not accidentally leak information, information to malicious party. So, so yeah, this is one of the topic that when I talk to different developers, they see like what kind of topic that you that you find interesting throughout the first day or second day, this is one of the topic that most of the people actually quite interested. So that's right. And so last year, I buy right Apple and force that we should actually, when we submit all the app to the app store, we should have enforced the ATS, the app transport security. If not, they will actually reject it. But last year, December 21st, they actually like say, they're going to delay it until when they until the next announced. So yeah, but it's actually it's actually good to implement as early as possible. And then our stand, this is the three, three variables that that Apple provide in our newly introduced it in our stand. So I will be kind of this like the proper explanation from the Apple website. So it's actually it's actually ensured that if it if you set it to yes, it's ensured that your media will actually has been if you say it to yes, means you actually do. You actually doesn't really follow the the ATS standard. So it's a key. You say, Oh, it's actually safe to use it. But even though it doesn't really follow the ATS standard. So this is for media. And this is quite similar. But this is for web content, which is like our web view. And it's usually we use it for our embedded browser. So you will actually encounter this problem. Let's say you are actually your web view actually connected to some HTTP website. So you will end up having a failed connection or some error connection. So so the next one and that's a lot local networking is actually a lot is actually more usually use it in for the intranet. So so do note that if you set or I mean, if you set the key to yes, you will need to justify to app stores that why do we need to set it to yes? Why are you not following the proper standard app transport security? So I showed a graph. This is one of the slide from the presentation. And so normally for HTTP web, web view, and this is WK web view, and you and UI web view and NS session. So normally on HTTP, it can it still can go through right now for but for ATS unsafe HTTPS, it won't. It will actually block the user from connecting to it. So for safe HTTPS, of course, it will be if it's okay to go through. And but unfortunately, in 10.2, there's kind of like a bug that even though by right for unsafe HTTPS, they shouldn't. So they are not, they can't really connect it to the they are not allowed to connect it. So it's considered a bug in 10.2 in for the for the web content. And say let's say for different combination of ATS in hours nine and 10, you have behaved differently. And from what I checked, get it from online, there's a source that he tried to compile it may make a clear statement. Like if let's say you're in hours nine, and you're asked in hours nine, and hours 10, if you are setting like one of the flag to yes or no, work out in that view, will it be allowed? Or it or in the URL session, whether in hours nine, is it is it allowed in 10 or nine? So this is like a guide for if one of you want, I mean, if the app actually need to connect to hours nine and 10. All right. So what's like three? And it's actually one of the topics. There's, there are actually quite a few presenter present on this, but I choose Yuzuki Ito. And he he presented his presentation actually tried to like persuade like why Swift, but because usually for server server, we use Python Ruby. And Swift is not really a common language that come into mind when you want to develop for server. So but why Swift? Because Swift is considered a safe language. So you you have types protocol associated that it will actually helps you to code safely. So and you have an X code that you actually help you to have, you can have the breakpoints for you to debug. So and in his project, he showed the back end service with Swift, which is actually by using Swift, we can claw crawl the website. So I crawled a website content by using Swift. And another project, another his personal project, he's actually used Swift that works with Raspberry Pi that to, it's actually the program air pressure sensor that runs every hour. And it will use the HTTPS post to publish the result to that by using the API. So which is one of the I find quite and you can one of the use case that you can play around. So there actually see like what kind of what kind of server Swift framework that that has in the market. And I find this tree is perfect is considered the most popular one considering the the stars. Yeah, so perfect. And it's actually from IBM. And vapor, I mean, all is actually open source. But kitchen, there's a IBM provide IBM, IBM actively support kitchen for Swift. So they even gave a presentation in 2016 on the topic of going server side with Swift open source. And so which they are using the IBM inquiry, a start company called strong loop, which is actually the maintainer of ExpressJS, which explain why the syntax in kitchen is somewhat similar to ExpressJS, which is if you if you don't know ExpressJS is one of the one of the routing language in for server. So they have free trial for 30 days for Kittura. And so I decided to try out the sample. It's just like a normal setup thing. It's not really hard to set up, which is quite a pleasant if it's not really intimidating. And the documentation so far is quite clear. So the last time I checked is actually they have 9,000 stars, well documented and syntax is also quite similar to ExpressJS. So in here, the every Swift project actually use the Swift package manager. So they will have a package JSON, mean Swift file. So so yeah, it's actually it's actually quite it's simple to set up and I find quite a lot of tutorials online to for me to get get my hands on server Swift on vapor. So yeah, this is also one of the my site projects on server side. So I've got quite a lot of pending stuff. So perfect is perfect the most. So it got 11,000 stars. And it aims to be the rails for Swift.  We shouldn't, I guess. So usually, I find it's quite easy for you to deploy your web to Heroku. So you can like take your code, initialize it to get rapport, and just push it to Heroku. And it will actually detect what type of application that you have. They will compile it. And so if, if, so if let's say Kerakor cannot automatically detect Swift, you can set a custom build pack that that help you to detect, I mean, like detect, build and run the project. So potting library to Swift. He actually like kind of say it's quite easy to pot library to Swift. So you just need to find a C base library, rabbit it with Swift, rug it into more Swifty way. And let's say, Libcur, Libxml, MySQL connector, kind of thing. So you can try your hands-on on like batch programs, API server, in how, in how deployment tools, command line, just script, script it with Swift. So another really simple casting that I tried my hands on.  So it's just like, it's nothing difficult. It doesn't, doesn't look really daunting. It looks very scary to me. Like, so I, that's why it's actually encouraged me to dig more, to do an explore more in server sites with. So yeah, I think I repeat my thoughts. So yeah, it's quite, I will actually continue my site project in server Swift. And testing, one of the testing presentation that I like in is actually making more objects more useful from John, from John, he actually, he's working for American Express. So he got like a few mock recommendation for testing. So usually we, when we create unit test, when we carry create unit test, we need to test whether this function has been run or not. We actually use Boolean. But he said, it's not really recommended to use Boolean. What if it actually run twice or three times? So it will actually like, let's say it might be actually set it to from true to false and back it to true.  So it's best to use integer instead of Boolean. And he, he introduced, he actually provide a code out in my, in my, in my, in my slides later, I will provide a code project from him that he actually used the file line to assert in the half a class. And he, I mean, he recommended this message for all the assert test, which is quite obvious because you might end up doesn't know what's the unit test is about. Maybe a few months later. And he said, to make your unit test less fragile, you should try to use, you should use predicate instead of equi, equility. So it's like, so predicate, let's say, I will, I would show an example later. So in, in this presentation is actually using a GitHub, I mean, a library called hand plus matches. And, yeah, so this is the sample for the file line. So why, why, why, why we need to use file line is because let's say if we actually do a mock, mock, this is the test, this is the testing that whether the order the right thing and the code actually code the right thing. So we try to make a false unit test, I mean, try to fill the unit test by saying by right, they should code, they shouldn't code three, three bowls of, three bowls of, three bowls of ramen. So when it failed, the error went back to the helper class, which is, let's say if you have a lot of unit tests that actually, that actually came up from, actually use this helper class, you might, I mean, all the arrow actually end up pointing to helper class and you doesn't know which unit, you can't know it right away that which test cases failed. So that's why by using file, file line, it will direct it back to the field test case. So you will know which test cases failed instead of the helper class. And yeah, so for the predicate handcraft matches are it actually has a lot of other language is it can it can be available in Java, Python Ruby, obviously, and I think there's recent, recent one is Swift. So, so yeah, this is the GitHub. And you can see the by using by, he recommended to use the predicate is by the, let's say, let's say the both, it doesn't need to be two, you can, if it's greater than two, greater than or equal to two is considered past, and you can straight away pass the test, it doesn't need to be equal straight away, if not, it's actually quite fragile. And let's say a contains in any orders, have prefix of Thomas before this actually Thomas go and yeah, have suffix prefix contain any orders or anything for a soup will pass it. So yeah, predicate. So and after this, I actually went on looking for some see if there's more testing frameworks or testing library, I found like nimble is having predicates and matches for this as well. So so I and actually more developers than I know use nimble. So yeah. And this is kind of like improve user engagement is actually I choose this because I find some, some designers like doesn't know the full potential of hours. So let's say they're don't really use much call spotlights or user activities where markup 3d touch.  Let's say it helps the user to find the items more quickly, find the items quickly. And let's say for call spotlights, actually it did the app search searchable on the spotlights. And for user activities, it actually saw the app state and restore and to restore it at a later time. But Markup is quite Markup is considered one of the common common in app feature and 3d touch to for building an application in 3d touch, not only the outside at the outside, but also you can use it inside the app that you can straight away navigate to the detail page. So this is like one of the things that you can suggest it to your fellow designer in your company. Yep. And app formatting is quite so right now we our company is trying to move away from storyboards if we can. So we are trying to code everything. We try to code things in in programmatically. And so to to code things in to be more organized, because like try to do it in the styling. So it's like we have a let's say we have a primary button, negative button. So you just set what kind of the style for primary button should be in ABC medium form. And the title should be invite. So you actually have a customer. So what if in the future that you designer decided like all the buttons should change colors, change pad, change padding or change with or something, you can you can go back to the one you can go back to one file and change it. And it doesn't need to go back to all the storyboards to change it. It will be really painful. So this is how we use it for I mean, use it when we call it. So you can it's actually quite straightforward that you just apply it just have your UI button and apply the primary style to the button. So not that difficult for this is like one of the rugged to be more 50 way file organization. So sometimes we used to organize the file into like there's a view model. There's a view model and there's a view controller. So you sometimes the view model is inside the view controller. So and sometimes when you have a screen, you have a feature that actually share among all the screen. So it doesn't know where to put the file actually. So in one of the presenter actually suggested to categorize it in application components and UI. So application will be like the base stuff like all the delicate stuff in long screen storyboards. So the components will be like, yeah, components will be like authentication comments, which is like things that will be used across the UI. So you I will be all the view controllers and protocol for this for the screen. And okay, so topics that I wish I can cover it today, but I can't. So you can look it up from the link that later I will be sharing up for for all the slide. It has all the the site is quite detailed. So when you read the slide, you will understand it. And that's actually at the realm realm website that she start releasing a lot of the records for that day. So you can actually take a look at it as well. All right, take away, take away from price with Tokyo, not only about technical stuff for three days, which is quite tiring for me. So it's actually quite a joyful experience. So if you let's I would really like to encourage if you got a chance, you should go to more conference overseas. You just talk to different people. And they actually coming I met with a random guy during the networking session. And he actually he was one of the presenter on the first day. And he says working for a genetic company thing to genetic company. So so yeah, it's actually quite fun to know about other company processes, how they do their testing, how they carry carry out their scrum, their agile, and their side project like all these object detection, accessibility or like inclusive design. And she quick just quite fun. It's just different from your normal days of commercial mobile project. So yeah, so after this Swift Tokyo, when you see like different people present, that's why it actually encouraged me to come back and try to present hopefully it's not really a bad presentation. So yeah, so so I joined the hackathon halfway. So so I believe next year they will still have that hackathon and workshop like Eric from the Swift on Android, he actually provide a workshop. So you can if you don't want to join hackathon, you can join workshops. And yeah, it's actually have a chance to introduce TigerSpike to other developers. So yeah, this is the slides link. And you can download it. I zip it up and zip it all things all the things together. So that's it. Thank you.


From around the globe, it's theCUBE with digital coverage of VeeamON 2020. Brought to you by Veeam. Hi everybody, welcome back to VeeamON 2020. My name is Dave Vellante and you're watching theCUBE's coverage of VeeamON. This is the first time we've done virtual VeeamON and we've got the Veeam power panel, Bill Largent CEO, Jim Krueger, the CMO, Danny Allen who's the CTO and Senior Vice President of Product Strategy all have been on earlier. Guys, great to see you. Thanks for coming back and digging out of the power panel. Appreciate it. Great. Thank you Dave. Glad to be here. Thank you. Okay, I want to start off, Bill. You get a business update. You know, we've sort of talked a lot about COVID. We can go back to that. But you guys, you know, as a private company, you divulge more information than most private companies and we appreciate that as an independent.   Everything seems to be happening, Bill. What can you tell us? Well, we had a great first quarter also that we kicked off where we had our transaction with Insight Venture Partners, which, you know, right in the middle of that quarter at the end of it, we had that activity that went on. That one might think would have disrupted the business that didn't. We had our plan for Q1, really excited about that. We announced our growth. Saw that here recently. We really pumped into our second quarter. We managed to transition everybody out of offices. We probably add 70% of our workforce, 75% of our workforce need to move. They did that. We had a fantastic April. We're having a very good May. So it's just a great start with a great customer base. So really excited about it. Yeah, you mentioned Insight. We obviously covered that and reported on that. Insight, they like growth.  They want growth. They want options down the road, optionality. Maybe it's a rule of 40, rule of, you know, the type of company. So that's got to be exciting for you guys and your employees. Yeah, I think it's pretty exciting. We've been around, a few of us have been around the Insight team since 2002. So a very well-known group of individuals to us. They are focused in the software space. They know the infrastructure space really well. My triple at our lead on the Insight team and his staff has helped us move into Act 2 or as we move into Act 2 and stepping up and moving into our annual recurring revenue focus versus more of a total contract value focus. But nice resource to have for things that we might want to do in the future related acquisitions. So we're really excited about it. I mean, if I'm in VC right now, I'm looking at SaaS. I'm looking at software. I'm looking for companies that have an annual recurring revenue model. I'm looking for adoption of products and those kind of KPIs. You guys fit that bill, maybe a larger size than obviously the early stage startup. But that's kind of the profile of the company that you want to invest in in the 2020s, isn't it? Absolutely. And I'd also say it's the kind of company we want to invest in in the futures. We go forward to bring in new technologies to expand market, progressable marketplace. Back to comments, we had discussions on it. What's it look like in 2030? And it's like, those are the places we're heading from. So, Danny, Pat Gelsinger's famous on theCUBE for saying that, look, if you don't ride the waves, it's going to become driftwood. So what are the mega trends that you guys are riding today and that you're seeing in the future that will keep you ahead of the pack? Well, we clearly talk a lot about cloud data management. So Act 2 for us is not just moving from perpetual licensing to subscription and evolving with the market at a business level. It's also at a technical level. And so we invested heavily, as you know, we demoed earlier today, Veeam Backup Propfist 365 version five. An important point, Act 2 for us is not just product. It's also product delivery. That's version five of a release of a product that came out three years ago. So Veeam Backup Propfist 365, we showed you Veeam Backup for AWS and you saw from Anton as well, supporting Google cloud storage and supporting all of the major cloud providers. So for us to not just ride the wave, but actually be ahead of everyone else, it's to embrace cloud data management and give the customers what they really need. Well, I think you guys are in a unique position too. I mean, you know, if you guys obviously sell on-prem, but if you're an on-prem infrastructure company that's really living on box margins, you know, you could talk the cloud talk, but it's not necessarily a tailwind for you guys. So Danny, how is cloud, explain how cloud is a tailwind for Veeam, you know, versus some of the other legacy players? Well, Veeam has always been, we always highlight simple, flexible, reliable, but one of the parts of flexible of course is being software defined. And we've been software defined from the very beginning. And if you're in a world where you have to go, take a box, plug it into the data center and rack and stack it and do, you know, be there physically, you're not going to survive in this type of environment. So being software defined helped us, not only win the data center, but to help our customers as they go through that evolution from on-prem to maybe just storing backups in the cloud to actually running their workloads in the cloud and protecting them there. So Jim, I want to turn it to you, sort of thinking about the Veeam brand. We talked earlier about how you guys have always punched above your weight, famous parties and so forth, but now you're a billion dollars now entering a new era, not, it's ironic that we're now doing virtual events, so no big giant party this year, but I feel like you guys are what, 14 year old company now and kind of grown up. You three and your colleagues are bringing, you know, lots of adult supervision. How should we think about the Veeam on or Veeam brand going forward? Yeah, I think the Veeam brand is critically important because there's just such a strong affinity and connection with customers. And I think one of the challenges as you get larger and go from one billion to two billion, a lot of companies miss the beat relative to staying connected to their customers. And that's something that we're putting a tremendous amount of focus on.  I think our key to success is not only bringing great products to market, but looking at the holistic picture relative to supporting customers and customer satisfaction, which is a key driver of the company, will help us to continue to build on the brands and have, you know, the best brand in the market. Well, I want to come back to you as the marketing whiz and the panel. I mean, you think about digital, we feel like the war is going to be won in digital in the next decade. I take the GNC example and you think about just even the term like customer relationship management, you know, we all use CRM systems, but I'm not sure I want a relationship with GNC, but I do know this, I want a good deal, right? If they're going to make me an offer, I'm going to look at that and these other brands and that's digital. That is having infrastructure and data that's obviously protected to be able to offer that at the right time for the right customer so that they can take advantage of it and have the right panels. I wonder if you could talk about what you see as a marketing pro, just in terms of digital and that customer intimacy. Yeah, yeah, so I think it's multifaceted. I think one of the key things that again, Veeam does that's different than other companies is that we have a direct connection with our customers. So, you know, our head of product management sends out an update every Sunday and goes into, you know, quite a bit of detail around sort of how to deploy this, how to deploy that and really creating a digital journey for the customer from a marketing perspective because yeah, like in any situation, you know, you don't want to talk to a salesperson right off the bat because you know they're going to try to sell you. So, you want to do some investigation. You need the content and information to help you move along that journey until you get to the point where, okay, now it's time. I've kind of narrowed it down and I need to talk to someone to give me some more information. So, I look at, you know, one of the key differentiators of Veeam is that digital prowess, which I think from the founding of the company that Ratner put into place, you know, it's carried us forward and we continue to put a lot of focus on that digital experience, which I think gives us definitely a leg up on the competition.  I'm interested in where you're placing Betz.  You've got some big name partners that are, you're moving a lot of product, you know, through those guys. Obviously, your heritage as a company is steep in technical development. You are a very successful sales organization, but so where are you placing your chips on the table these days and maybe, especially in the context of this pandemic, if anything has changed in your thinking? Yeah, well, the Betz will always be placed on the product side of it.  What are we doing on the partner side? We're continuing a pretty aggressive activity and making sure these partners have a simpler place as I've discussed before to do business with that gets more challenging the larger we get, but yeah, we'll keep that focus on it. The product offering has been, again, always go back to any of our taglines that just work, put us in the lab, we're gonna win, we're gonna win that technical decision process. And then we're putting pretty big bets on our employee base. We're all over the world, 4,300. I think the decisions we have, like a lot of companies have moving forward are gonna be, where are you gonna work from? Are you gonna work from that home office?  Or are you gonna not?  I don't think that's going to happen at all. So our bets will always be on bringing good product to marketplace, good technical decisions. So let's talk, Danny, about the product.    The answer to that would be focus, maniacal focus. So it's interesting that you brought up licensing. So one of the things that we're very focused on is making sure that licensing can move across all these different types of infrastructures. So, you know, Veeam Universal License allows you to do that, move a workload from physical to virtual to cloud, to back to application services, all with a single license. But we also do that at a product level too. One of the interesting things that we've been focused on is something internally, we call it the Veeam integration platform, that enables you to have a central, common control plane across the entire organization. But yet you can deploy in the native environments that make the most sense. So if you think about what we showed you earlier today with Veeam Backup for AWS, you're running on an interface that you deploy out of the AWS marketplace, but that product actually integrates back into Veeam Availability Suite. And so that's true of Veeam Backup for AWS, Veeam Backup for Azure, Veeam Backup for Nutanix. Every time we add a new capability across the platform, whether it's SaaS or virtual or cloud, we make sure that it still has that central connection to the main control plane. And that's why we call this cloud data management because it gives you that data management across all of these different infrastructures. It's clearly not easy to do, but the focus that we put on this results in our customers success ultimately. So I want to ask you guys about culture, Jim, I'll start with you. I mean, a lot of people, obviously, I'm sure you've heard it or asked you, is Veeam still going to have parties? You got your two founders who sort of set the notion of the culture, you know, Ratmir would always be right there in the mix, last one to leave, very hard charging. And that's kind of steep in the Veeam culture, but I'm interested in if there's been any sort of discernible change as you get bigger and bigger, how you're able to maintain that culture. You know, what are some of the things that you want to keep? And maybe some of the things that you want to evolve. Yeah, great question. And I think culture is, I'm a big believer that culture can really differentiate a company in the marketplace. And I think Veeam's culture in the past has really done that effectively. And I think that's, you know, it shows in the success of the company. So I definitely see it as, you know, as my job along with the rest of the executive team to continue to carry that torch forward.  And so that can be anything from a party, being totally open to your customers, listening to your customers, giving them different channels to give you feedback. And just being a company that's easy to do business with, I think is critically important. And those are some of the key things from a cultural perspective that we want to carry forward. You mentioned hard charging, absolutely being aggressive in the marketplace, bringing solutions to market that really hit the sweet spot relative to customer need, I think is again, one of the cultural pieces and that maniacal focus on customer satisfaction, which is absolutely key. So, well, I wonder, Bill, if you could comment, and maybe in this contact, you know, part of your job, of course, is TAM expansion. You've traditionally been a European based company, you're moving HQ to the US. Curious as to what effect that will have, both culturally and on TAM as well, you're extremely successful in overseas. Of course, so there's maybe even more penetration within the US. And obviously, you know, throughout the globe, we've certainly talked a lot about cloud, but maybe your thoughts on those points. Yeah, thanks very much. Well, really hopefully you see no impact on culture in a sense of our move from European headquarters to a US headquarters. We definitely felt it important to bring a US headquarters in place. We, you know, now have moved all US shareholders. So it's really critical. Our culture is really built on core values that we developed back in 2012 that really everything else branches off of. It's about product innovate and iterate. It's about everybody's sales. We clearly have that goal for everyone in the company and in the fact that we also want to win. So we'll fight hard to win. Bringing it to the US, you know, a lot of our competitors are based in the US. We think we can put up a, even though we've got great numbers against all of our competitors, we'll even bring the fight much harder now that we're in the United States as a headquarter place, but change nothing else internationally. Global focus. So Danny, every aisle of five or seven years or so, you know, Gartner, IDC, whoever put the other service, is that we just did a survey that X% of the customers are going to rethink their backup strategies in the next 24 months. You see that literally every half a decade. So, you know, what's the driving that now? I mean, certainly cloud is a huge factor. Edge, we're going to be talking to edge for the next many, many years. And then it's really going to start to drive revenue at some point, kind of like the cloud was 10 years ago. But so talk about how you guys sort of stay relevant in that conversation and what customers should be thinking about in terms of those transitions.  But the reality is what's happened is the industry itself goes through transition. So we go from physical to virtual and as they go to virtual, for example, they say, hey, I can't use my legacy provider. So I'm going to choose a new one and they choose Veeam. And then of course we go to cloud and we're going to go to containers and we're going to go to edge. And every time we go through those iterations, there is an opportunity for the next generation of platform to emerge. And so Veeam's focus here is to make sure that we're ahead of those trends to make sure we're thinking ahead of our customers. So right now, for example, you know, I spend an inordinate amount of time thinking about cloud and containers so that when the customer gets there, when they get to edge, when they get to all of these things, that they have a data management platforms that protects them. And step one is always going to be the same. I always say the step one for every iteration of infrastructure is just ingest the data because you need to protect it. It's only after you protect it and begin to manage it, be integrated into the business, can you begin to unleash it? But we go through this cycle over and over again. And ultimately it's the vendor, it's the partner that is most trusted that wins. And as Jim alluded to, our NPS scores speak for themselves. Our customer base speaks for itself. Our intimacy with the customer speaks for itself. And so as long as we keep that close connection, then we think we're well positioned to lead as we go through the next iteration of infrastructure. Okay, let's talk about the competition. Danny, let's stay with you. You know, you've got some well funded, not even startups anymore, but companies that are kind of going after the base, you've got a huge install base of legacy companies. I mean, I think it's easier for some of those guys to attack sort of a box-based solution. You guys are more software, but I'm sort of interested in your take, Danny, on why Veeam, how you compete with the shiny new toys and that obviously have momentum in the marketplace. Yeah, you know, the shiny new toys, they come out with a solution that is very packaged up and black box. You can't actually customize it very much for the user need. We don't believe that that's going to work in the longterm. And the reason I say that, look the pandemic we're in, if you can't go into the data center to rack and stack a box, if you can't actually work with the infrastructure that's already in place, then you're not positioned to work well in the longterm. And so we have this unfair advantage. We've been around for over a decade. We integrate with over 45 different storage vendors. That's not including the cloud vendors and all of our partners. And so we do have an unfair advantage with the history of all of these integrations. But that flexibility is really what our customers need. They don't want to be locked into the data center. They don't know two, three years from now, the strategy might change. They might say, take the workload, move it to the cloud. And so if your whole focus is on selling your customers something that ties them to their data center, that in itself is a challenge. And being software defined, we're well positioned to make them future proof for any evolutions that happen in the marketplace. So we're in a good place and we'll knock on wood that I think we're going to keep going. Yeah, that's an interesting answer, Danny. And not one that I expected, but it kind of makes sense in the context of a Q and A we had with Andy Jassy in the CUBE a while ago. And I was kind of pushing him on the zillion APIs. And he basically had a similar answer. Obviously cloud services is different, but essentially saying, we don't know where the market's going. So we want to have very granular control at kind of a primitive level. So we have that flexibility. And maybe there's a trade-off sometimes just in terms of what you called out of the box. But it's a very Andy Jassy like answer that strikes me. Well, it's certainly true that the, customers don't know a year from now, they've been using that hardware, but a year from now, two years from now, we run into another market impediment. They might want that money back. They might want flexibility to expand into a different geography or take advantage of the elasticity of the cloud and buying a piece of hardware. Just the very fact that you buy hardware, that essentially ties you into that hardware the next at least three years probably. Being software defined, you can continue to reuse and leverage all the assets that you already have without committing to a lock-in for the next period of time. So from a marketing standpoint, Jim, strategy, brand, customer intimacy, what, why Veeam, what you're in? Well, and Danny already talked a little bit about it in terms of kind of the three cornerstones of how we think our simplicity, flexibility and reliability. And as Bill talked about, when we get into a customer and if they're testing us out, trialing us out, nine times out of 10, we're going to win because they see those three key things and those three key things we hear on a daily basis from our customers of how important that is. We continue to build out on each of those. The challenge is keeping it simple and that's an area that we have to continue to focus on. But I think those are the key differentiators for us going forward. I think the flexibility piece is the integration with all the storage, our ecosystem of partners. We have, I think close to 40 partners that are sponsoring Veeam on here. So that's a key differentiator because we work across basically everybody who are agnostic. And again, just easy to do business with and a true partner. I got one more question for Danny and then I want to ask Bill to close, but guys, feel free to chime in on this one as well. But some of the things we haven't talked about much, Danny, containers, protecting containers, the edge. These are all sort of emerging opportunities. I know you've got some partners on the container side. The edge is early days, but there's whole new models of computing. Potentially a lot of data going to be created unclear how much is going to have to be persisted, but certainly with that much data, the IDC forecasts, a lot of us going to have to be protected. So your thoughts on some of those other emerging trends that we haven't talked about? Well, the key to this segment of the market, our partners trust us. We're thinking about this ahead of when they will actually need it. And you're right, I think we're early days in containers. I think we're early days in edge. We don't know, you know, we have a partner Ducks Unlimited where they're storing data for 60 years, use it from IoT sensors and they keep it for 60 years because they don't know in the future if that data is going to be relevant. And so our focus is to make sure that we're ahead of our customer base in terms of thinking of it and then making sure that our platform supports what they need as they need it. But you'll want to be careful about going too far in advance.  We're very pragmatic. We want to make sure that the problems that we're addressing that our platform fundamentally addresses where they are today and then also be in those discussions with them about where they're going to be tomorrow. Well, maybe some of that magic pixie dust will go into the COVID vaccine. That would be good. They'll bring us home. So, you know, the virtual forklifts are breaking down Veeamon 2020. What are the big takeaways from your first Veeamon as CEO? We've been to many, you know, I know, but what are the big takeaways as the virtual trucks are pulling away? Thanks very much for asking that question. We, you know, we did do our first Veeamon in 2014 and I can still remember when Ratmir came to me and said, let's do this. It's like, oh, you're going to get me. This is going to cost a fortune. Why would we ever? And then he's obviously right, continues to be right. So, hey, the story about Veeam is growth. When you're growing, you've got funds available. People interested you to innovate. You mentioned containers, Danny did also, and Kubernetes and, you know, we've got our friends at Casting that are here with us. Now, those are all important relationships and will continue to develop relationships that are like this. But why Veeam, what we've supported, we've got great customer support. We have a growth engine. We're going to continue that. We don't plan on being comfortable with where we are. We'll continue to enter and go after an additional TAM, but we'll also take care of that core base we came from. So really excited about where we've done. We had a lot of great breakout sessions. I keep, you know, Kubernetes was on, there's a lot of great ones. I did like the one though, and it was like falling in love with tape all over again. So when I first saw that, they brought that to my attention. It's like, ah, I went running for my eight track tapes and my John Fogarty and CCR, I found one. So I had to get readjusted to, ah, that's not what they mean. So in any event, I do think, we like to have a lot of fun. You'll see that. We get back to a, see where we go as far as a virtual versus an onsite V-mon in the future. We plan an onsite one. And if so, you'll, and you're there, you'll, you'll, we'll be at the party. Yeah, indeed. And I, but I do think there's going to be some learnings that we carry forward. And you know, I think for a while and maybe even for quite a long time there'll be some kind of hybrid going on. We just seem to live in a hybrid world. Guys, thanks so much for coming to theCUBE and making this a successful power panel. It was really a pleasure having you. Great. Thanks for having us. Thanks. Thank you. And thank you for watching everybody. This is Dave Vellante for theCUBE. Keep it right there. Our tenuous coverage of V-mon 2020. We're right back.


All right, our first question is from JJD101717. What is the relationship between strength and endurance? Are they inversely related? Would it be possible to train both? Yeah, great question. Not inversely though. Somewhat, there's somewhat, here's why. They're conflicting goals. They can be, and here's why. So think to yourself what kind of physical adaptations would occur to maximize strength versus the types of physical adaptations that would need to occur for endurance and compare the two. So let's talk about strength for a second. For strength, you're gonna want a central nervous system that fires forcefully and completely. So it's the CNS is like the electrical outlet. Like you plug it in, you get the juice. Boom, you want good strong juice coming out. Quick and hard. Quick and hard from the CNS to give you lots of strength or just a good solid signal. As far as the physical adaptations, bigger muscle fibers contract harder. So you're gonna want bigger muscles. This is why training for strength produces bigger muscles than training for endurance. You don't need to worry so much about energy efficiency because, or- There's even bursts. Yeah, you're not- Short bursts. Yeah, you're not doing strength for long, long periods of time. Although you are improving your energy efficiency when it comes to the short bursts, your body will learn to produce the fast types of energy faster, like ATP, right? ATP is that explosive energy. So your body will become more efficient at producing that. You may, your body may be able to store more ATP as you train for strength. That also means your muscle fibers get bigger. So overall, bigger muscles, louder central nervous system signal, those are the adaptations. Now let's go to endurance. For endurance, you need a muscle that can contract not very forcefully, but one that can contract for long periods of time. You need energy efficiency in the term of, in terms of the type of energy that you're gonna be using for that type of contraction, which is glycogen and fatty acids. A big muscle, not a good thing. A big muscle, just like an engine for a car, a bigger engine will produce more power, but will also use up more energy and gas. So for endurance, you want smaller muscles. It'll be economical. Yeah, you want smaller muscles that are energy efficient that can contract not forcefully, but consistently over long periods of time. Now that being said, it doesn't mean that these both don't also contribute to each other. Sure, absolutely. You can train just for endurance and actually get some strength. And you can train just for strength and get some endurance. So it's not, that's what I meant by, I don't think inversely related is. If you push them to the extremes they are though, right? If I'm pushing strength to the absolute max extreme, then if I train for endurance, I'll probably take away some strength and vice versa. So that's where they become. And so here's the thing with the body. The body has to make a compromise. So if you're asking your body for all these different types of adaptations and the way you ask your body is through your workouts, through your workouts and lifestyle and diet, you're sending the signal, this is what I want. I want more strength. I want more endurance. I want more whatever. When you're sending your body all these different signals, your body has to make a compromise. I need a car that is both explosive off the line zero to 60, but I also need a car that can travel for 1,000 miles without having to get a new tank of gas. What you're gonna get is something in the middle. Right, yeah. You know what I'm saying? This is why, when I recommend how to train this way, I typically want to nail down the person to give me one of them a little bit more important than the other. So I wanna get that from them. Like if you said it, you're like, oh, I want both. Okay, that's okay. We can agree that we want both, but is there one that's a little more important than the other for you? And then we're going to prioritize your programming that way. So, and the split's gonna look something like this where 60% of your training is focused on one, at least 60 to 70% is focused on one and then the other 30%. So if we were to look at like days, it would be three days, if I cared about strength more than anything else, three days a week, I am training strength focus and then maybe one or two days a week, I'm incorporating some sort of endurance training in there. Yeah, and this is too, like when I start looking into different sports that I have to really understand the athlete and what their desired outcome is in terms of like what attribute they're trying to build up more like for like a soccer player, a rugby player, something like that where it's sort of a hybrid of both, mainly like a rugby player, right? Cause you have to be explosive, but also you're constantly running and being like efficient with your energy. So, you know, what position do you play? Like, are you like all on the outside where you're just running constantly? And, you know, you need to really focus a little more on the endurance end of it. Are you really explosive? And, you know, the go-to guy out of a scrum to go right up and try and score. And like, so just as a coach to get a little more insight on those specific things, you can train for both. It's just gonna take away a little bit from both ends of that spectrum. Absolutely, so consider that for yourself. Which one do you want more? Do you wanna be extreme in one or the other? And then here's the final thing. They can both be a detriment to the other in the sense that if your strength is so bad, let's say you have terrible strength, you're very, very weak, your endurance will suffer also. So even if you're looking for maximum endurance, you have to have a certain baseline of strength in order to perform that endurance. And if your endurance is so terrible that you can't even perform your feats of strength, then the endurance, the lack of endurance is taken away from your strength. That's the other thing to consider. So I know for me as a lifter, somebody who's always interested in lifting weights and building muscle and getting stronger. I remember years ago, my cardiovascular endurance was so bad that I would get on a stationary bike and in 10 minutes I would be breathing hard. So I started training my endurance a little bit and I got stronger as a result. But it was because my endurance was so bad that it was holding me back. This is why I run my occasional mile just to kind of get a pulse on that. I'll run a mile and see how tough a mile is for me at whatever pace on the treadmill. And if it's something that I haven't done in months and I'm suffering from it, I'll kind of pick it up where I'm doing it one time a week or so, which is what I'm doing right now. Cause I just recently did that and I was gassed when I was doing it.  This is probably even affecting my weight training. I'd probably be getting better lifts if I had a little bit more endurance. So all I do is now, you know, once a week I'll start my workout with, after I do my mobility work, I'll go right over to the treadmill, I do my mile, I try and push my intensity on it, see if I can improve on my time and then I go into my training program. And so that kind of keeps that at that level to your point.


From around the globe, it's theCUBE with digital coverage of Red Hat Summit 2020, brought to you by Red Hat. Hi, I'm Stu Miniman and this is theCUBE's coverage of Red Hat Summit 2020. Of course, the event this year is digital. We're talking to Red Hat executives, partners and customers where they are around the globe, pulling them in remotely. Happy to welcome back to the program. One of our CUBE alumni on a very important topic of course at Red Hat Summit, talking about OpenShift. And joining me is Clayton Coleman, who's the OpenShift chief architect with Red Hat. Clayton, thanks so much for joining us. Thank you for having me today. All right, so before we get into the product, it's probably worthwhile that we talk about what's happening in the community and talking specifically, Kubernetes, the whole cloud native space. Normally we would have gotten together. I would have seen you at CUBECon at the end of March, but instead here we are at the end of April, looking out to more CNCF events later this year. But of course, Red Hat Summit is a great open source event and broad community. So we'd really love your viewpoint as to what's happening in that ecosystem. It's been a really interesting year. Obviously with an open source community, we react to this, like we always react to all the things that go on an open source. People come to the community and sometimes they have more time and sometimes they have less time. I think just from a community perspective, there've been a lot of people just reaching out to their colleagues outside of their companies, to their friends and coworkers and all of the different participants in the community. And there's been a lot of people getting together for a little bit of extra time, trying to connect virtually where they can't connect physically. And it's been great to at least see where we've come this year. We haven't had KubeCon and that'll be coming up later this year, but Kubernetes just had the 118 release. And I think Kubernetes is moving into that phase where it's a mature open source project. We've got a lot of the processes down. I'm really happy with the work that the steering committee has gone through. We handed off the last of the Bootstrap steering committee members, handed off to the new fully elected steering committee last year and it's gone absolutely smoothly, which has been phenomenal. The core project is trying to be a little bit more stable and to focus on closing out those loose ends, being a little bit more conservative to change. And at the same time, the ecosystem is really exploded in a number of directions. As Kubernetes becomes more of a bedrock technology for enterprises and individuals and startups and everything in between, we've really seen a huge amount of innovation in the space. And every year it just gets bigger and bigger. There's a lot of exciting projects that have never even talked to somebody on the Kubernetes project, but they have made and built and solved problems for their environments without us ever having to be involved, which I think is success. Yeah, so Clayton, one of the challenges when you talk to practitioners out there is just keeping up with the pace of change can really be challenging. Something we really saw acutely was Docker was rolling out updates every six weeks. Most customers aren't going to be able to change fast enough to keep up with things. Love your viewpoint both as to really what the CNCF says as well as how Red Hat thinks of the product. So you talked about Kubernetes 1.18. My understanding even Google isn't yet packaging and offering that version there. So there's a lag between things and as we start talking about managing across lots of clusters, how does Red Hat think of this? How should customers think about this? How do we make sure that we're staying secure and keeping updated on things without getting run over by the constant treadmill of change? The interesting part about Kubernetes is it's so much more than just that core project. No matter what any of us in the core Kubernetes project or in the products at Red Hat that build around it, go up and shift and layers on top. There's a whole ecosystem of components that most people think of as fundamental to accomplishing building applications, deploying them, running them, whether it's their continuous integration pipelines or it's their monitoring stacks. We really, as Kubernetes has become a little bit more conservative, I think we've really nailed down our processes for taking that change from the community, testing it. We run tens of thousands of automation tests a week on the latest and greatest Kubernetes code. We give it time to soak and we fit it together with all those pieces of the ecosystem and then make sure that they work well together. And I've noticed over the last two years that the rate of, oops, we missed that in Kubernetes 117 that by the time someone saw it, people were already using that, that started to go down. For us, it really hasn't been about the pace of keeping up with upstream, but it's about making sure that we can responsibly pull together all the other ecosystem components that are still a much newer and a little bit, how do we say they are in the exciting phase of their development? While still giving a predictable, reliable update stream, I would say that the challenges that most people are gonna see is how they bring together all those pieces. And that's something that on OpenShift, we think of as our goal is to help pull together all the pieces of this ecosystem and to make some choices for customers that make sense and to give them flexibility where it's not clear yet what the right choice might be or where different people could reasonably disagree. And I'm really excited. I feel like we've got our release cadence down and we're shipping the latest cube after it's had time to go through the review. And I think we've gotten better and better at that. So I'm really proud of the team at Red Hat and how they've worked within the community so that everybody benefits from that testing and that stability. Great. I'd like to hear you dig in a little bit on the application side. What's happening from the workloads that customers are using? What other innovations happening around that space? And how is Red Hat really helping really the infrastructure team and the developer team work even closer together like Red Hat has done for a long time? This is a great question. I'd say there's two key groups coming together. People are bringing substantial, important, critical production workloads and they expect things both to just work but also to be able to understand it. And they're making the transition a lot of folks I talked to are making the transition from previous systems. They've been running OpenShift for a while or they've been running Kubernetes for a while and they're getting ready to move a significant portion of their applications over. And so in the early days of any project you get the exciting green field development. You get to go play with new technologies but as you start moving first one and then 10 and then a hundred of your core business applications from VMs or from bare metal into containers you're taking advantage of that technology in a responsible way. And so the expectations on us as engineers and community members is to really make sure that we're closing out the little stuff.  So seeing a lot of that whether it's something new and exciting like model as a service for AI workloads or whether it's traditional big enterprise transaction processing apps. On the other side on that development model I think we're starting to see phase two or Kubernetes 2.0 in the community which is people are really leveraging the flexibility and the power of containers. Things that aren't necessarily new to people who got into containers early and they've had a chance to go through a couple of iterations but now people are starting to find patterns that up level development teams. So being able to run applications the same way on a local machine as in a production environment well those production environments are there now. And so people are really having to they're having to go through all of their tools and saying well does this process that works for an individual developer also work when I want to move it through my production or my staging environments to production? And so new projects like Knative and Tecton which are Kubernetes native that's just one part of the ecosystem around development on top of Kubernetes. There's tons of exciting projects out there from companies that have adopted the full stack of Kubernetes they built it into their mindset this idea of flexible infrastructure and we're seeing this explosion of new ways where Kubernetes is really just a detail and containers are just a detail and the fact that it's running this little thing called Docker down at the heart of it nobody talks about it anymore. And so that transition has been really exciting. I think there's a lot that we're trying to do to help developers and administrators see eye to eye and a lot of it is learning from the customers and users out there who've really paved the way which is the open source ways learning from others and helping others benefit from that. Yeah, I think you bring up a really important point. We've been saying for a couple of years now that Kubernetes should get to the point where it's boring and boring in a way also because it's going to be baked in everywhere. We saw from basically customers just taking the code really spinning a lot of their own things by building the stack to of course lots of customers have used OpenShift over the year too if I'm adopting public cloud more and more they're using those services from that standpoint. Can you talk a bit about how Red Hat is really integrating with public clouds and your architectural and technical philosophy on that and how might that be differ from some other companies that you might call a little bit more cloud adjacent as opposed to being deeply integrated with the public cloud. The interesting thing about Kubernetes is that while it was developed on top of the clouds it wasn't really built from day one assuming a cloud underneath it. And I think that was an opportunity that we really missed and to be fair we had to make the thing work first before we depended on these unreliable clouds. When we started the clouds were really hitting their stride on stability and reliability and people were, it was becoming the obvious choice. So some of what we've tried to do is take flexible infrastructure as a given, assume that the things that the cloud provides should be programmed for the benefit of the developer and the application. And I think that's a key trend is we're not using the cloud because our administration teams want us for using the cloud because it makes us more powerful as developers that enables new scenarios. It shortens the time between idea and reality. What we've done in OpenShift is we've really built around the idea of OpenShift running on a cloud should take advantage of that cloud to an extreme degree which is if infrastructure can be flexible the machines in that cluster need to come and go according to the demands of the applications on top of it. So giving a little bit more power to the cluster and taking a little bit of away from the cloud. But that benefits, that also needs to benefit those who are running on premise because I think as you noted, our goal is you want this ubiquitous Kubernetes environment everywhere. And the operations teams and the development teams and the DevOps teams in between need to have a consistent environment. And so if you can do this on the cloud but you don't have that flexibility on premise you've lost something. And so what we've tried to do as well is to think about those ideas that are what we think of as quote unquote cloud native that starts with immutable operating systems. It starts with everything being declarative and working backwards from, I want to have 15 machines and then the cluster or controllers on the cluster say, oh well, one of the machines has gone bad let's replace it. On the cloud you ask for a new cloud infrastructure provider or you ask the cloud API for a new machine and then you replace it automatically and no one knows any better. On premise, we'd love to do the same thing with both bare metal and virtualization on top of Kubernetes. So we had that flexibility to say you may not have all of the options but we should certainly be able to say, oh well, this hardware is bad or well the machine stopped so let's reboot it. And there's a lot of that same mindset that can be applied. We think that'll, if you need virtualization you can always use it but virtualization is a layer on top benefits from some of the same things that all the other extensions and applications on top of Kubernetes can benefit from. So trying to pave that layer make sure that you have flexible reliable storage on premise through RCEF and Red Hat storage products which are built on top of the cluster exactly like virtualization is built on top of the cluster so you get cloud native storage mixed in working with those teams to take those operational best practices. You know, there's, I think one of the things that interests me is no one 20 years ago who was running an early version of CEPH wouldn't have some approach to run these very large things at scales. Organizations like CERN have been using CEPH for over a decade at extremely large scale. Some of what our mindset is we think it's time to bake some of that knowledge actually into our software. For a very long time we've kind of been building out and adding more and more software but we always left the automation and the knowledge about how that software supposed to be run to the side. And so by taking that and we talk about operators Kubernetes really enshrines this principle is taking that idea of baking some of that operational knowledge into the software we ship though that software can rely on Kubernetes, OpenShift tries to hide the details of the infrastructure underneath and our goal I think in the long run is really just to make everybody's lives easier.  And we think there's a lot more room here that's really gonna improve how operations teams work with the software that they use day to day. So Clayton you mentioned virtualization is one of the topics in there of course virtualization is very prevalent in customers data center environment today. Red Hat OpenShift oftentimes in data centers is sitting on VMware environments. Of course recently VMware announced that they have Kubernetes baked into the solution and Red Hat has OpenShift with Red Hat virtualization. Maybe without going into too much depth and you probably have breakouts and white papers on this but what kind of decision point should customers be thinking about when they're deciding do I do this in bare metal? Do I do it in virtualization? What are some of the just high level trade-offs there when they need to make those decision points? I think the first one is virtualization is a mature technology. It's a known quantity for many organizations and so those who are comfortable with virtualization I'd say like any responsible architect or engineering team you don't want to stop using something that's working well just because you can. And a lot of what I would see as the transition that companies on is for some organizations without a big investment in virtualization they don't see the need for it anymore except as maybe a technical detail of how they isolate and secure workloads. One of the great things about virtualization technology that we're all aware of over the last couple of years is it creates a boundary between workloads and the underlying environment that doesn't mean that the underlying environment and containers can't be as secure or benefit from those same techniques. And so we're starting to see that in the community this kind of spectrum of virtualization all the way from the big traditional virtualization to very streamlined to stripped down virtualization wrappers around containers like some of the cloud providers use for their application environments. So I'm really excited about the open source community is touching each of these points on the spectrum. Some of our goals are, if you're happy with your infrastructure provider we want to work well with it. And that's kind of the pragmatic of everyone's at a different step in that journey. The benefit of containers is no matter how fast you make of the end it's never going to be quite as fast as a container. And it's never going to be quite as easy for a developer to run on their laptop. And I think working through this is there's still a lot of work that we as a community need to do around making it easier for developers to build containers and test them locally in smaller environments. But all of that flexibility can still benefit from a virtualization under later or virtualization used as an isolation technology. So projects like Cata and some of the work that's being done in the open source community around projects like Firecracker taking the same open source ideas and remixing them at different points gives us a lot of flexibility. So I would say I'm actually less interested in virtualization than all of the other technologies that are application centric. And at the heart of it a VM isn't really a developer centric idea. It's specifically an administrative concept that benefits the administrator and developers can take advantage of it. But I think all of the capabilities that you think of when you think of building an application like scaling out and making sure patches are applied, being able to roll back, separating your configuration and then all of the hundreds of other levels of complexity that we'll add around that like service mesh and the ability to gracefully tolerate failures in your database. These are where I think virtualization needs to work with the platform rather than being something that dominates how we think about the platform. It's application first, not being first. Yeah, no, you're absolutely right. The critique I've always given for a number of years now is if you look at virtualization, the promise was, let's take that old application that probably should have been updated and just shove it in a VM and never think about it again. That's not doing good things for the user. So if I look at that at one end of the spectrum, way at the other end of the spectrum, trying not to think about infrastructure, you mentioned Knative. So one of the things that I've been digging in trying to learn more about at Red Hat Summit has really been the OpenShift serverless. So give us the update on that piece. That's obviously a very different discussion than what we were just having from a virtualization standpoint. So how does OpenShift look at serverless? How does that tie into if I'm doing serverless in Amazon versus some of the other open source options for serverless, how should I be thinking about that? There's a lot of great choices on the spectrum out there. I think one of the interesting things, and I love the word spectrum here because Knative kind of sits at a spot where it tries to be, as the name says, it tries to be as Kubernetes-native as possible, which lets you tap into some of those additional capabilities when you need it. And one of the things I've always appreciated is the more restrictive a framework is, usually the better it is at doing that one thing and doing it really well. We learned this with Rails, we learned this with Node.js. And as people have built over the years, the idea of simple development platforms, the core function idea is a great simple idea. But sometimes you need to break out of that. You need extra flexibility or your application needs to run longer or slow start is actually an issue. One of the things I think is most interesting about Knative and I see comers and user think this way, it's a good point that gives you some of the flexibility of Kubernetes and a lot of the simplicity of functions as a service. But I think that there's going to be an inevitable set of use cases that tie into that, which are simpler, where an organization has a very opinionated way of running applications. And I think that flexibility will really benefit Knative, whereas some of the more opinionated frameworks around serverless lose a little bit of that. So that's one dimension that I still think Knative is well positioned to kind of capture the broadest possible audience, which for Kubernetes and containers was kind of our mindset. We wanted to solve enough of the problems that you can solve, you can run all your software. We don't have to solve all those problems to such a level that there's endless complexity, although we've been accused of having endless complexity in Kubernetes before. But just trying to think through what are the problems that everyone's going to have and give them a way out. At the same time, for us, when we think about productization functions as a service about integration, it's about taking applications and connecting them, connecting them through Kubernetes. And so it really depends on identity and access to data and tying that into your cloud environment if you're running on top of a cloud or tying it into your backend databases if you're on-premise. I think that is where the ecosystem is still working to bring together and standardize some of those pieces in Kubernetes or on top of Kubernetes. What I'm really excited about is the team, as much, there's been this core community effort to get a native to a GA quality. Alongside that, the OpenShift serverless team has been trying to make it a dramatically simpler action if you have Kubernetes and OpenShift. It's a one-click action to get started with Knative. And just like any other technology, how accessible it is determines how easy users find it to get started and to build the applications they need. So for us, it's not just about the core technology, it's about can someone who's not familiar with serverless or not familiar with Kubernetes bring up an editor and build a function and then deploy it on top of OpenShift, see it scale out like a normal Kubernetes application without having to know about pods or persistent volumes or nodes. And so these are some of the steps I've been really proud that the team's done. I think there's a huge amount of innovation that will happen this year and next year as the maturity of the Kubernetes ecosystem really grows up. We'll start to see standardized technologies for sharing identity across multiple clouds, across multiple environments. It's no good if you've got these applications on the cloud that need to tie into your corporate LDAP but you can't connect your corporate LDAP to the cloud. And so your applications need a third identity system. Nobody wants a third identity system. And so working through some of this, these are the challenges I think the hybrid organizations are already facing. And our job is just to work with them in the open source communities and with the cloud providers to partner with them in open source so that the technologies in Kubernetes fit very well into whatever environment they run in. All right, well, Clayton really appreciate all the updates there. I know the community is definitely looking forward to digging through some of the breakout sessions, reading all the new announcements. And of course, what we'll look forward to seeing you and the team participating in many of the, you know Kubernetes related events happen in later this year. That's right, it's going to be a good year. All right, thanks so much Clayton for joining us. I'm Stu Miniman and as always, thank you for watching theCUBE.


the filing status. And then if someone is married, now you have two people, which could possibly be both age, have the age factor met, and the blindness factor met, right? So you can see the combinations that we have actually gets fairly complex, because with a single filer, you have two added possible components, age and blindness that could have an impact on the standard deduction. And if married, you have two individuals, both of whom could have these two added conditions, you know, on each of them individual that could have an impact on the standard deduction for married filers. Okay, so don't check any boxes for your spouse if your filing status is head of household. So death of spouse in 2023. If your spouse was born before January 2, 1959, but you died in 2023 before reaching age 65, don't check the box that says quote spouse was born before January 2, 1959. So now we have this cutoff issue in the in the event of a death, which would hopefully be kind of a rare situation for that cutoff issue. A person is considered to reach age 65 on the day before the person's 65th birth date. Now, obviously, if you properly input this information into the tax return, if there was a death, for example, hopefully the tax return will help to do these cutoffs and these dates, but you want to be able to understand and interpret what the tax return is doing so you can explain it to a client and make sure the tax return is properly being populated. Example, your spouse was born on February 14, 1958, and died on February 13, 2023. Your spouse is considered age 65 at the time of death. Check the appropriate box for your spouse. So that is so then if you check the box for 65 older, then you might have again a benefit from a tax perspective so that you could so that you could possibly take a higher standard deduction. However, if your spouse died on February 12, 2023, your spouse isn't considered age 65. So notice it's somewhat arbitrary. They have to draw the line somewhere. And so they have that one day. So your spouse isn't considered age 65. Don't check the box. Death of taxpayer in 2023. So if you are preparing a return for someone who died in 2023, see publication 501 before completing the standard deduction information. You can find that on the IRS website. And then we have blindness. So if you weren't totally blind as of December 31, 2023, you must get a statement certified by your eye doctor or or or formal adult. I always get ophthalmologist. Okay, I can't say that word. The eye doctor or that is because because now you have this situation where you might get an increase to your standard deduction, which would be a benefit if you're claiming blindness. And now, of course, you have to have the question of are you actually blind to the point of recognition that you that you should get the tax benefit of it. So you need some type of verification from that from an essence, your eye doctor. So you can't see better than 2200 and your better eye with glasses or contact lenses. So obviously, we have two eyes and you know, one eye could be better than the other eye. And so now you can get pretty technical in terms of what the condition would be in order to be thought of as blind to get the higher standard deduction. Your field of vision is 20 degrees or less.


What up y'all, it's me again. So the other day I was having a conversation with a Facebook friend of mine, and she kinda, you know, she kinda checked me a little bit.  Why not provide value instead of just talking?  So today we're gonna talk a little bit about stocks, and first of all, just a disclaimer, I'm not a stockbroker, I'm a licensed mortgage loan originator, so I can go in depth about mortgages and home ownership, but I'm not gonna go too far in depth about stocks, but I'm just gonna give you like a 40,000 foot view, you know, just so you can get started if you have a couple dollars, whether you have $10, whether you have $100, whether you have like a grand, so you can dive into it because a lot of people don't even know where to get started. So one of the things that kinda got me on this whole, yo, I need to put people on game thing is I was looking at a post on Facebook, and you can look at it right here. And really what it talked about was, is it a problem with, you know, buying your kids, you know, nice shoes? As you can see in the post, like it's toddler shoes, so you see Nike's, you see Vans, you see Jordans, you see different things like that. So you know, if you Google these shoes, you'll see like, you know, the kids' version, the toddler version are like $60, $40, $50. And my whole stance what it was, it's stupid, it's idiotic, it's a bad idea. And it's part of the reason why the black community is where we are. So like, I think some projections say by 2040, black wealth, black net worth will be zero, at zero dollars and zero cents. So at that time that I looked at a share of Nike stock, it was trading for around $80, $80, $90. So it's time we change our mindset to, I'm going to spend $300 on, you know, these new Jordans they just dropped. When for that $300 you can own three shares of Nike stock, three shares of Nike stock. So now instead of going to the Foot Locker or going to your local mall and you hating on the dude who's walking out with four bags of shoes, now you could be, don't say it's five, basimo, basimo, because that affects how much money you make. So now instead of being a consumer, you're now an investor. So we're going to jump into my favorite app so far, Robinhood. So I started on Cash App with a few dollars and then I kind of graduated to Robinhood and Robinhood is kind of a good intermediate level. So you can learn about stocks, learn about the company, but it's not as in-depth as companies like Webull or eTrade or Yahoo Finance or whatever other companies are out there. So to jump into mine, you'll see it right here. So the example we're looking at is Tesla. So this morning I was checking Tesla. This is about 940. I was looking at Tesla. It was 731.64. So what that means is that's the stock price. So that means that Tesla right now, a share of Tesla cost $731.64 at that time. Now, I was lucky. I bought it two weeks ago, three weeks ago. I paid $425 for Tesla, $425.61. So pretty much I've made money. Now, if you click the link in my bio, you can download Robinhood through my link and you can kind of follow along and get started. You'll get a free stock. I'll get a free stock too. It's not going to be something too expensive. It'll probably be like $4 or maybe $6, but it gets you started to see how it works. And then in the green, you'll see how much it's moved since the stock market opened. So it's important to know the stock market opens every single day, well Monday through Friday from 9, I'm sorry, 9.30 to 4. And before 9.30, you'll have some pre-market movements, which just means people are buying and selling before it opens. And then after 4, you'll have aftermarket. So aftermarket lasts between 4 and 6. And then you'll see a lot of movement there too. But I like to just focus on the 9.30 to 4. You'll see the chart. Now the chart, really all it does is it tracks the price. So you'll see it kind of like an EKG, it goes up, down, up, down. So if the price goes up, it'll go up. Price goes down, it'll go down. Now when I took the screenshot, it was, you know, it had just opened. So like it might be down right now, I haven't checked, but you know, it's going to go up again, going to go down again, going to go up again. So you want to buy low and you want to sell high. That's what all that means. So below that, you'll see where it says 1D, 1M, 1, I'm sorry, 1W, 1M, 3M, 1Y, and 5Y. All that means is one day, so that's a chart for one day, one week, chart for one week, one month, chart for one month, three months, one year, five years. So as you change it, you can kind of see the chart is essentially zooming out. So you can get an idea of, okay, maybe today the stock price for Tesla was going down, but over the last year, has it been going up or has it been trending down? Over the past five years, has it been trending up or has it been trending down? And then you'll start to see how the world and politics affects stock prices in the stock market.  So again, we're using Tesla as an example. Below that, you'll see your position. So for me, my position is I just own one share. So I ain't got big money like that. So all I could afford at the time was one share of Tesla. It cost me right there 425.61. And then my equity value, that's pretty much how much it cost me and how much it's gone up on top of that. The statistics are just some things you could look at to get an idea of if this is a good company to buy right now, is it time to sell? Should I keep watching it or am I not really feeling it? So again, using Tesla as an example. So when the stock market opened today, Tesla was 698.58, my eyes are bad. And then below that, today's high. That's as high as it's been up until the time that I took the screenshot. Today's low. That's the lowest it's been. And then you'll see 52 WK. All that stands for is 52 weeks. So that's as high as it's been in a year. And then that's as low as it's been in a year. So people who are more in-depth with this, like my boy, AJ Gladney, if you really, really want to dive in, I can set you up with him and send you his way. They go into the dividends. They go into the volume. They go into all other metrics that you can use to figure out if this is the right stock for you or if this is the right time to buy or not. All the way at the bottom, it'll show you, like for me, I own a share. So it'll show me my history with trading Tesla. And then below that, it'll go into the information of Tesla. So for companies that you'll see that you might not know anything about, I mean, Tesla's pretty popular. So for companies you might not know anything about, you'll be able to get some information about them. Is this a solar company? Is this a pharmaceutical company? Is this a weed company? Weed stock is a goodbye, trust me. So yeah. The high level view of that, like I said, click the link in the bio, well, my bio, my comments or whatever to get started with that free share. And the big takeaway with this is stocks are a reflection of the world. When something is happening in the world, it could affect the stock price. And we need to, when you see old dudes read newspapers, you know, just watching CNN, watching Fox News, partly it's because, you know, they might be interested in that stuff. But the other piece of it too is that if they have money in the stock market, if they have 401K pension, they need to know what's going on in the world to know if it's time to sell, if it's time to buy, if it's time to just chill. So like you get to start seeing things on that high level.


everything can be taken from a man except his freedom to choose his attitude in the face of any given circumstances. Also, Victor Frankl said in his Book of Man's Search for Meaning about the use of paint in a Nazi concentration camp. Arguably, though, Frankl had no freedoms there. Did he really? No basic freedoms he couldn't decide when to get up, when to go to bed, where to live, what to do for a living? So what he's saying, I suppose, to us, which is a good reminder for us all, is that freedom isn't the absence of constraints. Freedom is the choice to choose your relationship to your givens, to your givens in your circumstances on any given day. Freedom is about what you do with what life has done is doing to you. I suppose is the lesson that he's passing on to us. It's not an easy lesson, is it? We've all got things in our lives that we want to change, can't change often. But what we can change is the meaning we attribute to it, our relationship with our given circumstances and, therefore, how that affects us on any given day. I've sent him much love to you all, but that leaves all your freedoms in that way today.