Image Title

Search Results for insights:

TheCUBE Insights | WiDS 2023


 

(energetic music) >> Everyone, welcome back to theCUBE's coverage of WiDS 2023. This is the eighth annual Women in Data Science Conference. As you know, WiDS is not just a conference or an event, it's a movement. This is going to include over 100,000 people in the next year WiDS 2023 in 200-plus countries. It is such a powerful movement. If you've had a chance to be part of the Livestream or even be here in person with us at Stanford University, you know what I'm talking about. This is Lisa Martin. I have had the pleasure all day of working with two fantastic graduate students in Stanford's Data Journalism Master's Program. Hannah Freitag has been here. Tracy Zhang, ladies, it's been such a pleasure working with you today. >> Same wise. >> I want to ask you both what are, as we wrap the day, I'm so inspired, I feel like I could go build an airplane. >> Exactly. >> Probably can't. But WiDS is just the inspiration that comes from this event. When you walk in the front door, you can feel it. >> Mm-hmm. >> Tracy, talk a little bit about what some of the things are that you heard today that really inspired you. >> I think one of the keyword that's like in my mind right now is like finding a mentor. >> Yeah. >> And I think, like if I leave this conference if I leave the talks, the conversations with one thing is that I'm very positive that if I want to switch, say someday, from Journalism to being a Data Analyst, to being like in Data Science, I'm sure that there are great role models for me to look up to, and I'm sure there are like mentors who can guide me through the way. So, like that, I feel reassured for some reason. >> It's a good feeling, isn't it? What do you, Hannah, what about you? What's your takeaway so far of the day? >> Yeah, one of my key takeaways is that anything's possible. >> Mm-hmm. >> So, if you have your vision, you have the role model, someone you look up to, and even if you have like a different background, not in Data Science, Data Engineering, or Computer Science but you're like, "Wow, this is really inspiring. I would love to do that." As long as you love it, you're passionate about it, and you are willing to, you know, take this path even though it won't be easy. >> Yeah. >> Then you can achieve it, and as you said, Tracy, it's important to have mentors on the way there. >> Exactly. >> But as long as you speak up, you know, you raise your voice, you ask questions, and you're curious, you can make it. >> Yeah. >> And I think that's one of my key takeaways, and I was just so inspiring to hear like all these women speaking on stage, and also here in our conversations and learning about their, you know, career path and what they learned on their way. >> Yeah, you bring up curiosity, and I think that is such an important skill. >> Mm-hmm. >> You know, you could think of Data Science and think about all the hard skills that you need. >> Mm, like coding. >> But as some of our guests said today, you don't have to be a statistician or an engineer, or a developer to get into this. Data Science applies to every facet of every part of the world. >> Mm-hmm. >> Finances, marketing, retail, manufacturing, healthcare, you name it, Data Science has the power and the potential to unlock massive achievements. >> Exactly. >> It's like we're scratching the surface. >> Yeah. >> But that curiosity, I think, is a great skill to bring to anything that you do. >> Mm-hmm. >> And I think we... For the female leaders that we're on stage, and that we had a chance to talk to on theCUBE today, I think they all probably had that I think as a common denominator. >> Exactly. >> That curious mindset, and also something that I think as hard is the courage to raise your hand. I like this, I'm interested in this. I don't see anybody that looks like me. >> But that doesn't mean I shouldn't do it. >> Exactly. >> Exactly, in addition to the curiosity that all the women, you know, bring to the table is that, in addition to that, being optimistic, and even though we don't see gender equality or like general equality in companies yet, we make progress and we're optimistic about it, and we're not like negative and complaining the whole time. But you know, this positive attitude towards a trend that is going in the right direction, and even though there's still a lot to be done- >> Exactly. >> We're moving it that way. >> Right. >> Being optimistic about this. >> Yeah, exactly, like even if it means that it's hard. Even if it means you need to be your own role model it's still like worth a try. And I think they, like all of the great women speakers, all the female leaders, they all have that in them, like they have the courage to like raise their hand and be like, "I want to do this, and I'm going to make it." And they're role models right now, so- >> Absolutely, they have drive. >> They do. >> Right. They have that ambition to take something that's challenging and complicated, and help abstract end users from that. Like we were talking to Intuit. I use Intuit in my small business for financial management, and she was talking about how they can from a machine learning standpoint, pull all this data off of documents that you upload and make that, abstract that, all that complexity from the end user, make something that's painful taxes. >> Mm-hmm. >> Maybe slightly less painful. It's still painful when you have to go, "Do I have to write you a check again?" >> Yeah. (laughs) >> Okay. >> But talking about just all the different applications of Data Science in the world, I found that to be very inspiring and really eye-opening. >> Definitely. >> I hadn't thought about, you know, we talk about climate change all the time, especially here in California, but I never thought about Data Science as a facilitator of the experts being able to make sense of what's going on historically and in real-time, or the application of Data Science in police violence. We see far too many cases of police violence on the news. It's an epidemic that's a horrible problem. Data Science can be applied to that to help us learn from that, and hopefully, start moving the needle in the right direction. >> Absolutely. >> Exactly. >> And especially like one sentence from Guitry from the very beginnings I still have in my mind is then when she said that arguments, no, that data beats arguments. >> Yes. >> In a conversation that if you be like, okay, I have this data set and it can actually show you this or that, it's much more powerful than just like being, okay, this is my position or opinion on this. And I think in a world where increasing like misinformation, and sometimes, censorship as we heard in one of the talks, it's so important to have like data, reliable data, but also acknowledge, and we talked about it with one of our interviewees that there's spices in data and we also need to be aware of this, and how to, you know, move this forward and use Data Science for social good. >> Mm-hmm. >> Yeah, for social good. >> Yeah, definitely, I think they like data, and the question about, or like the problem-solving part about like the social issues, or like some just questions, they definitely go hand-in-hand. Like either of them standing alone won't be anything that's going to be having an impact, but combining them together, you have a data set that illustrate a point or like solves the problem. I think, yeah, that's definitely like where Data Set Science is headed to, and I'm glad to see all these great women like making their impact and combining those two aspects together. >> It was interesting in the keynote this morning. We were all there when Margot Gerritsen who's one of the founders of WiDS, and Margot's been on the program before and she's a huge supporter of what we do and vice versa. She asked the non-women in the room, "Those who don't identify as women, stand up," and there was a handful of men, and she said, "That's what it's like to be a female in technology." >> Oh, my God. >> And I thought that vision give me goosebumps. >> Powerful. (laughs) >> Very powerful. But she's right, and one of the things I think that thematically another common denominator that I think we heard, I want to get your opinions as well from our conversations today, is the importance of community. >> Mm-hmm. >> You know, I was mentioning this stuff from AnitaB.org that showed that in 2022, the percentage of females and technical roles is 27.6%. It's a little bit of an increase. It's been hovering around 25% for a while. But one of the things that's still a problem is attrition. It doubled last year. >> Right. >> And I was asking some of the guests, and we've all done that today, "How would you advise companies to start moving the needle down on attrition?" >> Mm-hmm. >> And I think the common theme was network, community. >> Exactly. >> It takes a village like this. >> Mm-hmm. >> So you can see what you can be to help start moving that needle and that's, I think, what underscores the value of what WiDS delivers, and what we're able to showcase on theCUBE. >> Yeah, absolutely. >> I think it's very important to like if you're like a woman in tech to be able to know that there's someone for you, that there's a whole community you can rely on, and that like you are, you have the same mindset, you're working towards the same goal. And it's just reassuring and like it feels very nice and warm to have all these women for you. >> Lisa: It's definitely a warm fuzzy, isn't it? >> Yeah, and both the community within the workplace but also outside, like a network of family and friends who support you to- >> Yes. >> To pursue your career goals. I think that was also a common theme we heard that it's, yeah, necessary to both have, you know your community within your company or organization you're working but also outside. >> Definitely, I think that's also like how, why, the reason why we feel like this in like at WiDS, like I think we all feel very positive right now. So, yeah, I think that's like the power of the connection and the community, yeah. >> And the nice thing is this is like I said, WiDS is a movement. >> Yes. >> This is global. >> Mm-hmm. >> We've had some WiDS ambassadors on the program who started WiDS and Tel Aviv, for example, in their small communities. Or in Singapore and Mumbai that are bringing it here and becoming more of a visible part of the community. >> Tracy: Right. >> I loved seeing all the young faces when we walked in the keynote this morning. You know, we come here from a journalistic perspective. You guys are Journalism students. But seeing all the potential in the faces in that room just seeing, and hearing stories, and starting to make tangible connections between Facebook and data, and the end user and the perspectives, and the privacy and the responsibility of AI is all... They're all positive messages that need to be reinforced, and we need to have more platforms like this to be able to not just raise awareness, but sustain it. >> Exactly. >> Right. It's about the long-term, it's about how do we dial down that attrition, what can we do? What can we do? How can we help? >> Mm-hmm. >> Both awareness, but also giving women like a place where they can connect, you know, also outside of conferences. Okay, how do we make this like a long-term thing? So, I think WiDS is a great way to, you know, encourage this connectivity and these women teaming up. >> Yeah, (chuckles) girls help girls. >> Yeah. (laughs) >> It's true. There's a lot of organizations out there, girls who Code, Girls Inc., et cetera, that are all aimed at helping women kind of find their, I think, find their voice. >> Exactly. >> And find that curiosity. >> Yeah. Unlock that somewhere back there. Get some courage- >> Mm-hmm. >> To raise your hand and say, "I think I want to do this," or "I have a question. You explained something and I didn't understand it." Like, that's the advice I would always give to my younger self is never be afraid to raise your hand in a meeting. >> Mm-hmm. >> I guarantee you half the people weren't listening or, and the other half may not have understood what was being talked about. >> Exactly. >> So, raise your hand, there goes Margot Gerritsen, the founder of WiDS, hey, Margot. >> Hi. >> Keep alumni as you know, raise your hand, ask the question, there's no question that's stupid. >> Mm-hmm. >> And I promise you, if you just take that chance once it will open up so many doors, you won't even know which door to go in because there's so many that are opening. >> And if you have a question, there's at least one more person in the room who has the exact same question. >> Exact same question. >> Yeah, we'll definitely keep that in mind as students- >> Well, I'm curious how Data Journalism, what you heard today, Tracy, we'll start with you, and then, Hannah, to you. >> Mm-hmm. How has it influenced how you approach data-driven, and storytelling? Has it inspired you? I imagine it has, or has it given you any new ideas for, as you round out your Master's Program in the next few months? >> I think like one keyword that I found really helpful from like all the conversations today, was problem-solving. >> Yeah. >> Because I think, like we talked a lot about in our program about how to put a face on data sets. How to put a face, put a name on a story that's like coming from like big data, a lot of numbers but you need to like narrow it down to like one person or one anecdote that represents a bigger problem. And I think essentially that's problem-solving. That's like there is a community, there is like say maybe even just one person who has, well, some problem about something, and then we're using data. We're, by giving them a voice, by portraying them in news and like representing them in the media, we're solving this problem somehow. We're at least trying to solve this problem, trying to make some impact. And I think that's like what Data Science is about, is problem-solving, and, yeah, I think I heard a lot from today's conversation, also today's speakers. So, yeah, I think that's like something we should also think about as Journalists when we do pitches or like what kind of problem are we solving? >> I love that. >> Or like kind of what community are we trying to make an impact in? >> Yes. >> Absolutely. Yeah, I think one of the main learnings for me that I want to apply like to my career in Data Journalism is that I don't shy away from complexity because like Data Science is oftentimes very complex. >> Complex. >> And also data, you're using for your stories is complex. >> Mm-hmm. >> So, how can we, on the one hand, reduce complexity in a way that we make it accessible for broader audience? 'Cause, we don't want to be this like tech bubble talking in data jargon, we want to, you know, make it accessible for a broader audience. >> Yeah. >> I think that's like my purpose as a Data Journalist. But at the same time, don't reduce complexity when it's needed, you know, and be open to dive into new topics, and data sets and circling back to this of like raising your hand and asking questions if you don't understand like a certain part. >> Yeah. >> So, that's definitely a main learning from this conference. >> Definitely. >> That like, people are willing to talk to you and explain complex topics, and this will definitely facilitate your work as a Data Journalist. >> Mm-hmm. >> So, that inspired me. >> Well, I can't wait to see where you guys go from here. I've loved co-hosting with you today, thank you. >> Thank you. >> For joining me at our conference. >> Wasn't it fun? >> Thank you. >> It's a great event. It's, we, I think we've all been very inspired and I'm going to leave here probably floating above the ground a few inches, high on the inspiration of what this community can deliver, isn't that great? >> It feels great, I don't know, I just feel great. >> Me too. (laughs) >> So much good energy, positive energy, we love it. >> Yeah, so we want to thank all the organizers of WiDS, Judy Logan, Margot Gerritsen in particular. We also want to thank John Furrier who is here. And if you know Johnny, know he gets FOMO when he is not hosting. But John and Dave Vellante are such great supporters of women in technology, women in technical roles. We wouldn't be here without them. So, shout out to my bosses. Thank you for giving me the keys to theCube at this event. I know it's painful sometimes, but we hope that we brought you great stories all day. We hope we inspired you with the females and the one male that we had on the program today in terms of raise your hand, ask a question, be curious, don't be afraid to pursue what you're interested in. That's my soapbox moment for now. So, for my co-host, I'm Lisa Martin, we want to thank you so much for watching our program today. You can watch all of this on-demand on thecube.net. You'll find write-ups on siliconeangle.com, and, of course, YouTube. Thanks, everyone, stay safe and we'll see you next time. (energetic music)

Published Date : Mar 8 2023

SUMMARY :

I have had the pleasure all day of working I want to ask you both But WiDS is just the inspiration that you heard today I think one of the keyword if I leave the talks, is that anything's possible. and even if you have like mentors on the way there. you know, you raise your And I think that's one Yeah, you bring up curiosity, the hard skills that you need. of the world. and the potential to unlock bring to anything that you do. and that we had a chance to I don't see anybody that looks like me. But that doesn't all the women, you know, of the great women speakers, documents that you upload "Do I have to write you a check again?" I found that to be very of the experts being able to make sense from the very beginnings and how to, you know, move this and the question about, or of the founders of WiDS, and And I thought (laughs) of the things I think But one of the things that's And I think the common like this. So you can see what you and that like you are, to both have, you know and the community, yeah. And the nice thing and becoming more of a and the privacy and the It's about the long-term, great way to, you know, et cetera, that are all aimed Unlock that somewhere back there. Like, that's the advice and the other half may not have understood the founder of WiDS, hey, Margot. ask the question, there's if you just take that And if you have a question, and then, Hannah, to you. as you round out your Master's Program from like all the conversations of numbers but you need that I want to apply like to And also data, you're using you know, make it accessible But at the same time, a main learning from this conference. people are willing to talk to you with you today, thank you. at our conference. and I'm going to leave know, I just feel great. (laughs) positive energy, we love it. that we brought you great stories all day.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
JohnPERSON

0.99+

JohnnyPERSON

0.99+

Lisa MartinPERSON

0.99+

Lisa MartinPERSON

0.99+

Hannah FreitagPERSON

0.99+

MargotPERSON

0.99+

Tracy ZhangPERSON

0.99+

Dave VellantePERSON

0.99+

LisaPERSON

0.99+

Margot GerritsenPERSON

0.99+

SingaporeLOCATION

0.99+

CaliforniaLOCATION

0.99+

John FurrierPERSON

0.99+

TracyPERSON

0.99+

HannahPERSON

0.99+

Judy LoganPERSON

0.99+

27.6%QUANTITY

0.99+

Margot GerritsenPERSON

0.99+

2022DATE

0.99+

CodeORGANIZATION

0.99+

MumbaiLOCATION

0.99+

last yearDATE

0.99+

FacebookORGANIZATION

0.99+

todayDATE

0.99+

siliconeangle.comOTHER

0.99+

WiDSORGANIZATION

0.99+

two aspectsQUANTITY

0.99+

GuitryPERSON

0.98+

bothQUANTITY

0.98+

WiDSEVENT

0.98+

oneQUANTITY

0.98+

thecube.netOTHER

0.98+

BothQUANTITY

0.98+

over 100,000 peopleQUANTITY

0.98+

WiDS 2023EVENT

0.98+

one keywordQUANTITY

0.98+

next yearDATE

0.98+

200-plus countriesQUANTITY

0.98+

one sentenceQUANTITY

0.98+

IntuitORGANIZATION

0.97+

Girls Inc.ORGANIZATION

0.97+

YouTubeORGANIZATION

0.96+

one personQUANTITY

0.95+

two fantastic graduate studentsQUANTITY

0.95+

Stanford UniversityORGANIZATION

0.94+

Women in Data Science ConferenceEVENT

0.94+

around 25%QUANTITY

0.93+

StanfordORGANIZATION

0.93+

this morningDATE

0.92+

theCUBEORGANIZATION

0.88+

half the peopleQUANTITY

0.87+

Data Journalism Master's ProgramTITLE

0.86+

one thingQUANTITY

0.85+

eighth annualQUANTITY

0.83+

at least one more personQUANTITY

0.8+

next few monthsDATE

0.78+

halfQUANTITY

0.74+

one anecdoteQUANTITY

0.73+

AnitaB.orgOTHER

0.71+

key takeawaysQUANTITY

0.71+

TheCUBEORGANIZATION

0.71+

CUBE Insights Day 1 | CloudNativeSecurityCon 23


 

(upbeat music) >> Hey, everyone. Welcome back to theCUBE's day one coverage of Cloud Native SecurityCon 2023. This has been a great conversation that we've been able to be a part of today. Lisa Martin with John Furrier and Dave Vellante. Dave and John, I want to get your take on the conversations that we had today, starting with the keynote that we were able to see. What are your thoughts? We talked a lot about technology. We also talked a lot about people and culture. John, starting with you, what's the story here with this inaugural event? >> Well, first of all, there's two major threads. One is the breakout of a new event from CloudNativeCon/KubeCon, which is a very successful community and events that they do international and in North America. And that's not stopping. So that's going to be continuing to go great. This event is a breakout with an extreme focus on security and all things security around that ecosystem. And with extensions into the Linux Foundation. We heard Brian Behlendorf was on there from the Linux Foundation. So he was involved in Hyperledger. So not just Cloud Native, all things containers, Kubernetes, all things Linux Foundation as an open source. So, little bit more of a focus. So I like that piece of it. The other big thread on this story is what Dave and Yves were talking about on our panel we had earlier, which was the business model of security is real and that is absolutely happening. It's impacting business today. So you got this, let's build as fast as possible, let's retool, let's replatform, refactor and then the reality of the business imperative. To me, those are the two big high-order bits that are going on and that's the reality of this current situation. >> Dave, what are your top takeaways from today's day one inaugural coverage? >> Yeah, I would add a third leg of the stool to what John said and that's what we were talking about several times today about the security is a do-over. The Pat Gelsinger quote, from what was that, John, 2011, 2012? And that's right around the time that the cloud was hitting this steep part of the S-curve and do-over really has meant in looking back, leveraging cloud native tooling, and cloud native technologies, which are different than traditional security approaches because it has to take into account the unique characteristics of the cloud whether that's dynamic resource allocation, unlimited resources, microservices, containers. And while that has helped solve some problems it also brings new challenges. All these cloud native tools, securing this decentralized infrastructure that people are dealing with and really trying to relearn the security culture. And that's kind of where we are today. >> I think the other thing too that I had Dave is that was we get other guests on with a diverse opinion around foundational models with AI and machine learning. You're going to see a lot more things come in to accelerate the scale and automation piece of it. It is one thing that CloudNativeCon and KubeCon has shown us what the growth of cloud computing is is that containers Kubernetes and these new services are powering scale. And scale you're going to need to have automation and machine learning and AI will be a big part of that. So you start to see the new formation of stacks emerging. So foundational stacks is the machine learning and data apps are coming out. It's going to start to see more apps coming. So I think there's going to be so many new applications and services are going to emerge, and if you don't get your act together on the infrastructure side those apps will not be fully baked. >> And obviously that's a huge risk. Sorry, Dave, go ahead. >> No, that's okay. So there has to be hardware somewhere. You can't get away with no hardware. But increasingly the security architecture like everything else is, is software-defined and makes it a lot more flexible. And to the extent that practitioners and organizations can consolidate this myriad of tools that they have, that means they're going to have less trouble learning new skills, they're going to be able to spend more time focused and become more proficient on the tooling that is being applied. And you're seeing the same thing on the vendor side. You're seeing some of these large vendors, Palo Alto, certainly CrowdStrike and fundamental to their strategy is to pick off more and more and more of these areas in security and begin to consolidate them. And right now, that's a big theme amongst organizations. We know from the survey data that consolidating redundant vendors is the number one cost saving priority today. Along with, at a distant second, optimizing cloud costs, but consolidating redundant vendors there's nowhere where that's more prominent than in security. >> Dave, talk a little bit about that, you mentioned the practitioners and obviously this event bottoms up focused on the practitioners. It seems like they're really in the driver's seat now. With this being the inaugural Cloud Native SecurityCon, first time it's been pulled out of an elevated out of KubeCon as a focus, do you think this is about time that the practitioners are in the driver's seat? >> Well, they're certainly, I mean, we hear about all the tech layoffs. You're not laying off your top security pros and if you are, they're getting picked up very quickly. So I think from that standpoint, anybody who has deep security expertise is in the driver's seat. The problem is that driver's seat is pretty hairy and you got to have the stomach for it. I mean, these are technical heroes, if you will, on the front lines, literally saving the world from criminals and nation-states. And so yes, I think Lisa they have been in the driver's seat for a while, but it it takes a unique person to drive at those speeds. >> I mean, the thing too is that the cloud native world that we are living in comes from cloud computing. And if you look at this, what is a practitioner? There's multiple stakeholders that are being impacted and are vulnerable in the security front at many levels. You have application developers, you got IT market, you got security, infrastructure, and network and whatever. So all that old to new is happening. So if you look at IT, that market is massive. That's still not transformed yet to cloud. So you have companies out there literally fully exposed to ransomware. IT teams that are having practices that are antiquated and outdated. So security patching, I mean the blocking and tackling of the old securities, it's hard to even support that old environment. So in this transition from IT to cloud is changing everything. And so practitioners are impacted from the devs and the ones that get there faster and adopt the ways to make their business better, whether you call it modern technology and architectures, will be alive and hopefully thriving. So that's the challenge. And I think this security focus hits at the heart of the reality of business because like I said, they're under threats. >> I wanted to pick up too on, I thought Brian Behlendorf, he did a forward looking what could become the next problem that we really haven't addressed. He talked about generative AI, automating spearphishing and he flat out said the (indistinct) is not fixed. And so identity access management, again, a lot of different toolings. There's Microsoft, there's Okta, there's dozens of companies with different identity platforms that practitioners have to deal with. And then what he called free riders. So these are folks that go into the repos. They're open source repos, and they find vulnerabilities that developers aren't hopping on quickly. It's like, you remember Patch Tuesday. We still have Patch Tuesday. That meant Hacker Wednesday. It's kind of the same theme there going into these repos and finding areas where the practitioners, the developers aren't responding quickly enough. They just don't necessarily have the resources. And then regulations, public policy being out of alignment with what's really needed, saying, "Oh, you can't ship that fix outside of Germany." Or I'm just making this up, but outside of this region because of a law. And you could be as a developer personally liable for it. So again, while these practitioners are in the driver's seat, it's a hairy place to be. >> Dave, we didn't get the word supercloud in much on this event, did we? >> Well, I'm glad you brought that up because I think security is the big single, biggest challenge for supercloud, securing the supercloud with all the diversity of tooling across clouds and I think you brought something up in the first supercloud, John. You said, "Look, ultimately the cloud, the hyperscalers have to lean in. They are going to be the enablers of supercloud. They already are from an infrastructure standpoint, but they can solve this problem by working together. And I think there needs to be more industry collaboration. >> And I think the point there is that with security the trend will be, in my opinion, you'll see security being reborn in the cloud, around zero trust as structure, and move from an on-premise paradigm to fully cloud native. And you're seeing that in the network side, Dave, where people are going to each cloud and building stacks inside the clouds, hyperscaler clouds that are completely compatible end-to-end with on-premises. Not trying to force the cloud to be working with on-prem. They're completely refactoring as cloud native first. And again, that's developer first, that's data first, that's security first. So to me that's the tell sign. To me is if when you see that, that's good. >> And Lisa, I think the cultural conversation that you've brought into these discussions is super important because I've said many times, bad user behavior is going to trump good security every time. So that idea that the entire organization is responsible for security. You hear that all the time. Well, what does that mean? It doesn't mean I have to be a security expert, it just means I have to be smart. How many people actually use a VPN? >> So I think one of the things that I'm seeing with the cultural change is face-to-face problem solving is one, having remote teams is another. The skillset is big. And I think the culture of having these teams, Dave mentioned something about intramural sports, having the best people on the teams, from putting captains on the jersey of security folks is going to happen. I think you're going to see a lot more of that going on because there's so many areas to work on. You're going to start to see security embedded in all processes. >> Well, it needs to be and that level of shared responsibility is not trivial. That's across the organization. But they're also begs the question of the people problem. People are one of the biggest challenges with respect to security. Everyone has to be on board with this. It has to be coming from the top down, but also the bottom up at the same time. It's challenging to coordinate. >> Well, the training thing I think is going to solve itself in good time. And I think in the fullness of time, if I had to predict, you're going to see managed services being a big driver on the front end, and then as companies realize where their IP will be you'll see those managed service either be a core competency of their business and then still leverage. So I'm a big believer in managed services. So you're seeing Kubernetes, for instance, a lot of managed services. You'll start to see more, get the ball going, get that rolling, then build. So Dave mentioned bottoms up, middle out, that's how transformation happens. So I think managed services will win from here, but ultimately the business model stuff is so critical. >> I'm glad you brought up managed services and I want to add to that managed security service providers, because I saw a stat last year, 50% of organizations in the US don't even have a security operations team. So managed security service providers MSSPs are going to fill the gap, especially for small and midsize companies and for those larger companies that just need to augment and compliment their existing staff. And so those practitioners that we've been talking about, those really hardcore pros, they're going to go into these companies, some large, the big four, all have them. Smaller companies like Arctic Wolf are going to, I think, really play a key role in this decade. >> I want to get your opinion Dave on what you're hoping to see from this event as we've talked about the first inaugural standalone big focus here on security as a standalone. Obviously, it's a huge challenge. What are you hoping for this event to get groundswell from the community? What are you hoping to hear and see as we wrap up day one and go into day two? >> I always say events like this they're about educating, aspiring to action. And so the practitioners that are at this event I think, I used to say they're the technical heroes. So we know there's going to be another Log4j or a another SolarWinds. It's coming. And my hope is that when that happens, it's not an if, it's a when, that the industry, these practitioners are able to respond in a way that's safe and fast and agile and they're able to keep us protected, number one and number two, that they can actually figure out what happened in the long tail of still trying to clean it up is compressed. That's my hope or maybe it's a dream. >> I think day two tomorrow you're going to hear more supply chain, security. You're going to start to see them focus on sessions that target areas if within the CNCF KubeCon + CloudNativeCon area that need support around containers, clusters, around Kubernetes cluster. You're going to start to see them laser focus on cleaning up the house, if you will, if you can call it cleaning up or fixing what needs to get fixed or solved what needs to get solved on the cloud native front. That's going to be urgent. And again, supply chain software as Dave mentioned, free riders too, just using open source. So I think you'll see open source continue to grow, but there'll be an emphasis on verification and certification. And Docker has done a great job with that. You've seen what they've done with their business model over hundreds of millions of dollars in revenue from a pivot. Catch a few years earlier because they verify. So I think we're going to be in this verification blue check mark of code era, of code and software. Super important bill of materials. They call SBOMs, software bill of materials. People want to know what's in their software and that's going to be, again, another opportunity for machine learning and other things. So I'm optimistic that this is going to be a good focus. >> Good. I like that. I think that's one of the things thematically that we've heard today is optimism about what this community can generate in terms of today's point. The next Log4j is coming. We know it's not if, it's when, and all organizations need to be ready to Dave's point to act quickly with agility to dial down and not become the next headline. Nobody wants to be that. Guys, it's been fun working with you on this day one event. Looking forward to day two. Lisa Martin for Dave Vellante and John Furrier. You're watching theCUBE's day one coverage of Cloud Native SecurityCon '23. We'll see you tomorrow. (upbeat music)

Published Date : Feb 2 2023

SUMMARY :

to be a part of today. that are going on and that's the reality that the cloud was hitting So I think there's going to And obviously that's a huge risk. So there has to be hardware somewhere. that the practitioners is in the driver's seat. So all that old to new is happening. and he flat out said the And I think there needs to be So to me that's the tell sign. So that idea that the entire organization is going to happen. Everyone has to be on board with this. being a big driver on the front end, that just need to augment to get groundswell from the community? that the industry, these and that's going to be, and not become the next headline.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
JohnPERSON

0.99+

DavePERSON

0.99+

Dave VellantePERSON

0.99+

Brian BehlendorfPERSON

0.99+

LisaPERSON

0.99+

Dave VellantePERSON

0.99+

Lisa MartinPERSON

0.99+

John FurrierPERSON

0.99+

2011DATE

0.99+

MicrosoftORGANIZATION

0.99+

GermanyLOCATION

0.99+

YvesPERSON

0.99+

John FurrierPERSON

0.99+

50%QUANTITY

0.99+

Linux FoundationORGANIZATION

0.99+

North AmericaLOCATION

0.99+

USLOCATION

0.99+

firstQUANTITY

0.99+

CloudNativeConEVENT

0.99+

last yearDATE

0.99+

Arctic WolfORGANIZATION

0.99+

tomorrowDATE

0.99+

Pat GelsingerPERSON

0.99+

KubeConEVENT

0.99+

OneQUANTITY

0.99+

day oneQUANTITY

0.98+

todayDATE

0.98+

Linux FoundationORGANIZATION

0.98+

third legQUANTITY

0.98+

day twoQUANTITY

0.97+

Cloud Native SecurityCon 2023EVENT

0.97+

one thingQUANTITY

0.97+

each cloudQUANTITY

0.97+

two major threadsQUANTITY

0.96+

Cloud Native SecurityCon '23EVENT

0.96+

SolarWindsORGANIZATION

0.96+

CloudNativeSecurityCon 23EVENT

0.95+

oneQUANTITY

0.95+

Cloud Native SecurityConEVENT

0.95+

KubernetesTITLE

0.95+

dayQUANTITY

0.95+

singleQUANTITY

0.94+

dozens of companiesQUANTITY

0.94+

CrowdStrikeORGANIZATION

0.94+

Patch TuesdayTITLE

0.93+

Day 1QUANTITY

0.93+

HyperledgerORGANIZATION

0.93+

supercloudORGANIZATION

0.91+

hundreds of millions of dollarsQUANTITY

0.91+

2012DATE

0.89+

secondQUANTITY

0.88+

first timeQUANTITY

0.87+

PaloORGANIZATION

0.87+

two big high-order bitsQUANTITY

0.87+

Log4jORGANIZATION

0.86+

AltoLOCATION

0.86+

few years earlierDATE

0.85+

MarTech Market Landscape | Investor Insights w/ Jerry Chen, Greylock | AWS Startup Showcase S2 E3


 

>>Hello, everyone. Welcome to the cubes presentation of the 80, but startup showcases MarTech is the focus. And this is all about the emerging cloud scale customer experience. This is season two, episode three of the ongoing series covering the exciting, fast growing startups from the cloud AWS ecosystem to talk about the future and what's available now, where are the actions? I'm your host John fur. Today. We joined by Cub alumni, Jerry Chen partner at Greylock ventures. Jerry. Great to see you. Thanks for coming on, >>John. Thanks for having me back. I appreciate you welcome there for season two. Uh, as a, as a guest star, >><laugh>, you know, Hey, you know, season two, it's not a one and done it's continued coverage. We, we got the episodic, uh, cube flicks model going >>Here. Well, you know, congratulations, the, the coverage on this ecosystem around AWS has been impressive, right? I think you and I have talked a long time about AWS and the ecosystem building. It just continues to grow. And so the coverage you did last season, all the events of this season is, is pretty amazing from the data security to now marketing. So it's, it's great to >>Watch. And 12 years now, the cube been running. I remember 2013, when we first met you in the cube, we just left VMware just getting into the venture business. And we were just riffing the next 80. No one really kind of knew how big it would be. Um, but we were kinda riffing on. We kind of had a sense now it's happening. So now you start to see every vertical kind of explode with the right digital transformation and disruption where you see new incumbents. I mean, new Newton brands get replaced the incumbent old guard. And now in MarTech, it's ripe for, for disruption because web two has gone on to web 2.5, 3, 4, 5, um, cookies are going away. You've got more governance and privacy challenges. There's a slew of kind of ad tech baggage, but yet lots of new data opportunities. Jerry, this is a huge, uh, thing. What's your take on this whole MarTech cloud scale, uh, >>Market? I, I think, I think to your point, John, that first the trends are correct and the bad and the good or good old days, the battle days MarTech is really about your webpage. And then email right there. There's, there's the emails, the only channel and the webpage was only real estate and technology to care about fast forward, you know, 10 years you have webpages, mobile apps, VR experiences, car experiences, your, your, your Alexa home experiences. Let's not even get to web three web 18, whatever it is. Plus you got text messages, WhatsApp, messenger, email, still great, et cetera. So I think what we've seen is both, um, explosion and data, uh, explosion of channel. So sources of data have increases and the fruits of the data where you can reach your customers from text, email, phone calls, etcetera have exploded too. So the previous generation created big company responses, Equa, you know, that exact target that got acquired by Oracle or, or, um, Salesforce, and then companies like, um, you know, MailChimp that got acquired as well, but into it, you're seeing a new generation companies for this new stack. So I, I think it's exciting. >>Yeah. And you mentioned all those things about the different channels and stuff, but the key point is now the generation shifts going on, not just technical generation, uh, and platform and tools, it's the people they're younger. They don't do email. They have, you know, proton mail accounts, zillion Gmail accounts, just to get the freebie. Um, they're like, they're, they'll do subscriptions, but not a lot. So the generational piece on the human side is huge. Okay. And then you got the standards, bodies thrown away, things like cookies. Sure. So all this is makes it for a complicated, messy situation. Um, so out of this has to come a billion dollar startup in my mind, >>I, I think multiple billion dollars, but I think you're right in the sense that how we want engage with the company branch, either consumer brands or business brands, no one wants to pick a phone anymore. Right? Everybody wants to either chat or DM people on Twitter. So number one, the, the way we engage is different, both, um, where both, how like chat or phone, but where like mobile device, but also when it's the moment when we need to talk to a company or brand be it at the store, um, when I'm shopping in real life or in my car or at the airport, like we want to reach the brands, the brands wanna reach us at the point of decision, the point of support, the point of contact. And then you, you layer upon that the, the playing field, John of privacy security, right? All these data silos in the cloud, the, the, the, the game has changed and become even more complicated with the startup. So the startups are gonna win. Will do, you know, the collect, all the data, make us secure in private, but then reach your customers when and where they want and how they want it. >>So I gotta ask you, because you had a great podcast just this week, published and snowflake had their event going on the data cloud, there's a new kind of SAS platform vibe going on. You're starting to see it play out. Uh, and one of the things I, I noticed on your podcast with the president of Hashi Corp, who was on people should listen to that podcast. It's on gray matter, which is the Greylocks podcast, uh, plug for you guys. He mentioned he mentions the open source dynamic, right? Sure. And, and I like what he, things, he said, he said, software business has changed forever. It's my words. Now he said infrastructure, but I'm saying software in general, more broader infrastructure and software as a category is all open source. One game over no debate. Right. You agree? >>I, I think you said infrastructure specifically starts at open source, but I would say all open source is one more or less because open source is in every bit of software. Right? And so from your operating system to your car, to your mobile phone, open source, not necessarily as a business model or, or, or whatever, we can talk about that. But open source as a way to build software distribute, software consume software has one, right? It is everywhere. So regardless how you make money on it, how you build software, an open source community ha has >>One. Okay. So let's just agree. That's cool. I agree with that. Let's take it to the next level. I'm a company starting a company to sell to big companies who pay. I gotta have a proprietary advantage. There's gotta be a way. And there is, I know you've talked about it, but I have my opinion. There is needs to be a way to be proprietary in a way that allows for that growth, whether it's integration, it's not gonna be on software license or maybe support or new open source model. But how does startups in the MarTech this area in general, when they disrupt or change the category, they gotta get value creation going. What's your take on, on building. >>You can still build proprietary software on top of open source, right? So there's many companies out there, um, you know, in a company called rock set, they've heavily open source technology like Rock's DB under the hood, but they're running a cloud database. That's proprietary snowflake. You talk about them today. You know, it's not open source technology company, but they use open source software. I'm sure in the hoods, but then there's open source companies, data break. So let's not confus the two, you can still build proprietary software. There's just components of open source, wherever we go. So number one is you can still build proprietary IP. Number two, you can get proprietary data sources, right? So I think increasingly you're seeing companies fight. I call this systems intelligence, right, by getting proprietary data, to train your algorithms, to train your recommendations, to train your applications, you can still collect data, um, that other competitors don't have. >>And then it can use the data differently, right? The system of intelligence. And then when you apply the system intelligence to the end user, you can create value, right? And ultimately, especially marketing tech, the highest level, what we call the system of engagement, right? If, if the chat bot the mobile UI, the phone, the voice app, etcetera, if you own the system of engagement, be a slack, or be it, the operating system for a phone, you can also win. So still multiple levels to play John in multiple ways to build proprietary advantage. Um, just gotta own system record. Yeah. System intelligence, system engagement. Easy, right? Yeah. >>Oh, so easy. Well, the good news is the cloud scale and the CapEx funded there. I mean, look at Amazon, they've got a ton of open storage. You mentioned snowflake, but they're getting a proprietary value. P so I need to ask you MarTech in particular, that means it's a data business, which you, you pointed out and we agree. MarTech will be about the data of the workflows. How do you get those workflows what's changing and how these companies are gonna be building? What's your take on it? Because it's gonna be one of those things where it might be the innovation on a source of data, or how you handle two parties, ex handling encrypted data sets. I don't know. Maybe it's a special encryption tool, so we don't know what it is. What's your what's, what's your outlook on this area? >>I, I, I think that last point just said is super interesting, super genius. It's integration or multiple data sources. So I think either one, if it's a data business, do you have proprietary data? Um, one number two with the data you do have proprietary, not how do you enrich the data and do you enrich the data with, uh, a public data set or a party data set? So this could be cookies. It could be done in Brad street or zoom info information. How do you enrich the data? Number three, do you have machine learning models or some other IP that once you collected the data, enriched the data, you know, what do you do with the data? And then number four is once you have, um, you know, that model of the data, the customer or the business, what do you deal with it? Do you email, do you do a tax? >>Do you do a campaign? Do you upsell? Do you change the price dynamically in our customers? Do you serve a new content on your website? So I think that workflow to your point is you can start from the same place, what to do with the data in between and all the, on the out the side of this, this pipeline is where a MarTech company can have then. So like I said before, it was a website to an email go to website. You know, we have a cookie fill out a form. Yeah. I send you an email later. I think now you, you can't just do a website to email, it's a website plus mobile apps, plus, you know, in real world interaction to text message, chat, phone, call Twitter, a whatever, you know, it's >>Like, it's like, they're playing checkers in web two and you're talking 3d chess. <laugh>, I mean, there's a level, there's a huge gap between what's coming. And this is kind of interesting because now you mentioned, you know, uh, machine learning and data, and AI is gonna factor into all this. You mentioned, uh, you know, rock set. One of your portfolios has under the hood, you know, open source and then use proprietary data and cloud. Okay. That's a configuration, that's an architecture, right? So architecture will be important in terms of how companies posture in this market, cuz MarTech is ripe for innovation because it's based on these old technologies, but there's tons of workflows, but you gotta have the data. Right. And so if I have the best journey map from a client that goes to a website, but then they go and they do something in the organic or somewhere else. If I don't have that, what good is it? It's like a blind spot. >>Correct. So I think you're seeing folks with the data BS, snowflake or data bricks, or an Amazon that S three say, Hey, come to my data cloud. Right. Which, you know, Snowflake's advertising, Amazon will say the data cloud is S3 because all your data exists there anyway. So you just, you know, live on S3 data. Bricks will say, S3 is great, but only use Amazon tools use data bricks. Right. And then, but on top of that, but then you had our SaaS companies like Oracle, Salesforce, whoever, and say, you know, use our qua Marketo, exact target, you know, application as a system record. And so I think you're gonna have a battle between, do I just work my data in S3 or where my data exists or gonna work my data, some other application, like a Marketo Ella cloud Z target, um, or, you know, it could be a Twilio segment, right. Was combination. So you'll have this battle between these, these, these giants in the cloud, easy, the castles, right. Versus, uh, the, the, the, the contenders or the, or the challengers as we call >>'em. Well, great. Always chat with the other. We always talk about castles in the cloud, which is your work that you guys put out, just an update on. So check out greylock.com. They have castles on the cloud, which is a great thesis on and a map by the way ecosystem. So you guys do a really good job props to Jerry and the team over at Greylock. Um, okay. Now I gotta ask kind of like the VC private equity sure. Market question, you know, evaluations. Uh, first of all, I think it's a great time to do a startup. So it's a good time to be in the VC business. I think the next two years, you're gonna find some nice gems, but also you gotta have that cleansing period. You got a lot of overvaluation. So what happened with the markets? So there's gonna be a lot of M and a. So the question is what are some of the things that you see as challenges for product teams in particular that might have that killer answer in MarTech, or might not have the runway if there's no cash, um, how do people partner in this modern era, cuz scale's a big deal, right? Mm-hmm <affirmative> you can measure everything. So you get the combination of a, a new kind of M and a market coming, a potential growth market for the right solution. Again, value's gotta be be there. What's your take on this market? >>I, I, I think you're right. Either you need runway, so cash to make it through, through this next, you know, two, three years, whatever you think the market Turmo is or two, you need scale, right? So if you're at a company of scale and you have enough data, you can probably succeed on your own. If not, if you're kind of in between or early to your point, either one focus, a narrower wedge, John, just like we say, just reduce the surface area. And next two years focus on solving one problem. Very, very well, or number two in this MarTech space, especially there's a lot of partnership and integration opportunities to create a complete solution together, to compete against kind of the incumbents. Right? So I think they're folks with the data, they're folks doing data, privacy, security, they're post focusing their workflow or marketing workflows. You're gonna see either one, um, some M and a, but I definitely can see a lot of Coopers in partnership. And so in the past, maybe you would say, I'm just raise another a hundred million dollars and do what you're doing today. You might say, look, instead of raising more money let's partner together or, or merge or find a solution. So I think people are gonna get creative. Yeah. Like said scarcity often is good. Yeah. I think forces a lot more focus and a lot more creativity. >>Yeah. That's a great point. I'm glad you brought that up up. Cause I didn't think you were gonna go there. I was gonna ask that biz dev activity is going to be really fundamental because runway combined with the fact that, Hey, you know, if you know, get real or you're gonna go under is a real issue. So now people become friends. They're like, okay, if we partner, um, it's clearly a good way to go if you can get there. So what advice would you give companies? Um, even most experienced, uh, founders and operators. This is a different market, right? It's a different kind of velocity, obviously architectural data. You mentioned some of those key things. What's the posture to partner. What's your advice? What's the combat man manual to kind of compete in this new biz dev world where some it's a make or break time, either get the funding, get the customers, which is how you get funding or you get a biz dev deal where you combine forces, uh, go to market together or not. What's your advice? >>I, I think that the combat manual is either you're partnering for one or two things, either one technology or two customers or sometimes both. So it would say which partnerships, youre doing for technology EG solution completers. Like you have, you know, this puzzle piece, I have this puzzle piece data and data privacy and let's work together. Um, or number two is like, who can help you with customers? And that's either a, I, they can be channel for you or, or vice versa or can share customers and you can actually go to market together and find customers jointly. So ideally you're partner for one, if not the other, sometimes both. And just figure out where in your life cycle do you need? Um, friends. >>Yeah. Great. My final question, Jerry, first of all, thanks for coming on and sharing your in insight as usual. Always. Awesome final question for the folks watching that are gonna be partnering and buying product and services from these startups. Um, there's a select few great ones here and obviously every other episode as well, and you've got a bunch you're investing in this, it's actually a good market for the ones that are lean companies that are lean and mean have value. And the cloud scale does provide that. So a lot of companies are getting it right, they're gonna break through. So they're clearly gonna be getting customers the buyer side, how should they be looking through the lens right now and looking at companies, what should they look for? Um, and they like to take chances with seeing that. So it's not so much, they gotta be vetted, but you know, how do they know the winners from the pretenders? >>You know, I, I think the customers are always smart. I think in the, in the, in the past in market market tech, especially they often had a budget to experiment with. I think you're looking now the customers, the buyer technologies are looking for a hard ROI, like a return on investment. And before think they might experiment more, but now they're saying, Hey, are you gonna help me save money or increase revenue or some hardcore metric that they care about? So I think, um, the startups that actually have a strong ROI, like save money or increased revenue and can like point empirically how they do that will, will, you know, rise to the top of, of the MarTech landscape. And customers will see that they're they're, the customers are smart, right? They're savvy buyers. They, they, they, they, they can smell good from bad and they're gonna see the strong >>ROI. Yeah. And the other thing too, I like to point out, I'd love to get your reaction real quick is a lot of the companies have DNA, any open source or they have some community track record where communities now, part of the vetting. I mean, are they real good people? >>Yeah. I, I think open stores, like you said, in the community in general, like especially all these communities that move on slack or discord or something else. Right. I think for sure, just going through all those forums, slack communities or discord communities, you can see what's a good product versus next versus bad. Don't go to like the other sites. These communities would tell you who's working. >>Well, we got a discord channel on the cube now had 14,000 members. Now it's down to six, losing people left and right. We need a moderator, um, to get on. If you know anyone on discord, anyone watching wants to volunteer to be the cube discord, moderator. Uh, we could use some help there. Love discord. Uh, Jerry. Great to see you. Thanks for coming on. What's new at Greylock. What's some of the things happening. Give a quick plug for the firm. When you guys working on, I know there's been some cool things happening, new investments, people moving. >>Yeah. Look we're we're Greylock partners, seed series a firm. I focus at enterprise software. I have a team with me that also does consumer investing as well as crypto investing like all firms. So, but we're we're seed series a occasionally later stage growth. So if you're interested, uh, FA me@jkontwitterorjgreylock.com. Thank you, John. >>Great stuff, Jerry. Thanks for coming on. This is the Cube's presentation of the, a startup showcase. MarTech is the series this time, emerging cloud scale customer experience where the integration and the data matters. This is season two, episode three of the ongoing series covering the hottest cloud startups from the ADWS ecosystem. Um, John farrier, thanks for watching.

Published Date : Jun 29 2022

SUMMARY :

the cloud AWS ecosystem to talk about the future and what's available now, where are the actions? I appreciate you welcome there for season two. <laugh>, you know, Hey, you know, season two, it's not a one and done it's continued coverage. And so the coverage you did last season, all the events of this season is, So now you start to see every vertical kind of explode with the right digital transformation So sources of data have increases and the fruits of the data where you can reach your And then you got the standards, bodies thrown away, things like cookies. Will do, you know, Uh, and one of the things I, I noticed on your podcast with the president of Hashi Corp, So regardless how you make money on it, how you build software, But how does startups in the MarTech this area So let's not confus the two, you can still build proprietary software. or be it, the operating system for a phone, you can also win. might be the innovation on a source of data, or how you handle two parties, So I think either one, if it's a data business, do you have proprietary data? Do you serve a new content on your website? You mentioned, uh, you know, rock set. So you just, you know, live on S3 data. So you get the combination of a, a new kind of M and a market coming, a potential growth market for the right And so in the past, maybe you would say, I'm just raise another a hundred million dollars and do what you're doing today. get the customers, which is how you get funding or you get a biz dev deal where you combine forces, And that's either a, I, they can be channel for you or, or vice versa or can share customers and So it's not so much, they gotta be vetted, but you know, will, will, you know, rise to the top of, of the MarTech landscape. part of the vetting. just going through all those forums, slack communities or discord communities, you can see what's a If you know anyone on discord, So if you're interested, MarTech is the series this time, emerging cloud scale customer experience where the integration

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
MarTechORGANIZATION

0.99+

JohnPERSON

0.99+

JerryPERSON

0.99+

Jerry ChenPERSON

0.99+

AmazonORGANIZATION

0.99+

GreylockORGANIZATION

0.99+

CapExORGANIZATION

0.99+

2013DATE

0.99+

14,000 membersQUANTITY

0.99+

AWSORGANIZATION

0.99+

oneQUANTITY

0.99+

OracleORGANIZATION

0.99+

twoQUANTITY

0.99+

Brad streetLOCATION

0.99+

bothQUANTITY

0.99+

three yearsQUANTITY

0.99+

10 yearsQUANTITY

0.99+

two customersQUANTITY

0.99+

ADWSORGANIZATION

0.99+

12 yearsQUANTITY

0.99+

two partiesQUANTITY

0.99+

John farrierPERSON

0.98+

TodayDATE

0.98+

billion dollarsQUANTITY

0.98+

todayDATE

0.98+

S3TITLE

0.98+

SalesforceORGANIZATION

0.98+

3OTHER

0.97+

TwitterORGANIZATION

0.97+

two thingsQUANTITY

0.97+

Hashi CorpORGANIZATION

0.97+

John furPERSON

0.97+

GreylockPERSON

0.97+

VMwareORGANIZATION

0.96+

one problemQUANTITY

0.96+

this weekDATE

0.96+

TurmoORGANIZATION

0.95+

OneQUANTITY

0.95+

GreylocksPERSON

0.95+

4OTHER

0.94+

One gameQUANTITY

0.94+

5OTHER

0.93+

80QUANTITY

0.92+

firstQUANTITY

0.92+

CubORGANIZATION

0.91+

SnowflakeORGANIZATION

0.91+

greylock.comOTHER

0.91+

billion dollarQUANTITY

0.91+

season twoQUANTITY

0.91+

RockORGANIZATION

0.91+

TwilioORGANIZATION

0.9+

EquaORGANIZATION

0.9+

zillionQUANTITY

0.9+

GmailTITLE

0.9+

theCUBE Insights | Snowflake Summit 2022


 

(upbeat music) >> Hey everyone, welcome back to theCUBE's three day coverage of Snowflake Summit 22. Lisa Martin here with Dave Vellante. We have been here as I said for three days. Dave, we have had an amazing three days. The energy, the momentum, the number of people still here speaks volumes for- >> Yeah, I was just saying, you look back, theCUBE, when it started, early days was a big part of the Hadoop ecosystem. You know Cloudera kind of got it started, the whole big data movement, it was awesome energy, and that whole ecosystem has been, I think, just hoovered into the Snowflake ecosystem. They've taken over as the data company, the data cloud, I mean, that was Cloudera, it could have been Cloudera, and now they didn't, they missed it, it was a variety of factors, but Snowflake has nailed it. And now it's theirs to lose. Benoit talked about that on our previous segment, how he knew that technically Hadoop was too complex, and was going to fail, and they didn't know it was going to do this. They were going to turn their company into what we see here. But the event itself, Lisa, is almost 10,000 people, the right people, people are doing business, we've had a number of people tell us that they're booking deals. That's why people come to face-to-face shows, right? That's the criticism of virtual. It takes too long to close business. Salespeople want to be belly-to-belly. And this is a belly-to belly-show. >> It absolutely is. When you and I were trying to get into the keynote on Tuesday, we finally got in standing room only, multiple overflow rooms, and we're even hearing that, so this is day four of the summit for them, there are still queues to get into breakout sessions. The momentum, but the appetite for this flywheel, and what they're creating, but also they're involving this massively growing ecosystem in its evolution. It's that synergy was really very much heard, and echoed throughout pretty much all of our segments the last couple days. >> Yeah, it was amazing actually. So we like to go, we want to be in the front row in the keynotes, we're taking notes, we always do that. Sometimes we listen remotely, but when you listen remotely, you miss some things. When you're there, you can see the executives, you can feel their energy, you can chit chat to them on the side, be seen, whatever. And it was crazy, we couldn't get in. So we had to do our thing, and sneak our way in, and "Hey, we're media." "Oh yeah, come on in." And then no, they were taking us to a breakout room. We had to sneak in a side door, got like the last two seats, and wow, I'm glad we were in there because it gave us a better sense. When you're in the remote watching rooms you just can't get a sense of the energy. That's why I like to be there, I know you do too. And then to your point about ecosystem. So we've said many times that what Snowflake is developing is what we call supercloud. It's not just a SaaS, it's not just a cloud database, it's a new layer that they're creating. And so what are the attributes of that layer? Well, it hides the underlying complexity of the underlying primitives of the cloud. We've said that ad nauseam, and it adds new value on top. Well, what's that value that they're adding? Well, they're adding value of being able to share data, collaborate, have data that's governed, and secure, globally. And now the other hallmark of a cloud company is ecosystem. And so they're building that ecosystem much more rapidly than we saw at ServiceNow, which is Slootman's previous company. And the key to me is they've launched an application development platform, essentially a super PaaS, so that you can develop applications on top of the data cloud. And we're hearing tons about monetization. Duh, you could actually make money with data. You can package data into data products, and data services, or feed data products and services, and actually sell that in a cloud, in a supercloud. That's exactly what's happening here. So that's critical. I think my one question mark if I had to lay one out, is the other hallmark of a cloud is startup, startups come into that cloud. And I think we're seeing that, maybe not at the pace that AWS did, it's a little different. Snowflake are, they're whale hunters. They're after big companies. But it looks to me like they're relying on the ecosystem to be the startup innovators. That's the important thing about cloud, cloud brings scale. It definitely brings lower cost 'cause you're eliminating all this undifferentiated labor, but it also brings innovation through startups. So unlike AWS, who sold the startups directly, and startups built businesses on AWS, and by paying AWS, it's a little bit indirect, but it's actually happening where startups in the ecosystem are building products on the data cloud, and that ultimately is going to drive value for customers, and money for Snowflake, and ultimately AWS, and Google, and Azure. The other thing I would say is the criticism or concern that the cost of goods sold for cloud are going to be so high that it's going to force people to come back on-prem. I think it's a step in the wrong direction. I think cloud, and the cloud operating model is here to stay. I think it's going to be very difficult to replicate that on-prem. I don't think you can do cloud without cloud, and we'll see what the edge brings. >> Curious what your thoughts are. We were just at Dell technologies world a month or so ago when the big announcement, the Snowflake partnership there, cloud native companies recognizing, ah, there's still a lot of data that lives on-prem. Given that, and everything that we've heard the last couple of days, what are your thoughts around that and their partnerships there? >> So Dell is, I think finally, now maybe they weren't publicly talking like this, but certainly their marketing was defensive. But in the last year or so, Dell has really embraced cloud, not just the cloud operating model, Dell has said, "Look, we can build value on top of all these hyperscalers." And we saw some examples at Dell Tech World of them stepping their toe into supercloud. Project Alpine is an example, and there are others. And then of course the Snowflake deal, where Snowflake and Dell got together, I asked Frank Slootman how that deal came about. And 'cause I said, "Did the customer get you into a headlock?" 'Cause I presume that was the case. Customer said, "You got to do this or we're not going to do business with you." He said, "Well, no, not really. Michael and I had a chat, and that's how it started." Which was my other scenario, and that's exactly what happened I guess. The point being that those worlds are coming together. And so what it means for Dell is as they embrace cloud, as they develop supercloud capabilities, they're going to do a lot of business. Dell for sure knows how to sell, they know how to execute. What I would be doing if I were Dell, is I would be trying to substantially replicate what's happening in the cloud on-prem with on-prem data. So what happens with that Snowflake deal is, it's read-only data, you read the data into the cloud, the compute is in the cloud. And I should've asked Terry this, I mean Benoit. Can there be an architecture on-prem? We've seen at Vertica has one, it's called Vertica Eon where you separate compute from storage. It doesn't have unlimited elasticity, but you can grow, compute, and storage independently, and have a lot more. With Dell doing APEX on demand, it's cloudlike, they could begin to develop a little mini data cloud, or a big data cloud within on-prem that connects to the public cloud. So what Snowflake is missing, a big part of their TAM that they're missing is the on-prem. The Dell and Pure deals are forays into that, but this on-prem is massive, and Dell is the on-prem poster child. So I think again what it means for them is they've got to continue to embrace it, they got to do more in software, more in data management, they got to push on APEX. And I'd say the same thing for HPE. I think they're both well behind this in terms of ecosystems. I mean they're not even close. But they have to start, and they got to start somewhere, and they've got resources to make it happen. >> You said in your breaking analysis that you published just a few days ago before the event that Snowflake plans to create a de facto standard in data platforms. What we heard from our guests on this program, your mainstage session with Frank Slootman. Still think that? >> I do. I think it more than I believed it coming in. And the reason I called it that is because I am a super fan of Zhamak Dehghani and her data mesh. And what her vision is, it's kind of the Immaculate Conception, where she wants everything to be open, open standards, and those don't exist today. And I think she perfectly realizes the practicality of de facto standards are going to get to market, and add value sooner than open standards. Now open standards over time, and I'll come back to that, may occur, but that's clear to me what Snowflake is creating, is the de facto standard for data platforms, the data cloud, the supercloud. And what's most impressive, or I think really important, is they're layering applications now on top of that. The metric to me, and I don't know if we can even count this, but VMware used to use it. For every dollar spent on VMware license, $15 was spent in the ecosystem. It started at 1 to 1.5, 1 to 2, 1 to 10, 1 to 15, I think it went up to 1 to 30 at the max. I don't know how they counted that, but it's countable. Reasonable people can make estimates like that. And I think as the ecosystem grows, what Snowflake's doing is it's in many respects modeling the cloud, what the cloud has. Cloud has ecosystems, we talked about startups, and the cloud also has optionality. And optionality means open source. So what you saw with Apache Iceberg is we're going to extend to open technologies. What you saw with Hybrid tables is we're going to extend a new workloads like transactions. The other thing about Snowflake that's really impressive is you're seeing the vertical focus. Financial services, healthcare, retail, media and entertainment. It's very rare for a company in this tenure, they're only 10 years old, to really start going vertical with their go-to-market, and building expertise around that. I think what's going to happen is the GSIs are going to come in, they love to eat at the trough, the trough here is maybe not big enough for them yet, but it will be. And they're going to start to align with the GSIs, and they're going to do really well within those industries, connecting people, collaborating with data. But I think it's a killer strategy, but they're executing on it. >> Right, and we heard a lot of great customer stories from all of those four verticals that you talked about, and then some, that that direction and that pivot from a customer perspective, from a sales and marketing perspective is all aligned. And that was kind of one of the themes as well that Frank talked about in his keynote is mission alignment, mission alignment with customers, but also with the ecosystem. And I feel that I heard that with every customer conversation, with every partner conversation, and Snowflake conversation that we had over the last I think 36 segments, Dave. >> Yeah, I mean, yeah, it's the power of many versus the resources of one. And even though Snowflake tell you they have $5 billion in cash, and assets on the balance sheet, and that's fine, that's nothing compared to what an ecosystem has. And Amazon's part of that ecosystem. Azure is part of that ecosystem. Google is part of that ecosystem. Those companies have huge resources, and Snowflake it seems has figured out how to tap those resources, and build value on top of it. To me they're doing a better job than a lot of the cloud databases out there. They don't necessarily have a better database, in fact, I could argue that their database is less functional. And I would argue that actually in many cases. Their database is less functional if you just want a database. But if you want a data cloud, and an ecosystem, and develop applications on top of that, and to be able to monetize, that's unique, and that is a moat that they're building that is highly differentiable, and being able to do that relatively easily. I mean, I think they overstate the simplicity with which that is being done. We talked to some customers who said, he didn't say same wine, new bottle. I did ask him that, about Hadoop complexity. And he said, "No, it's not that bad." But you still got to put this stuff together. And I think in the early parts of a market that are immature, people get really excited because it's so much easier than what was previous. So my other question is, okay, what's somebody working on now, that's looking at what Snowflake's doing and saying, I can improve on that. And what's going to be really interesting to see is, can they improve on it in a way, and can they raise enough capital such that they can disrupt, or is Snowflake going to keep staying paranoid, 'cause they got good leaders, and keep executing? And then I think the other wild card is edge. Snowflake doesn't really have an edge strategy right now. I think they will develop one. >> Through the ecosystem? >> And I don't think they're missing the boat, and they'll do it through the ecosystem, exactly. I don't think they're missing the boat, I think they're just like, "Well, we don't know what to do today." It's all distributed data, and it's ephemeral, and nobody's storing the data. You know anything that comes back to the cloud, we get. But new architectures are emerging on the edge that are going to bring new economics. There's new silicon, you see what's happening with Apple, and the M1, the M1 Ultra, and the new systems that they've just developed. What Tesla is doing with custom silicon, and amazing things, and programmability of the arm model. So it's early days, but semiconductors are the mainspring of innovation in this industry. Without chips, you got nothing. And when you get innovations in silicon, it drives innovations in software, because developers go, "Wow, I can do that now?" I can do things in parallel, I can do things faster, I can do things more simply, and programmable at scale. So that's happening. And that's going to bring a new set of economics that the premise is that will eventually bleed into the data center. It will, it always does. And I guess the other thing is every 15 years or so, the world gets disrupted, the tech world. We're about 15, 16 years in now to the cloud. So at this point, everybody's like, "Wow this is insurmountable, this is all we'll ever see. Everything that's ever been invented, this is the model of the future." We know that's not the case. I don't know how it's going to get disrupted, but I think edge is going to be part of that. It could be public policy. Governments could come in and take big tech on, seems like Sharekhan wants to do that. So that's what makes this industry so fun. >> Never a dull moment, Dave. This has been a great three days hosting this show with you. We've uncovered a lot. Your breaking analysis was great to get me prepared for the show. If you haven't seen it, check it out on siliconangle.com. Thanks, Dave, I appreciate all of your insights. >> Thank you, Lisa, It's been a pleasure working with you. >> Always good to work with you. >> Awesome, great job. >> Likewise. Great job to the team. >> Yes, thank you to our awesome production team. They've kept us going for three days. >> Yes, and the team back, Kristin, and Cheryl, and everybody back at the office. >> Exactly, it takes a village. For Dave Vellante, I am Lisa Martin. We are wrappin' up three days of wall-to-wall coverage at Snowflake Summit 22 from Vegas. Thanks for watching guys, we'll see you soon. (upbeat music)

Published Date : Jun 17 2022

SUMMARY :

The energy, the momentum, And now it's theirs to lose. The momentum, but the And the key to me is they've launched the last couple of days, and Dell is the on-prem poster child. that Snowflake plans to is the GSIs are going to come in, And I feel that I heard that and assets on the balance And I guess the other thing to get me prepared for the show. a pleasure working with you. Great job to the team. Yes, thank you to our Yes, and the team guys, we'll see you soon.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
Frank SlootmanPERSON

0.99+

MichaelPERSON

0.99+

KristinPERSON

0.99+

Lisa MartinPERSON

0.99+

DavePERSON

0.99+

Dave VellantePERSON

0.99+

CherylPERSON

0.99+

AmazonORGANIZATION

0.99+

FrankPERSON

0.99+

TerryPERSON

0.99+

LisaPERSON

0.99+

AWSORGANIZATION

0.99+

Zhamak DehghaniPERSON

0.99+

DellORGANIZATION

0.99+

$15QUANTITY

0.99+

$5 billionQUANTITY

0.99+

VerticaORGANIZATION

0.99+

TuesdayDATE

0.99+

VegasLOCATION

0.99+

BenoitPERSON

0.99+

three daysQUANTITY

0.99+

GoogleORGANIZATION

0.99+

TeslaORGANIZATION

0.99+

Apache IcebergORGANIZATION

0.99+

three dayQUANTITY

0.99+

Snowflake Summit 22EVENT

0.99+

last yearDATE

0.99+

AppleORGANIZATION

0.99+

three daysQUANTITY

0.99+

1QUANTITY

0.99+

SnowflakeORGANIZATION

0.99+

15QUANTITY

0.98+

36 segmentsQUANTITY

0.98+

30QUANTITY

0.98+

1.5QUANTITY

0.98+

M1 UltraCOMMERCIAL_ITEM

0.98+

10QUANTITY

0.98+

todayDATE

0.98+

theCUBEORGANIZATION

0.97+

siliconangle.comOTHER

0.97+

bothQUANTITY

0.97+

Snowflake Summit 2022EVENT

0.97+

2QUANTITY

0.96+

ClouderaORGANIZATION

0.96+

M1COMMERCIAL_ITEM

0.94+

Vertica EonORGANIZATION

0.94+

two seatsQUANTITY

0.94+

Dell Tech WorldORGANIZATION

0.92+

few days agoDATE

0.92+

one questionQUANTITY

0.91+

oneQUANTITY

0.91+

ServiceNowORGANIZATION

0.91+

upQUANTITY

0.9+

VMwareORGANIZATION

0.9+

10 years oldQUANTITY

0.89+

TAMORGANIZATION

0.87+

four verticalsQUANTITY

0.85+

almost 10,000 peopleQUANTITY

0.84+

a month or so agoDATE

0.83+

last couple of daysDATE

0.82+

theCUBE Insights with Industry Analysts | Snowflake Summit 2022


 

>>Okay. Okay. We're back at Caesar's Forum. The Snowflake summit 2022. The cubes. Continuous coverage this day to wall to wall coverage. We're so excited to have the analyst panel here, some of my colleagues that we've done a number. You've probably seen some power panels that we've done. David McGregor is here. He's the senior vice president and research director at Ventana Research. To his left is Tony Blair, principal at DB Inside and my in the co host seat. Sanjeev Mohan Sanremo. Guys, thanks so much for coming on. I'm glad we can. Thank you. You're very welcome. I wasn't able to attend the analyst action because I've been doing this all all day, every day. But let me start with you, Dave. What have you seen? That's kind of interested you. Pluses, minuses. Concerns. >>Well, how about if I focus on what I think valuable to the customers of snowflakes and our research shows that the majority of organisations, the majority of people, do not have access to analytics. And so a couple of things they've announced I think address those are helped to address those issues very directly. So Snow Park and support for Python and other languages is a way for organisations to embed analytics into different business processes. And so I think that will be really beneficial to try and get analytics into more people's hands. And I also think that the native applications as part of the marketplace is another way to get applications into people's hands rather than just analytical tools. Because most most people in the organisation or not, analysts, they're doing some line of business function. Their HR managers, their marketing people, their salespeople, their finance people right there, not sitting there mucking around in the data. They're doing a job and they need analytics in that job. So, >>Tony, I thank you. I've heard a lot of data mesh talk this week. It's kind of funny. Can't >>seem to get away from it. You >>can't see. It seems to be gathering momentum, but But what have you seen? That's been interesting. >>What I have noticed. Unfortunately, you know, because the rooms are too small, you just can't get into the data mesh sessions, so there's a lot of interest in it. Um, it's still very I don't think there's very much understanding of it, but I think the idea that you can put all the data in one place which, you know, to me, stuff like it seems to be kind of sort of in a way, it sounds like almost like the Enterprise Data warehouse, you know, Clouded Cloud Native Edition, you know, bring it all in one place again. Um, I think it's providing, sort of, You know, it's I think, for these folks that think this might be kind of like a a linchpin for that. I think there are several other things that actually that really have made a bigger impression on me. Actually, at this event, one is is basically is, um we watch their move with Eunice store. Um, and it's kind of interesting coming, you know, coming from mongo db last week. And I see it's like these two companies seem to be going converging towards the same place at different speeds. I think it's not like it's going to get there faster than Mongo for a number of different reasons, but I see like a number of common threads here. I mean, one is that Mongo was was was a company. It's always been towards developers. They need you know, start cultivating data, people, >>these guys going the other way. >>Exactly. Bingo. And the thing is that but they I think where they're converging is the idea of operational analytics and trying to serve all constituencies. The other thing, which which also in terms of serving, you know, multiple constituencies is how snowflake is laid out Snow Park and what I'm finding like. There's an interesting I economy. On one hand, you have this very ingrained integration of Anaconda, which I think is pretty ingenious. On the other hand, you speak, let's say, like, let's say the data robot folks and say, You know something our folks wanna work data signs us. We want to work in our environment and use snowflake in the background. So I see those kind of some interesting sort of cross cutting trends. >>So, Sandy, I mean, Frank Sullivan, we'll talk about there's definitely benefits into going into the walled garden. Yeah, I don't think we dispute that, but we see them making moves and adding more and more open source capabilities like Apache iceberg. Is that a Is that a move to sort of counteract the narrative that the data breaks is put out there. Is that customer driven? What's your take on that? >>Uh, primarily I think it is to contract this whole notion that once you move data into snowflake, it's a proprietary format. So I think that's how it started. But it's hugely beneficial to the customers to the users, because now, if you have large amounts of data in parquet files, you can leave it on s three. But then you using the the Apache iceberg table format. In a snowflake, you get all the benefits of snowflakes. Optimizer. So, for example, you get the, you know, the micro partitioning. You get the meta data. So, uh, in a single query, you can join. You can do select from a snowflake table union and select from iceberg table, and you can do store procedures, user defined functions. So I think they what they've done is extremely interesting. Uh, iceberg by itself still does not have multi table transactional capabilities. So if I'm running a workload, I might be touching 10 different tables. So if I use Apache iceberg in a raw format, they don't have it. But snowflake does, >>right? There's hence the delta. And maybe that maybe that closes over time. I want to ask you as you look around this I mean the ecosystems pretty vibrant. I mean, it reminds me of, like reinvent in 2013, you know? But then I'm struck by the complexity of the last big data era and a dupe and all the different tools. And is this different, or is it the sort of same wine new new bottle? You guys have any thoughts on that? >>I think it's different and I'll tell you why. I think it's different because it's based around sequel. So if back to Tony's point, these vendors are coming at this from different angles, right? You've got data warehouse vendors and you've got data lake vendors and they're all going to meet in the middle. So in your case, you're taught operational analytical. But the same thing is true with Data Lake and Data Warehouse and Snowflake no longer wants to be known as the Data Warehouse. There a data cloud and our research again. I like to base everything off of that. >>I love what our >>research shows that organisation Two thirds of organisations have sequel skills and one third have big data skills, so >>you >>know they're going to meet in the middle. But it sure is a lot easier to bring along those people who know sequel already to that midpoint than it is to bring big data people to remember. >>Mrr Odula, one of the founders of Cloudera, said to me one time, John Kerry and the Cube, that, uh, sequel is the killer app for a Yeah, >>the difference at this, you know, with with snowflake, is that you don't have to worry about taming the zoo. Animals really have thought out the ease of use, you know? I mean, they thought about I mean, from the get go, they thought of too thin to polls. One is ease of use, and the other is scale. And they've had. And that's basically, you know, I think very much differentiates it. I mean, who do have the scale, but it didn't have the ease of use. But don't I >>still need? Like, if I have, you know, governance from this vendor or, you know, data prep from, you know, don't I still have to have expertise? That's sort of distributed in those those worlds, right? I mean, go ahead. Yeah. >>So the way I see it is snowflake is adding more and more capabilities right into the database. So, for example, they've they've gone ahead and added security and privacy so you can now create policies and do even set level masking, dynamic masking. But most organisations have more than snowflake. So what we are starting to see all around here is that there's a whole series of data catalogue companies, a bunch of companies that are doing dynamic data masking security and governance data observe ability, which is not a space snowflake has gone into. So there's a whole ecosystem of companies that that is mushrooming, although, you know so they're using the native capabilities of snowflake, but they are at a level higher. So if you have a data lake and a cloud data warehouse and you have other, like relational databases, you can run these cross platform capabilities in that layer. So so that way, you know, snowflakes done a great job of enabling that ecosystem about >>the stream lit acquisition. Did you see anything here that indicated there making strong progress there? Are you excited about that? You're sceptical. Go ahead. >>And I think it's like the last mile. Essentially. In other words, it's like, Okay, you have folks that are basically that are very, very comfortable with tableau. But you do have developers who don't want to have to shell out to a separate tool. And so this is where Snowflake is essentially working to address that constituency, um, to San James Point. I think part of it, this kind of plays into it is what makes this different from the ado Pere is the fact that this all these capabilities, you know, a lot of vendors are taking it very seriously to make put this native obviously snowflake acquired stream. Let's so we can expect that's extremely capabilities are going to be native. >>And the other thing, too, about the Hadoop ecosystem is Claudia had to help fund all those different projects and got really, really spread thin. I want to ask you guys about this super cloud we use. Super Cloud is this sort of metaphor for the next wave of cloud. You've got infrastructure aws, azure, Google. It's not multi cloud, but you've got that infrastructure you're building a layer on top of it that hides the underlying complexities of the primitives and the a p I s. And you're adding new value in this case, the data cloud or super data cloud. And now we're seeing now is that snowflake putting forth the notion that they're adding a super path layer. You can now build applications that you can monetise, which to me is kind of exciting. It makes makes this platform even less discretionary. We had a lot of talk on Wall Street about discretionary spending, and that's not discretionary. If you're monetising it, um, what do you guys think about that? Is this something that's that's real? Is it just a figment of my imagination, or do you see a different way of coming any thoughts on that? >>So, in effect, they're trying to become a data operating system, right? And I think that's wonderful. It's ambitious. I think they'll experience some success with that. As I said, applications are important. That's a great way to deliver information. You can monetise them, so you know there's there's a good economic model around it. I think they will still struggle, however, with bringing everything together onto one platform. That's always the challenge. Can you become the platform that's hard, hard to predict? You know, I think this is This is pretty exciting, right? A lot of energy, a lot of large ecosystem. There is a network effect already. Can they succeed in being the only place where data exists? You know, I think that's going to be a challenge. >>I mean, the fact is, I mean, this is a classic best of breed versus the umbrella play. The thing is, this is nothing new. I mean, this is like the you know, the old days with enterprise applications were basically oracle and ASAP vacuumed up all these. You know, all these applications in their in their ecosystem, whereas with snowflake is. And if you look at the cloud, folks, the hyper scale is still building out their own portfolios as well. Some are, You know, some hyper skills are more partner friendly than others. What? What Snowflake is saying is that we're going to give all of you folks who basically are competing against the hyper skills in various areas like data catalogue and pipelines and all that sort of wonderful stuff will make you basically, you know, all equal citizens. You know the burden is on you to basically we will leave. We will lay out the A P. I s Well, we'll allow you to basically, you know, integrate natively to us so you can provide as good experience. But the but the onus is on your back. >>Should the ecosystem be concerned, as they were back to reinvent 2014 that Amazon was going to nibble away at them or or is it different? >>I find what they're doing is different. Uh, for example, data sharing. They were the first ones out the door were data sharing at a large scale. And then everybody has jumped in and said, Oh, we also do data sharing. All the hyper scholars came in. But now what snowflake has done is they've taken it to the next level. Now they're saying it's not just data sharing. It's up sharing and not only up sharing. You can stream the thing you can build, test deploy, and then monetise it. Make it discoverable through, you know, through your marketplace >>you can monetise it. >>Yes. Yeah, so So I I think what they're doing is they are taking it a step further than what hyper scale as they are doing. And because it's like what they said is becoming like the data operating system You log in and you have all of these different functionalities you can do in machine learning. Now you can do data quality. You can do data preparation and you can do Monetisation. Who do you >>think is snowflakes? Biggest competitor? What do you guys think? It's a hard question, isn't it? Because you're like because we all get the we separate computer from storage. We have a cloud data and you go, Okay, that's nice, >>but there's, like, a crack. I think >>there's uniqueness. I >>mean, put it this way. In the old days, it would have been you know, how you know the prime household names. I think today is the hyper scholars and the idea what I mean again, this comes down to the best of breed versus by, you know, get it all from one source. So where is your comfort level? Um, so I think they're kind. They're their co op a Titian the hyper scale. >>Okay, so it's not data bricks, because why they're smaller. >>Well, there is some okay now within the best of breed area. Yes, there is competition. The obvious is data bricks coming in from the data engineering angle. You know, basically the snowflake coming from, you know, from the from the data analyst angle. I think what? Another potential competitor. And I think Snowflake, basically, you know, admitted as such potentially is mongo >>DB. Yeah, >>Exactly. So I mean, yes, there are two different levels of sort >>of a on a longer term collision course. >>Exactly. Exactly. >>Sort of service now and in salesforce >>thing that was that we actually get when I say that a lot of people just laughed. I was like, No, you're kidding. There's no way. I said Excuse me, >>But then you see Mongo last week. We're adding some analytics capabilities and always been developers, as you say, and >>they trashed sequel. But yet they finally have started to write their first real sequel. >>We have M c M Q. Well, now we have a sequel. So what >>were those numbers, >>Dave? Two thirds. One third. >>So the hyper scale is but the hyper scale urz are you going to trust your hyper scale is to do your cross cloud. I mean, maybe Google may be I mean, Microsoft, perhaps aws not there yet. Right? I mean, how important is cross cloud, multi cloud Super cloud Whatever you want to call it What is your data? >>Shows? Cloud is important if I remember correctly. Our research shows that three quarters of organisations are operating in the cloud and 52% are operating across more than one cloud. So, uh, two thirds of the organisations are in the cloud are doing multi cloud, so that's pretty significant. And now they may be operating across clouds for different reasons. Maybe one application runs in one cloud provider. Another application runs another cloud provider. But I do think organisations want that leverage over the hyper scholars right they want they want to be able to tell the hyper scale. I'm gonna move my workloads over here if you don't give us a better rate. Uh, >>I mean, I I think you know, from a database standpoint, I think you're right. I mean, they are competing against some really well funded and you look at big Query barely, you know, solid platform Red shift, for all its faults, has really done an amazing job of moving forward. But to David's point, you know those to me in any way. Those hyper skills aren't going to solve that cross cloud cloud problem, right? >>Right. No, I'm certainly >>not as quickly. No. >>Or with as much zeal, >>right? Yeah, right across cloud. But we're gonna operate better on our >>Exactly. Yes. >>Yes. Even when we talk about multi cloud, the many, many definitions, like, you know, you can mean anything. So the way snowflake does multi cloud and the way mongo db two are very different. So a snowflake says we run on all the hyper scalar, but you have to replicate your data. What Mongo DB is claiming is that one cluster can have notes in multiple different clouds. That is right, you know, quite something. >>Yeah, right. I mean, again, you hit that. We got to go. But, uh, last question, um, snowflake undervalued, overvalued or just about right >>in the stock market or in customers. Yeah. Yeah, well, but, you know, I'm not sure that's the right question. >>That's the question I'm asking. You know, >>I'll say the question is undervalued or overvalued for customers, right? That's really what matters. Um, there's a different audience. Who cares about the investor side? Some of those are watching, but But I believe I believe that the from the customer's perspective, it's probably valued about right, because >>the reason I I ask it, is because it has so hyped. You had $100 billion value. It's the past service now is value, which is crazy for this student Now. It's obviously come back quite a bit below its IPO price. So But you guys are at the financial analyst meeting. Scarpelli laid out 2029 projections signed up for $10 billion.25 percent free time for 20% operating profit. I mean, they better be worth more than they are today. If they do >>that. If I If I see the momentum here this week, I think they are undervalued. But before this week, I probably would have thought there at the right evaluation, >>I would say they're probably more at the right valuation employed because the IPO valuation is just such a false valuation. So hyped >>guys, I could go on for another 45 minutes. Thanks so much. David. Tony Sanjeev. Always great to have you on. We'll have you back for sure. Having us. All right. Thank you. Keep it right there. Were wrapping up Day two and the Cube. Snowflake. Summit 2022. Right back. Mm. Mhm.

Published Date : Jun 16 2022

SUMMARY :

What have you seen? And I also think that the native applications as part of the I've heard a lot of data mesh talk this week. seem to get away from it. It seems to be gathering momentum, but But what have you seen? but I think the idea that you can put all the data in one place which, And the thing is that but they I think where they're converging is the idea of operational that the data breaks is put out there. So, for example, you get the, you know, the micro partitioning. I want to ask you as you look around this I mean the ecosystems pretty vibrant. I think it's different and I'll tell you why. But it sure is a lot easier to bring along those people who know sequel already the difference at this, you know, with with snowflake, is that you don't have to worry about taming the zoo. you know, data prep from, you know, don't I still have to have expertise? So so that way, you know, snowflakes done a great job of Did you see anything here that indicated there making strong is the fact that this all these capabilities, you know, a lot of vendors are taking it very seriously I want to ask you guys about this super cloud we Can you become the platform that's hard, hard to predict? I mean, this is like the you know, the old days with enterprise applications You can stream the thing you can build, test deploy, You can do data preparation and you can do We have a cloud data and you go, Okay, that's nice, I think I In the old days, it would have been you know, how you know the prime household names. You know, basically the snowflake coming from, you know, from the from the data analyst angle. Exactly. I was like, No, But then you see Mongo last week. But yet they finally have started to write their first real sequel. So what One third. So the hyper scale is but the hyper scale urz are you going to trust your hyper scale But I do think organisations want that leverage I mean, I I think you know, from a database standpoint, I think you're right. not as quickly. But we're gonna operate better on our Exactly. the hyper scalar, but you have to replicate your data. I mean, again, you hit that. but, you know, I'm not sure that's the right question. That's the question I'm asking. that the from the customer's perspective, it's probably valued about right, So But you guys are at the financial analyst meeting. But before this week, I probably would have thought there at the right evaluation, I would say they're probably more at the right valuation employed because the IPO valuation is just such Always great to have you on.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
DavidPERSON

0.99+

Frank SullivanPERSON

0.99+

TonyPERSON

0.99+

MicrosoftORGANIZATION

0.99+

DavePERSON

0.99+

Tony BlairPERSON

0.99+

Tony SanjeevPERSON

0.99+

AmazonORGANIZATION

0.99+

GoogleORGANIZATION

0.99+

SandyPERSON

0.99+

David McGregorPERSON

0.99+

MongoORGANIZATION

0.99+

20%QUANTITY

0.99+

$100 billionQUANTITY

0.99+

Ventana ResearchORGANIZATION

0.99+

2013DATE

0.99+

last weekDATE

0.99+

52%QUANTITY

0.99+

Sanjeev Mohan SanremoPERSON

0.99+

more than one cloudQUANTITY

0.99+

2014DATE

0.99+

2029 projectionsQUANTITY

0.99+

two companiesQUANTITY

0.99+

45 minutesQUANTITY

0.99+

San James PointLOCATION

0.99+

$10 billion.25 percentQUANTITY

0.99+

one applicationQUANTITY

0.99+

OdulaPERSON

0.99+

John KerryPERSON

0.99+

PythonTITLE

0.99+

Summit 2022EVENT

0.99+

Data WarehouseORGANIZATION

0.99+

SnowflakeEVENT

0.98+

ScarpelliPERSON

0.98+

Data LakeORGANIZATION

0.98+

one platformQUANTITY

0.98+

this weekDATE

0.98+

todayDATE

0.98+

10 different tablesQUANTITY

0.98+

three quartersQUANTITY

0.98+

oneQUANTITY

0.97+

ApacheORGANIZATION

0.97+

Day twoQUANTITY

0.97+

DB InsideORGANIZATION

0.96+

one placeQUANTITY

0.96+

one sourceQUANTITY

0.96+

one thirdQUANTITY

0.96+

Snowflake Summit 2022EVENT

0.96+

One thirdQUANTITY

0.95+

two thirdsQUANTITY

0.95+

ClaudiaPERSON

0.94+

one timeQUANTITY

0.94+

one cloud providerQUANTITY

0.94+

Two thirdsQUANTITY

0.93+

theCUBEORGANIZATION

0.93+

data lakeORGANIZATION

0.92+

Snow ParkLOCATION

0.92+

ClouderaORGANIZATION

0.91+

two different levelsQUANTITY

0.91+

threeQUANTITY

0.91+

one clusterQUANTITY

0.89+

single queryQUANTITY

0.87+

awsORGANIZATION

0.84+

first onesQUANTITY

0.83+

Snowflake summit 2022EVENT

0.83+

azureORGANIZATION

0.82+

mongo dbORGANIZATION

0.82+

OneQUANTITY

0.81+

Eunice storeORGANIZATION

0.8+

wave ofEVENT

0.78+

cloudORGANIZATION

0.77+

first real sequelQUANTITY

0.77+

M c M Q.PERSON

0.76+

Red shiftORGANIZATION

0.74+

AnacondaORGANIZATION

0.73+

SnowflakeORGANIZATION

0.72+

ASAPORGANIZATION

0.71+

SnowORGANIZATION

0.68+

snowflakeTITLE

0.66+

ParkTITLE

0.64+

CubeCOMMERCIAL_ITEM

0.63+

ApacheTITLE

0.63+

MrrPERSON

0.63+

senior vice presidentPERSON

0.62+

Wall StreetORGANIZATION

0.6+

Steve McDowell, Moor Insights & Strategy | At Your Storage Service


 

(upbeat music) >> We're back with Steve McDowell, the Principal Analyst for Data & Storage at Moor Insights and Strategy. Hey Steve, great to have you on. Tell us a little bit about yourself. You've got a really interesting background and kind of a blend of engineering and strategy and what's your research focus? >> Yeah, so my research, my focus area is data and storage and all the things around that, whether it's On-Prem or Cloud or, you know, software as a service. My background, as you said, is a blend, right? I grew up as an engineer. I started off as an OS developer at IBM. I came up through the ranks and shifted over into corporate strategy and product marketing and product management, and I have been doing working as an industry analyst now for about five years at Moor Insights and Strategy. >> Steve, how do you see this playing out in the next three to five years? I mean, cloud got it all started, it's going to snowballing. You know, however you look at it percent of spending on storage that you think is going to land in as a service. How do you see the evolution here? >> IT buyers are looking at as a service and consumption base is, you know, a natural model. It extends the data center, brings all of the flexibility all of the goodness that I get from public cloud, but without all of the downside and uncertainty on cost and security and things like that, right, that also come with the public cloud and it's delivered by technology providers that I trust and that I know, and that I worked with, you know, for, in some cases, decades. So, I don't know that we have hard data on how much adoption there is of the model, but we do know that it's trending up, you know and every infrastructure provider at this point has some flavor of offering in the space. So, it's clearly popular with CIOs and IT practitioners alike. >> So Steve, organizations are at a they're different levels of maturity in their, their transformation journeys, and of course, as a result, they're going to have different storage needs that are aligned with their bottom line business objectives. From an IT buyer perspective, you may have data on this, even if it's anecdotal, where does storage as a service actually fit in and can it be a growth lever? >> It can absolutely be a growth leader. It gives me the flexibility as an IT architect to scale my business over time without worrying about how much money I have to invest in storage hardware. Right? So I, I get kind of, again, that cloud like flexibility in terms of procurement and deployment, but it gives me that control by oftentimes being on site within my premise, and then I manage it like a storage array that I own. So, you know, it's beautiful for for organizations that are scaling and it's equally nice for organizations that just want to manage and control cost over time. So, it's a model that makes a lot of sense and fits and certainly growing in adoption and in popularity. >> How about from a technology vendor perspective? You've worked for in the tech industry for companies? What do you think is going to define the winners and losers in this space? If you running strategy for a storage company, what would you say? >> I think the days of of a storage administrator managing, you know, rate levels and recovering and things of that sort are over, right? What these organizations like Pure delivering but they're offering is simplicity. It's a push button approach to deploying storage to the applications and workloads that need it, right? It becomes storage as a utility. So, it's not just the, you know the consumption based economic model of as a service. It's also the manageability that comes with that or the flexibility of management that comes with that. I can push a button, deploy bites to you know a workload that needs it, and it just becomes very simple, right, for the storage administrator, in a way that, you know kind of old school On-Prem storage can't really deliver. >> You know, I want to, I want to ask you, I mean I've been thinking about this because again, a lot of companies are, are you know, moving, hopping on the as a service bandwagon. I feel like, okay, in and of itself, that's not where the innovation lives. The innovation is going to come from making that singular experience from On-Prem to the clouds across clouds maybe eventually out to the edge. Do you, where do you see the innovation in as a service? >> Well, there's two levels of innovation, right? One, is business model innovation, right? I now have an organizational flexibility to build the infrastructure to support my digital transformation efforts, but on the product side and the offering side, it really is as you said, it's about the integration of experience. Every enterprise today touches a cloud in some way, shape or form. Right, I have data spread, not just in my data center, but at the edge, oftentimes in a public cloud, maybe a private cloud. I don't know where my data is, and it really lands on the storage providers to help me manage that and deliver that manageability experience to to the IT administrators. So, when I look at innovation in this space, you know, it's not just a a storage array and rack that I'm leasing, right, this is not another lease model. It's really fully integrated, you know end to end management of my data and yeah and all of the things around that. >> Yeah, so to your point about a lease model is if you're doing a lease, you know, yeah. You can shift CapEx to OPEX, but you're still committed to you have to over provision, whereas here and I wanted to ask you about that. It's an interesting model, right, because you got to read the fine print. Of course the fine print says you got to commit to some level typically, and then if, you know, if you go over you you charge for what you use and you can scale that back down and that's got to be very attractive for folks. I wonder if you we'll ever see like true cloud like consumption pricing, that has two edges to it, right? You see consumption based pricing in some of the software models and you know yeah, people like it, the, the lines of business maybe because they're paying in by the drink, but then procurement hates it because they don't have predictability. How do you see the pricing models? Do you see that maturing or do you think we're sort of locked in on, on where we're at? >> No, I do see that maturing, right? And when you work with a company like Pure to understand their consumption base and as a service and you know, when you work with a company like Pure to understand their consumption base and as a service offerings, it really is sitting down and understanding where your data needs are going to scale. Right? You buy in at a certain level, you have capacity planning. You can expand if you need to. You can shrink if you need to. So, it really does put more control in the hands of the IT buyer than, well certainly then traditional CapEx based On-Prem, but also more control than you would get, you know working with an Amazon or an Azure. >> Well the next 10 years, it ain't going to be like the last 10 years. Thanks Steve! We'll leave it there for now. Love to have you back. Look at, keep it right there. You don't want to miss this next segment where we dig into the customer angle. You're watching theCube production of At Your Storage Service, brought to you by PureStorage. One more. Okay, thanks Steve! We'll leave it there for now. I'd love to have you back. Keep it right there, At Your Storage Service continues in a moment. You're watching theCube. (upbeat music)

Published Date : Jun 2 2022

SUMMARY :

Hey Steve, great to have you on. or, you know, software as a service. on storage that you think is you know, a natural model. you may have data on this, So, you know, it's beautiful deploy bites to you know are you know, moving, hopping it really is as you said, to you have to over and as a service and you know, Love to have you back.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
StevePERSON

0.99+

Steve McDowellPERSON

0.99+

IBMORGANIZATION

0.99+

AmazonORGANIZATION

0.99+

PureORGANIZATION

0.99+

Moor Insights and StrategyORGANIZATION

0.99+

OPEXORGANIZATION

0.99+

two levelsQUANTITY

0.99+

two edgesQUANTITY

0.98+

PureStorageORGANIZATION

0.98+

OneQUANTITY

0.97+

five yearsQUANTITY

0.97+

about five yearsQUANTITY

0.95+

todayDATE

0.93+

CapExORGANIZATION

0.91+

threeQUANTITY

0.83+

next 10 yearsDATE

0.83+

decadesQUANTITY

0.81+

Moor InsightsORGANIZATION

0.79+

last 10 yearsDATE

0.79+

AzureTITLE

0.78+

At Your Storage ServiceORGANIZATION

0.76+

StrategyORGANIZATION

0.74+

One moreQUANTITY

0.72+

theCubeORGANIZATION

0.71+

Make Smarter IT Decisions Across Edge to Cloud with Data-Driven Insights from HPE CloudPhysics


 

(bright upbeat music) >> Okay, we're back with theCUBE's continuous coverage of HPE's latest GreenLake announcement, the continuous cadence that we're seeing here. You know, when you're trying to figure out how to optimize workloads, it's getting more and more complex. Data-driven workloads are coming in to the scene, and so how do you know, with confidence, how to configure your systems, keep your costs down, and get the best performance and value for that? So we're going to talk about that. With me are Chris Shin, who is the founder of CloudPhysics and the senior director of HPE CloudPhysics, and Sandeep Singh, who's the vice-president of Storage Marketing. Gents, great to see you. Welcome. >> Dave, it's a pleasure to be here. >> So let's talk about the problem first, Sandeep, if we could. what are you guys trying to solve? What are you hearing from customers when they talk to you about their workloads and optimizing their workloads? >> Yeah, Dave, that's a great question. Overall, what customers are asking for is just to simplify their world. They want to be able to go faster. A lot of business is asking IT, let's go faster. One of the things that cloud got right is that overall cloud operational experience, that's bringing agility to organizations. We've been on this journey of bringing this cloud operational agility to customers for their data states, especially with HPE GreenLake Edge-to-Cloud platform. >> Dave: Right. >> And we're doing that with, you know, powering that with data-driven intelligence. Across the board, we've been transforming that operational support experience with HPE InfoSight. And what's incredibly exciting is now we're talking about how we can transform that experience in that upfront IT procurement portion of the process. You asked me what are customers asking about in terms of how to optimize those workloads. And when you think about when customers are purchasing infrastructure to support their app workloads, today it's still in the dark ages. They're operating on heuristics, or a gut feel. The data-driven insights are just missing. And with this incredible complexity across the full stack, how do you figure out where should I be placing my apps, whether on Prim or in the public cloud, and/or what's the right size infrastructure built upon what's actually being consumed in terms of resource utilization across the board. That's where we see a tremendous opportunity to continue to transform the experience for customers now with data-driven insights for smarter IT decisions. >> You know, Chris, Sandeep's right. It's like, it's like tribal knowledge. Well, Kenny would know how to do that, but Kenny doesn't work here anymore. So you've announced CloudPhysics. Tell us more about what that is, what impact it's going to have for customers. >> Sure. So just as Sandeep said, basically the problem that exists in IT today is you've got a bunch of customers that are getting overwhelmed with more and more options to solve their business problems. They're looking at cloud options, they're looking at new technologies, they're looking at new sub-technologies and the level at which people are competing for infrastructure sales is down at the very, very, you know, splitting hairs level in terms of features. And they don't know how much of these they need to acquire. Then on the other side, you've got partners and vendors who are trying to package up solutions and products to serve these people's needs. And while the IT industry has, for decades, done a good job of automating problems out of other technology spaces, hasn't done a good job of automating their own problems in terms of what does this customer need? How do I best service them? So you've got an unsatisfied customer and an inadequately equipped partner. CloudPhysics brings those two together in a common data platform, so that both those customers and their partners can look at the same set of data that came out of their data center and pick the solutions that will solve their problems most efficiently. >> So talk more about the partner angle, because it sounds like, you know, if they don't have a Kenny, they really need some help, and it's got to be repeatable. It's got to be consistent. So how have partners reacting to this? >> Very, very strongly. Over the course of the four or five years that that CloudPhysics has been doing this in market, we've had thousands and thousands of VARs, SIs and others, as well as many of the biggest technology providers in the market today, use CloudPhysics to help speed up the sales process, but also create better and more satisfied customers. >> So you guys made... Oh, go ahead, please. >> Well, I was just going to chime into that. When you think about partners that with HPE CloudPhysics, where it supports heterogeneous data center environments, partners all of a sudden get this opportunity to be much more strategic to their customers. They're operating on real world insights that are specific to that customer's environment. So now they can really have a tailored conversation as well as offer tailored solutions designed specifically for the areas, you know, where help is needed. >> Well, I think it builds an affinity with the customer as well, because if the partners that trust advisor, if you give a customer some advice and it's kind of the wrong advice, "Hey, we got to go back and reconfigure that workload. We won't charge you that much for it". You're now paying twice. Like when an accountant makes a mistake on your tax return, you got to pay for that again. But so, you guys acquired CloudPhysics in February of this year. What can you tell us about what's transpired since then? How many engagements that you've done? What kind of metrics can you share? >> Yeah. Chris, do you want to weigh in for that? >> Sure, sure. The start of it really has been to create a bunch of customized analytics on the CloudPhysics platform to target specific sales motions that are relevant to HPE partners. So what do I mean by that? You'll remember that in May, we announced the Alletra Series 6,000 and 9,000. In tandem with that, CloudPhysics released a new set of analytics that help someone who's interested in those technologies figure out what model might be best for them and how much firepower they would need from one or the other of those solutions. Similarly, we have a bunch solutions and a market strength in the HCI world, hyper converged, and that's both SimpliVity and dHCI. And we've set up some analytics that specifically help someone who's interested in that form factor to accelerate, and again, pick the right solutions that will serve their exact applications needs. >> When you talk to customers, are they able to give you a sense as to the cost impacts? I mean, even if it's subjective, "Hey, we think we, you know, we save 10% versus the way we used to do it", or more or less. I mean, just even gut feel metrics. >> So I'll start that one, Sandeep. So there's sort of two ways to look at it. One thing is, because we know everything that's currently running in the data center - we discovered that - we have a pretty good cost of what it is costing them today to run their workloads. So anything that we compare that to, whether it's a transition to public cloud or a transition to a hosted VMware solution, or a set of new infrastructure, we can compare their current costs to the specific solutions that are available to them. But on the more practical side of things, oftentimes customers know intuitively this is a set of servers I bought four years ago, or this is an old array that I know is loose. It's not keeping up anymore. So they typically have some fairly specific places to start, which gives that partner a quick win, solving a specific customer problem. And then it can often boil out into the rest of the data center, and continual optimization can occur. >> How unique is this? I mean, is it, you know, can you give us a little glimpse of the secret sauce behind it? Is this kind of table stakes for the industry? >> Yeah. I mean, look, it's unique in the sense that CloudPhysics brings along over 200 metrics across the spectrum of virtual machines and guest OSs, as well as the overall CPU and RAM utilization, overall infrastructure analysis, and built in cloud simulators. So what customers are able to do is basically, in real time, be able to: A - be aware of exactly what their environment looks like; B - be able to simulate if they were going to move and give an application workload to the cloud; C - they're able to just right-size the underlying infrastructure across the board. Chris? >> Well, I was going to say, yeah, along the same lines, there have been similar technology approaches to different problems. Most notably in the current HPE portfolio, InfoSight. Best in class, data lake driven, very highly analytical machine learning, geared predominantly toward an optimization model, right? CloudPhysics is earlier in the talk track with the customer. We're going to analyze your environment where HPE may not even have a footprint today. And then we're going to give you ideas of what products might help you based on very similar techniques, but approaching a very different problem. >> So you've got data, you've got experience, you know what best practice looks like. You get a sense as to the envelope as to what's achievable, right? And that is just going to get better and better and better over time. One of the things that that I've said, and we've said on theCUBE, is that the definition of cloud is changing. It's expanding, it's not just public cloud anymore. It's a remote set of services, it's coming on Prim, there's a hybrid connection. We're going across clouds, we're going out to the edge. So can CloudPhysics help with that complexity? >> Yeah, absolutely. So we have a set of analytics in the cloud world that range from we're going to price your on-premise IT. We also have the ability to simulate a transition, a set of workloads to AWS, Azure, or Google Cloud. We also have the ability to translate to VMware based solutions on many of those public clouds. And we're increasingly spreading our umbrella over GreenLake as well, and showing the optimization opportunities for a GreenLake solution when contrasted with some of those other clouds. So there's not a lot of... >> So it's not static. >> It's not static at all. And Dave, you were mentioning earlier in terms such as proven. CloudPhysics now has operated on trillions of data points over millions of virtual machines across thousands of overall data assessments. So there's a lot of proven learnings through that as well as actual optimizations that customers have benefited from. >> Yes. I mean, there's benchmarks, but it's more than that because benchmarks tend to be static, okay. We consider rules of thumb. We're living in an age with a lot more data, a lot more machine intelligence. And so this is organic, it'll evolve. >> Sandeep: Absolutely. >> And the partners who work with their customers on a regular basis over at CloudPhysics, and then build up a history over time of what's changing in their data center can even provide better service. They can look back over a year, if we've been collecting, and they can see what the operating system landscape has changed, how different workloads have lost popularity, how other ones have gained. And they really can become a much better solution provider to that customer the longer CloudPhysics is used. >> Yeah, it gives your partners a competitive advantage, it's a much stickier model because the customer is going to trust your partner more if they get it right. So we're not going to change horses in the middle of the street. We're going to go back to the partner that set us up, and they keep getting better and better and better each time, we've got a good cadence going. All right. Sandeep, bring us home. What's your sort of summary? How should we think about this going forward? >> Well, I'll bring us right back to the way I started is, and to end, we're looking at how we continue to deliver best in class cloud operational experience for customers across the board with HPE GreenLake. And earlier this year, we unveiled this cloud operation experience for data, and for customers, that experience starts with a cloud consult where they can essentially discover services, consume services, that overall operational and support experience is transformed with HPE InfoSight. And now we're transforming this experience where any organization out there that's looking to get data-driven insights into what should they do next? Where should they place their workloads? How to right-size the infrastructure? And in the process, be able to transform how they are working and collaborating with their partners. They're able to do that now with HPE CloudPhysics, bringing these data driven insights for smarter IT decision-making. >> I like this a lot, because a lot of the cloud is trial and error. And when you try and you make a mistake, you're paying each time. So this is a great innovation to really help clients focus on the things that matter, you know, helping them apply technology to solve their business problems. Guys, thanks so much for coming to theCUBE. Appreciate it. >> Dave, always a pleasure. >> Thanks very much for having us. >> And keep it right there. We got more content from HPE's GreenLake announcements. Look for the cadence. One of the hallmarks of cloud is the cadence of announcements. We're seeing HPE on a regular basis, push out new innovations. Keep it right there for more. (bright upbeat music begins) (bright upbeat music ends)

Published Date : Sep 28 2021

SUMMARY :

and get the best performance the problem first, Sandeep, if we could. One of the things that cloud got right in terms of how to to have for customers. at the very, very, you know, and it's got to be repeatable. many of the biggest technology providers So you guys made... that are specific to that and it's kind of the wrong advice, Chris, do you want to weigh in for that? that are relevant to HPE partners. are they able to give you a sense that are available to them. C - they're able to just right-size in the talk track with the customer. And that is just going to get We also have the ability to simulate And Dave, you were mentioning earlier to be static, okay. And the partners who because the customer is going to trust And in the process, be able to transform on the things that matter, you know, One of the hallmarks of cloud

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
DavePERSON

0.99+

ChrisPERSON

0.99+

Chris ShinPERSON

0.99+

SandeepPERSON

0.99+

fourQUANTITY

0.99+

Sandeep SinghPERSON

0.99+

MayDATE

0.99+

CloudPhysicsORGANIZATION

0.99+

10%QUANTITY

0.99+

KennyPERSON

0.99+

thousandsQUANTITY

0.99+

HPEORGANIZATION

0.99+

twiceQUANTITY

0.99+

five yearsQUANTITY

0.99+

HPE CloudPhysicsORGANIZATION

0.99+

AWSORGANIZATION

0.99+

bothQUANTITY

0.99+

GreenLakeTITLE

0.99+

twoQUANTITY

0.98+

over 200 metricsQUANTITY

0.98+

OneQUANTITY

0.98+

two waysQUANTITY

0.98+

One thingQUANTITY

0.97+

over a yearQUANTITY

0.97+

each timeQUANTITY

0.96+

todayDATE

0.96+

HPE GreenLakeORGANIZATION

0.96+

four years agoDATE

0.96+

SandeepORGANIZATION

0.96+

earlier this yearDATE

0.95+

HPE InfoSightORGANIZATION

0.94+

theCUBEORGANIZATION

0.93+

InfoSightORGANIZATION

0.91+

GreenLakeORGANIZATION

0.9+

oneQUANTITY

0.9+

Alletra Series 6,000COMMERCIAL_ITEM

0.9+

trillions of data pointsQUANTITY

0.85+

millions of virtual machinesQUANTITY

0.85+

decadesQUANTITY

0.84+

Google CloudORGANIZATION

0.82+

February of this yearDATE

0.77+

9,000COMMERCIAL_ITEM

0.72+

data assessmentsQUANTITY

0.71+

firstQUANTITY

0.68+

moreQUANTITY

0.62+

AzureTITLE

0.57+

CloudPhysicsTITLE

0.53+

SimpliVityTITLE

0.49+

GreenLake EdgeTITLE

0.44+

dHCIORGANIZATION

0.36+

Enable an Insights Driven Business Michele Goetz, Cindy Maike | Cloudera 2021


 

>> Okay, we continue now with the theme of turning ideas into insights so ultimately you can take action. We heard earlier that public cloud first doesn't mean public cloud only. And a winning strategy comprises data, irrespective of physical location on prem, across multiple clouds at the edge where real-time inference is going to drive a lot of incremental value. Data is going to help the world come back to normal we heard, or at least semi normal as we begin to better understand and forecast demand and supply imbalances and economic forces. AI is becoming embedded into every aspect of our business, our people, our processings, and applications. And now we're going to get into some of the foundational principles that support the data and insights centric processes, which are fundamental to digital transformation initiatives. And it's my pleasure to welcome two great guests, Michelle Goetz, who's a Cube alum and VP and principal analyst at Forrester, and doin' some groundbreaking work in this area. And Cindy Maike who is the vice president of industry solutions and value management at Cloudera. Welcome to both of you. >> Welcome, thank you. >> Thanks Dave. >> All right Michelle, let's get into it. Maybe you could talk about your foundational core principles. You start with data. What are the important aspects of this first principle that are achievable today? >> It's really about democratization. If you can't make your data accessible, it's not usable. Nobody's able to understand what's happening in the business and they don't understand what insights can be gained or what are the signals that are occurring that are going to help them with decisions, create stronger value or create deeper relationships with their customers due to their experiences. So it really begins with how do you make data available and bring it to where the consumer of the data is rather than trying to hunt and peck around within your ecosystem to find what it is that's important. >> Great thank you for that. So, Cindy, I wonder in hearing what Michelle just said, what are your thoughts on this? And when you work with customers at Cloudera, are there any that stand out that perhaps embody the fundamentals that Michelle just shared? >> Yeah, there's quite a few. And especially as we look across all the industries that were actually working with customers in. A few that stand out in top of mind for me is one is IQVIA. And what they're doing with real-world evidence and bringing together data across the entire healthcare and life sciences ecosystems, bringing it together in different shapes and formats, making it accessible by both internally, as well as for the entire extended ecosystem. And then for SIA, who's working to solve some predictive maintenance issues within, they're are a European car manufacturer and how do they make sure that they have efficient and effective processes when it comes to fixing equipment and so forth. And then also there's an Indonesian based telecommunications company, Techsomel, who's bringing together over the last five years, all their data about their customers and how do they enhance a customer experience, how do they make information accessible, especially in these pandemic and post pandemic times. Just getting better insights into what customers need and when do they need it? >> Cindy, platform is another core principle. How should we be thinking about data platforms in this day and age? Where do things like hybrid fit in? What's Cloudera's point of view here? >> Platforms are truly an enabler. And data needs to be accessible in many different fashions, and also what's right for the business. When I want it in a cost and efficient and effective manner. So, data resides everywhere, data is developed and it's brought together. So you need to be able to balance both real time, our batch, historical information. It all depends upon what your analytical workloads are and what types of analytical methods you're going to use to drive those business insights. So putting in placing data, landing it, making it accessible, analyzing it, needs to be done in any accessible platform, whether it be a public cloud doing it on-prem or a hybrid of the two is typically what we're seeing being the most successful. >> Great, thank you. Michelle let's move on a little bit and talk about practices and processes, the next core principles. Maybe you could provide some insight as to how you think about balancing practices and processes while at the same time managing agility. >> Yeah, it's a really great question 'cause it's pretty complex when you have to start to connect your data to your business. The first thing to really gravitate towards is what are you trying to do. And what Cindy was describing with those customer examples is that they're all based off of business goals, off of very specific use cases. That helps kind of set the agenda about what is the data and what are the data domains that are important to really understanding and recognizing what's happening within that business activity and the way that you can affect that either in near time or real time, or later on, as you're doing your strategic planning. What that's balancing against is also being able to not only see how that business is evolving, but also be able to go back and say, "Well, can I also measure the outcomes from those processes and using data and using insight? Can I also get intelligence about the data to know that it's actually satisfying my objectives to influence my customers in my market? Or is there some sort of data drift or detraction in my analytic capabilities that are allowing me to be effective in those environments?" But everything else revolves around that and really thinking succinctly about a strategy that isn't just data aware, what data do I have and how do I use it? But coming in more from that business perspective, to then start to be data driven, recognizing that every activity you do from a business perspective leads to thinking about information that supports that and supports your decisions. And ultimately getting to the point of being insight driven, where you're able to both describe what you want your business to be with your data, using analytics to then execute on that fluidly and in real time. And then ultimately bringing that back with linking to business outcomes and doing that in a continuous cycle where you can test and you can learn, you can improve, you can optimize and you can innovate. Because you can see your business as it's happening. And you have the right signals and intelligence that allow you to make great decisions. >> I like how you said near time or real time, because it is a spectrum. And at one end of the spectrum, autonomous vehicles. You've got to make a decision in real time but near real-time, or real-time, it's in the eyes of the beholder if you will. It might be before you lose the customer or before the market changes. So it's really defined on a case by case basis. I wonder Michelle, if you could talk about in working with a number of organizations I see folks, they sometimes get twisted up in understanding the dependencies that technology generally, and the technologies around data specifically can sometimes have on critical business processes. Can you maybe give some guidance as to where customers should start? Where can we find some of the quick wins and high returns? >> It comes first down to how does your business operate? So you're going yo take a look at the business processes and value stream itself. And if you can understand how people, and customers, partners, and automation are driving that step by step approach to your business activities, to realize those business outcomes, it's way easier to start thinking about what is the information necessary to see that particular step in the process, and then take the next step of saying what information is necessary to make a decision at that current point in the process? Or are you collecting information, asking for information that is going to help satisfy a downstream process step or a downstream decision? So constantly making sure that you are mapping out your business processes and activities, aligning your data process to that helps you now rationalize do you need that real time, near real time, or do you want to start creating greater consistency by bringing all of those signals together in a centralized area to eventually oversee the entire operations and outcomes as they happen? It's the process, and the decision points, and acting on those decision points for the best outcome that really determines are you going to move in more of a real-time streaming capacity, or are you going to push back into more of a batch oriented approach? Because it depends on the amount of information and the aggregate of which provides the best insight from that. >> Got it. Let's, bring Cindy back into the conversation here. Cindy, we often talk about people, process, and technology and the roles they play in creating a data strategy that's logical and sound. Can you speak to the broader ecosystem and the importance of creating both internal and external partners within an organization? >> Yeah. And that's kind of building upon what Michelle was talking about. If you think about datas and I hate to use the phrase almost, but the fuel behind the process and how do you actually become insight-driven. And you look at the capabilities that you're needing to enable from that business process, that insight process. Your extended ecosystem on how do I make that happen? Partners and picking the right partner is important because a partner is one that actually helps you implement what your decisions are. So looking for a partner that has the capability that believes in being insight-driven and making sure that when you're leveraging data within your process that if you need to do it in a real-time fashion, that they can actually meet those needs of the business. And enabling on those process activities. So the ecosystem looking at how you look at your vendors, and fundamentally they need to be that trusted partner. Do they bring those same principles of value, of being insight driven? So they have to have those core values themselves in order to help you as a business person enable those capabilities. >> So Cindy I'm cool with fuel, but it's like super fuel when you talk about data. 'Cause it's not scarce, right? You're never going to run out. (Dave chuckling) So Michelle, let's talk about leadership. Who leads? What does so-called leadership look like in an organization that's insight driven? >> So I think the really interesting thing that is starting to evolve as late is that organizations, enterprises are really recognizing that not just that data is an asset and data has value, but exactly what we're talking about here, data really does drive what your business outcomes are going to be. Data driving into the insight or the raw data itself has the ability to set in motion what's going to happen in your business processes and your customer experiences. And so, as you kind of think about that, you're now starting to see your CEO, your CMO, your CRO coming back and saying, I need better data. I need information that's representative of what's happening in my business. I need to be better adaptive to what's going on with my customers. And ultimately that means I need to be smarter and have clearer forecasting into what's about ready to come. Not just one month, two months, three months, or a year from now, but in a week or tomorrow. And so that is having a trickle down effect to then looking at two other types of roles that are elevating from technical capacity to more business capacity. You have your chief data officer that is shaping the experiences with data and with insight and reconciling what type of information is necessary with it within the context of answering these questions and creating a future fit organization that is adaptive and resilient to things that are happening. And you also have a chief digital officer who is participating because they're providing the experience and shaping the information and the way that you're going to interact and execute on those business activities. And either running that autonomously or as part of an assistance for your employees and for your customers. So really to go from not just data aware to data-driven, but ultimately to be insight driven, you're seeing way more participation and leadership at that C-suite level and just underneath, because that's where the subject matter expertise is coming in to know how to create a data strategy that is tightly connected to your business strategy. >> Great, thank you. Let's wrap, and I've got a question for both of you, maybe Cindy, you could start and then Michelle bring us home. A lot of customers, they want to understand what's achievable. So it's helpful to paint a picture of a maturity model. I'd love to go there, but I'm not going to get there anytime soon, but I want to take some baby steps. So when you're performing an analysis on an insight driven organization, Cindy what do you see as the major characteristics that define the differences between sort of the early beginners sort of fat middle, if you will, and then the more advanced constituents? >> Yeah, I'm going to build upon what Michelle was talking about is data as an asset. And I think also being data aware and trying to actually become insight driven. Companies can also have data, and they can have data as a liability. And so when you're data aware, sometimes data can still be a liability to your organization. If you're not making business decisions on the most recent and relevant data, you're not going to be insight-driven. So you've got to move beyond that data awareness, where you're looking at data just from an operational reporting. But data's fundamentally driving the decisions that you make as a business. You're using data in real time. You're leveraging data to actually help you make and drive those decisions. So when we use the term you're data-driven, you can't just use the term tongue-in-cheek. It actually means that I'm using the recent, the relevant, and the accuracy of data to actually make the decisions for me, because we're all advancing upon, we're talking about artificial intelligence and so forth being able to do that. If you're just data aware, I would not be embracing on leveraging artificial intelligence. Because that means I probably haven't embedded data into my processes. Yes, data could very well still be a liability in your organization, so how do you actually make it an asset? >> Yeah I think data aware it's like cable ready. (Dave chuckling) So Michelle, maybe you could add to what Cindy just said and maybe add as well any advice that you have around creating and defining a data strategy. >> So every data strategy has a component of being data aware. This is like building the data museum. How do you capture everything that's available to you? How do you maintain that memory of your business? Bringing in data from your applications, your partners, third parties, wherever that information is available, you want to ensure that you're capturing it and you're managing and you're maintaining it. And this is really where you're starting to think about the fact that it is an asset, it has value. But you may not necessarily know what that value is yet. If you move into a category of data driven, what starts to shift and change there is you're starting to classify label, organize the information in context of how you're making decisions and how you do business. It could start from being more proficient from an analytic purpose. You also might start to introduce some early stages of data science in there. So you can do some predictions and some data mining to start to weed out some of those signals. And you might have some simple types of algorithms that you're deploying to do a next next best action, for example. And that's what data-driven is really about. You're starting to get value out of it. The data itself is starting to make sense in context of your business, but what you haven't done quite yet, which is what insight driven businesses are, is really starting to take away the gap between when you see it, know it, and then get the most value and really exploit what that is at the time when it's right, so in the moment. We talk about this in terms of perishable insights, data and insights are ephemeral. And we want to ensure that the way that we're managing that and delivering on that data and insights is in time with our decisions and the highest value outcome we're going to have, that that insight can provide us. So are we just introducing it as data-driven organizations where we could see spreadsheets and PowerPoint presentations and lots of mapping to help make longer strategic decisions, or are those insights coming up and being activated in an automated fashion within our business processes that are either assisting those human decisions at the point when they're needed, or an automated decisions for the types of digital experiences and capabilities that we're driving in our organization. So it's going from, I'm a data hoarder if I'm data aware to I'm interested in what's happening as a data-driven organization and understanding my data. And then lastly being insight driven is really where light between business, data and insight, there is none, it's all coming together for the best outcomes. >> Right, it's like people are acting on perfect or near perfect information. Or machines are doing so with a high degree of confidence. Great advice and insights, and thank you both for sharing your thoughts with our audience today, it was great to have you. >> Thank you. >> Thank you. >> Okay, now we're going to go into our industry deep dives. There are six industry breakouts. Financial services, insurance, manufacturing, retail communications, and public sector. Now each breakout is going to cover two distinct use cases for a total of essentially 12 really detailed segments. Now each of these is going to be available on demand, but you can scan the calendar on the homepage and navigate to your breakout session of choice. Or for more information, click on the agenda page and take a look to see which session is the best fit for you and then dive in. Join the chat and feel free to ask questions or contribute your knowledge, opinions, and data. Thanks so much for being part of the community, and enjoy the rest of the day. (upbeat music)

Published Date : Aug 2 2021

SUMMARY :

that support the data and Maybe you could talk and bring it to where that perhaps embody the fundamentals and how do they make sure in this day and age? And data needs to be accessible insight as to how you think that are allowing me to be and the technologies that is going to help satisfy and technology and the roles they play in order to help you as a business person You're never going to and the way that you're going to interact that define the to actually help you make that you have around creating and lots of mapping to help and thank you both for and navigate to your

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
Michelle GoetzPERSON

0.99+

Cindy MaikePERSON

0.99+

CindyPERSON

0.99+

DavePERSON

0.99+

MichellePERSON

0.99+

Michele GoetzPERSON

0.99+

TechsomelORGANIZATION

0.99+

ClouderaORGANIZATION

0.99+

one monthQUANTITY

0.99+

bothQUANTITY

0.99+

twoQUANTITY

0.99+

two monthsQUANTITY

0.99+

eachQUANTITY

0.99+

PowerPointTITLE

0.98+

first principleQUANTITY

0.98+

three monthsQUANTITY

0.98+

six industryQUANTITY

0.98+

IQVIAORGANIZATION

0.98+

two great guestsQUANTITY

0.97+

a yearQUANTITY

0.97+

todayDATE

0.97+

two distinct use casesQUANTITY

0.96+

first thingQUANTITY

0.96+

firstQUANTITY

0.94+

ForresterORGANIZATION

0.94+

tomorrowDATE

0.93+

oneQUANTITY

0.93+

each breakoutQUANTITY

0.91+

a weekQUANTITY

0.9+

12 really detailed segmentsQUANTITY

0.86+

two other typesQUANTITY

0.81+

last five yearsDATE

0.7+

Cloudera 2021ORGANIZATION

0.69+

EuropeanOTHER

0.68+

IndonesianOTHER

0.64+

CubeORGANIZATION

0.61+

SIAORGANIZATION

0.59+

CindyTITLE

0.33+

Krishna Kottapalli and Sumant Rao, Abacus Insights | AWS Startup Showcase


 

(upbeat music) >> Welcome to today's session of theCUBE's presentation of the AWS Startup Showcase, the Next Big Thing in AI, Security & Life Sciences. Today we're joined by Abacus Insights for the Life Sciences track, I'm your host, Natalie Ehrlich. Now we're going to be speaking about creating an innovation enabling data environment to accelerate your healthcare analytics journey, and we're now joined by our guests Krishna Kottapalli, chief commercial officer as well as Sumant Rao, chief product officer, both working at Abacus Insights, thank you very much for joining us. >> Thank you for having us. >> Well let's kick off with our theme Krishna, how can we create innovation enabling data environments in order to facilitate the healthcare analytics? >> Yeah, so I think if you sort of think about this that is a lot of data proliferating inside the healthcare system, and whether it's through the internal sources, external sources, devices, patient monitoring platforms, and so on, and all of this carries yeah all of these essentially carry, have useful data and intelligence, right, and essentially the users are looking to get insights out of it to solve problems. And we're also seeing that the journey that our clients are going through is actually a transformation journey, right so they are thinking about how do we seamlessly interact with our stakeholders, so their stakeholders being members and providers, so that they don't get frustrated and feel like they're interacting with multiple parts of the health plan, right, we typically when you call the health plan you feel like you're calling five different departments, so they want to have a seamless experience, and finally, I think the whole, you know, the data being you know, in the ecosystem within the patients, payers, and providers being able to operate and interact has intelligence. So what we, what we think about this is how do we take all of this and help our clients you know, digitize their, you know, path forward and create a way to deliver, you know enable them to do meaningful analytics. >> Well Sumant, when you think about your customers what are the key benefits that Abacus is providing? >> So that's a good question, so primarily speaking, we approach this as, you know a framework that drives innovation that enables data and analytics. I mean, that's really what we're trying to do here. What Abacus does though, is this is slightly different is how we think about this. So we firmly believe that data analytics is not a linear journey, I mean, you cannot say that, oh I'll build my data foundation first and then, you know have the data and then they shall come that's not how it works. So for us, the way Abacus approaches this is, we focus really heavily on the data foundation part of it first. But along the way in the process, a big part of our value statement is we engage and make sure we are driving business value throughout this piece. So, so general message is, you know make sure innovation for the sake of innovation data is not how you're approaching this, but think about your business users, get them engaged, have it small, milestone driven progress that you make along the way. So, so generally speaking, it's we're not tryna be just a platform who moves bits and bytes of information. The way we think about this is you know we'll help you along this journey, there are steps that happen that take you there. And because of which, the message to most of our customers is you focus on your core competence. You know your business, you have nuances in the data, you have nuances on needs that your customers need, you focus on that. The scale that Abacus brings because this is what we do day in day out is more along area of re-usability. So if within our customers, they've got data assets how do we reuse some of that? How does Abacus re-use the fact that because of our of what we do, we actually have data assets that, you know, we can bring data to life quickly. So, so general guidelines, right, so first is don't innovate for the sake of innovating. I mean, that's not going to get you far, respect the process that this is not a linear path, there's always value that's happening throughout the process, and that's, you know, Abacus will work closely with you to make sure you recognize that value. The second part is within your organization, you have assets. There's like major data assets, there's IP, there's things that can leverage that Abacus will do. And because we are a platform, what we focus on is configurability. We've done this for, I mean, a lot of us on the Abacus team come from healthcare space, we have got big payer DNA, we get this, and what we also know is data rules change. I mean, you know, it's really hard when you build a system that's tightly built and you cannot change and you cannot adapt as data rules change, so we've made that part of it easier. We have, we understand data governance, so we work closely with our payers data governance teams to make sure that part of it happens. And I think the last part of this which is really important, this in the context of this conversation is, all of this is good stuff, I mean, you've got massive data foundation, you've got, you know, healthcare expertise flowing in, you've got partnerships with data governance, all that is great. If you don't have best-in-class infrastructure supporting all of that, then you really, you will really have issues Erlich. I mean, that's just the way it works, and this is why, you know, we're built on the AWS stack which kind of helps us, and also helps our clients along with their cloud journey. So it's kind of an interesting set of events in terms of you know, again, I'm going to repeat this because it's important that we don't innovate for the sake of innovating, re-use your assets, leverage your existing IP, make things configurable, data changes, and then leverage best in class infrastructure, so Abacus strategy progresses across those four dimensions. >> And I mean, that's an excellent point about healthcare data being really nuanced and you know, Krishna would love to get your insights on what you see are the biggest opportunities in healthcare analytics now. >> Yeah, so the biggest opportunities are, you know there are two, we think about it in two dimensions, right, one is really around sort of the analytics use cases, and second is around the operational use cases, right, so if you think about a payer they're trying to solve both, and we see because of, you know, our the way we think about data, which is close to near real time, we are able to essentially serve up our clients with, you know helping them solve both their use cases. So think of this that, when you're a patient, you go to you know, you go to a CVS to do something, and then you go to your doctor's office to do something, right, to be, to be able to take a test. If all of these are known, to your payer care management team, if you will, in close to near real time then know, right, where you've been, what you can do how to be able to sort of intervene and so on and so forth, so from a next best action and operational use cases we see a lot of them emerging, new thanks to the cloud as well as thanks to infrastructure, which can do sort of near real time. So that's our own sort of operational use cases if you will. If, when you think about the analytics right, so, you know, every, all payers struggle with this, Which is you have limited dollars to be able to intervene with you know, a large set of population, right so every piece of data that you know, have about your patient, about the specific provider so on and so forth is able to actually, you know give you analytics to be able to intervene or engage if you will, with the patient in a very one-to-one manner. And what we find is at the end of the day if the patient is not engaged in this and the member or the patient is not engaged, you know in the healthcare, you know, value chain, if you will, then your dollars go to waste, and we feel that, in essentially both of these type of use cases can be sorted up really well with, with a unified data platform, as well as with upstack analytics. >> And now Sumant, I'd love to hear from you, you know you're really involved with the product, how do you see the competitive landscape? How do you make sure that your product is the best out there? >> So I think, I think a lot of that is we think about ourselves across three, three vectors. Talk about it as core platform, which is at a very minimal level of description, it's really moving bits and bytes from point A to point B. That's one part of it, right, and I think there's a, it's a pretty crowded space, it's a whole bunch of folks out there trying to, you know demonstrate that they can successfully land data from one point to the other. We do that too, we do that at scale. Where you'd start differentiating and pulling away from the pack is the second vector, which is enrichment. Now, this is where again, it's you have to understand healthcare data to really build a level of respect for how messy it can get. And you have to understand it and build it in a way where it's easy to keep up with the changes. We spend a lot of time, you know in building out a platform to do that so that we can implement data quickly. I mean, you know, for Abacus to bring a data source to life in less than 45 days, it's pretty straightforward. And it's you're talking on an average 6 or 12 months across the rest. Because we get this, we've got a library of rules, we understand how to bring this piece, so we start pulling away from the competitors, if you may. More along the enrichment vector, because that's where we think, getting high quality rules, getting these re-used, all of this is part of it, but then we bring another level of enrichment where we have, you know, we use public data sets, we use a reference data sets, we tie this, we fill in the blanks in the data. All of this is the end state, let's make the data shovel-ready for analytics. So we do all of that along the way, so now applying our expertise, cleansing data, making sure it's the gaps are all filled out and getting this ready and then comes the next part where we tie this data out. Cause it's one thing to bring in multiple sources quickly at scale high speed and all that good stuff, which is hard work, but you know, it's, it's expected now at the same time how do you put all that together in a meaningful manner with which we can actually, you know, land it and keep it ready? So that's two parts. So first is, the platform, the nuts and bolts, the pipes, all that is good stuff, the second is the enrichment. The third side, which is really where we start differentiating is distribution. We have a philosophy that, you know, really the mission of the whole company was to get data available. To solve use cases like the one Krishna just talked about. So rather than make this a massive change management program that takes five years to implement, and really scares your end users away, our philosophy is like let's have incremental use case all on the way, but let's talk to the users, let them interact with data as easy as they can. So we've built our partnerships on our distribution hub, which makes it easy, so an example is if you have someone in the marketing team, who really wants to analyze a particular population to reach out to them, and all they know is tableau, it is great. It should be as simple as saying, look what's the sliver of data you need to get your job done, how do you interact? So we've our distribution hub, is really is the part where, users come in, interact with the data with you know, we will meet you where you are is the underlying principle and that's how it operates. So, so I think on the first level of platform, yeah a crowded space everyone's fighting for that piece, the second part of it is enrichment where we really start pulling away using our expertise, and then at the end of it you've got the distribution part where you know you just want to make it available to users, and, you know, a lot of work has gone into getting this done but that's how we work. >> And if I could add a couple more things, Natalie, so the other thing is security, right so the reason that healthcare, healthcare players have not gone to the cloud until about three four years back, is the whole concern about security so we have invested a ton of resources and money to make sure that our platform is run in the most secure manner, and giving confidence to our clients, and it's an expensive process, right, even though you're on AWS you have to have your own certification that, so that that gives us a huge differentiator, and the last but not least is how we actually approach the whole data management deployment process, which is, our clients think about us in two dimensions, total cost of ownership, but typically 50 to 60% of what it would cost internally, and secondly, time to value, right, you can't have an infinitely long deployment cycle. So we think about those two and actually put our skin in the game and tie our, you know, tie our success to total cost of ownership and time to value. >> Well, just really quick in 1-2 sentences, would love to get your insight on Abacus's defining contribution to the future of cloud scale. >> Go ahead, Sumant. >> So as I see it, I think so part of it is we've got some of our clients who are payers and we've got them along their cloud journey trusting one of their key assets which is data, and letting us drive it. And this is really driven by domain expertise, a good understanding of data governance, and a great understanding of security, I mean, combining all of this, we've actually got our clients sitting and operating on, you know pretty significant cloud infrastructure successfully day in day out. So I think we've done our part as far as, you know helping folks along that journey. >> Yeah and just to close it out I would say it is speed, right, it is speed to deployment, you don't have to wait. You know, we have set up the infrastructure, set up the cloud and the ability to get things up and running is literally we think about it in weeks, and not months. >> Terrific, well, thank you both very much for insights, fantastic to have you on the show, really fascinating to hear about how Abacus is leveraging healthcare data expertise on its platform , to drive robust analytics, and of course, here we were joined by Abacus Insights, Krishna Kottapalli, the chief commercial officer, as well as Sumant Rao, the chief product officer, thank you again very much for your insights on this program and this session of the AWS Startup Showcase. (upbeat music)

Published Date : Jun 24 2021

SUMMARY :

thank you very much for joining us. of this and help our clients you know, and this is why, you know, and you know, Krishna would and we see because of, you know, our the competitors, if you may. and tie our, you know, the future of cloud scale. and operating on, you know and the ability to get fantastic to have you on the show,

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
Natalie EhrlichPERSON

0.99+

AbacusORGANIZATION

0.99+

Krishna KottapalliPERSON

0.99+

Sumant RaoPERSON

0.99+

50QUANTITY

0.99+

five yearsQUANTITY

0.99+

AWSORGANIZATION

0.99+

6QUANTITY

0.99+

Abacus InsightsORGANIZATION

0.99+

NataliePERSON

0.99+

twoQUANTITY

0.99+

two dimensionsQUANTITY

0.99+

12 monthsQUANTITY

0.99+

one pointQUANTITY

0.99+

second partQUANTITY

0.99+

threeQUANTITY

0.99+

second vectorQUANTITY

0.99+

bothQUANTITY

0.99+

secondQUANTITY

0.99+

one partQUANTITY

0.99+

less than 45 daysQUANTITY

0.99+

firstQUANTITY

0.99+

third sideQUANTITY

0.99+

60%QUANTITY

0.98+

three vectorsQUANTITY

0.98+

TodayDATE

0.98+

two partsQUANTITY

0.98+

five different departmentsQUANTITY

0.98+

KrishnaPERSON

0.98+

first levelQUANTITY

0.97+

oneQUANTITY

0.97+

todayDATE

0.97+

ErlichPERSON

0.96+

one thingQUANTITY

0.95+

theCUBEORGANIZATION

0.92+

1-2 sentencesQUANTITY

0.91+

Startup ShowcaseEVENT

0.9+

SumantPERSON

0.82+

three four years backDATE

0.8+

AWS Startup ShowcaseEVENT

0.79+

resourcesQUANTITY

0.63+

pointOTHER

0.63+

aboutDATE

0.62+

a tonQUANTITY

0.61+

secondlyQUANTITY

0.6+

SumantORGANIZATION

0.52+

coupleQUANTITY

0.45+

Patrick Moorhead, Moor Insights | HPE Discover 2021


 

>>Welcome back to HPD discovered 2021. The virtual edition. My name is Dave Volonte and you're watching the cubes continuous coverage of H. P. S. Big customer event. Patrick Moorehead is here of moor insights and strategy is the number one analyst in the research analyst. Business. Patrick. Always a pleasure. Great to see you, >>David. Great to see you too. And I know you're you're up there fighting for that number one spot to. It's great to see you and it's great to see you in the meetings that were in. But it's even more fun to be here on the cube. I love to be on the cube and every once in a while you'll even call me a friend of the cube, >>unquestionably my friend and so and I can't wait second half. I mean you're traveling right now. We're headed to Barcelona to mobile World Congress later on this month. So so we're gonna we're gonna see each other face to face this year. 100%. So looking forward to that. So you know, let's get into it. Um you know, before we get into H. P. E. Let's talk a little bit about what you're seeing in the market. We've got, you know, we we finally, it feels like the on prem guys are finally getting their cloud act together. Um it's maybe taken a while, but we're seeing as a service models emerge. I think it's resonating with customers. The clearly not everything is moving to the cloud. There's this hybrid model emerging. Multi cloud is real despite what, you know, >>some some >>cloud players want to say. And then there's this edges like jump ball, what are you seeing in the marketplace? >>Yeah. Davis, as exciting as ever in. Just to put in perspective, I mean the public cloud has been around for about 10 years and still only 20% around 20% of the data in 20% of the applications are there now will be a very important ones and I'm certainly not a public cloud denier, I never have been, but there are some missing pieces that need to come together. And you know, even five years ago we were debating dave the hybrid cloud. And I feel like when amazon brought out outposts, the conversation was over right now, what you have is cloud native folks building out hybrid and on prem capabilities, you have a classic on, on prem folks building out hybrid and as a service capabilities. And I really think it boils down 22 things. I mean it's, it's wanting to have more flexibility and you know, I hate to use it because it sounds like a marketing word, but agility, the ability to spin up things and spin down things in a very, a quick way. And uh you know what they've learned, The veterans also know, hey, let's do this in a way that doesn't lock us in too much into a certain vendor. And I've been around for a long time. David and I'm a realist too. Well, you have to lock yourself into something. Uh it just depends on what do you want to lock yourself into, but super exciting and what H. P. E. You know, when they further acts in the sea with Green Lake, I think it was four years ago, uh I think really started to stir the pot. >>You know, you mentioned the term cloud denial, but you know, and I feel like the narrative from, I like to determine as I think you should use the term veteran. You know, it's very, they're ours is the only industry patrick where legacy is a pejorative, but so, but the point I want to make is I feel like there's been a lot of sort of fear from the veteran players, but, but I look at it differently, I wonder what your take is. I, I think, I think I calculated that the Capex spending by the big four public clouds including Alibaba last year was $100 billion. That's like a gift to the world. Here we're gonna spend $100 billion like the internet. Here you go build. And so I, and I feel like companies like HP are finally saying, yeah, we're gonna build, we're gonna build a layer and we're gonna hide the complexity and we're gonna add value on top. What do you think about that? >>Yeah. So I think it's now, I wish, I wish the on prem folks like HP, you would have done it 10 years ago, but I don't think anybody expected the cloud to be as big as it's become over the last 10 years. I think we saw companies like salesforce with sas taking off, but I think it is the right direction because there are advantages to having workloads on prem and if you add an as a service capability on top of the top of that, and let's say even do a Coehlo or a managed service, it's pretty close to being similar to the public cloud with the exception, that you can't necessarily swipe a credit card for a bespoke workload if you're a developer and it is a little harder to scale out. But that is the next step in the equation day, which is having, having these folks make capital expenditures, make them in a Polo facility and then put a layer to swipe a credit card and you literally have the public cloud. >>Yeah. So that's, that's a great point. And that's where it's headed, isn't it? Um, so let's, let's talk about the horses on the track. Hp as you mentioned, I didn't realize it was four years ago. I thought it was, wow, That's amazing. So everybody's followed suit. You see, Dallas announced, Cisco has announced, uh, Lenovo was announced, I think IBM as well. So we, so everybody's sort of following suit there. The reality is, is it's taken some time to get this stuff standardized. What are you seeing from, from HP? They've made some additional announcements, discover what's your take on all this. >>Yeah. So HPD was definitely the rabbit here and they were first in the market. It was good to see. First off some of their, Um, announcements on, on how it's going and they talked about $428 billion 1200 customers over 900 partners and 95% retention. And I think that's important. Anybody who's in the lead and remember what aws I used to do with the slide with the amount of customers would just get bigger and bigger and bigger and that's a good way to show momentum. I like the retention part two which is 95%. And I think that that says a lot uh probably the more important announcements that they made is they talked about the G. A. Of some of their solutions on Green Lake and whether it is A. S. A. P. Hana. Ml apps HPC with Francis, VD. I was Citrus and video but they also brought more of what I would call a vertical layer and I'm sure you've seen the vertical ization of all of these cloud and as a service workloads. But what they're doing with Epic, with EMR and looseness, with financial payments and Splunk and intel with data and risk analysis and finally, a full stack for telco five G. One of the biggest secrets and I covered this about five years ago is HPV actually has a full stack that Western european carriers use and they're now extending that to five G. And um, so more horizontal, uh, and, and more vertical. That was the one of the big swipes, uh, that I saw that there was a second though, but maybe we can talk about these. >>Yeah. Okay. Okay. So, so the other piece of that of course is standardization right there there because there was a, there was a, there was a lot of customization leading up to this and everybody sort of, everybody always had some kind of financial game they can play and say, hey, there's an adversary as a service model, but this is definitely more of a standardized scalable move that H P E. Is making with what they call Lighthouse. Right? >>Yeah, that's exactly right. And I've talked to some Green Lake customers and they obviously gave it kudos or they wouldn't have HP wouldn't have served them up and they wouldn't have been buying it. But they did say, um, it took, it took a while, took some paperwork to get it going. It's not 100% of push button, but that's partially because hp allows you to customize the hardware. You want a one off network adapter. Hp says yes, right. You want to integrate a different type of storage? They said yes. But with Green Lake Lighthouse, it's more of a, what you see is what you get, which by the way, is very much like the public cloud or you go to a public cloud product sheet or order sheet. You're picking from a list and you really don't know everything that's underneath the covers, aside from, let's say, the speed of the network, the type of the storage and the amount of the storage you get. You do get to pick between, let's say, an intel processor, Graviton two or an M. D processor. You get to pick your own GPU. But that's pretty much it. And HP Lighthouse, sorry, Green Lake Lighthouse uh is bringing, I think a simplification to Green Lake that it needs to truly scale beyond, let's say the White House customers that HP Yeah, >>Well done. So, you know, and I hear your point about we're 10 years in plus. And to me this is like a mandate. I mean, this is okay, good, good job guys about time. But if I had a, you know, sort of look at the big player, it's like we have an oligopoly here in this, in this business. It's HP, Cisco, you got Dell Lenovo, you've got, you know, IBM, they're all doing this and they all have a different little difference, you know, waste of skin of catch. And your point about simplicity, it seems like HP HP is all in antony's like, okay, here's what we're going to announce that, you know, a while ago. So, and they seem to have done a good job with Wall Street and they got a simple model, you know, Dell is obviously bigger portfolio, much more complicated. IBM is even more complicated than that. I don't know so much about Lenovo and in Cisco of course, has acquired a ton of SAAS companies and sort of they've got a lot of bespoke products that they're trying to put together. So they've got, but they do have SAS models. So each of them is coming at it from a different perspective. How do you think? And so and the other point we got lighthouse, which is sort of Phase one, get product market fit. Phase two now is scale, codify standardized and then phase three is the moat build your unique advantage that protects your business. What do you see as HP ES sort of unique value proposition and moat that they can build longer term. >>That's a great, great question. And let me rattle off kind of what I'm seeing that some of these players here, So Cisco, ironically has sells the most software of any of those players that you mentioned, uh with the exception of IBM um and yeah, C I >>CSDB two. Yeah, >>yeah, they're the they're the number two security player, uh Microsoft, number one, So and I think the evaluation on the street uh indicate that shows that I feel like Dell tech is a very broad play because not only do they have servers, storage, networking insecurity, but they also have Pcs and devices. So it's a it's a scale and end play with a focus on VM ware solutions, not exclusively of course. Uh And um then you've got Lenovo who is just getting into the as a service game and are gosh, they're doing great in hyper scale, they've got scale there vertically integrated. I don't know if if too many people talk about that, but Lenovo does a lot of their own manufacturing and they actually manufacture Netapp storage solutions as well. So yeah, each of these folks brings a different game to the table. I think with h P e, what you're bringing the table is nimble. When HP and HP split, the number one thing that I said was that ah, h P E is going to have to be so much faster than it offsets the scale that Dell technology has and the HBs credit, although there, I don't think we're getting credit for this in the stock market yet. Um and I know you and I are both industry folks, not financial folks, but I think their biggest thing is speed and the ability to move faster. And that is what I've seen as it relates to the moat, which is a unique uh competitive advantage. Quite frankly, I'm still looking for that day uh in in in what that is. And I think in this industry it's nearly impossible. And I would posit that that any, even the cloud folks, if you say, is there something that AWS can do that as your can't if it put it put its mind to it or G C P. I don't think so. I think it's more of a kind of land and expand and I think for H P E. When it comes to high performance computing and I'm not just talking about government installations, I'm talking about product development, drug development. I think that is a landing place where H P. E already does pretty well can come in and expand its footprint. >>You know, that's really interesting um, observations. So, and I would agree with you. It's kind of like, this is a copycat industry. It's like the west coast offense like the NFL, >>so, >>so the moat comes from, you know, brand execution and your other point about when HP and HP split, that was a game changer because all of a sudden you saw companies like them, you always had a long term relationship with H P E, but or HP, but then they came out of the woodworks and started to explode. And so it really opened up opportunities. So it really is a execution, isn't it? But go ahead please. >>Dave if I had to pick something that I think HP HPV needs to always be ahead in as a service and listen you and I both know announcements don't mean delivery, but there is correlation between if you start four years ahead of somebody that other company is going to have to put just, I mean they're going to have to turn that ship and many of its competitors really big ships to be able to get there. So I think what Antonio needs to do is run like hell, right? Because it, it I think it is in the lead and as a service holistically doesn't mean they're going to be there forever, but they have to stay ahead. They have to add more horizontal solutions. They have to add more vertical solutions. And I believe that at some point it does need to invest in some Capex at somebody like Anna Quinn X play credit card swiper on top of that. And Dave, you have the public, you have the public cloud, you don't have all the availability zones, but you have a public cloud. >>Yeah, that's going to happen. I think you're right on. So we see this notion of cloud expanding. It's no longer just remote set of services. Somewhere out in the cloud. It's like you said, outpost was the sort of signal. Okay, We're coming on prem. Clearly the on prem uh, guys are connecting to the cloud. Multi cloud exists, we know this and then there's the edge but but but that brings me to that sort of vision and everybody's laying out of this this this seamless integration hiding the complexity log into my cloud and then life will be good. But the edge is different. Right? It's not just, you know, retail store or a race track. I mean there's the far edge, there's the Tesla car, there's gonna be compute everywhere and that sort of ties into the data. The data flows, you know the real time influencing at the edge ai new semiconductor models. You you came out of the semiconductor industry, you know it inside and out arm is exploding, dominating in the edge with apple and amazon Alexa and things like that. That's really where the action is. So this is a really interesting cocktail and soup that we have going on. How do >>you say? Well, you know, Dave if the data most data, I think one thing most everybody agrees on is that most of the data will be created on the edge, whether that's a moving edge a car, a smartphone or what I call an edge data center without tile flooring. Like that server that's bolted to the wall of Mcdonald's. When you drive through, you can see it versus the walmart. Every walmart has a raised tile floor. It's the edge to economically and performance wise, it doesn't make any sense to send all that data to the mother ships. Okay. And whether that's unproven data center or the giant public cloud, more efficient way is to do the compute at the closest way possible. But what it does, it does bring up challenges. The first challenge is security. If I wanted to, I could walk in and I could take that server off the Mcdonald's or the Shell gas station wall. So I can't do that in a big data center. Okay, so security, physical security is a challenge. The second is you don't have the people to go in there and fix stuff that are qualified. If you have a networking problem that goes wrong in Mcdonald's, there's nobody there that can help uh they can they can help you fix that. So this notion of autonomy and management and not keeping hyper critical data sitting out there and it becomes it becomes a security issue becomes a management issue. Let me talk about the benefits though. The benefits are lower latency. You want you want answers more quickly when that car is driving down the road And it has a 5GV 2 x communication cameras can't see around corners. But that car communicating ahead, that ran into the stop sign can, through Vita X talked to the car behind it and say, hey, something is going on there, you can't go to, you can't go to the big data center in the sky, let's make that happen, that is to be in near real time and that computer has to happen on the edge. So I think this is a tremendous opportunity and ironically the classic on prem guys, they own this, they own this space aside from smartphones of course, but if you look at compute on a light pole, companies like Intel have built complete architecture is to do that, putting compute into five G base stations, heck, I just, there was an announcement this week of google cloud and its gaming solution putting compute in a carrier edge to give lower latency to deliver a better experience. >>Yeah, so there, of course there is no one edge, it's highly fragmented, but I'm interested in your thoughts on kinda whose stack actually can play at the edge. And I've been sort of poking uh H P E about this. And the one thing that comes back consistently is Aruba, we we could take a room but not only to the, to the near edge, but to the far edge. And and that, do you see that as a competitive advantage? >>Oh gosh, yes. I mean, I would say the best acquisition That hp has made in 10 years has been aruba, it's fantastic and they also managed it in the right way. I mean it was part of HB but it was, it was managed a lot more loosely then, you know, a company that might get sucked into the board and I think that paid off tremendously. They're giving Cisco on the edge a absolute run for their money, their first with new technologies, but it's about the solution. What I love about what a ruble looks at is it's looking at entertainment solutions inside of a stadium, a information solution inside of an airport as opposed to just pushing the technology forward. And then when you integrate compute with with with Aruba, I think that's where the real magic happens. Most of the data on a permanent basis is actually video data. And a lot of it's for security, uh for surveillance. And quite frankly, people taking videos off, they're off their smartphones and downloaded video. I I just interviewed the chief network officer of T mobile and their number one bit of data is video, video uploaded, video download. But that's where the magic happens when you put that connectivity and the compute together and you can manage it in a, in an orderly and secure fashion. >>Well, I have you we have a ton of time here, but I I don't pick your brain about intel the future of intel. I know you've been following it quite closely, you always have Intel's fighting a forefront war, you got there battling a. M. D. There, battling your arm slash and video. They're they're taking on TSMC now and in foundry and, and I'll add china for the looming threat there. So what's your prognosis for for intel? >>Yeah, I liked bob the previous Ceo and I think he was doing a lot of of the right things, but I really think that customers and investors and even their ecosystem wanted somebody leading the company with a high degree of technical aptitude and Pat coming, I mean, Pat had a great job at VM or, I mean he had a great run there and I think it is a very positive move. I've never seen the energy at Intel. Probably in the last 10 years that I've seen today. I actually got a chance to talk with Pat. I visited Pat uhh last month and and talk to him about pretty much everything and where he wanted to take the company the way you looked at technology, what was important, what's not important. But I think first off in the world of semiconductors, there are no quick fixes. Okay. Intel has a another two years Before we see what the results are. And I think 2023 for them is gonna be a huge year. But even with all this competition though, Dave they still have close to 85% market share in servers and revenue share for client computing around 90%. Okay. So and they built out there networking business, they build out a storage business um with obtain they have the leading Aid as provider with Mobileye. And and listen I was I was one of Intel's biggest, I was into one of Intel's biggest, I was Intel's biggest customer when I was a compact. I was their biggest competitor at A. M. B. So um I'm not obviously not overly pushing or there's just got to wait and see. They're doing the right things. They have the right strategy. They need to execute. One of the most important things That Intel did is extend their alliance with TSMC. So in 2023 we're going to see Intel compute units these tiles they integrate into the larger chips called S. O. C. S. B. Manufactured by TSMC. Not exclusively, but we could see that. So literally we could have AMG three nanometer on TSMC CPU blocks, competing with intel chips with TSMC three nanometer CPU blocks and it's on with regard to video. I mean in video is one of these companies that just keeps going charging, charging hard and I'm actually meeting with Jensen wang this week and Arm Ceo Simon Segers to talk about this opportunity and that's a company that keeps on moving interestingly enough in video. If the Arm deal does go through will be the largest chip license, see CPU licensee and have the largest CPU footprint on on the planet. So here we have A and D. Who's CPU and Gpu and buying an F. P. G. A company called Xilinx, you have Intel, Cpus, Gpus machine learning accelerators and F. P. G. S and then you've got arms slashing video bit with everything as well. We have three massive ecosystems. They're gonna be colliding here and I think it's gonna be great for competition date. Competition is great. You know, when there's not competition in Cpus and Gpus, we know what happens, right. Uh, the B just does not go on and we start to stagnate. And I did, I do feel like the industry on CPU started to stagnate when intel had no competition. So bring it on. This is gonna be great for for enterprises then customers to, and then, oh, by the way, the custom Chip providers, WS has created no less than 15 custom semiconductors started with networking uh, and, and nitro and building out an edge that surrounded the general compute and then it moved to Inferential to for inference trainee um, is about to come out for training Graviton and gravitas to for general purpose CPU and then you've got Apple. So innovation is huge and you know, I love to always make fun of the software is eating the world. I always say yeah but has to run on something. And so I think the combination of semiconductors, software and cloud is just really a magical combination. >>Real quick handicap the video arm acquisition. What what are the odds that that they will be successful? They say it's on track. You've got to 2 to 13 to 1 10 to 1. >>I say 75%. Yes 25%. No China is always the has been the odd odd man out for the last three years. They scuttled the qualcomm NXP deal. You just don't know what china is going to do. I think the Eu with some conditions is gonna let this fly. I think the U. S. Is absolutely going to let this fly. And even though the I. P. Will still stay over in the UK, I think the U. S. Wants to see, wants to see this happen. Japan and Korea. I think we'll allow this china is the odd man out. >>In a word, the future of H. P. E. Is blank >>as a service >>patrick Moorehead. Always a pleasure my friend. Great to see you. Thanks so much for coming back in the cube. >>Yeah, Thanks for having me on. I appreciate that. >>Everybody stay tuned for more great coverage from HP discover 21 this is day Volonte for the cube. The leader and enterprise tech coverage. We'll be right back. >>Mm.

Published Date : Jun 23 2021

SUMMARY :

Patrick Moorehead is here of moor insights and strategy is the It's great to see you and it's great to see you in the meetings that were in. So you know, let's get into it. And then there's this edges like jump ball, what are you seeing in the marketplace? the conversation was over right now, what you have is cloud native folks building out hybrid I like to determine as I think you should use the term veteran. the cloud to be as big as it's become over the last 10 years. let's talk about the horses on the track. And I think that that says a lot uh that H P E. Is making with what they call Lighthouse. I think a simplification to Green Lake that it needs to truly So, and they seem to have done a good job with Wall Street and any of those players that you mentioned, uh with the exception of IBM Yeah, And I would posit that that any, even the cloud folks, if you say, It's like the west coast offense like the NFL, so the moat comes from, you know, brand execution and your other And Dave, you have the public, you have the public cloud, arm is exploding, dominating in the edge with center in the sky, let's make that happen, that is to be in near real time And and that, do you see that as a competitive And then when you integrate compute Well, I have you we have a ton of time here, but I I don't pick your brain about And I did, I do feel like the industry on CPU started to stagnate You've got to 2 to 13 to 1 10 to 1. I think the U. S. Is absolutely going to let Thanks so much for coming back in the cube. I appreciate that. The leader and enterprise tech coverage.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
DavidPERSON

0.99+

IBMORGANIZATION

0.99+

Dave VolontePERSON

0.99+

CiscoORGANIZATION

0.99+

DavePERSON

0.99+

PatPERSON

0.99+

LenovoORGANIZATION

0.99+

HPORGANIZATION

0.99+

AWSORGANIZATION

0.99+

100%QUANTITY

0.99+

BarcelonaLOCATION

0.99+

MicrosoftORGANIZATION

0.99+

H P EORGANIZATION

0.99+

patrick MooreheadPERSON

0.99+

PatrickPERSON

0.99+

walmartORGANIZATION

0.99+

TSMCORGANIZATION

0.99+

HPDORGANIZATION

0.99+

AlibabaORGANIZATION

0.99+

95%QUANTITY

0.99+

UKLOCATION

0.99+

75%QUANTITY

0.99+

$100 billionQUANTITY

0.99+

amazonORGANIZATION

0.99+

20%QUANTITY

0.99+

Patrick MooreheadPERSON

0.99+

2021DATE

0.99+

25%QUANTITY

0.99+

10 yearsQUANTITY

0.99+

DellORGANIZATION

0.99+

Patrick MoorheadPERSON

0.99+

appleORGANIZATION

0.99+

WSORGANIZATION

0.99+

four yearsQUANTITY

0.99+

last yearDATE

0.99+

AppleORGANIZATION

0.99+

T mobileORGANIZATION

0.99+

last monthDATE

0.99+

IntelORGANIZATION

0.99+

2023DATE

0.99+

13QUANTITY

0.99+

Anna QuinnPERSON

0.99+

firstQUANTITY

0.99+

XilinxORGANIZATION

0.99+

OneQUANTITY

0.99+

eachQUANTITY

0.99+

bothQUANTITY

0.99+

oneQUANTITY

0.99+

DavisPERSON

0.99+

10 years agoDATE

0.99+

FirstQUANTITY

0.99+

secondQUANTITY

0.99+

HP LighthouseORGANIZATION

0.98+

telcoORGANIZATION

0.98+

White HouseORGANIZATION

0.98+

Patrick Moorhead, Moor Insights | HPE Discover 2021


 

>>Welcome back to HPD discovered 2021. The virtual edition. My name is Dave Volonte and you're watching the cubes continuous coverage of H. P. S. Big customer event. Patrick Moorehead is here of moor insights and strategy is the number one analyst in the research analyst. Business. Patrick. Always a pleasure. Great to see you, >>David. Great to see you too. And I know you're you're up there fighting for that number one spot to. It's great to see you and it's great to see you in the meetings that were in. But it's even more fun to be here on the cube. I love to be on the cube and every once in a while you'll even call me a friend of the cube, >>unquestionably my friend and so and I can't wait second half. I mean you're traveling right now. We're headed to Barcelona to mobile World Congress later on this month. So so we're gonna we're gonna see each other face to face this year. 100%. So looking forward to that. So, you know, let's get into it. Um you know, before we get into H. P. E. Let's talk a little bit about what you're seeing in the market. We've got, you know, we we we finally, it feels like the on prem guys are finally getting their cloud act together. Um, it's maybe taken a while, but we're seeing as a service models emerge. I think it's resonating with customers. The clearly not everything is moving to the cloud. There's this hybrid model emerging. Multi cloud is real despite what, you know, >>some some >>cloud players want to say. And then there's this edges like jump ball, what are you seeing in the marketplace? >>Yeah. Davis, as exciting as ever in. Just to put in perspective, I mean, the public cloud has been around for about 10 years and still only 20%. Around 20% of the data in 20% of the applications are there now, albeit very important ones. And I'm certainly not a public cloud denier, I never have been, but there are some missing pieces that need to come together. And you know, even five years ago we were debating dave the hybrid cloud and I feel like when Amazon brought out outposts, the conversation was over right now, what you have is cloud native folks building out hybrid and on prem capabilities, you have the classic on prem folks building out hybrid and as a service capabilities. And I really think it boils down 22 things. I mean it's wanting to have more flexibility and you know, I hate to use it because it sounds like a marketing word, but agility, the ability to spin up things and spin down things in a very quick way. And uh, you know what they've learned. The veterans also know, hey, let's do this in a way that doesn't lock us in too much into a certain vendor. And I've been around for a long time. David and I'm a realist too. Well, you have to lock yourself into something. It just depends on what do you want to lock yourself into, but super exciting. And what H. P. E. When they threw the acts in the sea with Green Lake, I think it was four years ago, I think really started to stir the pot. >>You know, you mentioned the term cloud denial, but you know, and I feel like the narrative from, I like to determine is I think you should use the term veteran. You know, it's very, they're ours is the only industry patrick where legacy is a pejorative, but but but so but the point I want to make is I feel like there's been a lot of sort of fear from the veteran players, but I look at it differently. I wonder what you're taking. I think, I think, I think I calculated that the Capex spending by the big four public clouds including Alibaba last year was $100 billion. That's like a gift to the world. Here, we're going to spend $100 billion like the internet here you go build. And and so I, and I feel like companies like HP are finally saying, yeah, we're gonna build, we're gonna build a layer and we're gonna hide the complexity and we're gonna add value on top. What do you think about that? >>Yeah. So I think it's now, I wish, I wish the on prem folks like HP, you would have done it 10 years ago, but I don't think anybody expected the cloud to be as big as it's become over the last 10 years. I think we saw companies like salesforce with sas taking off, but I think it is the right direction because there are advantages to having workloads on prem and if you add an as a service capability on top of the top of that, and let's say even do a Coehlo or a managed service, it's pretty close to being similar to the public cloud with the exception, that you can't necessarily swipe a credit card for a bespoke workload if you're a developer and it is a little harder to scale out. But that is the next step in the equation day, which is having, having these folks make capital expenditures, make them in a polo facility and then put a layer to swipe a credit card and you literally have the public cloud. >>Yeah. So that's, that's a great point and that's where it's headed, isn't it? Um, so let's, let's talk about the horses on the track. Hp. As you mentioned, I didn't realize it was four years ago. I thought it was, wow, That's amazing. So everybody's followed suit. You see, Dallas announced, Cisco has announced, uh, Lenovo was announced, I think IBM as well. So we, so everybody started following suit there. The reality is, is it's taken some time to get this stuff standardized. What are you seeing from, from HP? They've made some additional announcements, discover what's your take on all this. >>Yeah. So HPD was definitely the rabbit here and they were first in the market. It was good to see, first off some of their, Um, announcements on, on how it's going. And they talked about 4, $28 billion 1200 customers over 900 partners and 95% retention. And I think that's important anybody who's in the lead and remember what Aws used to do with the slide with the amount of customers would just get bigger and bigger and bigger and that's a good way to show momentum. I like the retention part two which is 95%. And I think that that says a lot uh probably the more important announcements that they made is they talked about the G. A. Of some of their solutions on Green Lake and whether it was S. A. P. Hana Ml apps HPC with Francis V. I was Citrus in video but they also brought more of what I would call a vertical layer and I'm sure you've seen the vertical ization of all of these cloud and as a service workloads. But what they're doing with Epic with EMR and looseness, with financial payments and Splunk and intel with data and risk analysis and finally, a full stack for telco five G. One of the biggest secrets and I covered this about five years ago is HPV actually has a full stack that western european carriers use and they're now extending that to five G. And um, so more horizontal uh and and more vertical. That was the one of the big swipes uh that I saw that there was a second though, but maybe we can talk about these. >>Yeah. Okay, Okay. So, so the other piece of that of course is standardization right there there because there was a, there was, there was a lot of customization leading up to this and everybody sort of, everybody always had some kind of financial game they can play and say, hey, there's an adversary as a service model, but this is definitely more of a standardized scalable move that H P E. Is making with what they call Lighthouse, Right? >>Yeah, that's exactly right. And I've talked to some Green Lake customers and they obviously gave it kudos or they wouldn't have HP wouldn't have served them up and they wouldn't have been buying it. But they did say, um, it took, it took a while, took some paperwork to get it going. It's not 100% of push button, but that's partially because hp allows you to customize the hardware. You want a one off network adapter. Hp says yes, right. You want to integrate a different type of storage? They said yes. But with Green Lake Lighthouse, it's more of a, what you see is what you get, which by the way is very much like the public cloud or you go to a public cloud product sheet or order sheet. You're picking from a list and you really don't know everything that's underneath the covers, aside from, let's say the speed of the network, the type of the storage and the amount of the storage you get. You do get to pick between, let's say, an intel processor, Graviton two or an M. D processor. You get to pick your own GPU. But that's pretty much it. And HP Lighthouse, sorry, Green Lake Lighthouse uh, is bringing, I think a simplification to Green Lake that it needs to truly scale beyond, let's say, the white house customers at HP. Yeah, >>Well done. So, you know, and I hear your point about 10 years in, you know, plus and to me this is like a mandate. I mean, this is okay. Good, good job guys about time. But if I had a, you know, sort of look at the big players, like, can we have an oligopoly here in this, in this business? It's HP, Cisco, you got Dell Lenovo, you've got, you know, IBM, they're all doing this and they all have a different little difference, you know, waste of skin of catch. And your point about simplicity, it seems like HP HP is all in Antonio's like, okay, here's what we're going to announce that, you know, while ago, so, and they seem to have done a good job with Wall Street and they get a simple model, you know, Dell's obviously bigger portfolio, much more complicated. IBM is even more complicated than that. I don't know so much about Lenovo and in Cisco of course, has acquired a ton of SAAS companies and sort of they've got a lot of bespoke products that they're trying to put together, so they've got, but they do have SAS models. So each of them is coming at it from a different perspective. How do you think? And so and the other point we got lighthouse, which is sort of Phase one, get product market fit. Phase two now is scale codify standardized and then phase three is the moat build your unique advantage that protects your business. What do you see as HP? Es sort of unique value proposition and moat that they can build longer term. >>That's a great, great question. And let me rattle off kind of what I'm seeing that some of these these players here. So Cisco, ironically, has sells the most software of any of those players that you mentioned, uh with the exception of IBM. Um, and yeah, C >>ICSDB two. Yeah, >>yeah, they're the they're the number two security player, uh, Microsoft, number one. So and I think the evaluation on the street uh indicate that shows that I feel like uh Deltek is a is a very broad play because not only do they have servers, storage, networking and security, but they also have Pcs and devices, so it's a it's a scale and end play with a focus on VM ware solutions, not exclusively, of course. Uh And um then you've got Lenovo who is just getting into the as a service game and are gosh, they're doing great in hyper scale, they've got scale there vertically integrated. I don't know if if too many people talk about that, but Lenovo does a lot of their own manufacturing and they actually manufacture Netapp storage solutions as well. So yeah, each of these folks brings a different game to the table, I think with h P E, what your bring to the table is nimble. When HP and HP split, the number one thing that I said was that uh huh H P E is going to have to be so much faster than it offsets the scale that Dell technology has and the HBs credit, although there, I don't think we're getting credit for this in the stock market yet. Um, and I know you and I are both industry folks, not financial folks, but I think their biggest thing is speed and the ability to move faster and that is what I've seen as it relates to the moat, which is a unique uh, competitive advantage. Quite frankly, I'm still looking for that day in, in, in what that is and I think in this industry it's nearly impossible and I would posit that that any, even the cloud folks, if you say, is there something that AWS can do that Azure can't, if it put it put its mind to it or G C P. I don't think so. I think it's more of a kind of land and expand and I think for H P E, when it comes to high performance computing and I'm not just talking about government installations, I'm talking about product development, drug development, I think that is a landing place where H P E already does pretty well can come in and expand its footprint, >>you know, that's really interesting um, observations. So, and I would agree with you, it's kind of like, this is a copycat industry, it's like the west coast offense, like the NFL >>and >>so, so the moat comes from, you know, brand execution and your other point about when HP and HP split, that was a game changer, because all of a sudden you saw companies like them, you always had a long term relationship with H P E but or HP, but then they came out of the woodworks and started to explode. And so it really opened up opportunities. So it really >>is an execution, >>isn't it? But go ahead, please >>Dave if I had to pick something that I think HP HPV needs to always be ahead and as a service and listen, you know, I both know announcements don't mean delivery, but there is correlation between if you start four years ahead of somebody that other company is going to have to put just, I mean they're gonna have to turn that ship and many of its competitors really big ships to be able to get there. So I think what Antonio needs to do is run like hell, right, Because it, it, I think it is in the lead and as a service holistically doesn't mean they're going to be there forever, but they have to stay ahead. They have to add more horizontal solutions. They have to add more vertical solutions. And I believe that at some point it does need to invest in some Capex at somebody like ANna Quinn x play credit card swiper on top of that. And Dave, you have the public, you have the public cloud, you don't have all the availability zones, but you have a public cloud. >>Yeah, that's going to happen. I think you're right on. So we see this notion of cloud expanding. It's no longer just remote set of services. Somewhere out in the cloud. It's as you said, outpost was the sort of signal. Okay, We're coming on prem clearly the on prem, uh, guys are connecting to the cloud. Multi cloud exists, we know this and then there's the edge but but but that brings me to that sort of vision and everybody's laying out of this this this seamless integration hiding the complexity log into my cloud and then life will be good. But the edge is different. Right? It's not just, you know, retail store or a race track. I mean there's the far edge, there's the Tesla car, there's gonna be compute everywhere. And that sort of ties into the data. The data flows, you know the real time influencing at the edge ai new semiconductor models. You you came out of the semiconductor industry, you know it inside and out arm is exploding is dominating in the edge with with with apple and amazon Alexa and things like that. That's really where the action is. So this is a really interesting cocktail and soup that we have going on. How do you >>say? Well, you know, Dave if the data most data, I think one thing most everybody agrees on is that most of the data will be created on the edge. Whether that's a moving edge a car, a smartphone or what I call an edge data center without tile flooring. Like that server that's bolted to the wall of Mcdonald's. When you drive through, you can see it versus the walmart. Every walmart has a raised tile floor. It's the edge to economically and performance wise, it doesn't make any sense to send all that data to the mother ships. Okay. And whether that's unproven data center or the giant public cloud, more efficient way is to do the compute at the closest way possible. But what it does, it does bring up challenges. The first challenge is security. If I wanted to, I could walk in and I could take that server off the Mcdonald's or the Shell gas station wall. So I can't do that in a big data center. Okay, so security, Physical security is a challenge. The second is you don't have the people to go in there and fix stuff that are qualified. If you have a networking problem that goes wrong and Mcdonald's, there's nobody there that can help uh, they can they can help you fix that. So this notion of autonomy and management and not keeping hyper critical data sitting out there and it becomes it becomes a security issue becomes a management issue. Let me talk about the benefits though. The benefits are lower latency. You want you want answers more quickly when that car is driving down the road and it has a five G V two X communication cameras can't see around corners, but that car communicating ahead, that ran into the stop sign, can I through vi to X. Talk to the car behind it and say, hey, something is going on there, you can't go to, you can't go to the big data center in the sky to make that happen, that is to be in near real time and that computer has to happen on the edge. So I think this is a tremendous opportunity and ironically the classic on prem guys, they own this, they own this space aside from smartphones of course, but if you look at compute on a light pole, companies like Intel have built Complete architectures to do that, putting compute into 5G base stations. Heck, I just, there was an announcement this week of google cloud in its gaming solution putting compute in a carrier edge to give lower latency to deliver a better experience. >>Yeah, so there, of course there is no one edge, it's highly fragmented, but I'm interested in your thoughts on kind of who's stack actually can play at the edge. And I've been sort of poking uh H P E about this. And the one thing that comes back consistently is Aruba, we we can take a room but not only to the, to the near edge, but to the far edge. And and that, do you see that as a competitive advantage? >>Oh gosh, yes. I mean, I would say the best acquisition That hp has made in 10 years has been aruba it's fantastic. And they also managed it in the right way. I mean, it was part of HB but it was it was managed a lot more loosely then, you know, a company that might get sucked into the board. And I think that paid off tremendously. They're giving Cisco on the edge a absolute run for their money, their first with new technologies. But it's about the solution. What I love about what a ruble looks at is it's looking at entertainment solutions inside of a stadium, um a information solution inside of an airport as opposed to just pushing the technology forward. And then when you integrate compute with with with Aruba, I think that's where the real magic happens. Most of the data on a permanent basis is actually video data. And a lot of it's for security uh for surveillance. And quite frankly, people taking videos off, they're off their smartphones and downloading video. I I just interviewed the chief network officer of T mobile and their number one bit of data is video, video uploaded, video download. But that's where the magic happens when you put that connectivity and the compute together and you can manage it in a, in an orderly and secure fashion >>while I have you, we have a ton of time here, but I I don't pick your brain about intel, the future of intel. I know you've been following it quite closely, you always have Intel's fighting a forefront war. You got there, battling A. M. D. There, battling your arm slash and video. They're they're taking on TSMC now and in foundry and, and I'll add china for the looming threat there. So what's your prognosis for for intel? >>Yeah, I liked bob the previous Ceo and I think he was doing a lot of of the right things, but I really think that customers and investors and even their ecosystem wanted somebody leading the company with a high degree of technical aptitude and Pat coming, I mean, Pat had a great job at VM or, I mean, he had a great run there and I think it is a very positive move. I've never seen the energy At Intel probably in the last 10 years that I've seen today. I actually got a chance to talk with pat. I visited pat uhh last month and and talk to him about pretty much everything and where he wanted to take the company the way you looked at technology, what was important, what's not important. But I think first off in the world of semiconductors, there are no quick fixes. Okay. Intel has a another two years Before we see what the results are. And I think 2023 for them is gonna be a huge year. But even with all this competition though, Dave they still have close to 85% market share in servers and revenue share for client computing around 90%. Okay. So and they've built out there networking business, they build out a storage business um with with obtain they have the leading Aid as provider with Mobileye. And and listen I was I was one of Intel's biggest, I was into one of Intel's biggest, I was Intel's biggest customer when I was a compact. I was their biggest competitor at AMG. So um I'm not obviously not overly pushing or there's just got to wait and see. They're doing the right things. They have the right strategy. They need to execute. One of the most important things That Intel did is extend their alliance with TSMC. So in 2023 we're going to see Intel compute units these tiles, they integrate into the larger chips called S. O. C S B. Manufactured by TSMC. Not exclusively, but we could see that. So literally we could have AMG three nanometer on TSMC CPU blocks, competing with intel chips with TSMC three nanometer CPU blocks and it's on with regard to video. I mean in video is one of these companies that just keeps going charging, charging hard and I'm actually meeting with Jensen wang this week and Arms Ceo Simon Segers to talk about this opportunity and that's a company that keeps on moving interestingly enough in video. If the arm deal does go through will be the largest chip license, see CPU licensee and have the largest CPU footprint on the planet. So here we have AMG who's CPU and Gpu and buying an F. P. G. A company called Xilinx, you have Intel, Cpus, Gpus machine learning accelerators and F. P. G. S. And then you've got arms slashing video bit with everything as well. We have three massive ecosystems. They're gonna be colliding here and I think it's gonna be great for competition. Date. Competition is great. You know, when there's not competition in CPUs and Gpus, we know what happens right. Uh, the beach just does not go on and we start to stagnate. And I did, I do feel like the industry on CPU started to stagnate when intel had no competition. So bring it on. This is gonna be great for for enterprises then customers to and then, oh, by the way, you have the custom Chip providers. WS has created no less than 15 custom semiconductors started with networking and nitro and building out an edge that surrounded the general computer. And then it moved to Inferential for inference trainee um, is about to come out for training Graviton and Gravitas to for general purpose CPU and then you've got apple. So innovation is huge and I love to always make fun of the software is eating the world. I always say yeah but has to run on something. And so I think the combination of semiconductors software and cloud is just really a magical combination. >>Real quick handicap the video arm acquisition. What what are the odds that that they will be successful? They say it's on track. You got a 2 to 13 to 1 10 to 1. >>I say 75%. Yes 25%. No China is always the has been the odd odd man out for the last three years. They scuttled the Qualcomm NXp deal. You just don't know what china is going to do. I think the EU with some conditions is going to let this fly. I think the U. S. Is absolutely going to let this fly. And even though the I. P. Will still stay over in the UK, I think the U. S. Wants to see wants to see this happen, Japan and Korea I think we'll allow this china is the odd man out. >>In a word, the future of h p. E is blank >>as a service >>patrick Moorehead. Always a pleasure. My friend. Great to see you. Thanks so much for coming back in the cube. >>Yeah, Thanks for having me on. I appreciate that. >>Everybody stay tuned for more great coverage from HP discover 21 this is day Volonte for the cube. The leader and enterprise tech coverage. We'll be right back.

Published Date : Jun 10 2021

SUMMARY :

Patrick Moorehead is here of moor insights and strategy is the It's great to see you and it's great to see you in the meetings that were in. I think it's resonating with customers. And then there's this edges like jump ball, what are you seeing in the marketplace? the conversation was over right now, what you have is cloud native folks building out hybrid I like to determine is I think you should use the term veteran. the cloud to be as big as it's become over the last 10 years. let's talk about the horses on the track. I like the retention part that H P E. Is making with what they call Lighthouse, Right? the type of the storage and the amount of the storage you get. and they seem to have done a good job with Wall Street and they get a simple model, you know, So Cisco, ironically, has sells the most software Yeah, posit that that any, even the cloud folks, if you say, you know, that's really interesting um, observations. so, so the moat comes from, you know, brand execution and the lead and as a service holistically doesn't mean they're going to be there forever, is dominating in the edge with with with apple and amazon Alexa center in the sky to make that happen, that is to be in near real time And and that, do you see that as a competitive And then when you integrate compute intel, the future of intel. And I did, I do feel like the industry on CPU started to stagnate You got a 2 to 13 to 1 10 to 1. I think the U. S. Is absolutely going to let Thanks so much for coming back in the cube. I appreciate that. The leader and enterprise tech coverage.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
DavePERSON

0.99+

DavidPERSON

0.99+

IBMORGANIZATION

0.99+

CiscoORGANIZATION

0.99+

Dave VolontePERSON

0.99+

AWSORGANIZATION

0.99+

LenovoORGANIZATION

0.99+

AmazonORGANIZATION

0.99+

MicrosoftORGANIZATION

0.99+

TSMCORGANIZATION

0.99+

HPORGANIZATION

0.99+

BarcelonaLOCATION

0.99+

Patrick MoorheadPERSON

0.99+

75%QUANTITY

0.99+

PatrickPERSON

0.99+

patrick MooreheadPERSON

0.99+

walmartORGANIZATION

0.99+

$100 billionQUANTITY

0.99+

AlibabaORGANIZATION

0.99+

H P EORGANIZATION

0.99+

HPDORGANIZATION

0.99+

20%QUANTITY

0.99+

25%QUANTITY

0.99+

95%QUANTITY

0.99+

100%QUANTITY

0.99+

WSORGANIZATION

0.99+

DellORGANIZATION

0.99+

Patrick MooreheadPERSON

0.99+

2021DATE

0.99+

UKLOCATION

0.99+

amazonORGANIZATION

0.99+

PatPERSON

0.99+

appleORGANIZATION

0.99+

$100 billionQUANTITY

0.99+

Francis V.PERSON

0.99+

four yearsQUANTITY

0.99+

2023DATE

0.99+

IntelORGANIZATION

0.99+

13QUANTITY

0.99+

last yearDATE

0.99+

bothQUANTITY

0.99+

eachQUANTITY

0.99+

QualcommORGANIZATION

0.99+

AMGORGANIZATION

0.99+

CapexORGANIZATION

0.99+

oneQUANTITY

0.99+

Green LakeORGANIZATION

0.99+

last monthDATE

0.99+

10 years agoDATE

0.99+

XilinxORGANIZATION

0.99+

TeslaORGANIZATION

0.99+

T mobileORGANIZATION

0.98+

secondQUANTITY

0.98+

telcoORGANIZATION

0.98+

five years agoDATE

0.98+

DavisPERSON

0.98+

firstQUANTITY

0.98+

22 thingsQUANTITY

0.98+

The Data Drop: Industry Insights | HPE Ezmeral Day 2021


 

(upbeat music) >> Welcome friends to HPE Ezmeral's analytics unleashed. I couldn't be more excited to have you here today. We have a packed and informative agenda. It's going to give you not just a perspective on what HPE Ezmeral is and what it can do for your organization, but you should leave here with some insights and perspectives that will help you on your edge to cloud data journey in general. The lineup we have today is awesome. We have industry experts like Kirk Borne, who's going to talk about the shape this space will take to key customers and partners who are using Ezmeral technology as a fundamental part of their stack to solve really big, hairy, complex real data problems. We will hear from the execs who are leading this effort to understand the strategy and roadmap forward as well as give you a sneak peek into the new ISV ecosystem that is hosted in the Ezmeral marketplace. And finally, we have some live music being played in the form of three different demos. There's going to be a fun time so do jump in and chat with us at any time or engage with us on Twitter in real time. So grab some coffee, buckle up and let's get going. (upbeat music) Getting data right is one of the top priorities for organizations to affect digital strategy. So right now we're going to dig into the challenges customers face when trying to deploy enterprise wide data strategies and with me to unpack this topic is Kirk Borne, principal data scientist, and executive advisor, Booz Allen Hamilton. Kirk, great to see you. Thank you sir, for coming into the program. >> Great to be here, Dave. >> So hey, enterprise scale data science and engineering initiatives, they're non-trivial. What do you see as some of the challenges in scaling data science and data engineering ops? >> The first challenge is just getting it out of the sandbox because so many organizations, they, they say let's do cool things with data, but how do you take it out of that sort of play phase into an operational phase? And so being able to do that is one of the biggest challenges, and then being able to enable that for many different use cases then creates an enormous challenge because do you replicate the technology and the team for each individual use case or can you unify teams and technologies to satisfy all possible use cases. So those are really big challenges for companies organizations everywhere to about. >> What about the idea of, you know, industrializing those those data operations? I mean, what does that, what does that mean to you? Is that a security connotation, a compliance? How do you think about it? >> It's actually, all of those I'm industrialized to me is sort of like, how do you not make it a one-off but you make it a sort of a reproducible, solid risk compliant and so forth system that can be reproduced many different times. And again, using the same infrastructure and the same analytic tools and techniques but for many different use cases. So we don't have to rebuild the wheel, reinvent the wheel re reinvent the car. So to speak every time you need a different type of vehicle you need to build a car or a truck or a race car. There's some fundamental principles that are common to all of those. And that's what that industrialization is. And it includes security compliance with regulations and all those things but it also means just being able to scale it out to to new opportunities beyond the ones that you dreamed of when you first invented the thing. >> Yeah. Data by its very nature as you well know, it's distributed, but for a you've been at this awhile for years we've been trying to sort of shove everything into a monolithic architecture and in in hardening infrastructures or around that. And in many organizations it's become a block to actually getting stuff done. But so how, how are you seeing things like the edge emerge How do you, how do you think about the edge? How do you see that evolving and how do you think customers should be dealing with with edge and edge data? >> Well, that's really kind of interesting. I had many years at NASA working on data systems, and back in those days, the idea was you would just put all the data in a big data center and then individual scientists would retrieve that data and do analytics on it do their analysis on their local computer. And you might say that's sort of like edge analytics so to speak because they're doing analytics at their home computer, but that's not what edge means. It means actually doing the analytics the insights discovery at the point of data collection. And so that's that's really real time business decision-making you don't bring the data back and then try to figure out some time in the future what to do. And I think in autonomous vehicles a good example of why you don't want to do that because if you collect data from all the cameras and radars and lidars that are on a self-driving car and you move that data back to a data cloud while the car is driving down the street and let's say a child walks in front of the car you send all the data back at computes and does some object recognition and pattern detection. And 10 minutes later, it sends a message to the car. Hey, you need to put your brakes off. Well, it's a little kind of late at that point. And so you need to make those discoveries those insight discoveries, those pattern discoveries and hence the proper decisions from the patterns in the data at the point of data collection. And so that's data analytics at the edge. And so, yes, you can ring the data back to a central cloud or distributed cloud. It almost doesn't even matter if, if if your data is distributed sort of any use case in any data scientist or any analytic team and the business can access it then what you really have is a data mesh or a data fabric that makes it accessible at the point that you need it, whether it's at the edge or on some static post event processing, for example typical business quarter reporting takes a long look at your last three months of business. Well, that's fine in that use case, but you can't do that for a lot of other real time analytic decision making. >> Well, that's interesting. I mean, it sounds like you think of the edge not as a place, but as you know where it makes sense to actually, you know the first opportunity, if you will, to process the data at at low latency where it needs to be low latency is that a good way to think about it? >> Yeah, absolutely. It's the low latency that really matters. Sometimes we think we're going to solve that with things like 5G networks. We're going to be able to send data really fast across the wire. But again, that self-driving car has yet another example because what if you, all of a sudden the network drops out you still need to make the right decision with the network not even being . >> That darn speed of light problem. And so you use this term data mesh or data fabric double-click on that. What do you mean by that? >> Well, for me, it's, it's, it's, it's sort of a unified way of thinking about all your data. And when I think of mesh, I think of like a weaving on a loom, or you're creating a blanket or a cloth and you do weaving and you do that all that cross layering of the different threads. And so different use cases in different applications in different techniques can make use of this one fabric no matter what, where it is in the, in the business or again, if it's at the edge or, or back at the office one unified fabric, which has a global namespace. So anyone can access the data they need and sort of uniformly no matter where they're using it. And so it's, it's a way of unifying all of the data and use cases and sort of a virtual environment that it could have that no log you need to worry about. So what's what's the actual file name or what's the actual server this thing is on you can just do that for whatever use case you have. Let's I think it helps you enterprises now to reach a stage which I like to call the self-driving enterprise. Okay. So it's modeled after the self-driving car. So the self-driving enterprise needs the business leaders in the business itself, you would say needs to make decisions oftentimes in real time. All right. And so you need to do sort of predictive modeling and cognitive awareness of the context of what's going on. So all of these different data sources enable you to do all those things with data. And so, for example, any kind of a decision in a business any kind of decision in life, I would say is a prediction. It's you say to yourself if I do this such and such will happen if I do that, this other thing will happen. So a decision is always based upon a prediction about outcomes, and you want to optimize that outcome. So both predictive and prescriptive analytics need to happen in this in this same stream of data and not statically afterwards. And so that's, self-driving enterprises enabled by having access to data wherever you and whenever you need it. And that's what that fabric, that data fabric and data mesh provides for you, at least in my opinion. >> Well, so like carrying that analogy like the self-driving vehicle you're abstracting that complexity away in in this metadata layer that understands whether it's on prem or in the public cloud or across clouds or at the edge where the best places to process that data. What makes sense, does it make sense to move it or not? Ideally, I don't have to. Is that how you're thinking about it is that why we need this notion of a data fabric >> Right. It really abstracts away all the sort of the complexity that the it aspects of the job would require, but not every person in the business is going to have that familiarity with with the servers and the access protocols and all kinds of it related things. And so abstracting that away. And that's in some sense, what containers do basically the containers abstract away all the information about servers and connectivity and protocols and all this kind of thing. You just want to deliver some data to an analytic module that delivers me an insight or a prediction. I don't need to think about all those other things. And so that abstraction really makes it empowering for the entire organization. We like to talk a lot about data democratization and analytics democratization. This really gives power to every person in the organization to do things without becoming an it expert. >> So the last, last question we have time for here. So it sounds like. Kirk, the next 10 years of data are not going to be like the last 10 years, it'd be quite different. >> I think so. I think we're moving to this. Well, first of all, we're going to be focused way more on the why question, like, why are we doing this stuff? The more data we collect, we need to know why we're doing it. And what are the phrases I've seen a lot in the past year which I think is going to grow in importance in the next 10 years is observability. So observability to me is not the same as monitoring. Some people say monitoring is what we do. But what I like to say is, yeah, that's what you do but why you do it is observability. You have to have a strategy. Why, what, why am I collecting this data? Why am I collecting it here? Why am I collecting it at this time resolution? And so, so getting focused on those, why questions create be able to create targeted analytics solutions for all kinds of diff different business problems. And so it really focuses it on small data. So I think the latest Gartner data and analytics trending reports, so we're going to see a lot more focus on small data in the near future >> Kirk borne. You're a dot connector. Thanks so much for coming on the cube and being a part of the program. >> My pleasure (upbeat music) (relaxing upbeat music)

Published Date : Mar 17 2021

SUMMARY :

It's going to give you What do you see as some of the challenges and the team for each individual use case So to speak every time you need and how do you think customers at the point that you need the first opportunity, if you It's the low latency that really matters. And so you use this term data mesh in the business itself, you would say or at the edge where the best in the business is going to So the last, last question data in the near future on the cube and being

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
DavePERSON

0.99+

NASAORGANIZATION

0.99+

Kirk BornePERSON

0.99+

KirkPERSON

0.99+

GartnerORGANIZATION

0.99+

bothQUANTITY

0.99+

oneQUANTITY

0.99+

three different demosQUANTITY

0.98+

todayDATE

0.98+

first challengeQUANTITY

0.98+

first opportunityQUANTITY

0.98+

HPEORGANIZATION

0.98+

past yearDATE

0.96+

EzmeralORGANIZATION

0.96+

HPE EzmeralORGANIZATION

0.95+

TwitterORGANIZATION

0.94+

firstQUANTITY

0.93+

10 minutes laterDATE

0.93+

each individualQUANTITY

0.91+

Booz AllenORGANIZATION

0.83+

next 10 yearsDATE

0.83+

2021DATE

0.82+

HamiltonPERSON

0.79+

last 10 yearsDATE

0.7+

yearsQUANTITY

0.59+

three monthsQUANTITY

0.59+

Ezmeral DayEVENT

0.43+

Derek Manky Chief, Security Insights & Global Threat Alliances at Fortinet's FortiGuard Labs


 

>>As we've been reporting, the pandemic has called CSOs to really shift their spending priorities towards securing remote workers. Almost overnight. Zero trust has gone from buzzword to mandate. What's more as we wrote in our recent cybersecurity breaking analysis, not only Maseca pro secured increasingly distributed workforce, but now they have to be wary of software updates in the digital supply chain, including the very patches designed to protect them against cyber attacks. Hello everyone. And welcome to this Q conversation. My name is Dave Vellante and I'm pleased to welcome Derek manky. Who's chief security insights, and global threat alliances for four guard labs with fresh data from its global threat landscape report. Derek. Welcome. Great to see you. >>Thanks so much for, for the invitation to speak. It's always a pleasure. Multicover yeah, >>You're welcome. So first I wonder if you could explain for the audience, what is for guard labs and what's its relationship to fortunate? >>Right. So 40 grand labs is, is our global sockets, our global threat intelligence operation center. It never sleeps, and this is the beat. Um, you know, it's, it's been here since inception at port in it. So it's it's 20, 21 years in the making, since Fortinet was founded, uh, we have built this in-house, uh, so we don't go yum technology. We built everything from the ground up, including creating our own training programs for our, our analysts. We're following malware, following exploits. We even have a unique program that I created back in 2006 to ethical hacking program. And it's a zero-day research. So we try to meet the hackers, the bad guys to their game. And we of course do that responsibly to work with vendors, to close schools and create virtual patches. Um, and, but, you know, so it's, it's everything from, uh, customer protection first and foremost, to following, uh, the threat landscape and cyber. It's very important to understand who they are, what they're doing, who they're, uh, what they're targeting, what tools are they using? >>Yeah, that's great. Some serious DNA and skills in that group. And it's, it's critical because like you said, you can, you can minimize the spread of those malware very, very quickly. So what, what now you have, uh, the global threat landscape report. We're going to talk about that, but what exactly is that? >>Right? So this a global threat landscape report, it's a summary of, uh, all, all the data that we collect over a period of time. So we released this, that biannually two times a year. Um, cyber crime is changing very fast, as you can imagine. So, uh, while we do release security blogs, and, uh, what we call threat signals for breaking security events, we have a lot of other vehicles to release threat intelligence, but this threat landscape report is truly global. It looks at all of our global data. So we have over 5 million censorship worldwide in 40 guard labs, we're processing. I know it seems like a very large amount, but North of a hundred billion, uh, threat events in just one day. And we have to take the task of taking all of that data and put that onto scale for half a year and compile that into something, um, that is, uh, the, you know, that that's digestible. That's a, a very tough task, as you can imagine, so that, you know, we have to work with a huge technologies back to machine learning and artificial intelligence automation. And of course our analyst view to do that. >>Yeah. So this year, of course, there's like the every year is a battle, but this year was an extra battle. Can you explain what you saw in terms of the hacker dynamics over the past? Let's say 12 months. I know you do this twice a year, but what trends did you see evolving throughout the year and what have you seen with the way that attackers have exploited this expanded attack surface outside of corporate network? >>Yeah, it was quite interesting last year. It certainly was not normal. Like we all say, um, and that was no exception for cybersecurity. You know, if we look at cyber criminals and how they pivoted and adapted to the scrap threat landscape, cyber cyber criminals are always trying to take advantage of the weakest link of the chain. They're trying to always prey off here and ride waves of global trends and themes. We've seen this before in, uh, natural disasters as an example, you know, um, trying to do charity kind of scams and campaigns. And they're usually limited to a region where that incident happened and they usually live about two to three weeks, maybe a month at the most. And then they'll move on to the next to the next trip. That's braking, of course, because COVID is so global and dominant. Um, we saw attacks coming in from, uh, well over 40 different languages as an example, um, in regions all across the world that wasn't lasting two to three weeks and it lasted for the better part of a year. >>And of course, what they're, they're using this as a vehicle, right? Not preying on the fear. They're doing everything from initial lockdown, uh, fishing. We were as COVID-19 movers to, um, uh, lay off notices then to phase one, reopenings all the way up to fast forward to where we are today with vaccine rollover development. So there's always that new flavor and theme that they were rolling out, but because it was so successful for them, they were able to, they didn't have to innovate too much, right. They didn't have to expand and shifted to new to new trends. And themes are really developed on new rats families as an example, or a new sophisticated malware. That was the first half of the year and the second half of the year. Um, of course people started to experience COVID fatigue, right? Um, people started to become, we did a lot of education around this. >>People started to become more aware of this threat. And so, um, cyber criminals have started to, um, as we expected, started to become more sophisticated with their attacks. We saw an expansion in different ransomware families. We saw more of a shift of focus on, on, um, uh, you know, targeting the digital supply chain as an example. And so that, that was, that was really towards Q4. Uh, so it, it was a long lived lead year with success on the Google themes, um, targeting healthcare as an example, a lot of, um, a lot of the organizations that were, you know, really in a vulnerable position, I would say >>So, okay. I want to clarify something because my assumption was that they actually did really increase the sophistication, but it sounds like that was kind of a first half trends. Not only did they have to adapt and not have to, but they adapt it to these new vulnerabilities. Uh, my sense was that when you talk about the digital supply chain, that that was a fairly sophisticated attack. Am I, am I getting that right? That they did their sort of their, their, their increased sophistication in the first half, and then they sort of deployed it, did it, uh, w what actually happened there from your data? >>Well, if we look at, so generally there's two types of attacks that we look at, we look at the, uh, the premeditated sophisticated attacks that can have, um, you know, a lot of ramp up work on their end, a lot of time developing the, the, the, the weaponization phase. So developing, uh, the exploits of the sophisticated malware that they're gonna use for the campaign reconnaissance, understanding the targets, where platforms are developed, um, the blueprinting that DNA of, of, of the supply chain, those take time. Um, in fact years, even if we look back to, um, uh, 10 plus years ago with the Stuxnet attacks, as an example that was on, uh, nuclear centrifuges, um, and that, that had four different zero-day weapons at the time. That was very sophisticated, that took over two years to develop as an example. So some of these can take years of time to develop, but they're, they're, uh, very specific in terms of the targets are going to go after obviously the ROI from their end. >>Uh, the other type of attack that we see is as ongoing, um, these broad, wide sweeping attacks, and the reality for those ones is they don't unfortunately need to be too sophisticated. And those ones were the ones I was talking about that were really just playing on the cool, the deem, and they still do today with the vaccine road and development. Uh, but, but it's really because they're just playing on, on, um, you know, social engineering, um, using, uh, topical themes. And in fact, the weapons they're using these vulnerabilities are from our research data. And this was highlighted actually the first pop landscape before last year, uh, on average were two to three years old. So we're not talking about fresh vulnerabilities. You've got to patch right away. I mean, these are things that should have been patched two years ago, but they're still unfortunately having success with that. >>So you mentioned stuck next Stuxnet as the former sort of example, of one of the types of attacks that you see. And I always felt like that was a watershed moment. One of the most sophisticated, if not the most sophisticated attack that we'd ever seen. When I talk to CSOs about the recent government hack, they, they, they suggest I infer maybe they don't suggest it. I infer that it was of similar sophistication. It was maybe thousands of people working on this for years and years and years. Is that, is that accurate or not necessarily? >>Yeah, there's definitely a, there's definitely some comparisons there. Uh, you know, one of the largest things is, uh, both attacks used digital circuits certificate personation, so they're digitally signed. So, you know, of course that whole technology using cryptography is designed by design, uh, to say that, you know, this piece of software installed in your system, hassles certificate is coming from the source. It's legitimate. Of course, if that's compromised, that's all out of the window. And, um, yeah, this is what we saw in both attacks. In fact, you know, stocks in that they also had digitally designed, uh, certificates that were compromised. So when it gets to that level of students or, uh, sophistication, that means definitely that there's a target that there has been usually months of, of, uh, homework done by cyber criminals, for reconnaissance to be able to weaponize that. >>W w what did you see with respect to ransomware? What were the trends there over the past 12 months? I've heard some data and it's pretty scary, but what did you see? >>Yeah, so we're actually, ransomware is always the thorn in our side, and it's going to continue to be so, um, you know, in fact, uh, ransomware is not a new itself. It was actually first created in 1989, and they demanded ransom payments through snail mail. This was to appeal a box, obviously that, that, that didn't take off. Wasn't a successful on the internet was porn at the time. But if you look at it now, of course, over the last 10 years, really, that's where it ran. The ransomware model has been, uh, you know, lucrative, right? I mean, it's been, um, using, uh, by force encrypting data on systems, so that users had to, if they were forced to pay the ransom because they wanted access to their data back data was the target currency for ransomware. That's shifted now. And that's actually been a big pivotal over the last year or so, because again, before it was this let's cast a wide net, in fact, as many people as we can random, um, and try to see if we can hold some of their data for ransom. >>Some people that data may be valuable, it may not be valuable. Um, and that model still exists. Uh, and we see that, but really the big shift that we saw last year and the threat landscape before it was a shift to targeted rats. So again, the sophistication is starting to rise because they're not just going out to random data. They're going out to data that they know is valuable to large organizations, and they're taking that a step further now. So there's various ransomware families. We saw that have now reverted to extortion and blackmail, right? So they're taking that data, encrypting it and saying, unless you pay us as large sum of money, we're going to release this to the public or sell it to a buyer on the dark web. And of course you can imagine the amount of, um, you know, damages that can happen from that. The other thing we're seeing is, is a target of going to revenue services, right? So if they can cripple networks, it's essentially a denial of service. They know that the company is going to be bleeding, you know, X, millions of dollars a day, so they can demand Y million dollars of ransom payments, and that's effectively what's happening. So it's, again, becoming more targeted, uh, and more sophisticated. And unfortunately the ransom is going up. >>So they go to where the money is. And of course your job is to, it's a lower the ROI for them, a constant challenge. Um, we talked about some of the attack vectors, uh, that you saw this year that, that cyber criminals are targeting. I wonder if, if, you know, given the work from home, if things like IOT devices and cameras and, you know, thermostats, uh, with 75% of the work force at home, is this infrastructure more vulnerable? I guess, of course it is. But what did you see there in terms of attacks on those devices? >>Yeah, so, uh, um, uh, you know, unfortunately the attack surface as we call it, uh, so the amount of target points is expanding. It's not shifting, it's expanding. We still see, um, I saw, I mentioned earlier vulnerabilities from two years ago that are being used in some cases, you know, over the holidays where e-commerce means we saw e-commerce heavily under attack in e-commerce has spikes since last summer, right. It's been a huge amount of traffic increase everybody's shopping from home. And, uh, those vulnerabilities going after a shopping cart, plugins, as an example, are five to six years old. So we still have this theme of old vulnerabilities are still new in a sense being attacked, but we're also now seeing this complication of, yeah, as you said, IOT, uh, B roll out everywhere, the really quick shift to work from home. Uh, we really have to treat this as if you guys, as the, uh, distributed branch model for enterprise, right. >>And it's really now the secure branch. How do we take, um, um, you know, any of these devices on, on those networks and secure them, uh, because yeah, if you look at the, what we highlighted in our landscape report and the top 10 attacks that we're seeing, so hacking attacks hacking in tabs, this is who our IPS triggers. You know, we're seeing attempts to go after IOT devices. Uh, right now they're mostly, uh, favoring, uh, well in terms of targets, um, consumer grade routers. Uh, but they're also looking at, um, uh, DVR devices as an example for, uh, you know, home entertainment systems, uh, network attached storage as well, and IP security cameras, um, some of the newer devices, uh, what, the quote unquote smart devices that are now on, you know, virtual assistance and home networks. Uh, we actually released a predictions piece at the end of last year as well. So this is what we call the new intelligent edge. And that's what I think is we're really going to see this year in terms of what's ahead. Um, cause we always have to look ahead and prepare for that. But yeah, right now, unfortunately, the story is, all of this is still happening. IOT is being targeted. Of course they're being targeted because they're easy targets. Um, it's like for cybercriminals, it's like shooting fish in a barrel. There's not just one, but there's multiple vulnerabilities, security holes associated with these devices, easy entry points into networks. >>I mean, it's, um, I mean, attackers they're, they're highly capable. They're organized, they're well-funded they move fast, they're they're agile, uh, and they follow the money. As we were saying, uh, you, you mentioned, you know, co vaccines and, you know, big pharma healthcare, uh, where >>Did you see advanced, persistent >>Threat groups really targeting? Were there any patterns that emerged in terms of other industry types or organizations being targeted? >>Yeah. So just to be clear again, when we talk about AP teams, um, uh, advanced, specific correct group, the groups themselves they're targeting, these are usually the more sophisticated groups, of course. So going back to that theme, these are usually the target, the, um, the premeditated targeted attacks usually points to nation state. Um, sometimes of course there's overlap. They can be affiliated with cyber crime, cyber crime, uh, uh, groups are typically, um, looking at some other targets for ROI, uh, bio there's there's a blend, right? So as an example, if we're looking at the, uh, apt groups I had last year, absolutely. Number one I would say would be healthcare. Healthcare was one of those, and it's, it's, it's, uh, you know, very unfortunate, but obviously with the shift that was happening at a pop up medical facilities, there's a big, a rush to change networks, uh, for a good cause of course, but with that game, um, you know, uh, security holes and concerns the targets and, and that's what we saw IPT groups targeting was going after those and, and ransomware and the cyber crime shrine followed as well. Right? Because if you can follow, uh, those critical networks and crippled them on from cybercriminals point of view, you can, you can expect them to pay the ransom because they think that they need to buy in order to, um, get those systems back online. Uh, in fact, last year or two, unfortunately we saw the first, um, uh, death that was caused because of a denial of service attack in healthcare, right. Facilities were weren't available because of the cyber attack. Patients had to be diverted and didn't make it on the way. >>All right. Jericho, sufficiently bummed out. So maybe in the time remaining, we can talk about remediation strategies. You know, we know there's no silver bullet in security. Uh, but what approaches are you recommending for organizations? How are you consulting with folks? >>Sure. Yeah. So a couple of things, um, good news is there's a lot that we can do about this, right? And, um, and, and basic measures go a long way. So a couple of things just to get out of the way I call it housekeeping, cyber hygiene, but it's always worth reminding. So when we talk about keeping security patches up to date, we always have to talk about that because that is reality as et cetera, these, these vulnerabilities that are still being successful are five to six years old in some cases, the majority two years old. Um, so being able to do that, manage that from an organization's point of view, really treat the new work from home. I don't like to call it a work from home. So the reality is it's work from anywhere a lot of the times for some people. So really treat that as, as the, um, as a secure branch, uh, methodology, doing things like segmentations on network, secure wifi access, multi-factor authentication is a huge muscle, right? >>So using multi-factor authentication because passwords are dead, um, using things like, uh, XDR. So Xers is a combination of detection and response for end points. This is a mass centralized management thing, right? So, uh, endpoint detection and response, as an example, those are all, uh, you know, good security things. So of course having security inspection, that that's what we do. So good threat intelligence baked into your security solution. That's supported by labs angles. So, uh, that's, uh, you know, uh, antivirus, intrusion prevention, web filtering, sandbox, and so forth, but then it gets that that's the security stack beyond that it gets into the end user, right? Everybody has a responsibility. This is that supply chain. We talked about. The supply chain is, is, is a target for attackers attackers have their own supply chain as well. And we're also part of that supply chain, right? The end users where we're constantly fished for social engineering. So using phishing campaigns against employees to better do training and awareness is always recommended to, um, so that's what we can do, obviously that's, what's recommended to secure, uh, via the endpoints in the secure branch there's things we're also doing in the industry, um, to fight back against that with prime as well. >>Well, I, I want to actually talk about that and talk about ecosystems and collaboration, because while you have competitors, you all want the same thing. You, SecOps teams are like superheroes in my book. I mean, they're trying to save the world from the bad guys. And I remember I was talking to Robert Gates on the cube a couple of years ago, a former defense secretary. And I said, yeah, but don't, we have like the best security people and can't we go on the offensive and weaponize that ourselves. Of course, there's examples of that. Us. Government's pretty good at it, even though they won't admit it. But his answer to me was, yeah, we gotta be careful because we have a lot more to lose than many countries. So I thought that was pretty interesting, but how do you collaborate with whether it's the U S government or other governments or other other competitors even, or your ecosystem? Maybe you could talk about that a little bit. >>Yeah. Th th this is what, this is what makes me tick. I love working with industry. I've actually built programs for 15 years of collaboration in the industry. Um, so, you know, we, we need, I always say we can't win this war alone. You actually hit on this point earlier, you talked about following and trying to disrupt the ROI of cybercriminals. Absolutely. That is our target, right. We're always looking at how we can disrupt their business model. Uh, and, and in order, there's obviously a lot of different ways to do that, right? So a couple of things we do is resiliency. That's what we just talked about increasing the security stack so that they go knocking on someone else's door. But beyond that, uh, it comes down to private, private sector collaborations. So, uh, we, we, uh, co-founder of the cyber threat Alliance in 2014 as an example, this was our fierce competitors coming in to work with us to share intelligence, because like you said, um, competitors in the space, but we need to work together to do the better fight. >>And so this is a Venn diagram. What's compared notes, let's team up, uh, when there's a breaking attack and make sure that we have the intelligence so that we can still remain competitive on the technology stack to gradation the solutions themselves. Uh, but let's, let's level the playing field here because cybercriminals moved out, uh, you know, um, uh, that, that there's no borders and they move with great agility. So, uh, that's one thing we do in the private private sector. Uh, there's also, uh, public private sector relationships, right? So we're working with Interpol as an example, Interfor project gateway, and that's when we find attribution. So it's not just the, what are these people doing like infrastructure, but who, who are they, where are they operating? What, what events tools are they creating? We've actually worked on cases that are led down to, um, uh, warrants and arrests, you know, and in some cases, one case with a $60 million business email compromise fraud scam, the great news is if you look at the industry as a whole, uh, over the last three to four months has been for take downs, a motet net Walker, uh, um, there's also IE Gregor, uh, recently as well too. >>And, and Ian Gregor they're actually going in and arresting the affiliates. So not just the CEO or the King, kind of these organizations, but the people who are distributing the ransomware themselves. And that was a unprecedented step, really important. So you really start to paint a picture of this, again, supply chain, this ecosystem of cyber criminals and how we can hit them, where it hurts on all angles. I've most recently, um, I've been heavily involved with the world economic forum. Uh, so I'm, co-author of a report from last year of the partnership on cyber crime. And, uh, this is really not just the pro uh, private, private sector, but the private and public sector working together. We know a lot about cybercriminals. We can't arrest them. Uh, we can't take servers offline from the data centers, but working together, we can have that whole, you know, that holistic effect. >>Great. Thank you for that, Derek. What if people want, want to go deeper? Uh, I know you guys mentioned that you do blogs, but are there other resources that, that they can tap? Yeah, absolutely. So, >>Uh, everything you can see is on our threat research blog on, uh, so 40 net blog, it's under expired research. We also put out, uh, playbooks, w we're doing blah, this is more for the, um, the heroes as he called them the security operation centers. Uh, we're doing playbooks on the aggressors. And so this is a playbook on the offense, on the offense. What are they up to? How are they doing that? That's on 40 guard.com. Uh, we also release, uh, threat signals there. So, um, we typically release, uh, about 50 of those a year, and those are all, um, our, our insights and views into specific attacks that are now >>Well, Derek Mackie, thanks so much for joining us today. And thanks for the work that you and your teams do. Very important. >>Thanks. It's yeah, it's a pleasure. And, uh, rest assured we will still be there 24 seven, three 65. >>Good to know. Good to know. And thank you for watching everybody. This is Dave Volante for the cube. We'll see you next time.

Published Date : Feb 26 2021

SUMMARY :

but now they have to be wary of software updates in the digital supply chain, Thanks so much for, for the invitation to speak. So first I wonder if you could explain for the audience, what is for guard labs Um, and, but, you know, so it's, it's everything from, uh, customer protection first And it's, it's critical because like you said, you can, you can minimize the um, that is, uh, the, you know, that that's digestible. I know you do this twice a year, but what trends did you see evolving throughout the year and what have you seen with the uh, natural disasters as an example, you know, um, trying to do charity Um, people started to become, we did a lot of education around this. on, um, uh, you know, targeting the digital supply chain as an example. in the first half, and then they sort of deployed it, did it, uh, w what actually happened there from um, you know, a lot of ramp up work on their end, a lot of time developing the, on, um, you know, social engineering, um, using, uh, topical themes. So you mentioned stuck next Stuxnet as the former sort of example, of one of the types of attacks is designed by design, uh, to say that, you know, um, you know, in fact, uh, ransomware is not a new of, um, you know, damages that can happen from that. and cameras and, you know, thermostats, uh, with 75% Yeah, so, uh, um, uh, you know, unfortunately the attack surface as we call it, uh, you know, home entertainment systems, uh, network attached storage as well, you know, big pharma healthcare, uh, where and it's, it's, it's, uh, you know, very unfortunate, but obviously with So maybe in the time remaining, we can talk about remediation strategies. So a couple of things just to get out of the way I call it housekeeping, cyber hygiene, So, uh, that's, uh, you know, uh, antivirus, intrusion prevention, web filtering, And I remember I was talking to Robert Gates on the cube a couple of years ago, a former defense secretary. Um, so, you know, we, we need, I always say we can't win this war alone. cybercriminals moved out, uh, you know, um, uh, that, but working together, we can have that whole, you know, that holistic effect. Uh, I know you guys mentioned that Uh, everything you can see is on our threat research blog on, uh, And thanks for the work that you and your teams do. And, uh, rest assured we will still be there 24 seven, And thank you for watching everybody.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
Dave VellantePERSON

0.99+

2006DATE

0.99+

Derek MackiePERSON

0.99+

1989DATE

0.99+

2014DATE

0.99+

Ian GregorPERSON

0.99+

fiveQUANTITY

0.99+

15 yearsQUANTITY

0.99+

75%QUANTITY

0.99+

DerekPERSON

0.99+

Dave VolantePERSON

0.99+

20QUANTITY

0.99+

FortinetORGANIZATION

0.99+

twoQUANTITY

0.99+

$60 millionQUANTITY

0.99+

InterpolORGANIZATION

0.99+

two typesQUANTITY

0.99+

Robert GatesPERSON

0.99+

last yearDATE

0.99+

Derek MankyPERSON

0.99+

first halfQUANTITY

0.99+

U S governmentORGANIZATION

0.99+

12 monthsQUANTITY

0.99+

40 guard labsQUANTITY

0.99+

todayDATE

0.99+

FortiGuard LabsORGANIZATION

0.99+

one caseQUANTITY

0.99+

one dayQUANTITY

0.99+

firstQUANTITY

0.99+

last summerDATE

0.99+

GoogleORGANIZATION

0.99+

half a yearQUANTITY

0.99+

a monthQUANTITY

0.98+

three weeksQUANTITY

0.98+

oneQUANTITY

0.98+

both attacksQUANTITY

0.98+

COVID-19OTHER

0.98+

this yearDATE

0.98+

10 plus years agoDATE

0.98+

Security InsightsORGANIZATION

0.98+

over two yearsQUANTITY

0.98+

InterforORGANIZATION

0.98+

two years agoDATE

0.97+

two times a yearQUANTITY

0.96+

million dollarsQUANTITY

0.96+

40 grand labsQUANTITY

0.96+

Zero trustQUANTITY

0.96+

four monthsQUANTITY

0.95+

Derek mankyPERSON

0.95+

JerichoPERSON

0.95+

millions of dollars a dayQUANTITY

0.95+

OneQUANTITY

0.95+

40 netQUANTITY

0.94+

pandemicEVENT

0.94+

COVIDOTHER

0.94+

thousands of peopleQUANTITY

0.94+

over 5 million censorshipQUANTITY

0.94+

fourQUANTITY

0.93+

twice a yearQUANTITY

0.92+

one thingQUANTITY

0.9+

40 guard.comOTHER

0.9+

a hundred billionQUANTITY

0.89+

about 50QUANTITY

0.89+

six years oldQUANTITY

0.89+

ChiefPERSON

0.89+

over 40 different languagesQUANTITY

0.88+

threeQUANTITY

0.87+

about twoQUANTITY

0.86+

Stuxnet attacksEVENT

0.86+

zero-day weaponsQUANTITY

0.86+

Q4DATE

0.86+

21 yearsQUANTITY

0.85+

Maseca proORGANIZATION

0.85+

two years oldQUANTITY

0.85+

Global Threat AlliancesORGANIZATION

0.83+

EMBARGO Derek Manky Chief, Security Insights & Global Threat Alliances, FortiGuard Labs


 

>>As we've been reporting, the pandemic has called CSOs to really shift their spending priorities towards securing remote workers. Almost overnight. Zero trust has gone from buzzword to mandate. What's more as we wrote in our recent cybersecurity breaking analysis, not only Maseca pro secured increasingly distributed workforce, but now they have to be wary of software updates in the digital supply chain, including the very patches designed to protect them against cyber attacks. Hello everyone. And welcome to this Q conversation. My name is Dave Vellante and I'm pleased to welcome Derek manky. Who's chief security insights, and global threat alliances for four guard labs with fresh data from its global threat landscape report. Derek. Welcome. Great to see you. >>Thanks so much for, for the invitation to speak. It's always a pleasure. Multicover yeah, >>You're welcome. So first I wonder if you could explain for the audience, what is for guard labs and what's its relationship to fortunate? >>Right. So 40 grand labs is, is our global sockets, our global threat intelligence operation center. It never sleeps, and this is the beat. Um, you know, it's, it's been here since inception at port in it. So it's it's 20, 21 years in the making, since Fortinet was founded, uh, we have built this in-house, uh, so we don't go yum technology. We built everything from the ground up, including creating our own training programs for our, our analysts. We're following malware, following exploits. We even have a unique program that I created back in 2006 to ethical hacking program. And it's a zero-day research. So we try to meet the hackers, the bad guys to their game. And we of course do that responsibly to work with vendors, to close schools and create virtual patches. Um, and, but, you know, so it's, it's everything from, uh, customer protection first and foremost, to following, uh, the threat landscape and cyber. It's very important to understand who they are, what they're doing, who they're, uh, what they're targeting, what tools are they using? >>Yeah, that's great. Some serious DNA and skills in that group. And it's, it's critical because like you said, you can, you can minimize the spread of those malware very, very quickly. So what, what now you have, uh, the global threat landscape report. We're going to talk about that, but what exactly is that? >>Right? So this a global threat landscape report, it's a summary of, uh, all, all the data that we collect over a period of time. So we released this, that biannually two times a year. Um, cyber crime is changing very fast, as you can imagine. So, uh, while we do release security blogs, and, uh, what we call threat signals for breaking security events, we have a lot of other vehicles to release threat intelligence, but this threat landscape report is truly global. It looks at all of our global data. So we have over 5 million censorship worldwide in 40 guard labs, we're processing. I know it seems like a very large amount, but North of a hundred billion, uh, threat events in just one day. And we have to take the task of taking all of that data and put that onto scale for half a year and compile that into something, um, that is, uh, the, you know, that that's digestible. That's a, a very tough task, as you can imagine, so that, you know, we have to work with a huge technologies back to machine learning and artificial intelligence automation. And of course our analyst view to do that. >>Yeah. So this year, of course, there's like the every year is a battle, but this year was an extra battle. Can you explain what you saw in terms of the hacker dynamics over the past? Let's say 12 months. I know you do this twice a year, but what trends did you see evolving throughout the year and what have you seen with the way that attackers have exploited this expanded attack surface outside of corporate network? >>Yeah, it was quite interesting last year. It certainly was not normal. Like we all say, um, and that was no exception for cybersecurity. You know, if we look at cyber criminals and how they pivoted and adapted to the scrap threat landscape, cyber cyber criminals are always trying to take advantage of the weakest link of the chain. They're trying to always prey off here and ride waves of global trends and themes. We've seen this before in, uh, natural disasters as an example, you know, um, trying to do charity kind of scams and campaigns. And they're usually limited to a region where that incident happened and they usually live about two to three weeks, maybe a month at the most. And then they'll move on to the next to the next trip. That's braking, of course, because COVID is so global and dominant. Um, we saw attacks coming in from, uh, well over 40 different languages as an example, um, in regions all across the world that wasn't lasting two to three weeks and it lasted for the better part of a year. >>And of course, what they're, they're using this as a vehicle, right? Not preying on the fear. They're doing everything from initial lockdown, uh, fishing. We were as COVID-19 movers to, um, uh, lay off notices then to phase one, reopenings all the way up to fast forward to where we are today with vaccine rollover development. So there's always that new flavor and theme that they were rolling out, but because it was so successful for them, they were able to, they didn't have to innovate too much, right. They didn't have to expand and shifted to new to new trends. And themes are really developed on new rats families as an example, or a new sophisticated malware. That was the first half of the year and the second half of the year. Um, of course people started to experience COVID fatigue, right? Um, people started to become, we did a lot of education around this. >>People started to become more aware of this threat. And so, um, cyber criminals have started to, um, as we expected, started to become more sophisticated with their attacks. We saw an expansion in different ransomware families. We saw more of a shift of focus on, on, um, uh, you know, targeting the digital supply chain as an example. And so that, that was, that was really towards Q4. Uh, so it, it was a long lived lead year with success on the Google themes, um, targeting healthcare as an example, a lot of, um, a lot of the organizations that were, you know, really in a vulnerable position, I would say >>So, okay. I want to clarify something because my assumption was that they actually did really increase the sophistication, but it sounds like that was kind of a first half trends. Not only did they have to adapt and not have to, but they adapt it to these new vulnerabilities. Uh, my sense was that when you talk about the digital supply chain, that that was a fairly sophisticated attack. Am I, am I getting that right? That they did their sort of their, their, their increased sophistication in the first half, and then they sort of deployed it, did it, uh, w what actually happened there from your data? >>Well, if we look at, so generally there's two types of attacks that we look at, we look at the, uh, the premeditated sophisticated attacks that can have, um, you know, a lot of ramp up work on their end, a lot of time developing the, the, the, the weaponization phase. So developing, uh, the exploits of the sophisticated malware that they're gonna use for the campaign reconnaissance, understanding the targets, where platforms are developed, um, the blueprinting that DNA of, of, of the supply chain, those take time. Um, in fact years, even if we look back to, um, uh, 10 plus years ago with the Stuxnet attacks, as an example that was on, uh, nuclear centrifuges, um, and that, that had four different zero-day weapons at the time. That was very sophisticated, that took over two years to develop as an example. So some of these can take years of time to develop, but they're, they're, uh, very specific in terms of the targets are going to go after obviously the ROI from their end. >>Uh, the other type of attack that we see is as ongoing, um, these broad, wide sweeping attacks, and the reality for those ones is they don't unfortunately need to be too sophisticated. And those ones were the ones I was talking about that were really just playing on the cool, the deem, and they still do today with the vaccine road and development. Uh, but, but it's really because they're just playing on, on, um, you know, social engineering, um, using, uh, topical themes. And in fact, the weapons they're using these vulnerabilities are from our research data. And this was highlighted actually the first pop landscape before last year, uh, on average were two to three years old. So we're not talking about fresh vulnerabilities. You've got to patch right away. I mean, these are things that should have been patched two years ago, but they're still unfortunately having success with that. >>So you mentioned stuck next Stuxnet as the former sort of example, of one of the types of attacks that you see. And I always felt like that was a watershed moment. One of the most sophisticated, if not the most sophisticated attack that we'd ever seen. When I talk to CSOs about the recent government hack, they, they, they suggest I infer maybe they don't suggest it. I infer that it was of similar sophistication. It was maybe thousands of people working on this for years and years and years. Is that, is that accurate or not necessarily? >>Yeah, there's definitely a, there's definitely some comparisons there. Uh, you know, one of the largest things is, uh, both attacks used digital circuits certificate personation, so they're digitally signed. So, you know, of course that whole technology using cryptography is designed by design, uh, to say that, you know, this piece of software installed in your system, hassles certificate is coming from the source. It's legitimate. Of course, if that's compromised, that's all out of the window. And, um, yeah, this is what we saw in both attacks. In fact, you know, stocks in that they also had digitally designed, uh, certificates that were compromised. So when it gets to that level of students or, uh, sophistication, that means definitely that there's a target that there has been usually months of, of, uh, homework done by cyber criminals, for reconnaissance to be able to weaponize that. >>W w what did you see with respect to ransomware? What were the trends there over the past 12 months? I've heard some data and it's pretty scary, but what did you see? >>Yeah, so we're actually, ransomware is always the thorn in our side, and it's going to continue to be so, um, you know, in fact, uh, ransomware is not a new itself. It was actually first created in 1989, and they demanded ransom payments through snail mail. This was to appeal a box, obviously that, that, that didn't take off. Wasn't a successful on the internet was porn at the time. But if you look at it now, of course, over the last 10 years, really, that's where it ran. The ransomware model has been, uh, you know, lucrative, right? I mean, it's been, um, using, uh, by force encrypting data on systems, so that users had to, if they were forced to pay the ransom because they wanted access to their data back data was the target currency for ransomware. That's shifted now. And that's actually been a big pivotal over the last year or so, because again, before it was this let's cast a wide net, in fact, as many people as we can random, um, and try to see if we can hold some of their data for ransom. >>Some people that data may be valuable, it may not be valuable. Um, and that model still exists. Uh, and we see that, but really the big shift that we saw last year and the threat landscape before it was a shift to targeted rats. So again, the sophistication is starting to rise because they're not just going out to random data. They're going out to data that they know is valuable to large organizations, and they're taking that a step further now. So there's various ransomware families. We saw that have now reverted to extortion and blackmail, right? So they're taking that data, encrypting it and saying, unless you pay us as large sum of money, we're going to release this to the public or sell it to a buyer on the dark web. And of course you can imagine the amount of, um, you know, damages that can happen from that. The other thing we're seeing is, is a target of going to revenue services, right? So if they can cripple networks, it's essentially a denial of service. They know that the company is going to be bleeding, you know, X, millions of dollars a day, so they can demand Y million dollars of ransom payments, and that's effectively what's happening. So it's, again, becoming more targeted, uh, and more sophisticated. And unfortunately the ransom is going up. >>So they go to where the money is. And of course your job is to, it's a lower the ROI for them, a constant challenge. Um, we talked about some of the attack vectors, uh, that you saw this year that, that cyber criminals are targeting. I wonder if, if, you know, given the work from home, if things like IOT devices and cameras and, you know, thermostats, uh, with 75% of the work force at home, is this infrastructure more vulnerable? I guess, of course it is. But what did you see there in terms of attacks on those devices? >>Yeah, so, uh, um, uh, you know, unfortunately the attack surface as we call it, uh, so the amount of target points is expanding. It's not shifting, it's expanding. We still see, um, I saw, I mentioned earlier vulnerabilities from two years ago that are being used in some cases, you know, over the holidays where e-commerce means we saw e-commerce heavily under attack in e-commerce has spikes since last summer, right. It's been a huge amount of traffic increase everybody's shopping from home. And, uh, those vulnerabilities going after a shopping cart, plugins, as an example, are five to six years old. So we still have this theme of old vulnerabilities are still new in a sense being attacked, but we're also now seeing this complication of, yeah, as you said, IOT, uh, B roll out everywhere, the really quick shift to work from home. Uh, we really have to treat this as if you guys, as the, uh, distributed branch model for enterprise, right. >>And it's really now the secure branch. How do we take, um, um, you know, any of these devices on, on those networks and secure them, uh, because yeah, if you look at the, what we highlighted in our landscape report and the top 10 attacks that we're seeing, so hacking attacks hacking in tabs, this is who our IPS triggers. You know, we're seeing attempts to go after IOT devices. Uh, right now they're mostly, uh, favoring, uh, well in terms of targets, um, consumer grade routers. Uh, but they're also looking at, um, uh, DVR devices as an example for, uh, you know, home entertainment systems, uh, network attached storage as well, and IP security cameras, um, some of the newer devices, uh, what, the quote unquote smart devices that are now on, you know, virtual assistance and home networks. Uh, we actually released a predictions piece at the end of last year as well. So this is what we call the new intelligent edge. And that's what I think is we're really going to see this year in terms of what's ahead. Um, cause we always have to look ahead and prepare for that. But yeah, right now, unfortunately, the story is, all of this is still happening. IOT is being targeted. Of course they're being targeted because they're easy targets. Um, it's like for cybercriminals, it's like shooting fish in a barrel. There's not just one, but there's multiple vulnerabilities, security holes associated with these devices, easy entry points into networks. >>I mean, it's, um, I mean, attackers they're, they're highly capable. They're organized, they're well-funded they move fast, they're they're agile, uh, and they follow the money. As we were saying, uh, you, you mentioned, you know, co vaccines and, you know, big pharma healthcare, uh, where >>Did you see advanced, persistent >>Threat groups really targeting? Were there any patterns that emerged in terms of other industry types or organizations being targeted? >>Yeah. So just to be clear again, when we talk about AP teams, um, uh, advanced, specific correct group, the groups themselves they're targeting, these are usually the more sophisticated groups, of course. So going back to that theme, these are usually the target, the, um, the premeditated targeted attacks usually points to nation state. Um, sometimes of course there's overlap. They can be affiliated with cyber crime, cyber crime, uh, uh, groups are typically, um, looking at some other targets for ROI, uh, bio there's there's a blend, right? So as an example, if we're looking at the, uh, apt groups I had last year, absolutely. Number one I would say would be healthcare. Healthcare was one of those, and it's, it's, it's, uh, you know, very unfortunate, but obviously with the shift that was happening at a pop up medical facilities, there's a big, a rush to change networks, uh, for a good cause of course, but with that game, um, you know, uh, security holes and concerns the targets and, and that's what we saw IPT groups targeting was going after those and, and ransomware and the cyber crime shrine followed as well. Right? Because if you can follow, uh, those critical networks and crippled them on from cybercriminals point of view, you can, you can expect them to pay the ransom because they think that they need to buy in order to, um, get those systems back online. Uh, in fact, last year or two, unfortunately we saw the first, um, uh, death that was caused because of a denial of service attack in healthcare, right. Facilities were weren't available because of the cyber attack. Patients had to be diverted and didn't make it on the way. >>All right. Jericho, sufficiently bummed out. So maybe in the time remaining, we can talk about remediation strategies. You know, we know there's no silver bullet in security. Uh, but what approaches are you recommending for organizations? How are you consulting with folks? >>Sure. Yeah. So a couple of things, um, good news is there's a lot that we can do about this, right? And, um, and, and basic measures go a long way. So a couple of things just to get out of the way I call it housekeeping, cyber hygiene, but it's always worth reminding. So when we talk about keeping security patches up to date, we always have to talk about that because that is reality as et cetera, these, these vulnerabilities that are still being successful are five to six years old in some cases, the majority two years old. Um, so being able to do that, manage that from an organization's point of view, really treat the new work from home. I don't like to call it a work from home. So the reality is it's work from anywhere a lot of the times for some people. So really treat that as, as the, um, as a secure branch, uh, methodology, doing things like segmentations on network, secure wifi access, multi-factor authentication is a huge muscle, right? >>So using multi-factor authentication because passwords are dead, um, using things like, uh, XDR. So Xers is a combination of detection and response for end points. This is a mass centralized management thing, right? So, uh, endpoint detection and response, as an example, those are all, uh, you know, good security things. So of course having security inspection, that that's what we do. So good threat intelligence baked into your security solution. That's supported by labs angles. So, uh, that's, uh, you know, uh, antivirus, intrusion prevention, web filtering, sandbox, and so forth, but then it gets that that's the security stack beyond that it gets into the end user, right? Everybody has a responsibility. This is that supply chain. We talked about. The supply chain is, is, is a target for attackers attackers have their own supply chain as well. And we're also part of that supply chain, right? The end users where we're constantly fished for social engineering. So using phishing campaigns against employees to better do training and awareness is always recommended to, um, so that's what we can do, obviously that's, what's recommended to secure, uh, via the endpoints in the secure branch there's things we're also doing in the industry, um, to fight back against that with prime as well. >>Well, I, I want to actually talk about that and talk about ecosystems and collaboration, because while you have competitors, you all want the same thing. You, SecOps teams are like superheroes in my book. I mean, they're trying to save the world from the bad guys. And I remember I was talking to Robert Gates on the cube a couple of years ago, a former defense secretary. And I said, yeah, but don't, we have like the best security people and can't we go on the offensive and weaponize that ourselves. Of course, there's examples of that. Us. Government's pretty good at it, even though they won't admit it. But his answer to me was, yeah, we gotta be careful because we have a lot more to lose than many countries. So I thought that was pretty interesting, but how do you collaborate with whether it's the U S government or other governments or other other competitors even, or your ecosystem? Maybe you could talk about that a little bit. >>Yeah. Th th this is what, this is what makes me tick. I love working with industry. I've actually built programs for 15 years of collaboration in the industry. Um, so, you know, we, we need, I always say we can't win this war alone. You actually hit on this point earlier, you talked about following and trying to disrupt the ROI of cybercriminals. Absolutely. That is our target, right. We're always looking at how we can disrupt their business model. Uh, and, and in order, there's obviously a lot of different ways to do that, right? So a couple of things we do is resiliency. That's what we just talked about increasing the security stack so that they go knocking on someone else's door. But beyond that, uh, it comes down to private, private sector collaborations. So, uh, we, we, uh, co-founder of the cyber threat Alliance in 2014 as an example, this was our fierce competitors coming in to work with us to share intelligence, because like you said, um, competitors in the space, but we need to work together to do the better fight. >>And so this is a Venn diagram. What's compared notes, let's team up, uh, when there's a breaking attack and make sure that we have the intelligence so that we can still remain competitive on the technology stack to gradation the solutions themselves. Uh, but let's, let's level the playing field here because cybercriminals moved out, uh, you know, um, uh, that, that there's no borders and they move with great agility. So, uh, that's one thing we do in the private private sector. Uh, there's also, uh, public private sector relationships, right? So we're working with Interpol as an example, Interfor project gateway, and that's when we find attribution. So it's not just the, what are these people doing like infrastructure, but who, who are they, where are they operating? What, what events tools are they creating? We've actually worked on cases that are led down to, um, uh, warrants and arrests, you know, and in some cases, one case with a $60 million business email compromise fraud scam, the great news is if you look at the industry as a whole, uh, over the last three to four months has been for take downs, a motet net Walker, uh, um, there's also IE Gregor, uh, recently as well too. >>And, and Ian Gregor they're actually going in and arresting the affiliates. So not just the CEO or the King, kind of these organizations, but the people who are distributing the ransomware themselves. And that was a unprecedented step, really important. So you really start to paint a picture of this, again, supply chain, this ecosystem of cyber criminals and how we can hit them, where it hurts on all angles. I've most recently, um, I've been heavily involved with the world economic forum. Uh, so I'm, co-author of a report from last year of the partnership on cyber crime. And, uh, this is really not just the pro uh, private, private sector, but the private and public sector working together. We know a lot about cybercriminals. We can't arrest them. Uh, we can't take servers offline from the data centers, but working together, we can have that whole, you know, that holistic effect. >>Great. Thank you for that, Derek. What if people want, want to go deeper? Uh, I know you guys mentioned that you do blogs, but are there other resources that, that they can tap? Yeah, absolutely. So, >>Uh, everything you can see is on our threat research blog on, uh, so 40 net blog, it's under expired research. We also put out, uh, playbooks, w we're doing blah, this is more for the, um, the heroes as he called them the security operation centers. Uh, we're doing playbooks on the aggressors. And so this is a playbook on the offense, on the offense. What are they up to? How are they doing that? That's on 40 guard.com. Uh, we also release, uh, threat signals there. So, um, we typically release, uh, about 50 of those a year, and those are all, um, our, our insights and views into specific attacks that are now >>Well, Derek Mackie, thanks so much for joining us today. And thanks for the work that you and your teams do. Very important. >>Thanks. It's yeah, it's a pleasure. And, uh, rest assured we will still be there 24 seven, three 65. >>Good to know. Good to know. And thank you for watching everybody. This is Dave Volante for the cube. We'll see you next time.

Published Date : Feb 23 2021

SUMMARY :

but now they have to be wary of software updates in the digital supply chain, Thanks so much for, for the invitation to speak. So first I wonder if you could explain for the audience, what is for guard labs Um, and, but, you know, so it's, it's everything from, uh, customer protection first And it's, it's critical because like you said, you can, you can minimize the um, that is, uh, the, you know, that that's digestible. I know you do this twice a year, but what trends did you see evolving throughout the year and what have you seen with the uh, natural disasters as an example, you know, um, trying to do charity Um, people started to become, we did a lot of education around this. on, um, uh, you know, targeting the digital supply chain as an example. in the first half, and then they sort of deployed it, did it, uh, w what actually happened there from um, you know, a lot of ramp up work on their end, a lot of time developing the, on, um, you know, social engineering, um, using, uh, topical themes. So you mentioned stuck next Stuxnet as the former sort of example, of one of the types of attacks is designed by design, uh, to say that, you know, um, you know, in fact, uh, ransomware is not a new of, um, you know, damages that can happen from that. and cameras and, you know, thermostats, uh, with 75% Yeah, so, uh, um, uh, you know, unfortunately the attack surface as we call it, uh, you know, home entertainment systems, uh, network attached storage as well, you know, big pharma healthcare, uh, where and it's, it's, it's, uh, you know, very unfortunate, but obviously with So maybe in the time remaining, we can talk about remediation strategies. So a couple of things just to get out of the way I call it housekeeping, cyber hygiene, So, uh, that's, uh, you know, uh, antivirus, intrusion prevention, web filtering, And I remember I was talking to Robert Gates on the cube a couple of years ago, a former defense secretary. Um, so, you know, we, we need, I always say we can't win this war alone. cybercriminals moved out, uh, you know, um, uh, that, but working together, we can have that whole, you know, that holistic effect. Uh, I know you guys mentioned that Uh, everything you can see is on our threat research blog on, uh, And thanks for the work that you and your teams do. And, uh, rest assured we will still be there 24 seven, And thank you for watching everybody.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
Dave VellantePERSON

0.99+

2006DATE

0.99+

Derek MackiePERSON

0.99+

1989DATE

0.99+

2014DATE

0.99+

Ian GregorPERSON

0.99+

fiveQUANTITY

0.99+

15 yearsQUANTITY

0.99+

75%QUANTITY

0.99+

DerekPERSON

0.99+

20QUANTITY

0.99+

Dave VolantePERSON

0.99+

FortinetORGANIZATION

0.99+

twoQUANTITY

0.99+

$60 millionQUANTITY

0.99+

InterpolORGANIZATION

0.99+

two typesQUANTITY

0.99+

Robert GatesPERSON

0.99+

last yearDATE

0.99+

FortiGuard LabsORGANIZATION

0.99+

first halfQUANTITY

0.99+

U S governmentORGANIZATION

0.99+

12 monthsQUANTITY

0.99+

40 guard labsQUANTITY

0.99+

todayDATE

0.99+

one caseQUANTITY

0.99+

one dayQUANTITY

0.99+

firstQUANTITY

0.99+

last summerDATE

0.99+

GoogleORGANIZATION

0.99+

half a yearQUANTITY

0.99+

a monthQUANTITY

0.98+

three weeksQUANTITY

0.98+

oneQUANTITY

0.98+

both attacksQUANTITY

0.98+

COVID-19OTHER

0.98+

this yearDATE

0.98+

10 plus years agoDATE

0.98+

EMBARGOPERSON

0.98+

over two yearsQUANTITY

0.98+

InterforORGANIZATION

0.98+

two years agoDATE

0.97+

two times a yearQUANTITY

0.96+

million dollarsQUANTITY

0.96+

40 grand labsQUANTITY

0.96+

Zero trustQUANTITY

0.96+

four monthsQUANTITY

0.95+

Derek mankyPERSON

0.95+

JerichoPERSON

0.95+

millions of dollars a dayQUANTITY

0.95+

OneQUANTITY

0.95+

40 netQUANTITY

0.94+

pandemicEVENT

0.94+

COVIDOTHER

0.94+

thousands of peopleQUANTITY

0.94+

over 5 million censorshipQUANTITY

0.94+

fourQUANTITY

0.93+

twice a yearQUANTITY

0.92+

one thingQUANTITY

0.9+

40 guard.comOTHER

0.9+

Derek MankyPERSON

0.89+

a hundred billionQUANTITY

0.89+

about 50QUANTITY

0.89+

six years oldQUANTITY

0.89+

over 40 different languagesQUANTITY

0.88+

ChiefPERSON

0.87+

Security Insights & Global Threat AlliancesORGANIZATION

0.87+

threeQUANTITY

0.87+

about twoQUANTITY

0.86+

Stuxnet attacksEVENT

0.86+

zero-day weaponsQUANTITY

0.86+

Q4DATE

0.86+

21 yearsQUANTITY

0.85+

Maseca proORGANIZATION

0.85+

two years oldQUANTITY

0.85+

cyber threat AllianceORGANIZATION

0.83+

3 4 Insights for All v3 clean


 

>>Yeah. >>Welcome back for our last session of the day how to deliver career making business outcomes with Search and AI. So we're very lucky to be hearing from Canada. Canadian Tire, one of Canada's largest and most successful retailers, have been powered 4.5 1000 employees to maximize the value of data with self service insights. So today we're joining us. We have Yarrow Baturin, who is the manager of Merch analytics and planning to support at Canadian Tire and then also Andrea Frisk, who is the engagement manager manager for thoughts. What s O U R Andrea? Thanks so much for being here. And with >>that, >>I'll pass the mic to you guys. >>Thank you for having us. Um, already, I I think I'll start with an introduction off who I am, what I do. A Canadian entire on what Canadian pair is all about. So, as a manager of Merch analytics at Canadian Tire, I support merchant organization with reporting tools, and then be I platform to enable decision making on a day to day basis. What is? Canadian Tire's Canadian tire is one of the largest retailers in Canada. Um, serving Canadians with a number of lines of business spanning automotive fixing, living, playing and SNG departments. We have a number of banners, including sport check Marks Party City Phl that covers more than 1700 locations. So as an organization, we've got vast variety of different data, whether it's product or loyalty. Now, as the time goes on, the number of asks the number off data points. The complexity of the analysis has been increasing on banned traditional tools. Analytical tools such as Excel Microsoft Access do find job but start hitting their limitations. So we started on the journey of exploring what other B I platforms would be suitable for our needs. And the criteria that we thought about as we started on that journey is to make sure that we enable customization as well as the McCarthy ization of data. What does that mean? That means we wanted to ensure that each one of the end users have ability to create their own versions off the report while having consistency from the data standpoint, we also wanted Thio ensure that they're able to create there at hawks search queries and draw insights based on the desired business needs. As each one of our lines of business as each one of our departments is quite unique in their nature. And this is where thoughts about comes into play. Um, you checked off all the boxes? Um, as current customers, as potential customers, you will discover that this is the tool that allows that at hawks search ability within a matter of seconds and ability to visualize the information and create those curated pin boards for each one of the business units, depending on what the needs are. And now where? I guess well, Andrea will talk a little bit more about how we gained adoption, but the usage was like and how we, uh, implemented the tool successfully in the organization. >>Okay, so I actually used to work for Canadian tire on DSO. During that time, I helped Thio build training and engaging users to sort of really kick start our use cases. Andi, the ongoing process of adopting thought spot through Canadian Tire s 01 of the sort of reasons that we moved into using thought spot was there was a need Thio evolve, um, in order to see the wealth of data that we had coming in. So the existing reporting again. And this is this sort of standard thoughts bought fix is, um, it brings the data toe. Everyone on git makes it more accessible, so you get more out of your data. So we want to provide users with the ability to customize what they could see and personalized three information so that they could get their specific business requirements out of the data rather than relying on the weekly monthly quarterly reporting. That was all usually fairly generic eso without the ability to deep dive in. So this gave the users the agility thio optimize their campaigns, optimize product murder, urgency where products are or where there's maybe supply chain gaps. Andi just really bring this out for trillions of rose to become accessible. Thio the Canadian tire. That's what user base think. That's the slide. >>That's the slight, Um So as Andrea talked about the business use of the particular tool, let's talk a little bit about how we set it up and a wonderful journey of how it's evolved. So we first implemented 5.3 version of that spot on the Falcon server on we've been adding horsepower to it over time. Now mhm. What I want to stress is the importance off the very first, Data said. That goes into the tool toe. Actually engage the users and to gain the adoption and to make sure there is no argument whether the tool is accurate or not. So what we've started with is a key p I marked layer with all the major metrics that we have and all the available permutations and combinations off the dimensions, whether it's a calendar dimension, proud of dimension or, let's say, customer attribute now, as we started with that data set, we wanted to make sure that we're we have the ability to add and the dimensions right. So now, as we're implementing the tool, we're starting to add in more dimension tables to satisfy the needs off our clients if you want to call it that way as they want to evolve their analytics. So we started adding in some of the store attributes we started adding in some of the product attributes on when I refer to a product attributes, let's say, uh, it involves costs and involves prices involved in some of the strategic internal pieces that we're thinking about now as the comprehensive mark contains right now, in our instance, close to five billion records. This is where it becomes the one source of truth for people declaring information against right so as they go in, we also wanted to make sure when they Corey thought spot there, we're really Onley. According one source of data. One source of truth. It became apparent over time, obviously, that more metrics are needed. They might not be all set up in that particular mark. And that's when we went on the journey off implementing some of the new worksheets or some of the new data sets particularly focused on the four looking pieces. And uh, that's where it becomes important to say This is how you gain the interest and keep the interests of the public right. So you're not just implementing a number off data sets all at once and then letting the users be you're implementing pieces and stages. You're keeping the interest thio, the tool relevant. You're keeping, um, the needs of the public in mind. Now, as you can imagine on the Falcon server piece, um, adding in the horsepower capacity might become challenging the mawr. Billions of Rosie erratic eso were actually in the middle of transitioning our environment to azure in snowflake so that we can connect it. Thio embrace capability of thoughts cloud. And that's where I'm looking forward to that in 2021 I truly believe this will enable us Thio increase the speed off adoption Increase the speed of getting insights out of the tool and scale with regards Thio new data sets that we're thinking about implementing as we're continuing our thoughts about journey >>Okay, so how we drove adoption Thio 4500 plus users eso When we first started Thio approach our use case with the merchants within Canadian Tire We had meetings with these users with who are used place is gonna be with and sort of found out. What are they searching for, Where they typically looking at what existing reports are available for them. Andi kind of sought out to like, What are those things where you're pulling this on your own or someone else's pulling this data because it's not accessible yet And we really use that as our foundation to determine one what data we needed to initially bring into the system but also to sort of create those launchpad pin boards that had the base information that the users we're gonna need so that we could twofold, make it easy for them, toe adopt into the tool and also quickly start Thio, deactivate or discontinue those reports. And just like these air now only available in thought spot because with the sort of formatting within thought spot around dates, it's really easy to make this year's report last year report etcetera. Just have everything roll over every month or a recorder s. So that was kind of some of the pre work foundation when we originally did it. But really, it's been a lot of training, a lot of training. So we conducted ah, lot of in person training, obviously pre co vid eso. We've started to train the group that we targeted, which was the merchants and all of the like, surrounding support groups. Eso we had planners going in and training as well, so that everyone who was really closely connected to the merchants I had an idea of what thoughts about what was and how to use it and where the reports were, and so we just sort of rolled it out that way, and then it started to fly like wildfire. Eso the merchants start to engage with supply chain to have conversations, or the merchants were engaging with the vendors to sort of have negotiations about pricing. And they're creating these reports and getting the access to the information so quickly, and they're sharing it out that we had other groups just coming to us asking, How do I get into thoughts about how can I get in on DSO on top of those groups, we also sought out other heavy analytics groups such a supply chain where we felt like they could have the same benefits if they on boarded into thought spot with their data as well on Ben. Just continuing to evolve the training roll out. Um, you know, we continued to engage with the users, >>so >>we had a newsletter briefly Thio, sort of just keep informing users of the new data coming in or when we actually upgraded our system. So the here are the new features that you'll start seeing. We did virtual trainings and maintaining an F A Q document with the incoming questions from the users, and then eventually evolved into a self guided learning so that users that were coming to a group, or maybe we've already done a full rollout could come in and have the opportunity to learn how to use thought spot, have examples that were relevant to the business and really get started. Eso then each use case sort of after our initial started to build into a formula of the things that we needed to have. So you need to understand it. Having SMEs ready and having the database Onda worksheets built out sort of became the step by step path to drive adoption. Um, from an implementation timeline, I think they're saying, Took about two months and about half of that waas Kenny entire figuring out how figuring out our security, how to get the data in on, Do we need the time to set up the environment and get on Falcon? So then, after that initial two months, then each use case that we come through. Generally, we've got users trained and SMEs set up within about 2 to 3 weeks after the data is ingested. It's not obviously, once snowflakes set up on the data starts to get into that and the data feeds in, then you're really just looking at the 2 to 3 weeks because the data is easily connected in, >>um, no. All right, let's talk about some of the use cases. So we started with what data we've implemented. Andrea touched upon what Use a training look like what the back curate that piece wants. Now let's talk a little bit about use cases and how we actually leverage thoughts bought together the insights. So the very first one is ultimately the benefit of the tool to the entire organization. Israel Time insights. To reiterate what Andrea said, we first implemented the tool with our buyers. They're the nucleus of any retail organization as they work with everybody within the company and as the buyer's eyes, Their responsibility to ensure both the procurement and the sales channel, um, stays afloat at the end of the day, right? So they need information on a regular basis. They needed fast. They needed timely, and they needed in a fashion that they choose to digest it. It right? Not every business is the same. Not every individual is the same. They consume digest, analyze information differently. And that's what that's what allows you to dio whether it's the search, whether it's a customized onboard, please now supply chain unexpected things. As Andrea mentioned Irish work a lot of supply chain. What is the goal of supply chain to receive product and to be able to ship that product to the stores Now, as our organization has been growing and is doing extremely well, we've actually published Q three results recently. Um, the aspect off prioritization at D C level becomes very important, And what drives some of that prioritization is the analysis around what the upcoming sales would be for specific products for specific categories. And that's where again thoughts. But is one of the tools that we've utilized recently to set our prioritization logic from both inbound and outbound us. It's right because it gives you most recent results. It gives you most granular results, depending on the business problem that you're trying to tackle. Now let's chat a little bit about covert 19 response, because this one is an extremely interesting case as a pandemic hit back in March. Um, as you can imagine, the everyday life a Canadian entire became as business unusual is our executives referred to it under business unusual. This speed and the intensity of the insights and the analytics has grown exponentially. And the speed and the intensity of the insights is driven by the fact that we were trying Thio ensure that we have the right selection of products for our Canadian customers because that's ultimately bread and butter off all of the retailers is the customers, right? So thoughts bought allowed us to have early trends off both sales and inventory patterns, where, whether we were stalking out of some of the products in specific stories of provinces, whether we saw some of the upload off different lines of business, depending on the region, ality right as pandemic hit, for example, um, gym's closed restaurants closed. So as Canadian pack carries a wide variety of different lines of business, we actually offer a wide selection of exercise equipment and accessories, cycling products as well as the kitchen appliances and kitchen accessories pieces. Right? So all of those items started growing exponentially and in certain areas more than others. And this is where thoughts about comes into play. A typical analysis on what the region ality of the sales has been over the last couple of days, which is lifetime and pandemic terms, um, could have taken days weeks for analysts to ultimately cobbled together an Excel spreadsheet. Meanwhile, it can take a couple of seconds for 12 Korean tosspot set up a PIN board that can be shared through a wide variety of individuals rather than fording that one Excel spreadsheet that gets manipulated every single time. And then you don't get the right inside. So from again merch supply chain covert response aspect of things. That spot has been one of those blessings and one of those amazing tools to utilize and improve the speed off insights, improved the speed of analytics and improve the speed of decision making that's ultimately impacting, then consumer at the store level. So Andrea talked about 4500 users that we have that number of school. But what I owe the recently like to focus on, uh, Andrew and I laughing because I think the last time we've spoken at a larger forum with the fastball community, I think we had only 500 users. That was in the beginning >>of the year in in February, we were aiming to have like 1000 >>exactly. So mission accomplished. So we've got 4500 employees now. Everybody asked me, Yeah, that's a big number, but how many times do people actually log in on a weekly or daily basis? I'm or interested in that statistic? So lately, um, we've had more than 400 users on the weekly basis. What's what's been cool lately is, uh, the exponential growth off ad hoc ways. So throughout October, we've reached a 75,000 ad hoc ways in our system and about 13,000 PIN board views. So why is that's that's significant? We started off, I would say, in January of 2020 when Andrea refers to it, I think we started off with about 40 45,000 ad hoc worries a month. So again, that was cool. But at the end of the day, we were able to thio double that amount as more people migrate to act hawk searches from PIN board views, and that's that's a tremendous phenomena, because that's what that's about is all about. So I touched upon a little bit about exercise and cycling. So these are our quarterly results for Q two, um, that have showed tremendous growth that we did not plan for, that we were able to achieve with, ultimately the individuals who work throughout the organization, whether it's the merch organization or whether it's the supply chain side of the business. But coming together and utilizing a B I platform by tools such a hot spot, we can see triple digit growth results. Eso What's next for us users at Hawks searches? That's fantastic. I would still like to get to more than 1200 people on the weekly basis. The cool number to me is if all of our lifetime users were you were getting into the tool on a weekly basis. That would be cool. And what's proven to be true is ultimately the only way to achieve it is to keep surprising and delighting them and your surprising and delighting them with the functionality of the tool. With more of the relevant content and ultimately data adding in more data, um, is again possible through ET else, and it's possible through pulling that information manually. But it's expensive, expensive not from the sense of monetary value, but it's expensive from the size time, all of those aspects of things So what I'm looking forward to is migrating our platform to azure in snowflake and being able thio scale our insights accordingly. Toe adding more data to Adam or incites more, uh, more individual worksheets and data sets for people to Korea against helps the each one of the individuals learn. Get some of the insights. Helps my team in particular be, well, more well versed in the data that we have existing throughout the organization. Um, and then now Andrea, in touch upon how we scale it further and and how each one of the individuals can become better with this wonderful >>Yeah, soas used a zero mentioned theater hawk searches going up. It's sort of it's a little internal victory because our starting platform had really been thio build the pin boards to replicate what the users were already expecting. So that was sort of how we easily got people in. And then we just cut off the tap Thio, whatever the previous report waas. So it gave them away. Thio get into the tool and understand the information. So now that they're using ad hoc really means they understand the tool. Um, then they they have the data literacy Thio access the information and use it how they need. So that's it's a really cool piece. Um, that worked on for Canadian tire. A very report oriented and heavy organization. So it was a good starting platforms. So seeing those ad hoc searches go up is great. Um, one of the ways that we sort of scaled out of our initial group and I kind of mentioned this earlier I sort of stepped on my own toes here. Um is that once it was a proven success with the merchants and it started to spread through word of mouth and we sought out the analyst teams. Um, we really just kept sort of driving the insights, finding the data and learning more about the pieces of the business. As you would like to think he knows everything about everything. He only knows what he knows. Eso You have to continue to cultivate the internal champions. Um Thio really keep growing the adoption eso find this means that air excited about the possibility of using thought spot and what they can do with it. You need to find those people because they're the ones who are going to be excited to have this rapid access to the information and also to just be able to quickly spend less time telling a user had access it in thought spot. Then they would running the report because euro mentioned we basically hit a curiosity tax, right? You you didn't want to search for things or you didn't want to ask questions of the data because it was so conversed. Um, it was took too much time to get the data. And if you didn't know exactly what you were looking for, it was worse. So, you know, you wouldn't run a query and be like, Oh, that's interesting. Let me let me now run another query of all that information to get more data. Just not. It's not time effective or resource effective. Actually, at the point, eso scaling the adoption is really cultivating those people who are really into it as well. Um, from a personal development perspective, sort of as a user, I mean, one who doesn't like being smartest person in the room on bought spot sort of provides that possibility. Andi, it makes it easier for you to get recognized for delivering results on Dahlia ble insights and sort of driving the business forward. So you know, B b that all star be the Trailblazer with all the answers, and then you can just sort of find out what really like helping the organization realized the power of thought spot on, baby. Make it into a career. >>Amazing. I love love that you've joined us, Andrea. Such a such an amazing create trajectory. No bias that all of my s o heaps of great information there. Thank you both. So much for sharing your story on driving such amazing adoption and the impact that you've been able to make a T organization through. That we've got a couple of minutes remaining. So just enough time for questions. Eso Andrea. Our first questions for you from your experience. What is one thing you would recommend to new thoughts about users? >>Um, yeah, I would say Be curious and creative. Um, there's one phrase that we used a lot in training, which was just mess around in the tool. Um, it's sort of became a catchphrase. It is really true. Just just try and use it. You can't break. It s Oh, just just play around. Try it you're only limitation of what you're gonna find is your own creativity. Um, and the last thing I would say is don't get trapped by trying to replicate things. Is that exactly as they were? B, this is how we've always done it. Isin necessarily The the best move on day isn't necessarily gonna find new insights. Right. So the change forces you thio look at things from a different perspective on defined. Find new value in the data. >>Yeah, absolutely. Sage advice there. Andan another one here for Yaro. So I guess our theme for beyond this year is analytics meets Cloud Open for everyone. So, in your experience, what does What does that mean for you? >>Wonderful question. Yeah. Listen, Angela Okay, so to me, in short, uh, means scale and it means turning Yes. Sorry. No, into a yes. Uh, no, I'm gonna elaborate. Is interest is laughing at me a little bit. That's right. >>I can talk >>Fancy Two. Okay, So scale from the scale perspective Cloud a zai touched upon Throw our conversation on our presentation cloud enables your ability Thio store have more data, have access to more data without necessarily employing a number off PTL developers and going toe a number of security aspect of things in different data sources now turning a no into a yes. What does that mean with more data with more scalability? Um, the analytics possibilities become infinite throughout my career at Canadian Tire. Other organizations, if you don't necessarily have access thio data or you do not have the necessary granularity, you always tell individuals No, it's not possible. I'm not able to deliver that result. And quite often that becomes the norm, saying no becomes the norm. And I think what we're all striving towards here on this call Aziz part the conference is turning that no one say yes on then making a yes a new, uh, standard a new form. Um, as we have more access to the data, more access to the insights. So that would be my answer. >>Love it. Amazing. Well, that kind of brings in into this session. So thank you, everyone for joining us today on did wrap up this dream. Don't miss the upcoming product roadmap eso We'll be sticking around to speak thio some of the speakers you heard earlier today and I'll make the experts round table, and you can absolutely continue the conversation with this life. Q. On Q and A So you've got an opportunity here to ask questions that maybe keep you up at night. Perhaps, but yet stay tuned for the meat. The experts secrets to scaling analytics adoption after the product roadmap session. Thanks everyone. And thank you again for joining us. Guys. Appreciate it. >>Thank you. Thanks. Thanks.

Published Date : Dec 10 2020

SUMMARY :

Welcome back for our last session of the day how to deliver career making business outcomes with Search And the criteria that we thought about as we started on that journey of the sort of reasons that we moved into using thought spot was there was a need Thio the business use of the particular tool, let's talk a little bit about how we set it up and boards that had the base information that the users we're gonna need so that we could of the things that we needed to have. and the intensity of the insights is driven by the fact that we were trying Thio But at the end of the day, we were able to thio double that amount as more people Um, one of the ways that we sort of scaled out of our initial group and I kind on driving such amazing adoption and the impact that you've been able to make a T organization through. So the change forces you thio look at things from a different perspective on So I guess our theme for beyond this year is analytics meets Cloud so to me, in short, uh, means scale and And quite often that becomes the norm, saying no becomes the norm. the experts round table, and you can absolutely continue the conversation with this life. Thank you.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
AndreaPERSON

0.99+

Andrea FriskPERSON

0.99+

CanadaLOCATION

0.99+

AngelaPERSON

0.99+

January of 2020DATE

0.99+

AndrewPERSON

0.99+

Yarrow BaturinPERSON

0.99+

FebruaryDATE

0.99+

2QUANTITY

0.99+

Merch analyticsORGANIZATION

0.99+

4500 employeesQUANTITY

0.99+

first questionsQUANTITY

0.99+

Canadian TireORGANIZATION

0.99+

OctoberDATE

0.99+

2021DATE

0.99+

AdamPERSON

0.99+

one phraseQUANTITY

0.99+

KoreaLOCATION

0.99+

ExcelTITLE

0.99+

One sourceQUANTITY

0.99+

last yearDATE

0.99+

MarchDATE

0.99+

more than 1700 locationsQUANTITY

0.99+

oneQUANTITY

0.99+

12QUANTITY

0.99+

todayDATE

0.99+

more than 1200 peopleQUANTITY

0.99+

one sourceQUANTITY

0.99+

1000QUANTITY

0.99+

3 weeksQUANTITY

0.99+

more than 400 usersQUANTITY

0.98+

bothQUANTITY

0.98+

two monthsQUANTITY

0.98+

firstQUANTITY

0.98+

4.5 1000 employeesQUANTITY

0.98+

CoreyPERSON

0.97+

each oneQUANTITY

0.97+

four looking piecesQUANTITY

0.96+

this yearDATE

0.96+

trillions of roseQUANTITY

0.96+

about two monthsQUANTITY

0.96+

each use caseQUANTITY

0.96+

KennyPERSON

0.96+

about 40 45,000 adQUANTITY

0.96+

McCarthyPERSON

0.95+

75,000 adQUANTITY

0.95+

EsoORGANIZATION

0.95+

five billion recordsQUANTITY

0.95+

three informationQUANTITY

0.94+

first oneQUANTITY

0.93+

CanadianOTHER

0.93+

earlier todayDATE

0.91+

ThioORGANIZATION

0.9+

500 usersQUANTITY

0.9+

ThioPERSON

0.9+

hawksORGANIZATION

0.9+

about 2QUANTITY

0.89+

both salesQUANTITY

0.88+

pandemicEVENT

0.88+

MicrosoftORGANIZATION

0.87+

about 4500 usersQUANTITY

0.86+

Ido Safruti, PerimeterX | Cloud Native Insights


 

>> From The Cube Studios in Palo Alto, in Boston, connecting with thought leaders around the globe. These are Cloud Native Insights. >> Hi, I'm Stu Miniman the host of Cloud Native Insights where we're talking to companies and practitioners about how they take advantage of the innovation and agility of the cloud. Happy to welcome to the program I have first time guests, you know, Ido Safruti he is the co-founder and CTO of Perimeter X going to talk him in a dual role, both as a practitioner and their adoption of Cloud Native Technologies serverless specifically as well as they are a Cloud Native supplier in the security realm. Ido thanks so much for joining us. Nice to have you on the program. >> Yeah, good to be here. Thanks. >> All right. So Ido, if you could, you're co founder of Perimeter X, give us just, if you would, a little bit of your background and you know, what Perimeter X does and we'll, go into it from there. >> Sure. So as CTO, I'm in charge of the research, engineering, and product team at Perimeter X, we are a vendor, a Cloud Native vendor of web application security protecting all kinds of different business logic abuses for our customers, mostly large websites that are in demand of web-scale. So not only doing the protection or the application, but also integrated into multiple infrastructure and running at scale. We're solving problems like account takeover, carding, a major card data skimming and so on. >> One of the conversations we've been having the last couple of years from security is, you know, there's no shortage of new threats, the surface area of attack, keep getting more here in 2020, everybody's working from home more, the people that are doing attacks didn't stop working. So if you could just, you know, how long has Perimeter X been around? And I want to lead up to the discussion of serverless, you know, what was the architecture considerations before? And what started leading you towards making a change architecturally? >> Yeah, so Perimeter X was founded almost six years ago, a little less than six years ago. And we were a Cloud Native Solution to begin with. We identified the challenges of where the gap security in native cloud application is. For in many cases, security solutions are not leveraging the breadth and the new architecture of where applications are built. And we're more of trying to slap in a standard enterprise security and on other cloud infrastructure. When we started, we wanted to integrate and adopt the cloud and adopt the flexibility of the specificity of the edge to help enhance our customer's infrastructure by adding security onto that versus forcing them to rearchitect it when they integrate security into it. >> Well, it's addressing, you say six years ago. I can't remember hearing the term Cloud Native that long ago. Obviously Cloud has been around for a while, but when I started this one of the discussions around Cloud Native was, Oh, people were talking about adopting containers and Kubernetes. And I said, they're great tools to help from, you know, the infrastructure standpoint, but you're talking about right, living in the Cloud, taking advantage of cloud services, you know. That's where we really see the opportunity in Cloud Native. So, you know, when you say you were built for the cloud, but you know, things like containers, server lists probably weren't doing those six years ago, maybe, or were you? >> Actually, yeah, so we started early versions of obviously all dockerized Grenades was not that great back then. So we were orchestrating some things on our own and gradually adopting other orchestration and mesh for our own service that is obviously running on multiple cloud vendors. But from us, from our point of view, the key for cloud was how can we enable our customers, and how can we integrate better with them in a way that enhance their infrastructure versus add friction? Because the challenge usually with security, is that security in most cases or traditionally, was adding friction and delays and complexity to developer process. And we're designing our solution to begin with on how can we leverage these new technologies? How can we leverage the fact that CDNs and edges are becoming smarter and can, you can start deploying your own payloads and logic to make our logic integrated with them and to partner with this cloud players in order to enable our customers to add these additional tiers. And I think this is from my point of view, one of the key capabilities of having the capabilities of computed edge and serverless, is making a lightweight integration and making your existing infrastructure smarter by making it easy to incorporate third party vendors or other solutions or more logic without forcing a wholly architectural solution. >> Yeah, no, no. You bring up some great points. I remember back the early days of Docker, it was, can we get the atomic unit to be closer to what the application is. But you know, my background is in infrastructure and it was okay, It went from the server to the VM, to the container. Yeah, there's an application that sits on top of it, but I don't think about it as opposed to serverless starts with the developer first and you know, how I build my application and then there are certain things that I have to worry about the platform. So, help us understand doing containers, looking at serverless, was it okay, we're going to completely overhaul and throw out what we had because there's something new and better. Are you doing still some containers and some serverless? Help us understand, you know, what drove that transition and what the outcomes were? >> Yeah, so our infrastructure our machine learning algorithms, the data processing that the heavy lifting that we're running on our own infrastructure, which is again, Cloud Native Infrastructure. But something that we're managing in many cases is using containers is using other environments because we were running heavy payloads. We're not fully relying on some other platform to run for us. We're leveraging a lot of these technologies to run it and run it in a more efficient way. Where we're adopting serverless is both in some of the front end decisions. So making smarter load balancing decision integrating with some other cloud vendors to help make sure that requests are coming in the right view, and things like this, but where it is more important even then is how can we make ourselves relevant for customers to adopt serverless and how can we help introduce security into these environments? Because, if you're looking at traditional security, if you're, if you're so it's more about, if I go to that one, how can I enable our customers adopt serverless? How can I enable our customers adopt new technologies into cloud? Because it could be a limitation if you're, if you're a security policy or if your architecture is such, that requires everything to go through a specific security proxy or some firewall, it may force you to utilize very limited architectures. If you want to deploy now with payload on some, on Lambda or on, on your CDN, it typically will be way in front of your traditional enterprise security solutions. How can you make that application smarter? How can you make that application sort, self-sufficient by connecting modules, by making sure that you're including modules that integrate security, and bring the security with you everywhere. So, so this is the motion that we're trying to define here. >> Well, and I'm sure you've got a really interesting viewpoint that I'd love to hear on this, Ido. So if you look at, you know, most new technologies, especially in the cloud space, serverless specifically, you know, costs that should be less expensive, you know, flexible. I should be able to, you know, make changes, and speed. I should be able to do more faster, but always when you look at those, you say, well, but what about security? Can I do all of those things, you know, be faster, better, cheaper, more agile, and not be less secure? So I'd love to hear any thoughts you have on kind of the, you know, the typical things, but also your security angle on them? >> Yeah. So one of the benefit of using serverless, and I think there are two types, initially thinking of serverless one is running your code in some, backend application, that may access different things, but you don't need to manage for scale because there is some platform that manage that. Which is one great option, what you're seeing more and more, and we're working in collaboration with Fastly and where you can see that on other edge platforms is having this notion of serverless, How can you deploy code to the edge? And the benefit there is that you can mitigate a lot of the risks outside your data center, outside of your cloud, that if there is, and this is where security plays so well with that, because you want to mitigate the risks and the attack as far away from your application as possible. So if you can deploy the logic that is doing that, or making decisions at the edge, it helps you improve your infrastructure cost. It helps you improve some of the applications that are still in the backend, so you can gradually forward deploy some of the logic that is relevant at the edge and getting the scalability, getting this ability to scale without limit, because a CDN or edge vendor, he has a lot of capacity and withhold if it's a denial of service attack, or if it's any other type of attack, weigh this logic in hand. Or even, sometimes it's just skill. Maybe you had a very good marketing campaign and you were having a lot of traffic. If you can deploy this skill somewhere that can handle that in a distributed, efficient way, you are having even better. >> Well, and it sounds like that that fits into what Perimeter X does. You know, when I think about edge, you know, scale concerns, security concerns are, you know, some of those top of mind as are just, you know, how. You know, can automation things like machine learning or AI help me? Cause usually that scale or a distributed nature of it means that it's not necessarily something that people alone could take care of themselves. Am I getting right, a little bit where Perimeter X is helping their customers? >> Yeah, yeah, yeah. And the idea is to connect, to help and to help offline offset some of the logic or some of the capabilities that, that you don't want your business to be an expert in. So if you're a retailer, you want to be able to sell the best to optimize accomodation for your customers and to handle that you don't want to be an expert in detecting bots or in identifying malicious code or things of that sort. And if you can offset that and with a lightweight, easy integration that does not limit your ability to innovate and adopt new technologies, this is what we're trying to help. Let us focus at this. But by integrating the edge by integrating with partners like Fastly and so that we can help enhance the infrastructure and add more capabilities, where you can focus on doing your own business and we can help allow and enable additional technologies. >> Along your serverless journey, what partners, what other vendors were helpful along the way? As I've looked at it, it's a relatively young ecosystem, but it's robust. So, you know, I'm curious who, some of the companies that have helped along the way? >> Yep. I think Fastly is definitely one that is from their earlier infrastructure. They always had the component of exposing their edge and making it more programmable via configuration and setting logic. And now rolling out a computed edge that is giving even more flexibility. Other CDNs are opening their edge as well with all kinds of tools, again, Lambda from AWS and other services. So this is one component of how do you manage that? How do you always read that? There are issues of how much state can you manage their access to data? And there are different services that allows that. Other platforms, which are more of the platform as a service that are not traditionally considered serverless. And you can think of it as eCommerce platforms helps you deploy your logic and some sometimes go to application into their ecosystem and helps you focus on again, managing your application. So think of Magento, think of a Salesforce cloud, these kind of commerce applications that you can deploy your logic. They're all fit into that ecosystem of help you. You want to write your code to that, your key on and let someone else manage the scale, let someone else manage some of the things that are common tool. >> Well, yeah, that's definitely one you see diversity of solutions at edge. You know, very different from if you were thinking kind of their traditional enterprise data center. Any, you know, as a CTO, when you look at edge, you know, where we were the maturation of this whole solution, or are there areas specifically that you expect in the next, you know, six, 12, 18 months that we will see some things solidify, mature down the line. >> Yeah. Yeah. So I think that the state where the edge compute is at now is more about deploying logic that is remote from the data center. So there is a limit. And if you look across different vendors to the more IO or data access capabilities of these loads. So if you can write the code and make it self sufficient, it's easier and it's more common to find platforms that will love it. What you're starting to see is how you add the data layer into that tier and making it more accessible. And that opens the gate for many more reach an interesting reputation, because once you can have a key value store, and once you can manage a state and modify configuration, you can then start deploying more complex applications and make more decisions. Do I see the billing system running entirely on the edge? probably not. There are things where you want to store it in the database. There are things that make sense to have it in some backend infrastructure, but a lot of payloads more and more environments are going there. And I think these additional services of queuing services, data services, database like services. So can, can I run a transaction on the edge? These kinds of technologies are currently emerging and you can see them in different levels for different vendors. And they will definitely open the gate even further for more and more patrons will be adopted at the edge. >> All right. Well, Ido last question I have for you, What advice would you give for your peers out there? as you said, you know, you were early in Docker adoption. You've done serverless adoption, you know, Edge is something that is gaining a lot of attention. What advice would you give to people here in 2020 as they look at, you know, the variety of Cloud Native options out there? >> I think the easy one is anything new that you build look around and figure out what is the best technology that can help you get there faster? And how can you build in a more strategic way for C-suite executive, if it's the CTO, CIO, CSO, think on how can you enable your team to move faster? How can you enable your team by the solutions and technologies that you select to have the flexibility of moving faster? how can you enable them to, to adopt new technologies and make it available? How can, and this is, you need some practices because you need to make sure that you are getting the right metrics. So whenever that you're using vendors that will help you collect and monitor the services and get the insights, because suddenly if anyone can deploy anything anywhere, then there is some concern about loss of control. So finding the right vendors that can help you or adopting the right processes that helps you gain this visibility while still enabling them to go anywhere. This is key. At least for us, it was key. And this is from wearing my product hat when we're building our services, this is what we're trying to enable our customers to do with this security. >> Well, Ido Safruti, thank you so much for sharing your journey, really appreciate you having on the program. >> Sure, thanks. >> And if you have people we should talk to, I would love hearing the stories of Cloud Native, how those adjustments are going and sharing your information with your peers. I'm Stu Miniman and look forward to hearing more your Cloud Native sites. (Calming music)

Published Date : Sep 3 2020

SUMMARY :

leaders around the globe. Nice to have you on the program. Yeah, good to be here. So Ido, if you could, So as CTO, I'm in charge of the of years from security is, you know, and the new architecture of but you know, things like you can start deploying your and you know, how I build my application How can you make that application smarter? So if you look at, you know, And the benefit there is that you as are just, you know, how. and to handle that you don't want to be an So, you know, I'm curious applications that you can that you expect in the next, and once you can manage a as they look at, you know, the variety of How can you enable your team by the thank you so much for And if you have

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
Ido SafrutiPERSON

0.99+

Palo AltoLOCATION

0.99+

Stu MinimanPERSON

0.99+

Perimeter XORGANIZATION

0.99+

sixQUANTITY

0.99+

2020DATE

0.99+

IdoPERSON

0.99+

BostonLOCATION

0.99+

two typesQUANTITY

0.99+

Cloud Native InsightsORGANIZATION

0.99+

12QUANTITY

0.99+

LambdaTITLE

0.99+

AWSORGANIZATION

0.99+

six years agoDATE

0.99+

bothQUANTITY

0.98+

one componentQUANTITY

0.97+

PerimeterXORGANIZATION

0.97+

oneQUANTITY

0.97+

FastlyORGANIZATION

0.96+

The Cube StudiosORGANIZATION

0.96+

MagentoTITLE

0.96+

Cloud NativeTITLE

0.95+

Cloud Native TechnologiesORGANIZATION

0.95+

18 monthsQUANTITY

0.95+

first timeQUANTITY

0.95+

Cloud Native InsightsORGANIZATION

0.94+

Cloud NativeORGANIZATION

0.94+

OneQUANTITY

0.92+

less thanDATE

0.91+

one great optionQUANTITY

0.9+

CTOPERSON

0.89+

firstQUANTITY

0.81+

DockerTITLE

0.81+

CloudTITLE

0.79+

dualQUANTITY

0.77+

last couple of yearsDATE

0.7+

SalesforceTITLE

0.63+

Evan Weaver & Eric Berg, Fauna | Cloud Native Insights


 

(bright upbeat music) >> Announcer: From theCUBE studios in Palo Alto in Boston, connecting with thought leaders around the globe, these are Cloud Native Insights. >> Hi, I'm Stu Miniman, the host of Cloud Native Insights. We talk about cloud native, we're talking about how customers can take advantage of the innovation and agility that's out there in the clouds, one of the undercurrents, not so hidden if you've been watching the program so far. We've talked a bit about serverless, say something that's helping remove the friction, allowed developers to take advantage of technology and definitely move really fast. So I'm really happy to welcome to the program, for coming from Fauna. First of all, I have the CTO and Co-founder, who's Evan Weaver. And also joining him is the new CEO Eric Berg. They said, both from Fauna, talking serverless, talking data as an API and talking the modern database. So first of all, thank you both for joining us. >> Thanks for having us Stu. >> Hi, good to be here. >> All right, so Evan, we're going to start with you. I love talking to founders always. If you could take us back a little bit, Fauna as a project first before it was a company, you of course were an early employee at Twitter. So if you could just bring us back a little bit, what created the Fauna project and bring us through a brief history if you would. >> So I was employee 15 and Twitter, I joined in 2008. And I had a database background, I was sort of a performance analyst and worked on Ruby on Rails sites at CNET networks with the team that went on to found GitHub actually. Now I went to Twitter 'cause I wanted Twitter the product to stay alive. And for no greater ambition than that. And I ended up running the back end engineering team there and building out all the distributed storage for the core business objects, tweets, timelines, the social graph, image storage, the cache, that kind of thing. And this was early in the cloud era. API's were new and weird. You couldn't get Amazon EC2 off the shelf easily. We were racking hardware and code ancient center. And there were no databases or platforms for data of any kind. They really let us the Twitter engineering team focus on building the product. And we did a lot of open source work there. Some of which has influenced Fauna, originally, Twitter's open source was hosted on the Fauna GitHub account, which predated Twitter like you mentioned. And I was there for four years build out the team, basically scaled the site, especially scaled the Twitter.com API. And we just never found a platform which was suitable for what we were trying to accomplish. Like a lot of what Twitter did was itself a platform. We had developers all over the world using the Twitter API to interact with tweets. And we're frustrated that we basically had to become specialists in data systems because there wasn't a data API, we can just build the product on. And ultimately, then data API that we wished we had, is now Fauna. >> Well, it's a story we've loved hearing. And it's fascinating one, is that the marketplace wasn't doing what we needed. Often open source is a piece of that, how do we scale that out? How do we build that? Realized that the problem that you have is what others have. And hey, maybe there's a company. So could you give us that transition, Fauna as a product, as a company, where was it understood that, hey, there's a lot of other people that can take advantage from some of the same tools that you needed before. >> I mean, we saw it in the developers working with the Twitter platform. We weren't like, your traditional database experiences, either manage cloud or on-prem, you have to administrate the machine, and you're responsible for its security and its availability and its location and backups and all that kind of thing. People building against Twitter's API weren't doing that. They're just using the web interface that we provided to them. It was our responsibility as a platform provider. We saw lots of successful companies being built on the API, but obviously, it was limited specifically to interacting with tweets. And we also saw peers from Twitter who went on to found companies, other people we knew in the startup scene, struggling to just get something out the door, because they had to do all this undifferentiated heavy lifting, which didn't contribute to their product at all, if they did succeed and they struggled with scalability problems and security problems and that kind of thing. And I think it's been a drag on the market overall, we're essentially, in cloud services. We're more or less built for the enterprise for mature and mid market and enterprise companies that already had resources to put behind these things, then wasn't sort of the cloud equivalent of the web, where individuals, people with fewer resources, people starting new projects, people doing more speculative work, which is what we originally and Jack was doing at Twitter, it just get going and build dynamic web applications. So I think the move to cloud kind of left this gap, which ultimately was starting to be filled with serverless, in particular, that we sort of backtracked from the productivity of the '90s with the lamp era, you can do everything on a single machine, nobody bothered you, you didn't have to pay anyone, just RPM install and you're good to go. To this Kubernetes, containers, cloud, multi site, multi region world where it's just too hard to get a basic product out the door and now serverless is sort of brought that around full circle, we see people building those products again, because the tools have probably matured. >> Well, Evan, I really appreciate you helping set the table. I think you've clearly articulated some of the big challenges we're seeing in the industry right now. Eric, I want to bring you into the conversation. So you relatively recently brought in as CEO, came from Okta a company that is also doing quite well. So give us if you could really the business opportunity here, serverless is not exactly the most mature market, there's a lot of interest excitement, we've been tracking it for years and see some good growth. But what brought you in and what do you see is that big opportunity. >> Yeah, absolutely, so the first thing I'll comment on is what, when I was looking for my next opportunity, what was really important is to, I think you can build some of the most interesting businesses and companies when there are significant technological shifts happening. Okta, which you mentioned, took advantage of the fact of SaaS application, really being adopted by enterprise, which back in 2009, wasn't an exactly a known thing. And similarly, when I look at Fauna, the move that Evan talked about, which is really the maturation of serverless. And therefore, that as an underpinning for a new type of applications is really just starting to take hold. And so then there creates opportunities that for a variety of different people in that stack that to build interesting businesses and obviously, the databases is an incredibly important part of that. And the other thing I've mentioned is that, a lot of people don't know this but there's a very good chunk of Okta's business, which is what they call their customer identity business, which is basically, servicing of identity is a set of API's that people can integrate into their applications. And you see a lot of enterprises using this as a part of their digital transformation effort. And so I was very familiar with that model and how prevalent, how much investment, how much aid was out there for customers, as every company becoming a software company and needing to rethink their business and build applications. And so you put those two trends together and you just see that serverless is going to be able to meet the needs of a lot of those companies. And as Evan mentioned, databases in general and traditionally have come with a lot of complexity from an operational perspective. And so when you look at the technology and some of the problems that Fauna has solved, in terms of really removing all of that operational burden when it comes to starting with and scaling a database, not only locally but globally. It's sort of a new, no brainer, everybody would love to have a database that scales, that is reliable and secure that they don't have to manage. >> Yeah, Eric, one follow up question for you. I think back a few years ago, you talked to companies and it's like, okay, database is the center of my business. It's a big expense. I have a team that works on it. There have been dealt so much change in the database market than most customers I talked to, is I have lots of solutions out there. I'm using Mongo, I've got Snowflake, Amazon has flavors of things I'm looking at. Snowflake just filed for their IPO, so we see the growth in the space. So maybe if you could just obviously serverless is a differentiation. There's a couple of solutions out there, like from Amazon or whether Aurora serverless solution but how does Fauna look to differentiate. Could you give us a little bit of kind of compared to the market out there? >> Sure, yeah, so at the high level, just to clarify, at the super high level for databases, there tends to be two types operational databases and then data warehouse which Snowflake is an example of a data warehouse. And as you probably already know, the former CEO of Snowflake is actually a chairman of Fauna. So Bob Muglia. So we have a lot of good insight into that business. But Fauna is very much on the operational database side. So the other half of that market, if you will, so really focused on being the core operational store for your application. And I think Evan mentioned it a little bit, there's been a lot of the transformation that's happened if we rewind all the way back to the early '90s, when it was Oracle, and Microsoft SQL Server were kind of the big players there. And then as those architectures basically hit limits, when it came to applications moving to the web, you had this whole rise in a lot of different no SQL solutions, but those solutions sort of gave up on some of the promises of a relational database in order to achieve some of the ability to scale in the performance required at the web. But we required then a little bit more sophistication, intelligence, in order to be able to basically create logic in your application that could make up for the fact that those databases didn't actually deliver on the promises of traditional relational databases. And so, enter Fauna and it's really sort of a combination of those two things, which is providing the trust, the security and reliability of a traditional relational database, but offering it as serverless, as we talked about, at the scale that you need it for a web application. And so it's a very interesting combination of those capabilities that we think, as Evan was talking about, allows people who don't have large DevOps teams or very sophisticated developers who can code around some of the limitations of these other databases, to really be able to use a database for what they're looking for. What I write to it is what I'm going to read from it and that we maintain that commitment and make that super easy. >> Yeah, it's important to know that the part of the reason that operational database, the database for mission critical business data has remained a cost center is because the conventional wisdom was that something like Fauna was impossible to build. People said, you literally cannot in information science create a global API for data which is transactional and consistent and suitable for relying on, for mission critical, user login, banking payments, user generated content, social graphs, internal IT data, anything that's irreplaceable. People said, there can be no general service that can do this ubiquitously a global internet scale, you have to do it specifically. So it's sort of like, we had no power company. Instead, you could call up Amazon, they drive a truck with a generator to your house and hook you up. And you're like, right on, I didn't have to like, install the generator myself. But like, it's not a good experience. It's still a pain in the neck, it's still specific to the location you're at. It's not getting utility computing from the cloud the way, it's been a dream for many decades that we get all our services through brokers and API's and the web and it's finally real with serverless. I want to emphasize that the Fauna it technology is new and novel. And based on and inspired by our experience at Twitter and also academic research with some of our advisors like Dr. Daniel Abadi. It's one of the things that attracted us, Snowflake chairman to our company that we'd solve groundbreaking problems in information science in the cloud, just the way Snowflakes had. >> Yeah, well and Evan, yeah please go on Eric. >> Yeah, I'm just going to have one thing to that, which is, in addition, I think when you think about Fauna and you mentioned MongoDB, I think they're one of a great examples of database companies over the last decade, who's been able to build a standalone business. And if you look at it from a business model perspective, the thing that was really successful for them is they didn't go into try to necessarily like, rip and replace in big database migrations, they started evolving with a new class of developers and new applications that were being developed and then rode that obviously into sort of a land and expand model into enterprises over time. And so when you think about Fauna from your business value proposition is harnessing the technological innovation that Evan talked about. And then combining this with a product that bottoms up developer first business motion that kind of rides this technological shift into you creating a presence in the database market over time. >> Well, Evan, I just want to go back to that, it's impossible comment that you made, a lot of people they learn about a technology and they feel that that's the way the technology works. Serverless is obviously often misunderstood from the name itself, too. We had a conversation with Andy Jassy, the CEO of AWS a couple years ago, and he said, "If I could rebuild AWS from the ground up today, "it would be using all serverless," that doesn't mean only lambda, but they're rebuilding a lot of their pieces underneath it. So I've looked at the container world and we're only starting the last year or so, talking about people using databases with Kubernetes and containers, so what is it that allows you to be able to have as you said, there's the consistency. So we're talking about acid there, not worry about things like cold starts, which are thing lots of people are concerned about when it comes to serverless and help us understand a little bit that what you do and the underlying technologies that you leverage. >> Yeah, databases are always the last to evolve because they're the riskiest to change and the hardest to build. And basically, through the cloud era, we've done this lift and shift of existing on premises solutions, especially with databases into cloud machines, but it's still the metaphor of the physical computer, which is the overriding unit of granularity mental concept, everything like you mentioned, containers, like we had machines then we had Vms, now we have containers, it's still a computer. And the database goes in that one computer, in one spot and it sits there and you got to talk to it. Wherever that is in the world, no matter how far away it is from you. And people said, well, the relational database is great. You can use locks within a single machine to make sure that you're not conflicting your data when you update it, you going to have transactionality, you can have serialize ability. What do you do, if you want to make that experience highly available at global scale? We went through a series of evolutions as an industry. From initially that the on-prem RDBMS to things like Google's percolator scheme, which essentially scales that up to data center scale and puts different parts of the traditional database on different physical machines on low latency links, but otherwise doesn't change the consistency properties, then to things like Google Spanner, which rely on synchronized atomic clocks to guarantee consistency. Well, not everyone has synchronized atomic clocks just lying around. And they're also, their issues with noisy neighbors and tenancy and things because you have to make sure that you can always read the clock in a consistent amount of time, not just have the time accurate in the first place. And Fauna is based on and inspired and evolved from an algorithm called Calvin, which came out of a buddy's lab at Yale. And what Calvin does is invert the traditional database relationship and say, instead of doing a bunch of work on the disk and then figuring out which transactions won by seeing what time it is, we will create a global pre determined order of transactions which is arbitrary by journaling them and replicating them. And then we will use that to essentially derive the time from the transactions which have already been committed to disk. And then once we know the order, we can say which one's won and didn't win and which happened before, happen after and present the appearance of consistency to all possible observers. And when this paper came out, it came out about a decade ago now I think, it was very opaque. There's a lot of kind of hand waving exercises left to the reader. Some scary statements about how wasn't suitable for things that in particular SQL requires. We met, my co-founder and I met as Fauna chief architect, he worked on my team at Twitter, at one of the database groups. We were building Fauna we were doing our market discovery or prototyping and we knew we needed to be a global API. We knew we needed low latency, high performance at global scale. We looked at Spanner and Spanner couldn't do it. But we found that this paper proposed a way that could and we can see based on our experience at Twitter that you could overcome all these obstacles which had made the paper overall being neglected by industry and it took us quite a while to implement it at industrial quality and scale, to qualify it with analysts and others, prove to the world that it was real. And Eric mentioned Mongo, we did a lot of work with Cassandra as well at Twitter, we're early in the Cassandra community. Like I wrote, the first tutorial for Cassandra where data stacks was founded. These vendors were telling people that you could not have transactionality and scale at the same time, and it was literally impossible. Then we had this incrementalism like things with Spanner. And it wasn't till Fauna that anyone had proved to the world that that just wasn't true. There was more marketing around their failure to solve the information science problem, than something fundamental. >> Eric, I'm wondering if you're able to share just order of magnitude, how many customers you have out there from a partnership standpoint, we'd like to understand a little bit how you work or fit into the public cloud ecosystems out there. I noticed that Alphabets General Venture Fund was one of the contributors to the last raise. And obviously, there's some underlying Google technology there. So if you could just customers and ecosystem. >> Yeah, so as I mentioned, we've had a very aggressive product lead developer go to market. And so we have 10s of thousands of people now on the service, using Fauna at different levels. And now we're focused on, how do we continue to build that momentum, again, going back to the model of focus on a developer lead model, really what we're focused on there is taking everything that Evan just talked about, which is real and very differentiated in terms of the real core tech in the back end and then combining that with a developer experience that makes it extremely easy to use and really, we think that's the magic in terms of what Fauna is bringing, so we got 10s of thousands of users and we got more signing up every day, coming to the service, we have an aggressive free plan there and then they can migrate up to higher paying plans as they consume over time. And the ecosystem, we're aggressively playing in the broader serverless ecosystem. So what we're looking at is as Evan mentioned, sometimes the databases is the last thing to change, it's also not necessarily the first thing that a developer starts from when they think about building their application or their website. And so we're plugging into the larger serverless ecosystem where people are making their choices about potentially their compute platform or maybe a development platform like I know you've talked to the folks over at JAMstack, sorry at Netlify and Purcell, who are big in the JAMstack community and providing really great workflows for new web and application developers on these platforms. And then at the compute layer, obviously, our Amazon, Google, Microsoft all have a serverless compute solution. CloudFlare is doing some really interesting things out at the edge. And so there's a variety of people up and down that stack, if you will, when people are thinking about this new generation of applications that we're plugging into to make sure that the Fauna is that the default database of choice. >> Wonderful, last question, Evan if I could, I love what I got somebody with your background. Talk about just so many different technologies maturing, give us a little bit as to some of the challenges you see serverless ecosystem, what's being attacked, what do we still need to work on? >> I mean, serverless is in the same place that Lamp was in the in the early '90s. We have the old conservatives ecosystem with the JAMstack players that Eric mentioned. We have closed proprietary ecosystems like the AWS stack or the Google Firebase stack. As to your point, Google has also invested in us so they're placing their bets widely. But it's seeing the same kind of criticism. That Lamp, the Linux, Apache, MySQL, PHP, Perl, it's not mature, it's a toy, no one will ever use this for real business. We can't switch from like DV2 or mumps to MySQL, like no one is doing that. The movement and the momentum in serverless is real. And the challenge now is for all the vendors in collaboration with the community of developers to mature the tools as those the products and applications being built on the new more productive stack also mature, so we have to keep ahead of our audience and make sure we start delivering and this is partly why Eric is here. Those those mid market and ultimately enterprise requirements so that business is built on top of Fauna today, can grow like Twitter did from small to giant. >> Yeah, I'd add on to that, this is reminiscent for me, back in 2009 at Okta, we were one of the early ISVs that built on in relied 100% on AWS. At that time there was still, it was very commonplace for people racking and stacking their own boxes and using Colo and we used to have conversations about I wonder how long it's going to be before we exceed the cost of this AWS thing and we go and run our own data centers. And that would be laughable to even consider today, right, no one would ever even think about that. And I think serverless is in a similar situation where the consumption model is very attractive to get started, some people sitting there, is it going to be too expensive as I scale. And as Evan mentioned, when we think about if you fast forward to kind of what the innovation that we can anticipate both technologically and economically it's just going to be the default model that people are going to wonder why they used to spend all these time managing these machines, if they don't have to. >> Evan and Eric, thank you so much, is great to hear the progress that you've made and big supporters, the serverless ecosystem, so excited to watch the progress there. Thanks so much. >> Thanks Stu. >> Thanks for having us Stu. >> All right and I'm Stu Miniman. Stay tuned. Every week we are putting out the Cloud Native Insights. Appreciate. Thank you for watching. (bright upbeat music)

Published Date : Aug 28 2020

SUMMARY :

leaders around the globe, of the innovation and going to start with you. We had developers all over the is that the marketplace cloud equivalent of the web, some of the big challenges and secure that they don't have to manage. is the center of my business. of the ability to scale that the part of the reason Yeah, well and Evan, And so when you think about Fauna and the underlying and the hardest to build. or fit into the public the last thing to change, to some of the challenges And the challenge now that people are going to wonder why and big supporters, the the Cloud Native Insights.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
EvanPERSON

0.99+

EricPERSON

0.99+

AmazonORGANIZATION

0.99+

JackPERSON

0.99+

Andy JassyPERSON

0.99+

AWSORGANIZATION

0.99+

2008DATE

0.99+

GoogleORGANIZATION

0.99+

Bob MugliaPERSON

0.99+

2009DATE

0.99+

MicrosoftORGANIZATION

0.99+

Palo AltoLOCATION

0.99+

Eric BergPERSON

0.99+

Stu MinimanPERSON

0.99+

SnowflakeORGANIZATION

0.99+

AmazoORGANIZATION

0.99+

OracleORGANIZATION

0.99+

TwitterORGANIZATION

0.99+

NetlifyORGANIZATION

0.99+

four yearsQUANTITY

0.99+

100%QUANTITY

0.99+

two typesQUANTITY

0.99+

FaunaORGANIZATION

0.99+

Daniel AbadiPERSON

0.99+

MySQLTITLE

0.99+

Evan WeaverPERSON

0.99+

OktaORGANIZATION

0.99+

two thingsQUANTITY

0.99+

last yearDATE

0.99+

firstQUANTITY

0.99+

one computerQUANTITY

0.99+

JAMstackORGANIZATION

0.99+

bothQUANTITY

0.99+

PHPTITLE

0.99+

Alphabets General Venture FundORGANIZATION

0.99+

oneQUANTITY

0.99+

early '90sDATE

0.98+

CNETORGANIZATION

0.98+

FirstQUANTITY

0.98+

StuPERSON

0.98+

BostonLOCATION

0.98+

MongoORGANIZATION

0.97+

LinuxTITLE

0.97+

single machineQUANTITY

0.97+

first thingQUANTITY

0.97+

Tom Preston-Werner | Cloud Native Insights


 

>> Presenter: From theCUBE studios in Palo Alto in Boston, connecting with thought leaders around the globe, these are cloud native insights. >> Hi, I'm Stu Miniman, the host of Cloud Native Insights. When we launched this program, we talked about, how do we take advantage of the innovation and agility that's in the cloud? And of course, one of the big components that we've talked about for many years on theCUBE is, how do we empower developers? and developers are helping change things, and I'm really happy to welcome to the program first time guests that helped build many of the tools that developers are very well familiar. So Tom Preston Werner, he is the co-founder of Chatterbug, he is the creator of redwoodjs, we had an early episode, the JAMstack Netlify team, he's also on the board for that, and we'll talk about those pieces. People might know him, if you check him out on Wikipedia, you know, GitHub, he was one of the co-founders as well as held both CTO and CEO roles there. I could go on but Tom, thank you so much for joining us. >> Thank you for having me. >> All right, so let's start there, Tom, you know, when I live in the enterprise space, how do you take advantage of new things? One of the biggest challenges out there is, let's go to something new, but let's do it the old way. And we know that that really doesn't take advantage of it you know, I think back to the oldest, some of the older technologies, it's like, well, you know, if I talk to people that are riding horses, what do they want? You know, well, I want faster horses, not the, you know, let's completely change things. I was hearing a stat that, you know, back in the early days of cars, we had like, 30% of them were electric cars, and now it's one. So what's old is new again, but I digress. One, as I mentioned, you know, GitHub, of course, is, you know, such a fundamental piece when we look at in the technology space over the last decade, you know, get in general, GitHub, specifically, of course, has created so much value engaged, you know, just millions and millions of developers and transform businesses. Take us back a little bit and you know, like to get your philosophy on, you know, building tools, how do you do it? How do you think about it? And what's inspired you? >> Yeah, I think it goes a long way back to just wanting to build things for the community. One of the first big projects I worked on was called Gravatar, and I remember laying in bed staring at the ceiling, just trying to think up some idea that that would contribute to what we then called The Blogosphere, and I came up with an idea for avatars that would follow you around and I coded it up and I got it out to a few bloggers and they started using it, and it caught on and it was really, it really introduced me to this idea that no matter who you are, where you come from, or what your background is, you know, I grew up in Iowa, things are very different there. And with with the Internet, and the ability to code, you can impact the world in really significant ways. And so it follows on from there, and I think GitHub is an extension of that desire to really put things into the world that will be useful for people, and knowing that, if you have the ability to code and especially with the advent of web applications as a common tool, there's such power in that you have global reach, you just need a computer and the ability to code and you can create these things, and GitHub kind of became that. It was just, it started out really as a side project, and I hoped that someday it would be able to support me to work on it full time. But I, we started building it just because we wanted it to exist. And that's most of what I work on is, is just ideas that I want to exist in the world. >> Yeah, it's been one of those great trends to watch at, you know, there were certain technologies that used to have to be a nation state, or, you know, one of the one of the global 50 companies to take advantage of it. Now, tools like GitHub, making it so that, you know, the smallest company or even the individuals can participate in communities, can create and build you know, the building is such an important theme. So Maybe, let's fast forward a little bit if we would, I mentioned Netlify and JAMstack, you talked about the blogosphere, that team is helping to really reinvent how we think about the web, you know, it's real time, It's high performance, and you know, we need to be able to get that to where everybody is. So, you know, back in the early days, web pages, you know, relatively static and, you know, had certain criteria, and now, of course, you know, edge devices and the global population change things. So, you know, you, you've been engaged in a, you know, huge supporter of that project, and that'll lead us towards the redwoods discussion, but maybe bring us as to how you got involved there, and what got you excited? >> Well, like you said, Everything old is new again and I think that's true in fashion. It's also true in technology, in a lot of ways, and the JAMstack really is taking these old ideas where the web started, taking files and just serving them as static files and it's super fast, and it's extremely secure. This is how the internet started, and now we've sort of come full circle. But we've added a lot of really nice things and workflows on top of that. And so my journey into the JAMstack, I suppose, started more than a decade ago, when I started working on a project called Jekyll, that's a, I called it at the time, A Blog Aware Static Site Generator. So you would write your blog articles, and you would run it through Jekyll, and that would take your markdown, you'd write your articles in markdown, and it would combine them with a, some kind of a theme that you would have, and that would output static pages that represented your blog, and then you could serve those from any kind of static blog serving system. GitHub had has one built in called GitHub Pages, and so we ended up adopting Jekyll for GitHub Pages. So everything that you put up on GitHub Pages. would be run through Jekyll, and so it was a really natural place to put your blog. And so I had a blog post, one of my blog posts using Jekyll was called Blogging Like A Hacker. And it was this idea that you don't need WordPress, you don't need to have a database somewhere that's, that's hackable, that's going to cause you security problems, all the WordPress admin stuff that constantly is being attacked. You don't need all that, like you can just write articles in flat files, and then turn them into a blog statically and then put those up to serve them somewhere, right? And so when I say it like that, it sounds a little bit like the JAMstack, right? That's not how we thought about it at the time, because it was really hard to do dynamic things. So if you wanted to have comments on your blog for instance, then you needed to have some third party service that you would embed a component onto your blog, so you could receive comments. And so you had to start gluing things together, but even then, again, that sounds a little bit like the JAMstack. So it's all of these ideas that have been, evolving over the last decade to 15 years, that now we finally have an entire tool chain and adding Git on top of that and Git based workflows, and being able to push to GitHub and someone like Netlify can pick those up and publish them, and you have all these third party services that you can glue together without having to build them yourself. All of the billing things, like there's just the ecosystem is so much more advanced now, so many more bits are available for you to piece together that in a very short amount of time, you can have an extremely performant site capable of taking payments, and doing all of the dynamic things that we want to do. Well, many, I should say many of the dynamic things that we want to do, and it's fast and secure. So it's like the web used to be when the web started, but, now you can do all the modern things that you want to do. >> You're giving me flashbacks remembering how I glued discus into my Tumblr instance when that was rolling out. (laughing) >> That's what I was referring to, discuss. >> Yeah, so absolutely, you talk about there's just such a robust ecosystem out there, and one of the real challenges we have out there is, people will come in and they say, "Oh my gosh, where do I start?" And it's like, well, where do you want to go? There's the Paradox of Choice, and that I believe is one of the things that led you to create Redwoods. So help explain to our audience you know, you created this project Redwood, it related to JAMstack, but, but I'll let you explain you know, what it is in life needed? >> Yeah, Redwood is a response to a couple of things. One of those things, is the JavaScript world has, as everything has evolved in tremendous way, in all kinds of ways and almost entirely positive I think. The language itself has been improved so much from when I was a teenager using view source and copy pasting stuff into you know, some random X Files fan site. To now it's a first class language I can compete with with everything, from a ergonomics perspective. I really enjoy programming in it and I come from a Ruby, Ruby on Rails background and now I'm very happy in JavaScript that was not true even five, seven years ago, right? So JavaScript itself has changed a lot. Along with that comes NPM in the whole packaging universe, of availability of modules, right? So most of the things that you want to do, you can go and you can search and find code that's going to do those things for you, and so being able to, to just pull those into your projects so easily. That is amazing, right? The power that that gives you is tremendous. The problem comes in when, like you said, you have the Paradox of Choice. Now you have, not just one way to do something, but you have 100 ways to do something, right? And now as a as a developer, and especially as a new developer, someone who's just learning how to build web applications, you come into this and you say, all you see is the complexity, just overwhelming complexity, and every language goes through this. They go through a phase of sort of this Cambrian explosion of possibilities as people get excited, and you see that the web is embracing these technologies, and you see what's possible. Everyone gets excited and involved and starts creating solution after solution after solution, often times to the same problems. And that's a good thing, right, like exploring the territory is a good and necessary part of the evolution of programming languages and programming ecosystems. But there's comes a time where that becomes overwhelming and starts to trend towards being a negative. And so at Chatterbug, which is a foreign language learning service, if you want to learn how to speak French or Spanish or German, we'll help you do that, as part of that work, we started using react on the front end, because I really love what react brings you from a JavaScript and interactivity perspective. But along with react, you have to make about 50 other choices of technologies to use to actually create a fully capable website, something for state management, you got to choose a way to do JavaScript or sorry, CSS. There's 100 things that you have to choose, and it's, it seems very arbitrary and you go through a lot of churn, you choose one, and then the next day an article comes out and then people raving about another one, and then you choose, you're like, Oh, that one looks really nice. You know, grass is always greener, and so Redwood is a bit of a, an answer to that, or a response to that, which is to say, we've learned a lot of things now about what works in building with react, especially on the front end. And what I really want to do is have a tool that's more like Ruby on Rails, where I come from, having done years and years of Ruby on Rails, what GitHub was built with. And Ruby on Rails presents to you a fully capable web application framework that has made all the choices or most of the choices, many of the important choices. And the same is kind of missing in the JavaScript TypeScript world and so, when I saw Netlify come out with their feature where you could commit the code for a lambda function to your repository, and if you push that up to GitHub, Netlify will grab it, and they will orchestrate deploying that code to an AWS lambda so that you can run business logic in a lambda but without having to touch AWS, because touching AWS is another gigantic piece of complexity, and their user interfaces are sometimes challenging, I'll say. That, that then made me think that, here finally is the ability to combine everything that's awesome about the JAMstack and static files, and security, and this workflow, with the ability to do business logic, and that sounded to me like the makings of a full stack web application framework, and I kept waiting for someone to come out and be like, hey, tada, like we glued this all together, and here's your thing, that's rails, but for the JAMstack, JavaScript, TypeScript world and nobody was doing it. And so I started working on it myself, and that has become Redwoodjs. >> It's one of the things that excited me the early days when I looked into Serverless was that, that low bar to entry, you know, I didn't have to have, you know, a CS degree or five years of understanding a certain code base to be able to take advantage of it. Feels like you're hoping to extend that, it believe it's one of your passions, you know, helping with with Chatterbug and like, you know, helping people with that learning. What do you feel is the state out there? What's your thoughts about kind of the future of jobs, when it when it comes to this space? >> I think the future of jobs in technology and especially software development is, I mean, there is no, there is no better outlook for any profession than that. I mean, this is the, this is where the world is going, more and more of what we want to accomplish, we do in software and it happens across every industry. I mean, just look at Tesla's for instance, right? You think about automobiles and the car that you owned, you know, 10 years ago, and you're like, I don't know, I know there's a computer in here somewhere, but like, I don't really, you know, either the software for it is terrible, and you're like, who, when was the last time you actually use the navigation system in your car, right? You just like get like just turn that off because it's, it's so horrible. And then Tesla comes along and says, hey, what if we actually made all this stuff useful, and had a thoughtful interface and essentially built a car that where everything was controlled with software, and so now cars are are basically software wrapped in hardware, and the experience is amazing. And the same is true of everything, look at your, look at how many things that your phone has replaced that used to be physical devices. Look at manufacturing processes, look at any any element of bureaucracy, all of this stuff is mediated by computers, and oftentimes it's done badly. But this just shows how much opportunity there is speaking of like governmental websites, right, you go to the DMV, and you try to schedule an appointment, and you just have no confidence that that's going to work out because the interfaces feel like they were written 15 years ago, and sometimes I think they were, written that long ago. But there's so much, there's still so much improvement to be had and all of that is going to take developers to do it. Unless, you know, we figure out how to get AI to do it for us, and there's been some very interesting things lately around that angle, but to me, it's, humans will always be involved. And so, at some level, humans are telling machines what to do, whether you're doing it more or less directly, and having the ability to tell machines what to do gives you tremendous leverage. >> Yeah, we're big fans, if you know Erik Bryjolfsson and Andy McAfee from MIT, they've, you know, are very adamant that it's the combination of people plus machines that always will win against either people alone or machines alone. Tom, what, you know, right now we're in the middle of a global pandemic, there're financially, there's a lot of bad news around the globe right now. I've talked to many entrepreneurs that said, well, a downturn market is actually a great time to start something new. You're an investor, you've helped build lots of things. We talked a lot about lowering the bar for people to create and build new things. What do you see are some of the opportunities out there, if you know, you had to recommend for the entrepreneurs out there? Where should they be looking? >> I'd say look at all of the things in your life that have become challenging, because where there's challenge, where there's pain, there's opportunity for solutions. And especially when there's a big environmental change, which we see right now, with COVID-19, obviously has changed a lot of our behaviors and made some of the things that used to be easy. It's made those a lot harder, and so you see, certain segments of the economy are doing extremely well, namely technology and things that allow us to do interviews like this instead of in person, and so those industries are doing extremely well. So you look at the you look at the stock market in the United States, and it's it's very interesting, because while much of the country is suffering, the people that are already wealthy are doing very well, and technology companies are doing very well. And so the question for me is, what are the opportunities that we have, leveraging technology in the internet, to where we can create more opportunities for more people, to get people back to work, right? I think there's so much opportunity there. Just look at education, like the entire concept of educating kids right now and I have three. So we feel this very much, it has been turned on its head. And so we so you see many people looking for solutions in that space, and that's, I think that's as it should be. When things get, when things get challenged when our, our normal daily experience is so radically changed, there's opportunity there, because people are willing to change more quickly in a crisis, right? Because you need, you need something like any solution. And so some choice is going to be made, and where that's happening, then you can find early adopters more easily, than you can under other circumstances, and so in economic downturns, you often see that kind of behavior where these are crisis moments for people, you have an opportunity to come in and if you have something that could solve a problem for them, then you can get a user where that may have not been a problem for a person before. So where there is, where there is a crisis, there is always opportunity to help people solve their problems in different and better ways to address that crisis. So again, it goes back to pain, you know, and it doesn't have to be the pain from a crisis. It could be a pain from from anything. Just like with GitHub, it was, it was hard to share code as developers like it was, there was too much pain, and this was, we started it in 2008, right after the housing crisis. It was unrelated to that, but it turns out that when you start a company, when the economy is depressed in a certain way, then at least you can look forward to the economy getting better as you are building your company. >> Oh, Tom, Preston Werner, thank you so much for joining pleasure talking with you. I appreciate all of your input. >> Absolutely, thanks for having me. >> I'm Stu Miniman, thank you for joining this Episode of cloud native insights. Thank you for watching the theCUBE. (light music)

Published Date : Aug 21 2020

SUMMARY :

leaders around the globe, and agility that's in the cloud? I was hearing a stat that, you know, and the ability to code and and now, of course, you know, edge devices and then you could serve those when that was rolling out. That's what I was So help explain to our audience you know, So most of the things that you want to do, that low bar to entry, you and the car that you owned, if you know, you had to recommend So again, it goes back to pain, you know, thank you so much for joining I'm Stu Miniman, thank you for joining

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
TomPERSON

0.99+

threeQUANTITY

0.99+

Palo AltoLOCATION

0.99+

Tom Preston WernerPERSON

0.99+

IowaLOCATION

0.99+

2008DATE

0.99+

Stu MinimanPERSON

0.99+

Andy McAfeePERSON

0.99+

Ruby on RailsTITLE

0.99+

TeslaORGANIZATION

0.99+

United StatesLOCATION

0.99+

30%QUANTITY

0.99+

COVID-19OTHER

0.99+

100 thingsQUANTITY

0.99+

millionsQUANTITY

0.99+

Preston WernerPERSON

0.99+

five yearsQUANTITY

0.99+

Erik BryjolfssonPERSON

0.99+

GitHubORGANIZATION

0.99+

AWSORGANIZATION

0.99+

100 waysQUANTITY

0.99+

JavaScriptTITLE

0.99+

50 companiesQUANTITY

0.99+

SpanishOTHER

0.99+

one wayQUANTITY

0.98+

MITORGANIZATION

0.98+

FrenchOTHER

0.98+

TypeScriptTITLE

0.98+

RubyTITLE

0.98+

BostonLOCATION

0.98+

ChatterbugORGANIZATION

0.97+

oneQUANTITY

0.97+

bothQUANTITY

0.97+

JavaScript TypeScriptTITLE

0.97+

15 years agoDATE

0.97+

GermanOTHER

0.96+

JAMstackTITLE

0.96+

OneQUANTITY

0.96+

GitTITLE

0.96+

NetlifyORGANIZATION

0.95+

theCUBEORGANIZATION

0.94+

10 years agoDATE

0.94+

WordPressORGANIZATION

0.93+

first classQUANTITY

0.91+

seven years agoDATE

0.9+

Tom Preston-WernerPERSON

0.9+

TumblrORGANIZATION

0.89+

redwoodsPERSON

0.89+

first timeQUANTITY

0.88+

15 yearsQUANTITY

0.85+

last decadeDATE

0.84+

WikipediaORGANIZATION

0.83+

Cloud Native InsightsORGANIZATION

0.82+

more than a decade agoDATE

0.82+

first bigQUANTITY

0.81+

JekyllORGANIZATION

0.81+

JekyllTITLE

0.8+

JAMstackORGANIZATION

0.79+

Corey Quinn, The Duckbill Group | Cloud Native Insights


 

>>from the Cube Studios in Palo Alto in Boston, connecting with thought leaders around the globe. These are cloud native insights. Hi, I'm stew Minimum and the host of Cloud Native Insights. And the threat that we've been pulling on with Cloud Native is that we needed to be able to take advantage of the innovation and agility that cloud in the ecosystem around it can bring, not just the location. It's It's not just the journey, but how do I take advantage of something today and keep being able to move for Happy to welcome back to the program one of our regulars and someone that I've had lots of discussion about? Cloud Cloud. Native Serverless So Cory Quinn, the Keith Cloud economists at the Duck Bill Group. Corey, always good to see you. Thanks for joining us. >>It is great to see me. And I always love having the opportunity to share my terrible opinions with people who then find themselves tarred by the mere association. And there's certainly no exception to use, too. Thanks for having me back. Although I question your judgment. >>Yeah, you know, what was that? Pandora's box. I open when I was like Hey, Corey, let's try you on video so much. And if people go out, they can look at your feet and you've spent lots of money on equipment. You have a nice looking set up. I guess you missed that one window of opportunity to get your hair cut in San Francisco during the pandemic. But be doesn't may Corey, why don't you give our audience just the update You went from a solo or mentor of the cloud? First you have a partner and a few other people, and you're now you've got economists. >>Yes, it comes down to separating out. What I'm doing with my nonsense from other people's other people's careers might very well be impacted by it considered tweet of mine. When you start having other clouds, economists and realize, okay, this is no longer just me we're talking about here. It forces a few changes. I was told one day that I would not be the chief economist. I smile drug put on a backlog item to order a new business cards because it's not like we're going to a lot of events these days, and from my perspective, things continue mostly a base. The back. To pretend people now means that there's things that my company does that I'm no longer directly involved with, which is a relief, that absolutely, ever. But it's been an interesting right. It's always strange. Is the number one thing that people who start businesses say is that if they knew what they were getting into, they'd never do it again. I'm starting to understand that. >>Yeah, well, Corey, as I mentioned you, and I have had lots of discussions about Cloud about multi Cloud server. Listen, like when you wrote an article talking about multi cloud is a worse practice. One of the things underneath is when I'm using cloud. I should really be able to leverage that cloud. One of the concerns that when you and I did a cube con and cloud native con is does multi cloud become a least common denominator? And a comment that I heard you say was if I'm just using cloud and the very basic services of it, you know, why don't I go to an AWS or an azure which have hundreds of services? Maybe I could just find something that is, you know, less expensive because I'm basically thinking of it as my server somewhere else. Which, of course, cloud is much more than so you do with a lot of very large companies that help them with their bills. What difference there differentiates the companies that get advantage from the cloud versus those that just kind of fit in another location, >>largely the stories that they tell themselves internally and how they wind up adapting to cloud. If the reason I got into my whole feel about why multi cloud is a worst practice is that of you best practices a sensible defaults, I view multi cloud as a ridiculous default. Sure, there are cases where it's important, and so I don't say I'm not suggesting for a second that those people who are deciding to go down that are necessarily making wrong decisions. But when you're building something from scratch with this idea toward taking a single workload and deploying it anywhere in almost every case, it's the wrong decision. Yes, there are going to be some workloads that are better suited. Other places. If we're talking about SAS, including that in the giant wrapper of cloud definition in terms of what was then, sure you would be nuts to wind of running on AWS and then decide you're also going to go with codecommit instead of git Hub. That's not something sensible people to use get up or got sick. But when I am suggesting, is that the idea of building absolutely every piece of infrastructure in a way that avoids any of the differentiated offerings that your primary cloud provider uses is just generally not a great occasionally you need to. But that's not the common case, and people are believing that it is >>well, and I'd like to dig a little deeper. Some of those differentiated services out there there are concerned, but some that said, You know, I think back to the past model. I want to build something. I can have it live ever anywhere. But those differentiated services are something that I should be able to get value out of it. So do you have any examples, or are there certain services that you have his favorites that you've seen customers use? And they say, Wow, it's it's something that is effective. It's something that is affordable, and I can get great value out of this because I didn't have to build it. And all of these hyper scaler have lots of engineers built, building lots of cool things. And I want to take advantage of that innovation. >>Sure, that's most of them. If we're being perfectly honest, there are remarkably few services that have no valid use cases for no customer anywhere. A lot of these solve an awful lot of pain that customers have. Dynamodb is a good example of this Is that one a lot of folks can relate to. It's super fast, charges you for what you use, and that is generally yet or a provision Great. But you don't have to worry about instances. You have to worry about scaling up or scaling down in the traditional sense. And that's great. The problem is, is great. How do I migrate off of this on to something else? Well, that's a good question. And if that is something that you need to at least have a theoretical exodus for, maybe Dynamo DV is the wrong service for you to pick your data store personally. If I have to build for a migration in mind on no sequel basis, I'll pick mongo DB every time, not because it's any easier to move it, but because it's so good at losing data, that'll have remarkably little bit left. Migrate. >>Yeah, Corey, of course. One of the things that you help customers with quite a bit is on the financial side of it. And one of the challenges if I moved from my environment and I move to the public cloud, is how do I take advantage not only of the capability to the cloud but the finances of the cloud. I've talked to many customers that when you modernize your pull things apart, maybe you start leveraging serverless capabilities. And if I tune things properly, I can have a much more affordable solution versus that. I just took my stuff and just shoved it all in the cloud kind of a traditional lift and shift. I might not have good economics. When I get to the cloud. What do you see along those lines? >>I'd say you're absolutely right with that assessment. If you are looking at hitting break even on your cloud migration in anything less than five years, it's probably wrong. The reason to go to Cloud is not to save money. There are edge cases where it makes sense, Sure, but by and large you're going to wind up spending longer in the in between state that you would believe eventually you're going to give up and call it hybrid game over. And at some point, if you stall long enough, you'll find that the cloud talent starts reaching out of your company. At which point that Okay, great. Now we're stuck in this scenario because no one wants to come in and finish the job is harder than we thought we landed. But it becomes this story of not being able to forecast what the economics are going to look like in advanced, largely because people don't understand where their workloads start and stop what the failure modes look like and how that's going to manifest itself in a cloud provider environment. That's why lift and shift is popular. People hate, lift and ship. It's a terrible direction to go in. Yeah, so are all the directions you can go in as far as migrating, short of burning it to the ground for insurance money and starting over, you've gotta have a way to get from where you are, where you're going. Otherwise, migration to be super simple. People with five weeks of experience and a certification consult that problem. It's but how do you take what's existing migrated end without causing massive outages or cost of fronts? It's harder than it looks. >>Well, okay, I remember Corey a few years ago when I talk to customers that were using AWS. Ah, common complaint was we had to dedicate an engineer just to look at the finances of what's happening. One of the early episodes I did of Cloud Native Insights talked to a company that was embracing this term called Been Ops. We have the finance team and the engineering team, not just looking back at the last quarter, but planning understanding what the engineering impacts were going forward so that the developers, while they don't need tohave all the spreadsheets and everything else, they understand what they architect and what the impact will be on the finance side. What are you hearing from your customers out there? What guidance do you give from an organizational standpoint as to how they make sure that their bill doesn't get ridiculous? >>Well, the term fin ops is a bit of a red herring in there because people immediately equate it back to cloud ability before their app. Geo acquisitions where the fin ops foundation vendors are not allowed to join except us, and it became effectively a marketing exercise that was incredibly poorly executed in sort of poisoned the well. Now the finance foundations been handed off to the Cloud Native Beauty Foundation slash Lennox Foundation. Maybe that's going to be rehabilitated, but we'll have to find out. One argument I made for a while was that developers do not need to know what the economic model in the cloud is going to be. As a general rule, I would stand by that. Now someone at your company needs to be able to have those conversations of understanding the ins and outs of various costs models. At some point you hit a point of complexity we're bringing in. Experts solve specific problems because it makes sense. But every developer you have does not need to sit with 3 to 5 days course understanding the economics of the cloud. Most of what they need to know if it's on a business card, it's on an index card or something small that is carplay and consult business and other index ramos. But the point is, is great. Big things cost more than small things. You're not charged for what you use your charger for. What you forget to turn off and being able to predict your usage model in advance is important and save money. Data transfers Weird. There are a bunch of edge cases, little slice it and ribbons, but inbound data transfer is generally free. Outbound, generally Austin arm and a leg and architect accordingly. But by and large for most development product teams, it's built something and see if it works first. We can always come back later and optimize costs as you wind up maturing the product offering. >>Yeah, Cory, it's some of those sharp edges I've love learning about in your newsletter or some of your online activities there, such as you talked about those egress fees. I know you've got a nice diagram that helps explain if you do this, it costs a lot of money. If you do this, it's gonna cost you. It cost you a lot less money. Um, you know, even something like serverless is something that in general looks like. It should be relatively expensive, but if you do something wrong, it could all of a sudden cost you a lot of money. You feel that companies are having a better understanding so that they don't just one month say, Oh my God, the CFO called us up because it was a big mistake or, you know, where are we along that maturation of cloud being a little bit more predictable? >>Unfortunately, no. Where near I'd like us to be it. The story that I think gets missed is that when you're month over, month span is 20% higher. Finance has a bunch of questions, but if they were somehow 20% lower, they have those same questions. They're trying to build out predictive models that align. They're not saying you're spending too much money, although by the time the issues of the game, yeah, it's instead help us understand and predict what's happening now. Server less is a great story around that, because you can tie charges back to individual transactions and that's great. Except find me a company that's doing that where the resulting bill isn't hilariously inconsequential. A cloud guru Before they bought Lennox, I can't get on stage and talk about this. It serverless kind of every year, but how? They're spending $600 a month in Lambda, and they have now well, over 100 employees. Yeah, no one cares about that money. You can trace the flow of capital all you want, but it grounds up to No one cares at some point that changes. But there's usually going to be far bigger fish to front with their case, I would imagine, given, you know, stream video, they're probably gonna have some data transfer questions that come into play long before we talk about their compute. >>Yeah, um, what else? Cory, when you look at the innovation in the cloud, are there things that common patterns that you see that customers are missing? Some of the opportunities there? How does the customers that you talk to, you know, other than reading your newsletter, talking Teoh their systems integrator or partner? How are they doing it? Keeping up with just the massive amount of change that happens out >>there. Get customers. AWS employees follow the newsletter specifically to figure out what's going on. We've long since passed a Rubicon where I can talk incredibly convincingly about services that don't really exist. And Amazon employees won't call me out on the joke that I've worked in there because what the world could ever say that and then single. It's well beyond any one person's ability to keep it all in their head. So what? We're increasingly seeing even one provider, let alone the rest. Their events are outpacing them and no one is keeping up. And now there's the persistent, never growing worry that there's something that just came out that could absolutely change your business for the better. And you'll never know about it because you're too busy trying to keep up with all the other number. Every release the cloud provider does is important to someone but none of its important everyone. >>Yeah, Corey, that's such a good point. When you've been using tools where you understand a certain way of doing things, how do you know that there's not a much better way of doing it? So, yeah, I guess the question is, you know, there's so much out there. How do people make sure that they're not getting left behind or, you know, keep their their their understanding of what might be able to be used >>the right answer. There, frankly, is to pick a direction and go in it. You can wind up in analysis paralysis issues very easily. And if you talk about what you've done on the Internet, the number one responsible to get immediately is someone suggesting an alternate approach you could have taken on day one. There is no one path forward for any six, and you can second guess yourself that the problem is that you have to pick a direction and go in it. Make sure it makes sense. Make sure the lines talk to people who know what's going on in the space and validate it out. But you're going to come up with a plan right head in that direction, I assure you, you are probably not the only person doing it unless you're using. Route 53 is a database. >>You know, it's an interesting thing. Corey used to be said that the best time to start a project was a year ago. But you can't turn back time, so you should start it now. I've been saying for the last few years the best time to start something would be a year from now, so you can take advantage of the latest things, but you can't wait a year, so you need to start now. So how how do you make sure you maintain flexibility but can keep moving projects moving forward? E think you touched on that with some of the analysis paralysis, Anything else as to just how do you make sure you're actually making the right bets and not going down? Some, you know, odd tangent that ends up being a debt. >>In my experience, the biggest problem people have with getting there is that they don't stop first to figure out alright a year from now. If this project has succeeded or failed, how will we know they wind up building these things and keeping them in place forever, despite the fact that cost more money to run than they bring in? In many cases, it's figure out what success looks like. Figure out what failure looks like. And if it isn't working, cut it. Otherwise, you're gonna wind up, went into this thing that you've got to support in perpetuity. One example of that one extreme is AWS. They famously never turn anything off. Google on the other spectrum turns things off as a core competence. Most folks wind up somewhere in the middle, but understand that right now between what? The day I start building this today and the time that this one's of working down the road. Well, great. There's a lot that needs to happen to make sure this is a viable business, and none of that is going to come down to, you know, build it on top of kubernetes. It's going to come down. Is its solving a problem for your customers? Are people they're people in to pay for the enhancement. Anytime you say yes to that project, you're saying no to a bunch of others. Opportunity Cost is a huge thing. >>Yeah, so it's such an important point, Cory. It's so fundamental when you look at what what cloud should enable is, I should be able to try more things. I should be able to fail fast on, and I shouldn't have to think about, you know, some cost nearly as much as I would in the past. We want to give you the final word as you look out in the cloud. Any you know, practices, guidelines, you can give practitioners out there as to make sure that they are taking advantage of the innovation that's available out there on being able to move their company just a little bit faster. >>Sure, by and large, for the practitioners out there, if you're rolling something out that you do not understand, that's usually a red flag. That's been my problem, to be blunt with kubernetes or an awful lot of the use cases that people effectively shove it into. What are you doing? What if the business problem you're trying to solve and you understand all of its different ways that it can fail in the ways that will help you succeed? In many cases, it is stupendous overkill for the scale of problem most people are throwing. It is not a multi cloud answer. It is not the way that everyone is going to be doing it or they'll make fun of you under resume. Remember, you just assume your own ego. In this sense, you need to deliver an outcome. You don't need to improve your own resume at the expense of your employer's business. One would hope, >>Well, Cory, always a pleasure catching up with you. Thanks so much for joining me on the cloud. Native insights. Thank you. Alright. Be sure to check out silicon angle dot com if you click on the cloud. There's a whole second for cloud Native insights on your host to minimum. And I look forward to hearing more from you and your cloud Native insights Yeah, yeah, yeah, yeah, yeah.

Published Date : Aug 14 2020

SUMMARY :

And the threat that we've been pulling on with Cloud Native is And I always love having the opportunity to share my terrible opinions with people Yeah, you know, what was that? When you start having other clouds, economists and realize, okay, this is no longer just me One of the concerns that when you and I did a cube is that of you best practices a sensible defaults, I view multi cloud as a ridiculous default. examples, or are there certain services that you have his favorites that you've maybe Dynamo DV is the wrong service for you to pick your data store personally. One of the things that you help customers with quite a bit is on the financial in the in between state that you would believe eventually you're going to give up and call it hybrid game over. One of the early episodes I did of Cloud Native Insights talked to a company that Well, the term fin ops is a bit of a red herring in there because people immediately equate it back to cloud but if you do something wrong, it could all of a sudden cost you a lot of money. I would imagine, given, you know, stream video, they're probably gonna have some data transfer questions that come into play AWS employees follow the newsletter specifically to figure out what's that they're not getting left behind or, you know, keep their their their understanding of what Make sure the lines talk to people who know what's going on in the space and validate it out. of the latest things, but you can't wait a year, so you need to start now. and none of that is going to come down to, you know, build it on top of kubernetes. on, and I shouldn't have to think about, you know, some cost nearly as much as I would in the past. of you under resume. And I look forward to hearing more from you and your cloud Native insights Yeah,

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
3QUANTITY

0.99+

20%QUANTITY

0.99+

Corey QuinnPERSON

0.99+

AWSORGANIZATION

0.99+

Palo AltoLOCATION

0.99+

San FranciscoLOCATION

0.99+

five weeksQUANTITY

0.99+

CoryPERSON

0.99+

AmazonORGANIZATION

0.99+

CoreyPERSON

0.99+

PandoraORGANIZATION

0.99+

Duck Bill GroupORGANIZATION

0.99+

last quarterDATE

0.99+

one monthQUANTITY

0.99+

sixQUANTITY

0.99+

less than five yearsQUANTITY

0.99+

Cube StudiosORGANIZATION

0.99+

over 100 employeesQUANTITY

0.99+

BostonLOCATION

0.98+

GoogleORGANIZATION

0.98+

5 daysQUANTITY

0.98+

OneQUANTITY

0.98+

singleQUANTITY

0.98+

FirstQUANTITY

0.98+

oneQUANTITY

0.98+

todayDATE

0.98+

hundreds of servicesQUANTITY

0.98+

LennoxORGANIZATION

0.98+

one providerQUANTITY

0.97+

Cloud CloudORGANIZATION

0.97+

Lennox FoundationORGANIZATION

0.96+

The Duckbill GroupORGANIZATION

0.96+

Cloud Native Beauty FoundationORGANIZATION

0.96+

DynamodbORGANIZATION

0.96+

a yearQUANTITY

0.95+

SASORGANIZATION

0.95+

Cory QuinnPERSON

0.95+

$600 a monthQUANTITY

0.95+

a year agoDATE

0.95+

One exampleQUANTITY

0.94+

pandemicEVENT

0.94+

one extremeQUANTITY

0.93+

Cloud Native InsightsORGANIZATION

0.93+

day oneQUANTITY

0.93+

Cloud NativeORGANIZATION

0.92+

firstQUANTITY

0.89+

one windowQUANTITY

0.88+

One argumentQUANTITY

0.88+

one personQUANTITY

0.87+

Been OpsORGANIZATION

0.85+

secondQUANTITY

0.81+

few years agoDATE

0.8+

muchQUANTITY

0.79+

one dayQUANTITY

0.78+

single workloadQUANTITY

0.75+

kQUANTITY

0.72+

LambdaTITLE

0.72+

last few yearsDATE

0.69+

egressORGANIZATION

0.68+

Keith CloudORGANIZATION

0.67+

NativeORGANIZATION

0.62+

yearQUANTITY

0.6+

stew MinimumPERSON

0.59+

a yearDATE

0.57+

RouteTITLE

0.56+

Dynamo DVORGANIZATION

0.54+

RubiconCOMMERCIAL_ITEM

0.51+

AustinLOCATION

0.45+

53ORGANIZATION

0.28+

Forrest Brazeal, A Cloud Guru | Cloud Native Insights


 

>> From theCUBE's studios in Palo Alto, in Boston, connecting with thought leaders around the globe. These are Cloud Native Insights. >> Hi, I'm Stu Miniman, the host of Cloud Native Insights. And when we talk about cloud native, we're talking about how do I take advantage of the agility in innovation, in cloud and the ecosystem out there? And a big question is if I'm a company that's not born in the cloud, or if I'm person that's not steeped in the knowledge of leveraging and using all of these wonderful tools out there, how do I get there? To help us dig into the people and company moving to cloud and adopt the use of these technologies, happy to welcome to the program, Forrest Brazeal. He is a senior manager with A Cloud Guru is his official title, but he is the cloud bard, as many people know in a bard, of course, an oral transition. He creates poems, he sings, he's got a book coming out to illustrate the cloud and really great to be able to talk to you Forrest. Thanks so much for joining us. >> Hey, it's great to be on the show, Stu, thanks for having me. >> All right, so first if you could just share a little bit about your background. So you joined A Cloud Guru, you know, relatively recently, I'd seen some of the cartoons and videos you've done in the past. You've got kind of a renaissance man look, you're not just a tech guy, as I said, you do have some of those musical pursuits also. So I'd love to hear a little of your background. >> Yeah, so I've been an engineer for a long time. I've been an engineer, been a manager of engineers, a consultant, and that's from, you know, startups ranging all the way up to the fortune 50. So I've seen a lot of enterprises in other companies at various stages of their cloud journey. From, you know, just trying to figure out how to get to the cloud out of the data center, all the way to being very cloud native. As you were saying in your intro, you know, figuring out how to build directly on cloud services. I'm very passionate about that. Very passionate about helping people figure out how to take that next step. Not to be a stucker, to get into a state where they are, but to figure out how to get, as I say up the Serverless ladder, right to that next stage of cloud native adoption. And I've realized that, you know, a lot of these technologies and a lot of these concepts, these practices are very abstract. And sometimes what helps the most is to put that in a format that people can engage with. And so I draw and I sometimes sing and I write all sorts of things just to try to help people understand. You know, even though these technologies and practices, these ideas are abstract, they don't have to be difficult, right? Everybody's got some intuitive understanding of why a doctor exists or why a lawyer exists. It's a little bit harder to get your head around, you know, why does a cloud architect exist? What do they build, right? And that's what I try to do with things like the book, The Read Aloud Cloud, that's coming out in just a couple of months. >> All right, so I love that, you know, helping companies understand these things because, you know, for so many years it was like, ah, well we need a mandate for the cloud. You know, cloud, cloud, cloud. When I started this, it was, you know, cloud is not a destination. There is how do we really take advantage of cloud? And there was one post that you wrote talking about lift and shift. And it was one of those things that we've seen for years, there's arguments of, you know, is lift and shift good, if it's bad? And of course the reality is sometimes lift and shift is needed, but it is step one of what you need to do, because if you're not taking advantage of the cloud, the rift reaches a certain point that you say, oh my gosh, maybe I'm not taking advantage of it, maybe the cost don't make sense, and therefore we scrambled and we pull things back and we celebrate repatriation, which to my mind was always, oh, geez, we kind of didn't understand it, we failed. And then we kind of went back to doing what we didn't want to do. So walk us through, if you could, we've even got an illustration of yours that we'll talk about, but you know, give us, you know, what is the proper way that people should think about lift and shift? >> Yeah, exactly. And to be clear, I'm not dissing lift and shift as a concept. It's very necessary in a lot of cases and you can reel off a bunch of reasons why lift and shift would be an important stepping stone in a cloud journey. And of course, that could be just, you know, I've got to get out of the data center, right? Because my lease is expiring or, you know, my servers are haunted and the whole thing is on fire. I've talked to people who, you know, have fireworks stored in their data center, literally that they're afraid are going to go off, right? The roof is leaking. It's time to get out of there and just get to someplace that's professionally managed. You could be using a lift and shift migration almost as like a financial engineering tactic to go from a CapEx to an OPEX model, right? And tie what you're doing a little bit more closely to what you're spending. There's several other reasons that you might choose to have lift and shift is that first stage you might want just to get your feet wet a little bit in cloud. You know, you might not have the confidence or the expertise in-house to build on fully cloud native services right now, you've got to go in and get your Ops teams hands-on right with the technologies and with the tooling so that they understand a little better, how to get you to that next step. But the really, really key thing is lift and shift is a phase you've got to get through it, you've got to keep innovating. And a lot of people don't realize that they think they can go to the cloud, pick up their servers, run them pretty much as they did in the data center, they can stop there, and they're going to get longterm benefits from cloud. And over time, that gets less and less true. Because as I say, once you move that first VM into EC2 or whatever the case may be, you've started a shot clock on your chances for success in the cloud. That clock is ticking cause your initial benefits are very front-loaded. You're potentially getting some initial cost wins as your, hopefully matching your usage a little bit better to what you're spending on infrastructure, right? You're potentially getting some time to learn and plan for version two of your cloud infrastructure. But the longer you stay in that lift and shift states, some dangers are going to start compounding. Because in the absence of a true cloud native strategy, your teams, your Ops teams, your governance teams, if you have those, right? They're going to continue to do things the way they did it in the data center. Because they don't have true SRE, they don't have true automation, they're going to build manual slow error-prone processes that are going to drag down your time to value your MTTR, all those operational metrics at you look at. You're going to see those costs winds actually start to evaporate because you know, you're still running that legacy monolith, You can't effectively charge back spend to different units inside of your business, you realize you're not getting that value, you thought you were running. You know, because you're running the cloud like a data center, and let's be honest, that's super expensive. And then unfortunately over time, and usually you start hitting this threshold 18 months, two years out, your best people, the experts who were bringing you to the cloud in the first place, they get disillusioned because they're not seeing the continued forward motion that they'd been led to believe was going to happen. And so they start moving on, you get brain drain, and now you've created this new legacy swamp of poor procedures and practices, the very thing that you were hoping to avoid. And so at that point, the negative side effects of the lift and shift have overwhelmed, the benefits you thought you were going to get. That's when you're lift and shift shot clock has expired. And that's what you want to avoid by continuing to innovate and continuing to refactor towards a true cloud native deployment. >> Yeah, well, again, I thought that the visual was excellent and it's so good to explain, you know, what is the journey we're going through? What are the decision points? You might look through some of these and say, oh, well, you know, these three definitely apply to my business, some of the others I might not be concerned about, but I can take that and apply it to what I'm doing. So that that's the company side of things. You know, Forrest, you're an AWS Serverless Hero, and also in your day job, your company helps people with the training. So let's talk about people. You know, when it comes to, you know, how do we get involved? One of the things I loved about the Serverless community from the early times that I met it, was, it seemed that the bar to enter was relatively low. So many of these things, it's like, ah, well, do I have the basic skill set? Do I understand how to get there? How do I actually get to where I need to be? And that so many people are hesitant to start that journey, cause it just seems so daunting. So what are you seeing out there? You know, give us the landscape in 2020 as to, you know, how we move forward. And I know you've got a project you've been doing called the cloud resume challenge. So, you know, definitely talk a little bit about that too. >> Yeah, for sure. So look, even going beyond 2020, I think the numbers I've heard, we're looking at potentially a hundred million software developers being added to the workforce over the course of the next decade and change. That's a lot of people who are going to have to interact with these services who are going to have to build and create value on top of cloud infrastructure. And so there's a huge need for us to continue to create abstractions and to create guided, you know, best practices and principles that will help people get where they need to be with as little unnecessary work as possible. And really that's a lot of what underlay the Serverless community and the ideas behind that. I've been involved in Serverless for a long time, going back to when I was, you know, building on Serverless inside of large companies early on in that revolution. And I've carried that forward now with my work as an AWS Serverless Hero, even the work that I'm doing at A Cloud Guru. And really the bar to entry, as you mentioned, is so low, because you're cutting out a lot of things that were seen as sort of gate keeping mechanisms in the past. You know, oh, if you haven't learned this underlying protocol or whatever, then you don't qualify as a real developer. Serverless turns out on its head and says, no, I'm providing you with abstractions that you're going to be able to build on top of. And you're going to be able to focus so much more of your energy on things that actually provide value for the business. And yeah, that kind of started as a very leading edge, early adopter thing, but we're seeing more and more even large enterprises. We're seeing that start to click and they're realizing, you know, wherever I can, wherever I'm not potentially constrained by legacy practices or other code bases, I do want to explore, you know, seeing how quickly I can turn a prototype around, how quickly I can A, B, C, D, E, F, G test something if you will, by spinning up these low cost prototypes in the cloud, right on infrastructure, that's just costing me fractions of a cent to run. There's some really, really compelling avenues that even larger businesses can explore. But taking it back to the individual for a second, Think about, you know, I'm in the middle of a global pandemic, okay? And potentially I'm looking for a career switch now more than ever, I'm thinking, you know, I'd like to get into development, I'd like to get into IT. And it's so close to me now. You look at these services out there, like Networkify which you and I were talking about before the break, right? Talking about how easy those technologies make it for someone to get out there and actually we do web development. But you still need someone to kind of step alongside you and say, you know, these are the things you need to care about, these are things that might be irrelevant. There's an explosion, almost like an infodemic, if you will, of information out there that makes it really hard for folks who are trying to actually skill up, and who're trying to make that transition into tech and into code. That's what A Cloud Guru does of course, which is that the company I work for. We've got about 2.2 million learners on our platform right now that we're helping to scale up and take that step toward the modern tech skills that they need to succeed. The cloud resume challenge, which you mentioned is something I've been doing kind of on the side. And that's a project-based approach that compliments a lot of the additional training that I was talking about. Where we say, you know, I'm going to give you a project, it's going to have some sort of spec based steps to it. So you're going to create a resume, but it's going to be deployed, you know, in the cloud, you're going to have to do some source control, some CICD, some, you know, all these other things that are going to be built into a basic DevOps competency. You're going to have to go away and do some Googling and open some tabs, in order to figure this out on your own cause the project doesn't tell you exactly how to do it. So you actually wind up with some kind of some pain. There's some failure involved there, and that of course is what makes the learning stick. And so we've got people working this on every continent now, we've had many people that have completed it, we've seen people get interviewed. We've seen people get hired coming out of a totally non tech background. So that's really exciting. And you know, those stories, aren't going to be unusual forward. We're going to see more and more of this, and really that's what these cloud abstracting technologies have allowed us to do. Probably it wouldn't be possible to do something like the cloud resume challenge 20 years ago, the barrier to entry with, you know, even just procuring the infrastructure you'd need to be successful in a reasonable amount of time, you know, was accessible to everybody, but now we're there. Those services are at your fingertips. You just need a little bit of guidance, a little bit of curation to get you down the right path. >> Well, yeah, it was actually, you know, what excited me when I first met the ACG team was the bar to entry was so low. In previous decades, you talk about, you know, how much time and how much money I needed to spend just to get some of these courses, even if they were online. And it was just order of magnitudes easier and, you know, built for that cloud environment that I can start I can pause, I have learning resources, and it's been really impressive to watch the expansion of the team there. I'm curious, when you look at, you know, certifications out there, when you look at the need for jobs out there, if I'm not, you know, if I'm in the tech industry, what are some of the things that you think that people should be learning moving forward to? Where would you recommend people start looking there? >> Yeah, absolutely. So I think one thing, a lot of people miss is, you know, it's a good idea to get started with technologies that are new, if you're new. Because let's be real, you can't ask for five years of experience in a technology that's only been around for 18 months. So it's really smart to major on something and get good at something that not a lot of people are good at yet. And you say, well, how do I know that technology is going to take off and succeed? Well, the fact of the matter is even if that specific technology doesn't, you still have a much greater understanding of the problem space, and you'll be right at the cutting edge, ready to jump in on, you know, whatever the next thing is. So I always recommend that people look at things like Serverless and the managed services that are coming out. Get really good at automating, you know, services on the major cloud providers pick AWS, Azure, GCP, right? And just make that your thing, don't specialize in too niche of an area, you know, especially if you're very new, but especially pick a cloud provider, get good at working with the basic services, you'll find that that sets you apart more than, for example, I don't know, going after a certification that's been around for 20 years, that tons and tons of people in the job market have, right? That doesn't necessarily set you apart as much as some of these modern skills do. So I definitely recommend that. >> Yeah, it's funny for us, actually, I laugh a little bit. You mentioned that you've been doing Serverless for a long time, and I'm like, well, okay, I remember sitting in the audience at 80 bus Re-invent when Lambda was unveiled, I think it was re:Invent 2014. So, you know, there's nobody out there that's been, "Oh, I've been doing this for a decade." We always laugh, when there's a job applications out there and say, oh, okay, you know, I want 10 years of a technology that's been around for five years. But yeah, maybe there's one other, a cartoon that you brought along talking about the difference between transition cloud, excuse me, cloud translation and cloud fluency. Maybe just walk through that difference. And especially people that have been in the industry for awhile, how do we make sure that we're actually embracing and understanding and moving to that cloud world, not just, you know, cloud washing? >> Yeah, that's a good word. You know, something that struck me, I think a bit of an epiphany that I had around the time that I started at A Cloud Guru and keep in mind, I'm coming out of years of having worked with these large organizations and try and help them figure out how to migrate to cloud. And what I had seen is there's a lot of these kind of central cloud teams, if you will, that get established right at the beginning of an organization's cloud adoption. And that's a well known pattern, you know, this "cloud center of excellence", if you will, that people establish. A lot of times, those are small teams. You take your best cloud people and you say, okay, you define the standards and the processes that are going to get us to cloud, and they do that. And then they're shocked when nobody adopts the standards, right? And the migration sort of stalls, and they're not having the impact that they expected to have. And what turns out is going on is just having that small group of people who understands cloud, surrounded by this huge legacy, diaspora of legacy, you know, product and engineering teams that don't speak the language of cloud, if you will. Means that anytime you want to innovate, or anytime you want to make a move, you've got to go through this process of translation. You've got to go to those legacy teams who were saying, what's EC2 instance again? You know, how do you spell S3? I thought that I wanted to log into the AWS Console, but this access and secret key, isn't going into my password box, right? You know, they have that low level of competency. And so you're constantly having to explain everything you're going back and forth, and that of course leads to kind of less sophisticated architectures that leads to poor outcomes, and it takes you much longer to get where you want to go. That's that process of cloud translation. That's an anti-pattern. So instead of that, what we try to advocate for is what we call cloud fluency. Just like with any other language you want your entire organization as much as possible to speak the language of cloud at some baseline level. We do that through a couple of things. Of course, obviously through training and certification, cloud certifications can be a great proxy to measure how well your organization's cloud competency is improving. But also through taking those cloud experts, those central experts that previously were kind of in their ivory tower doing their own thing and embed them as much as you can in a roving fashion with these legacy product teams and help them to improve, right? Sort of teach them to fish so that you're not putting all the weight on that central team to be the only experts. Because that doesn't scale, those people are going to burn out. They're going to get overwhelmed with support tickets, we see that over and over again. So you want to empower those teams. And we want to actually talk a little bit less about a cloud center of excellence sometimes, and a little more about a cloud center of enablement, right? Where we want to, instead of knowing the most about cloud, we want to show the most about cloud to those other teams. That's a sustainable pattern for success. That's what we try to do through A Cloud Guru, and that's what I try to advocate for individually, wherever I can, because I've seen people burnt out. I don't want that to happen. >> Yeah, for those of us that have been through a few of these waves here, it's something that you're right, you need to actually be involved in embracing these technologies. You don't have a center for internet usage anymore. If you think about, you know, everybody now for the most part has used the internet, understand some of pieces, it needs to be the same way when it comes to cloud. It just becomes the underlying substrate and, you know, bring forward the innovation and agility that people are looking for. All right, Forrest, last thing we talked about, you've got a book coming out a little bit later this year, The Read Aloud Cloud, give us the quick thing, you know, love, it's visual, is very accessible and definitely looking forward to hearing about that. >> Yes, yes, exciting. So it'll be out in September from Wiley. And basically you've seen a couple of the cartoons over the course of this time here. But, you know, I've been drawing for a long time trying to help people get a sense for what the cloud is and in a way that they can understand and get a grasp on. And so what The Read Aloud Cloud is, it's the history and practice of cloud computing. And it takes you from the mainframe days through artificial intelligence. And along the way, we talk about the basics of cloud architecture, we talk about security, We talk about resilience and all those important things. But it's written and drawn in a way that can be accessible even to a nontechnical person. So the person who's never been able to understand what it is that you do. And I include, you know, potentially your CEO in that conversation, right? This is a book you can hand to them that you can put on your desk, it'll give you a chuckle. But I think there's actually some really strong ability for you to gain actually a concrete visual understanding those really abstract terminologies that float around with cloud. Again, what we're doing is not necessarily complicated, it's just really abstract, it's really arcane. So let's put it in a format where we can get our heads around and hopefully have a good laugh while we're doing it. That's what The Read Aloud Cloud is, and you can check that out, wherever books are sold. >> All right, well Forrest Brazeal. Thank you so much for joining us, real pleasure talking with you. And absolutely we need to make sure that "cloud" becomes as ubiquitous as computers and the internet have before us. Really pleasure chatting with you, thanks so much for joining. >> Awesome, thanks so much Stu, it's great to be here. All right, and I'm Stu Miniman, looking forward to hearing more about your Cloud Native Insights. (bright upbeat music)

Published Date : Aug 7 2020

SUMMARY :

leaders around the globe. to talk to you Forrest. Hey, it's great to be on the show, Stu, you know, relatively recently, And I've realized that, you know, All right, so I love that, you know, I've talked to people who, you know, it seemed that the bar to the barrier to entry with, you know, the bar to entry was so low. ready to jump in on, you know, and say, oh, okay, you know, to get where you want to go. give us the quick thing, you know, And I include, you know, and the internet have before us. it's great to be here.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
Palo AltoLOCATION

0.99+

Stu MinimanPERSON

0.99+

10 yearsQUANTITY

0.99+

Forrest BrazealPERSON

0.99+

five yearsQUANTITY

0.99+

2020DATE

0.99+

AWSORGANIZATION

0.99+

SeptemberDATE

0.99+

18 monthsQUANTITY

0.99+

20 yearsQUANTITY

0.99+

two yearsQUANTITY

0.99+

BostonLOCATION

0.99+

StuPERSON

0.99+

NetworkifyORGANIZATION

0.99+

The Read Aloud CloudTITLE

0.99+

firstQUANTITY

0.99+

OneQUANTITY

0.98+

ForrestPERSON

0.98+

oneQUANTITY

0.98+

20 years agoDATE

0.97+

ACGORGANIZATION

0.97+

EC2TITLE

0.96+

theCUBEORGANIZATION

0.96+

A Cloud GuruORGANIZATION

0.96+

next decadeDATE

0.96+

one postQUANTITY

0.95+

first stageQUANTITY

0.95+

threeQUANTITY

0.93+

LambdaORGANIZATION

0.92+

later this yearDATE

0.92+

ServerlessORGANIZATION

0.91+

about 2.2 millionQUANTITY

0.91+

one thingQUANTITY

0.89+

S3TITLE

0.87+

hundred million softwareQUANTITY

0.84+

step oneQUANTITY

0.84+

CapExORGANIZATION

0.83+

version twoOTHER

0.82+

OPEXORGANIZATION

0.82+

a decadeQUANTITY

0.79+

Cloud Native InsightsORGANIZATION

0.77+

A Cloud GuruORGANIZATION

0.76+

Cloud NativeTITLE

0.74+

first placeQUANTITY

0.74+

pandemicEVENT

0.74+

tons andQUANTITY

0.71+

Cloud GuruTITLE

0.71+

AWS Serverless HeroORGANIZATION

0.66+

Invent 2014EVENT

0.65+

AzureORGANIZATION

0.65+

yearsQUANTITY

0.64+

Cloud NativeORGANIZATION

0.61+

GCPORGANIZATION

0.61+

ServerlessCOMMERCIAL_ITEM

0.6+

Read AloudTITLE

0.59+

secondQUANTITY

0.59+

previousDATE

0.58+

WileyPERSON

0.55+

tonsQUANTITY

0.54+

80 bus Re-inventEVENT

0.53+

centQUANTITY

0.52+

ConsoleCOMMERCIAL_ITEM

0.49+

fortune 50TITLE

0.39+

ServerlessTITLE

0.38+

HeroORGANIZATION

0.36+

Matt Biilmann & Chris Bach, Netlify | Cloud Native Insights


 

>> Narrator: From theCUBE Studios in Palo Alto in Boston, connecting with thought leaders all around the world, this is a CUBE conversation. >> Hi, I'm Stu Miniman, the host of Cloud Native Insights. And when we kicked off this program, Cloud Native Insights, we wanted to talk about the innovation and agility that's happening, not just Cloud as a location. We're going to draw down a little bit into one of the very important pieces of a company and that's their websites and their applications, that live in that environment. And of course, that comes from a lot of changes over the years. Any of us that have been in tech for a couple of decades have worked from the early days, to of course today's multimedia globally distributed environment and everyone during the global pandemic, of course, has been (indistinct) straining their use of the internet. So really excited to welcome to the program the two co-founders of Netlify. I have Matt Biilmann, who is the CEO, and his co-founder Christian Bach, who is the president both of Netlify really the company behind Jamstack, which we're going to explain and talk about a bit. Matt and Chris, thank you so much for joining us. >> Thanks for having us. >> Thank you for having us >> All right so, let's start with just some of the basics. I expect that some of our audience is not familiar with Jamstack. You do a quick Google search and it's JavaScript, its APIs, its markup. And you say, okay, I understand what a bunch of that means. But, yeah, if you could give us kind of a compare contrast to what web development was before and how Jamstack's really helping to revolutionize what's happening in this space. >> Yes, so for many years, we built websites and web applications with an application based architecture, where every website or every application would be this monolithic application with typically like a load balancer, a set of web servers, application servers, and that database and every request through a page would go through this whole stack it would pass through the application layer, talk to the database, fetch template, merge data and template, build HTML on the fly and send it back to the user. And basically what we saw happening and what's been happening with the Jamstack is this decoupling of the actual front-end presentation layer of the websites and web applications and then the back-end layer. And the advantages there is that if you can really pre-build the front-end application layer, you can take the actual HTML, or an application shell and distribute it across a globally distributed network, you can get it into the hands of the user's browser very quickly. And then the back end, what we've seen happening there is that it's split up to all these different APIs and services you no longer have your one monolithic back end you have all these different services. Where some of your own but a lot of them are other people's services like Stripe or Twilio or Algolia or Contentful. So we've seen this shift to this architecture, where we're considered in a way that the stack has moved up a little from the old tooling where something like the LAMP stack would be common in really naming the programming language, the specific web server, the Linux server, the operating system, and so on right? And then up to a level where it's really about getting an application into the browser, using JavaScript as the runtime and talking to this whole new economy of APIs and services. >> Yeah, Chris I wonder if you could bring us inside your customers and the companies that you talk to. I think about for the longest time it was, maybe I just outsource my web development, but website is one of those key components that I share my value, I share what's going on, I want to be able to change it pretty often and there's so much more that I can do today than I could have done 10 years ago. We've watched that mark. So, help us understand, what skill sets do people need to have? what type of companies are using Jamstack? And, bring in if you can, Netlify. How is this a business and not just, an open source standards movement, that's helping to revolutionize what's happening? >> Absolutely, I mean, First of all, people using this and companies use this is extremely wide. Wide vertical, right? Its very horizontal. This is anyone with a digital property basically, right? I think what we've seen all the time is that, that we have a lot more channels than we used to have, right? So we started off just maybe having the one dot com, right? With limited functionality. And today, you have a multiple channels, right? You have the landing pages, you have the domains, you have lots of activities online. You have mobile apps and commerce is often a big part of it, and I would say especially the last few months, there's a lot of people that had the digital convergence points as one of many. And now it's the only ones, right? So I think it's become extremely important. I also think that when you look at your web infrastructure in general, it has been very complex, right? And you need a lot of different people, right? And you need to maintain staging environments, production lines, development environments. You need to, have a wide set of skills to maintain these things, right? And if a web developer wanted to do a lot of things, right? They have to go and tap DevOps and so on on the shoulder, right? And I think what the Jamstack is about saying, hey, you can get so much further as a web developer. Now, if you take the modern built tools, you can take the Git workflows, and you wrap around the browser that has become a full-fledged operating system and the API economy as Matt was just talking about. You have these workflows, or you potentially have these workflows, where you can get so much further, right? And that's very much Netlify submission. So Netlify saw this opportunity of decoupling the front end from the back end of the building from the hosting of creating an approach to making websites that would be many times faster, 'cause you have multiple points of origin and you don't feel fredurous. It's many times safer. There's not that huge surface area of attack. It's much more scalable, and so on. It was sort of a win-win-win. But the problem was, there was no viable workflow. If you take a traditional CDN, and you put it in, it doesn't matter really, if it's one or the other. As good as they (indistinct) services, they're all meant to sit in front of an origin, right? They're meant to buffer something. And if you have the gems, there's no origin in that way, right? The network in itself has to be an origin so it has to be architectured quite differently. And then there's a lot of things around CDCI and how you server lists and so on. That all had to be sort of re-merged . And Netlify is that glue, it is that platform that takes you from local development all the way out to edge nodes. But allows you to mix and match any tool. So it's not program independent. So you can say, well, we use a build tool, and that's PHP or Ruby or JavaScript, the react or Next or whatever it might be, right? And we use these APIs for this server, for this property. Over here we have a commerce site. Over here, we have a dotcom, that needs a huge enterprise CMS with tons of stakeholders. But the thing is that all of those now becomes something that plugs into your website. Rather than have to drive the website itself. And that's sort of frees up the silos. So when we see people using Netlify, we have companies using Netlify. Big Fitness Company, for example, that own fitness company that uses us for developer documentation, or their marketing sites, but also for their dotcom. But even if you go to the equipment that people have at home, and you log in, that's actually using some very nifty identity and remote based access control for Netlify and if you watch the video there, it's also going through a Netlify player, all right? We have fast food chains that has their dotcom and their marketing sites, but also the kiosks down in the store like the menus, the screens there. Rather than being an old Windows NT server running some .NET application in a dusty corner, why not have it like that? And so, both the category but also Netlify sort of brings in a solution and because it's decoupled from all those architectural choices, that means that you can now use the solution in a much, much wider setting. And we were sort of first to market doing this. They get serverless approach where you just push your serverless functions to get better Netlify. First Feature Deploy Previews Were invented by us and so on. So the Jamstack is an extremely wide fundamental architectural approach that matches basically anyone that wants to build web properties. Netlify is the segnostic wide platform that just makes it possible. >> Yeah, good Chris actually, I saw the Peloton use case up on the website and you're right, a very different experience rather than I bring my device, is it synced? Does it work with it? Really integrates those solutions. And you just brought up serverless, which is actually how I got connected to talk in Netlify. So, Matt, sorry, I think you wanted to jump in there but I was wondering if you could help us. I've looked at serverless and what the promise of serverless of course, is that I don't need to think about that underlying infrastructure. I just like developers build our applications. Well, feels like that's really the same mission that you have. And they're serverless is a piece of your story. So, maybe explain (indistinct) that out a little for us. >> Absolutely, I think it ties in, right? Basically, what we saw just from a architectural perspective was this approach of really decoupling front end and back end and so on and working in a new way that gave a lot of benefits to the inducers in performance and security and so on right? But on the other hand, early on, what we saw was that to adopt that approach, like developers had to deal with lot of different moving pieces like CICD, CDN. What to do about the API endpoints that didn't need to be dynamic, and so on. And as Netlify, what we saw was that we could give one intro and workflow for all of this and make it extremely easy for developers to work with this thing. And serverless plays a really important piece there, right? Because when Amazon pioneered AWS Lambda and took it to the world, right? I think the promise also for the front-end web developers of being able to simply write code and then not have to worry at all about where is it actually running? How are we scaling it? How are we operating it and so on, right? That's a really powerful promise, right? But at the same time, in the same way, what we saw earlier on was that for a front-end team to actually adopt serverless functions as part of the Jamstack, it introduced another level of complexity of now having to manage your serverless functions independent from your front end figuring out API Gateway endpoints for every one of them. And how about deployment pipeline for your functions layer versus deployment pipelines for the actual front end layer that's supposed to talk to those front ends. How about staging environments versus to production environments? How do you manage all that, right? So we saw that there was this inherent incredible potential, but also a lot of complexity, right? And as Netlify we saw that if we could give front end developers a web developers in general, an ene-to-end workflow, where they can work both with the front-end framework, write the code that will get deployed into the browser, but also just have a folder where they can write this serverless functions and then know that Netlify will take care of all of the wiring, right? When you open a pull request and get with new function we'll give you a URL on our globally distributed CDN where you can view both the whole front end, but also the function and sidestep sort of all of the complexities of linking together API Gateways, to functions of managing CICD pipelines and test environments and so on. And in the end, the serverless functions starts becoming a really important part of this Jamstack approach, right? Because you have this world where you have a front end that's often talking to many different APIs and services where again, some of your own and some other people's services. But really often you need some place to glue those together or to build your own custom API endpoint that talks to a couple of them and it has access to server site secrets and so on, right? And this idea of not having to suddenly operate and manage a whole set of servers and infrastructure just for that part of it, but simply just writing the code and then knowing, that you don't have to worry about the operation scalability or anything around that code. That's a really powerful paradigm. >> Yeah, that's one of the real challenges of the Cloud as you talk about the Paradox of Choice. There's so many ways to do things. Not necessarily... It's simple anybody... I was a blogger for many years and it was like, well, I'll just use the self-hosted WordPress, because I don't want to have to worry about that piece of it. Matt, I watched it you did a presentation talking about if I wanted to do WordPress hosted in a AWS that absolutely is not simple. I heard a podcast from one of your board members, Tom Preston Werner, talking about we need to be more opinionated. We need to be able to give more guidance to developers, maybe Chris if you could, how are we when the proliferation of choice, keeps increasing, making sure that people can... How do I make that decision tree? And how do we try to keep it simple? >> Absolutely, I mean, and I actually think that, that's a super relevant question, because you have a lot of choice as a web developer today. Front-end developers used to cut out Photoshop files and turn them into HTML, right? Now with the new advanced markup, and they have all these frameworks and flavors of JavaScript to choose between and there's these powerful build tools, And all those workflows and the browser can do everything you can imagine, right? And so yeah, there is a lot of choice out there, right? And I think, for Netlify what's extremely important is that we are opinionated in the right places. And so when it comes to, for example, a front-end tool and built tools and these things that web developers often face with having to choose between. Our role is to make it as simple as possible to use any of them. But also give you the opportunity of saying, well, this new paradigm allows you to actually mix and match, right? It allows you to use this tool for this property and this tool for this property and gives you a ton of flexibility. But still, come under one roof of a platform like Netlify. And I think that is very powerful. And so we also don't want to choose for you, we want to inform your choices and we want to make it as easy as possible to go and say, hey, these are my needs, what direction should I be going? And of course, we work with enterprise clients, so on migration services, and so on, right? And where we help them a lot with that. But if we locked down on a single flavor, or a single bill tool or a single front end framework, then we also limit the application of what we bring to market and we want to remain a little more open-ended there. But I think there's a lot complexity, a platform like Netlify is all about simplification. So all that wiring that Matt just mentioned, that at least goes, right? You don't spend hours configuring bondage caching and trying to find those edge cases, it just works. And that's a huge game changer for a lot of people, right? But there's definitely parts of the ecosystem that has a lot of choice. And we do our best to inform. And I think, under hand holding part, adjacent to that is the story of, well, do we then start using content management systems? Is this a whole new? Is it out with the old and in with the new? And I would say, you still have a lot of those needs, right? You still have non-technical people, for example, that needs to be able to update and create moves and content, and so on, right? And create content. And so you very often will need and an E-commerce solution or content management systems and so on. But what we're seeing there, is that we're speaking basically with every single major CMS out there. That are saying we're working on a headless system, or we already have a headless version, or we just gone full headless, that means that we work decoupled. So we don't no longer need to build the site. But we just provide like an independent source of content. And then it plugs into a platform like Netlify. So that can bring a lot of simplicity. And now you just have to maintain your content, but you don't have to worry about all the different environments and what is up to date and how does some of the infrastructure look like you press a button that commits to get a default preview, and it looks the same everywhere. >> I'm curious, what impact the current global pandemic has had on Netlify, and your customers. I saw you've got a COVID tracking project that you've done. But also now just there's different considerations when I think about what services I need to access from the web and what kind of connectivity the ultimate end user would have. So, what learnings have you had? What's involved there? >> In, obviously we, it depends a lot on, as Chris mentioned, right? The game circus is adopted horizontally across all kinds of areas and businesses and so on, right? So, we've of course seen businesses in sectors that are having a hard time and on the other hand, we've seen businesses and sectors that are exploding, right? We did immediately when the lockdown started happening and the pandemic started happening we set aside like a free plan for projects working in the space of tackling the information sharing around COVID and finding solutions and so on. And that was really interesting to see you mention the COVID tracking project, right? Which was a project like built a short time by small group of distributed incredibly talented front end developers and scientists and so on, right? And I think it was interesting to see that, how the Jamstack and our tooling and so on also really made it possible for them to build as a small distributed team the set of data information and tooling to a global audience, right? Seeing huge traffic peaks at time and just knowing that their architecture and our infrastructure could handle it for them. >> All right. Chris, I've got one, a little bit off to the side here. When I look at what Netlify is doing, you talk about having an open and independent web. And while we are fully supportive of that, we're a little concerned sometimes. If you look at what's happening across the globe, there's a lot of discussions. Will the internet actually fragment? Will certain countries wall off certain environments? Any concerns there? What do you look at? What are you hearing from your customers when you talk about that mission? >> It's one of the big challenges of all time, right? I think we all maybe took for given the Internet as the standard it became right? The way that you can publish without permission is pretty magnificent, right? And it would be indescribably painful for civilization if we lost that, right? And I think fragmentation is something that we all have to sort of worry around. From the way we see it, is that the web, the traditional monolithic approach, right? To which led to as a web that wasn't secure enough and wasn't scalable enough and wasn't performing enough and that's, for example, what opened the door for mobile applications, right? Where it just didn't make sense to pull in the UI every time you turn the page. So we ended up with a form that's it. We prebuilt the application, you download it, and then you speak to service for anything then atmosphere come up with it, right. And that makes perfect sense. That's basically the same architecture that we're bringing to the web a very large scale. Of course, the problem is that now there are gatekeepers there, right? There people, you have to ask for permission to publish and so on. And, and there are other attempts to say, "Hey, we need a performing web." And there's a very big players out there that say, "Let's come over and just..." Do we even need to call it the Internet? Can we just call it our company website? I'm not going to name any names here, right? But leading down, it's what we've called walled gardens, that are great for absolutely no one except for the company. And what we believe is that if you have a web that is secure and is scalable, and it's performant enough to justify at least the architecture maintaining and not having to run into any walled gardens and still say no, you don't need to use a handful of commercial platforms if you want to be heard rather than have your own web properties on your own custom domains, right? I think that's the part of the open independent viable web that we're fighting for. Basically, one that adopts and keeps adopting an architecture that is something that levels the playing field. And then they would also say, why Netlify? I mean, a few years before we started, like, try configuring your own CDN. And like that was reserved for the very, very large tech players. Now you can comment, you can literally click a button on Netlify, you get custom domain and ACS post process site that's globally distributed, automatically integrated into get. And that's on the premium plan. And so as a startup, you can level set together with everyone else and be available widely across the globe without performance issues, immediately. And so in that way, I'm also seeing that's a democrat sensation of performance, right? That means that, that's great. And for places where you see developing economies, where you often have brownouts, where you often can't depend on having viable services and is locally and so on, this idea of having he cover that and having something that's just automatically, you know what, don't even worry about it, because it's already ready to go in all these packets all around the world. That's a huge game changer. That's actually what we see a lot of adoption of the gems they can never find in those places as well. Guess that's just such a promise to the architecture. So, I hear what you're saying and I'm also very concerned about a fragmented web for political reasons as well across the globe. And from our angle, the way we fight for this is to make sure that it retains using an architecture that makes it accessible for me. >> Yeah, I heard many years ago, a friend of mine said, if you're a technologist it means that in general you are a technology optimist, which I definitely try to be. So, I love Chris how you've just brought in some of the potential opportunity Matt, I want to give you just... People out there they hear like oh, 5G is coming, it's going to completely change the world. Anything that you're seeing on your side as to real opportunities that we will see, just a step function in what your company is using. Jamstack, partnering with Netlify in your ecosystem. What are some of the early things that you see that are exciting you down the line for this? >> Part of it is simply like the whole ecosystem around the gem stalk growing up and the tooling, the APIs, the frameworks available around it, and the level of innovation that's triggered. And especially how it's triggering in... Especially how we're seeing like the potential for small, distributed teams to work together and build things with a global impact in a short time. And I remember a couple of years ago, we did a hackathon with together with freeCodeCamp. And of course, like since it was with freeCodeCamp, it was mostly like teams were mostly fairly new to programming and so on, right? It was pretty amazing to see what over a weekend with this architecture and with this tooling, with the vendors that were present there and helping out and so on, what the small teams could actually get done in a weekend, right? Like I remember the winning team had an app where the whole room would see an image on the main stage screen and then on their phone, try to place that image on the map and you would real time see how people ranked, how close they got and get a winner and so on, right? And that was all just from combining APIs and tooling, like history, like Netlify, like Honor Bee, like Google Maps, and so on, right? And I think, in some way we shouldn't forget just how much this kind of ecosystem of readily available APIs and services around this front end stake. It's allowing people to build things that years ago would have taken a very big team probably like a year to build, and suddenly you can have a relatively small group of relatively new programmers built something really impressive, right? So I think that's a trend we'll see continue accelerating And me and Chris are personally involved in advising and helping out a lot of these new startups in the space that are trying to bring new tooling to the world that makes more and more of these things possible and accessible. >> Well, Chris and Matt, I really appreciate you both joining such an exciting space. Talk about the cloud, agility and innovation, such a robust ecosystem. Thank you so much for joining. >> Thanks for having us. >> Thanks for having us. >> And I'm Stu Miniman. Thank you for joining and look forward to hearing more about your CUBE insight. (soft music)

Published Date : Jul 31 2020

SUMMARY :

leaders all around the world, and everyone during the And you say, okay, I understand is that if you can really companies that you talk to. And if you have the gems, is that I don't need to that you don't have to worry And how do we try to keep it simple? and it looks the same everywhere. I need to access from the web and the pandemic started happening What are you hearing from your customers and then you speak to service that are exciting you and the level of innovation I really appreciate you both joining Thank you for joining and

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
MattPERSON

0.99+

ChrisPERSON

0.99+

Matt BiilmannPERSON

0.99+

Christian BachPERSON

0.99+

Chris BachPERSON

0.99+

Stu MinimanPERSON

0.99+

Palo AltoLOCATION

0.99+

NetlifyORGANIZATION

0.99+

AmazonORGANIZATION

0.99+

Tom Preston WernerPERSON

0.99+

RubyTITLE

0.99+

freeCodeCampTITLE

0.99+

JavaScriptTITLE

0.99+

PHPTITLE

0.99+

AWSORGANIZATION

0.99+

TwilioORGANIZATION

0.99+

bothQUANTITY

0.98+

PhotoshopTITLE

0.98+

todayDATE

0.98+

10 years agoDATE

0.97+

BostonLOCATION

0.97+

JamstackPERSON

0.97+

oneQUANTITY

0.97+

StripeORGANIZATION

0.97+

firstQUANTITY

0.96+

Google MapsTITLE

0.96+

GitTITLE

0.96+

LinuxTITLE

0.95+

Big Fitness CompanyORGANIZATION

0.94+

a yearQUANTITY

0.94+

AlgoliaORGANIZATION

0.94+

two co-foundersQUANTITY

0.94+

ContentfulORGANIZATION

0.94+

.NETTITLE

0.93+

Windows NTTITLE

0.92+

LAMPTITLE

0.91+

DevOpsTITLE

0.91+

theCUBE StudiosORGANIZATION

0.91+

dotcomORGANIZATION

0.9+

pandemicEVENT

0.9+

COVIDOTHER

0.89+

single flavorQUANTITY

0.88+

CloudTITLE

0.87+

last few monthsDATE

0.85+

single bill toolQUANTITY

0.85+

FirstQUANTITY

0.84+

single frontQUANTITY

0.83+

Dan Hubbard, Lacework | Cloud Native Insights


 

>> Narrator: From theCUBE Studios in Palo Alto in Boston, connecting with thought leaders around the globe, these are Cloud Native Insights. >> Hi, I'm Stu Miniman the host of cloud native insights. And when we started this weekly program, we look at Cloud Native and you know, what does that mean? And of course, one of the most important topics in IT coming into 2020 was security. And once the global pandemic hit, security went from the top issue to oh my gosh, it's even more important. I've said a few times on the program while most people are working from home, it did not mean that the bad actors went home, we've actually seen an increase in the need for security. So really happy to be able to dig in and talk about what is Cloud Native security, and what should that mean to users? And to help me dig into this important topic, happy to welcome back to the program one of our CUBE alumni Dan Hubbard, he is the CEO of Lacework. Dan thanks so much for joining us. >> Thanks Stu. Happy to be here. >> Alright, so we don't want to argue too much on the Cloud Native term, I agree with you and your team. It's a term that like cloud before, it doesn't necessarily have a lot of meaning. But when we talk about modernization, we talked about customers leveraging the opportunity in innovation and cloud security of course is super important. You know most of us probably remember back, you go back a few years and it's like, "Oh well I adopt cloud. "It's secure, right? "I mean, it should just be built into my platform. "And I should have to think about that." Well, I don't think there's anybody out there at least hopefully there's not anybody out there that thinks that anything that I go to will just be inherently fully secure. So give us a little bit if you would, you know where you see us here in 2020 security's a complex landscape. What are you seeing? >> Yeah, so you know a lot of people as you said, used to talk about what's called the shared responsibility model, which was the cloud provider is responsible for a bunch of things. Like the physical access to the data center, the network, the hypervisor and you know that the core file system and operating system and then you're responsible for everything else that you could configure. But there's something that's not talked about as much. And that's kind of the shared irresponsibility model that's happening within companies where developers are saying they're not responsible for security saying that they're moving too fast. And so what we are seeing is that you know, as people migrate to the cloud or of course are born in the cloud, this notion of DevSecOps, or you know SecDevOps whatever you want to call it, is really about the architecture and the organization. It's not just about technology, and it's not just about people. And it's more about layer seven and eight, than it is about layer one to three. And so there's a bunch of trends that we're seeing in successful companies and customers and prospects will be seeing the market around how do they get to that level of cooperation between the security and the developers in the operation teams? >> Yeah Dan, first of all fully agree with what you're saying. I know when I go to like serverless.com they've got everybody chanting that security is everyone's responsibility. You know I think back to DevOps as a trend, when I read the Phoenix project it was, oh hey, the security is not something that you do bolt on, we're looking at after it's something that you need to shift into everyone thinking about it. Security is just going to be baked in along the process all the way. So the DevOps fail us when it comes to security, why do we need DevSecOps? You know why are you know as you say seven and eight the you know, political and organizational challenges still so much of an issue you know, decades into this discussion? >> Yeah. You know I think there's a few moving parts here and kind of post COVID is even more interesting is that companies have incredibly strategic initiatives to build applications that are core to their business. And in post COVID it's almost existential to their business. If you think of you know, markets like retail and hospitality and restaurants you know, they have to figure out how to digitize and how to deliver their business without potentially physical you know, access to two locations. So as that speed has happened, some of the safety has been left behind. And it's easy to say you have to kind of you know, one of our mantras is to run with speed and safety. But it's kind of hard to run with scissors you know, and be safe at the same time. So some of it is just speed. And the other is that unfortunately, the security people in many ways and the security products and a lot of the security solutions that are out there, the incumbents if you will, are trying to deliver their current solution in a cloud way. So they're doing sometimes it's called Cloud built or you know what I call Cloud washing and they're delivering a system that's not applicable to the modern infrastructure in the modern way that developers are building. So then you have a clash between the teams of like, "Hey I want to do this." And then I'd be like, "No you can't do that get out of our way. "This is strategic to the business." So a lot of it has just been you know, kind of combination of all those factors. >> Alright so Dan, we'll go back to Cloud Native security, you talked about sometimes people are Cloud washing, or they're just taking what they had putting it in the cloud. Sometimes it's just, oh hey we've got a SaaS model on this. Other times I hear cloud native security, and it just means hey I've got some hooks into Containers or Kubernetes. What does modern security look like? Help us understand a little bit. You mentioned some of the you know, legacy vendors what they're doing. I see lots of new security startups, some in you know specifically in that, you know, Kubernetes space. There's already been some acquisitions there. So you know, what do you see out there? You know what's good, what's bad in the trends that you're seeing? >> Yeah so I think the one thing that we really believe is that this is such a large problem that you have to be 100% focused on it. You know if you're doing this, you know, securing your infrastructure and securing your modern applications, and doing other parts of the business whether it's you know securing the endpoints of the laptops of the company and the firewall and authentication and all kinds of other things you have competing interests. So focus is pretty key. And it's obviously a very large addressable problem. What the market is telling us is a few things. The first one is that automation is critical. They may not have as many people to solve the problem. And the problem set is moving at such a scale that it's very, very hard to keep up. So a lot of people ask me you know, what do I worry about? You know, how do I stay awake at night? Or how do I get to sleep? And really the things I'm worried most about in the way where I spend most of my time on the product side is about how fast are builders building? Not necessarily about the bad guys. Now the bad guys are coming and they're doing all kinds of innovative and interesting things. But usually it starts off with the good guys and how they're deploying and how they're building. And you know, the cloud providers literally are releasing API's and new acronyms almost weekly it seems. So like new technology is being created such a scale. So automation the ability to adapt to that is one key message that we hear from the customers. The other is that it has to solve or go across multiple categories. So although things like Kubernetes and Containers are very popular today. The cloud security tackle and challenges is much more complex than that. You've got infrastructure as code, you've got server lists, you've got kind of fragmented workloads, whether some are Containers, some are VMs, maybe some are armies and then some are Kubernetes. So you've got a very fragmented world out there, and all of it needs to be secured. And then the last one is probably the most consistent theme we're hearing is that as DevOps becomes involved, because they know the application and the stack much better than security, it has to fit into your modern workflow of DevOps. So that means you know, deep integrations into Jira and Slack and PagerDuty and New Relic and Datadog are a lot more important in integrating to your you know, Palo Alto firewall and your Cisco IDs system and your endpoint you know antivirus. So those are the real key trends that we're seeing from the customers. >> Yeah Dan, you bring up a really important point, leveraging automation. I'm wondering what you're hearing from customers, because there definitely is a little bit of concern, especially if you take something like security and say, okay well, automation. Is that something that I'm just going to let the system do it? Or is it giving me to getting me to a certain point that then a human makes the final decision and enacts what's going to happen there? Where are we along that journey? >> Yeah, so I think of automation in two lenses. The first lens is efficacy, which is you know do I have to write rules? And do I have to tune train and alter the system over time? Or can it do that on my behalf? Or is there a combination of both? So the notion of people writing rules and building rules is very, very hard in this world because things are moving so quickly. You know, what is the KMS you know threat surface? The threat attacks are just changing. And typically what happens when you write rules is they're either too narrow and you messed up or they're too broad you just get way too much noise. So there's automating the efficacy of the system. That's one that's really critical. The other one that is becoming more important is in the past it was called enforcement. And this is how do I automate a response to your efficacy. And in this scenario it were very, very early days. Some vendors have come out and said you know, we can do full remediation and blocking. And typically what happens is the DevOps team kind of gives the Heisman to the security team it says, "No, you're not doing that." You know this is my production servers, and my infrastructure that's you know running our business, you can't block anything without us knowing about it. So I think we're really early. I believe that you know we're going to move to a world that's more about orchestration and automation, where there's a set of parameters where you can orchestrate certain things or maybe an ops assist mode. You know for example, we have some customers that will send our alerts to Slack, then they have a Slack bot and they say, "Okay, is it okay that Bob just opened "an S3 bucket in this region, yes or no?" No, and then it runs a serverless function and closes it. So there's kind of a what we call driver assist mode versus you know full you know, no one behind the steering wheel today. But I think it's going to mature over time. >> Yeah, Dan one of the other big challenges customer has is that their environments are even more fragmented than they would in the past. So often they're leveraging multiple cloud providers, multiple SaaS providers then they have their hosting providers. And security is something that I need to have holistically across these environments but not have to worry about okay, do I have the skill set and understanding between those environments? Hopefully you know that's something you see out there and want to understand, you know how the security industry in general and maybe Lacework specifically is helping customers, get their arms a little bit more around that multi cloud challenge if you will? >> Yeah. So I totally agree things are you know, I think we have this Silicon Valley, West Coast bias that the world is all you know, great. And it says to utopia Kubernetes, modern infrastructure, everything runs up and down, and it's all you know super easy. The reality is much different. Even in the most sophisticated sets of infrastructure in the most sophisticated customers are very fragmented and diverse. The other challenge that security runs into is security in the past a lot of traditional security mindsets are all about point in time. And they're really all about inventory. So you know, I know used to be able to ask, you know a security person, how many servers do you have? Where are they? What are they doing this? They say, "Oh, you know we have 10 racks with 42 servers in each rack. "And here's our IP addresses." Nowadays, the answer is kind of like, "I don't know what time is it you know, "how busy is a service?" It's very ephemeral. So you have to have a system which can adapt with the ephemeral nature of everything. So you know in the past it was really difficult to spin up, say 10,000 servers in a Asia data center for four hours to do research you know. Security probably know if that's happening, you know they would know through a number of different ways could make big change control window would be really hard they have to ship the units, they bake them in you know, et cetera. Nowadays that's like three lines of code. So the security people have to know and get visibility into the changes and have an engine which can determine those changes and what the risk profile of those in near real time. >> Yeah it's the what we've seen is the monitoring companies out there now talking all about observability. Its real time, it's streamings. You know it reminds me of you know my physics. So you know Heisenberg's uncertainty principle when you try to measure something, you already can't because it's already changed. So what does that mean-- >> Dan: Yeah. >> You know what does security look like in my you know, real time serverless ever changing world? You know, how is it that we are going to be able to stay secure? >> Yeah, so I think there are some really positive trends. The first one is that this is kind of a reboot. So this is kind of a restart. You know there are things we've learned in the past that we can bring forward but it's also an opportunity to kind of clean the slate and think about how we can rebuild the infrastructure. The first kind of key one is that over time security in the traditional data center started understanding less and less about the application over time, what they did was they built this big fortress around it, some called it defense in depth you know, the Security Onion whatever you want to call it you know, the M&M'S. But they were really lacking in the understanding of the application. So now security really has to understand the application because that's the core of what's important. And that allows them to be smarter about what are the changes in their environment, and if those are good, bad or indifferent. The other thing that I think is interesting is that compliance was kind of a dirty word that no one really wanted to talk about. It was kind of this boring thing or auditors would show up once every six months go through a very complex checklist and say you're okay. Now compliance is actually very sophisticated. And the ability to look at your configuration in near real time and understand if you are compliant or following best practices is real. And we do that for our customers all the time. You know we can tell them how they're doing against the compliance standard within a you know, a minute timeframe. And we can tell that they're drifting in and out of that. And the last one and the one that I think most are excited about is really the journey towards least privileges and minimizing the scope of your attack surface within your developers and their access in your infrastructure. Now it's... We're pretty far from there, it's an easy thing to say it's a pretty hard thing to do. But getting towards and driving towards that journey of least privilege I think is where most people are looking to go. >> Alright Dan, I want to go back to something that we talked about early in the conversation, that relationship with the cloud providers themselves, so you know talking AWS, Azure, Google Cloud and the like. How should customers be thinking about how they manage security, dealing with them dealing with companies like Lacework and the ecosystem you mentioned in companies like Datadog and the New Relic? You know how do they sort through and manage how they can maintain those relationships? >> So there's kind of the layer eight relationships, of course which are starting you know in particular with the cloud providers, it's a lot more about bottoms up relationships and very technical understanding of product and features, than it is about being on the golf course, and you know eating steak dinners. And that's very different you know, security and buying IT infrastructure was very relationship driven in the past. Now you really especially with SaaS and subscriptions, you're really proving out your technology every day. You know I say kind of trust is built on consistent positive results over time. So you really have to have trust within your solution and within that service and that trust is built on obviously a lot of that go to market business side. But more often than not it's now being built on the ability for that solution to get better over time because it's a subscription. You know how do you deliver more features and increase value to the customer as you do more things over time? So that's really, really important. The other one is like, how do I integrate the technology together? And I believe it's more important for us to integrate our stack with the cloud provider with the adjacent spaces like APM and metrics and monitoring and with open source, because open source really is a core component to this. So how do we have the API's and integrations and the hooks and the visibility into all of those is really, really important for our customers in the market? >> Well Dan as I said at the beginning, security is such an important topic to everyone out there. You know we've seen from practitioners we talked to for the last few years not only is it a top issue it's a board level discussion for pretty much every company out there. So I want to give you the final word as to in today's you know modern era, what advice do you give to users out there to make sure that they are staying as secure as possible? >> Yeah so you know first and foremost, people often say, "Hey you know, when we build our business, "you know, it'd be a good problem to start have to worry "about customers and you know, "all kinds of people using the service. "And you know, we'll worry about security then." And it's easy lip service to say start it as early as possible. The reality is sometimes it's hard to do that. You've got all kinds of competing interests, you're trying to build a business and an application and everything else depending obviously, the maturity of your organization. I would say that this is a great time to kind of crawl, walk, run. And you don't have to think about it. If you're building in the cloud you don't have to think of the end game you know right away, you can kind of stair step into that. So you know my suggestion to people that are moving into the cloud is really think about compliance and configuration best practices first and visibility, and then start thinking of the more complex things like triage alerts and how does that fit into my workflow? How do I look at breaches down the line? Now for the more mature orgs that are taking, you know an application or a new application or Stack and just dropping it in, those are the ones that should really think about how do I fit security into this new world order? And how do I make it as part of the design process? And it's not about how do I take my existing security stack and move it over? That's like taking, you know a centralized application moving to the cloud and calling it cloud. You know if you're going to build in the cloud, you have to secure it the same way that you're building it in a modern way. So really think about you know, modern, you know new generation vendors and solutions and a combination of kind of your provider, maybe some open source and then a service, of course like Lacework. >> Alright well Dan Hubbard, thank you so much for helping us dig into this important topic Cloud Native security, pleasure talking with you. >> Thank you. Have a great day. >> And I'm Stu Miniman your hosts for Cloud Native Insights and looking forward to hearing more of your Cloud Native Insights in the future. (upbeat music)

Published Date : Jul 24 2020

SUMMARY :

leaders around the globe, it did not mean that the Happy to be here. I agree with you and your team. the hypervisor and you know the you know, political and And it's easy to say you You mentioned some of the you know, So a lot of people ask me you know, Yeah Dan, you bring up kind of gives the Heisman to that multi cloud challenge if you will? that the world is all you know, great. So you know Heisenberg's the compliance standard within a you know, and the ecosystem you mentioned And that's very different you know, as to in today's you know modern era, So really think about you know, thank you so much for helping us Have a great day. and looking forward to hearing more

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
Dan HubbardPERSON

0.99+

DanPERSON

0.99+

10 racksQUANTITY

0.99+

100%QUANTITY

0.99+

DatadogORGANIZATION

0.99+

Palo AltoLOCATION

0.99+

Stu MinimanPERSON

0.99+

2020DATE

0.99+

AsiaLOCATION

0.99+

AWSORGANIZATION

0.99+

42 serversQUANTITY

0.99+

10,000 serversQUANTITY

0.99+

HeisenbergPERSON

0.99+

StuPERSON

0.99+

LaceworkORGANIZATION

0.99+

firstQUANTITY

0.99+

CiscoORGANIZATION

0.99+

Silicon ValleyLOCATION

0.99+

BobPERSON

0.99+

two locationsQUANTITY

0.99+

bothQUANTITY

0.99+

New RelicORGANIZATION

0.99+

two lensesQUANTITY

0.99+

one key messageQUANTITY

0.99+

M&M'SORGANIZATION

0.99+

BostonLOCATION

0.98+

Cloud Native InsightsORGANIZATION

0.98+

first oneQUANTITY

0.98+

DevSecOpsTITLE

0.98+

SlackTITLE

0.98+

DevOpsTITLE

0.97+

four hoursQUANTITY

0.97+

Cloud NativeTITLE

0.97+

eightQUANTITY

0.97+

first lensQUANTITY

0.97+

each rackQUANTITY

0.97+

todayDATE

0.97+

CUBEORGANIZATION

0.96+

sevenQUANTITY

0.95+

SecDevOpsTITLE

0.93+

KubernetesTITLE

0.93+

oneQUANTITY

0.92+

COVIDTITLE

0.92+

one thingQUANTITY

0.91+

theCUBE StudiosORGANIZATION

0.9+

PagerDutyORGANIZATION

0.9+

Palo AltoORGANIZATION

0.89+

CloudTITLE

0.89+

threeQUANTITY

0.88+

SlackORGANIZATION

0.87+

AzureORGANIZATION

0.87+

JiraORGANIZATION

0.85+

S3TITLE

0.83+

serverless.comOTHER

0.83+

Cloud Native InsightsORGANIZATION

0.78+

three linesQUANTITY

0.78+

layer sevenOTHER

0.77+

pandemicEVENT

0.76+

West CoastLOCATION

0.75+

Cloud Native InsightsTITLE

0.74+

last few yearsDATE

0.73+

eightOTHER

0.7+

ContainersORGANIZATION

0.69+

Google CloudORGANIZATION

0.69+

KubernetesORGANIZATION

0.68+

every six monthsQUANTITY

0.66+

William Janssen, DeltaBlue | Cloud Native Insights


 

>> From theCUBE studios in Palo Alto in Boston, connecting with thought leaders around the globe, these are cloud native insights. >> Welcome to another episode of Cloud Native Insights. I'm your host Stu Miniman and of course with Cloud Native Insights will really help understand you know, where we have gone from cloud, how we are taking advantage of innovation, a real driver for what happens in the spaces of course developers. You think back to the early days, it was often developers that were grabbing a credit card, using cloud services and then it had to be integrated into what was being done and the rest of the organization saw the large rise of DevOps and all the other pieces around that, that help bring in things like security and finance and the like. Happy to welcome to the program first time guest, William Janssen. He is the CEO of DeltaBlue. Deep in this discussion of cloud native DeltaBlue is a European company helping with continuous deployment across cross cloud providers in the space. William, thanks so much for joining us, nice to see you. >> Glad to be on the show, thank you Stu. >> All right, so one of the reasons I'm glad to have you on is because of some of the early episodes here, you know we were discussing really what cloud native is and what it should be. I had my first interview on the program, Joep Piscaer, who you know, had given the analogy and said when you talked about DevOps, DevOps isn't something you could buy. But it's something that lots of vendors would try to sell you. And we're trying to dispel, lots of companies out there, they're like, "Oh, cloud native, well we support Kubernetes. "And we have this tool and you should buy our cloud native, "you know, A, B, C or D." So, want to start a little first with what you see out there and what you think the ultimate goal and outcome of cloud native should be? >> I think cloud native, to start with your last question, I think cloud native should make life fun again. We have a lot of technical problems, we solve them in technical things. You mentioned Kubernetes but Kubernetes is solving a technical problem. And introducing another technical problem. So what I think cloud native should do is focus on what you're actually good at. So a developer should develop. Someone from the infrastructure, an operator, should focus on their key points and not try to mix it up. So, not Kubernetes, Kubernetes is again introducing another technical issue. Our view on cloud native is that people should have fun again and should be focusing on what they're good at. And so it's not about technology, it's about getting the procedures right and focusing on the things you love to do. And not to talk to the cross border, talk to a lot of developers and solve operational kind of things. That's what we try to solve and that's our view of cloud native. >> Yeah, I'll poke that a little bit because one thing you say, people should do what they're good at. It's really what is important for the business, what do we need to get done? There's often new skills that we need to do. So it's really great if we could just keep doing the same thing we're doing. We know how to do it. We optimize it, we play with all of our geek knobs. But the drumbeat that I hear is, we need to be agile, we need to be able to create new applications. IT needs to be responsive for the business and rather than in the past it was about, building this beautiful stack that we could optimize and build these pieces together. Today, the analogy I hear more is, there's layers out there, there's lots of different tooling, especially if you look at the developer world. There is just too many options out there. So, maybe bring us a little bit as to you know, what DeltaBlue does. How you look at allowing developers to build what they, new things that they need but not be, I guess the word, locked into a certain place or certain technology. >> Yes, I've been on IT for 20 years. So I've seen a lot of things go around. And when we started out with DeltaBlue, the only thing we had in mind is how could we make the lifecycle of applications and all the things you had to do, the government around applications way more easy. Back in the days, we already saw that containerization solved some of the issues. But it solves technical issues. So like when you start coding, you don't need to go to the network card anymore. We took the same approach to our cloud native approach. So we started on the top level. We started with applications in mind. And the things back in the day you had Bitnami already had the option to have a VM or standard installation of an application. So what we see is that nowadays, many developers and many organizations try to focus on that specific part, how to get your code into some kind of under configuration solution. We take that for granted. There are so many great solutions out there, already tried to solve that problem. So instead of reinventing that wheel again, we take that for granted. But we take another approach. We think that if the application is there, you need to test it. You need to take it into production. You want to have several versions of a specific application into the production environment. So what we've tried to solve with our platform is to make that part of the life cycle, let's call it horizontal version of your application lifecycle, not getting an application built or running up different stuff, we take that for granted. We take the horizontal approach. How to get your traditional application from your development environment to your testing, acceptance. That's a different kind of people test your application, security testing before you take it into production. And that should be all be done from a logical point of view. So we built one web interface, a logical portal. And you can simply drag and drop any type of application, not just a more than micro service oriented or Kubernetes based application but any type of application from your acceptance environment to your production environment. That's going to solve the real problem. So now, any business can have 10 different acceptance environments for even your old legacy SAP or your Intershop environment. That's going to get your business value. So going back to your definition of cloud native, getting that kind of abstraction between getting your and code your application and get it get somewhere up and running and all the stuff that's needs to be done from your development environment into the production environment. That's going to add to your business value. That's going to speed up your time to market, that's going to make sure that you have a better cloud quality because now you can test even your legacy application from 10 different points of view and 10 different types of different branches, all in a parallel environment. So, when we started with DeltaBlue, we took a different approach, took the technical stuff for granted, and focus on all the government around applications and the governance that's the thing, I think that's the most important part in the cloud native discussion. >> So governance, especially in Europe, has a lot of importance there. If you could, bring us inside a little bit, customers you're talking to, where they are in this journey. If you've got an example of something you're doing specifically we'd love to hear how that happens in real world. >> Yes we have many different customers but I think one of our best examples, for example is Wunderman Thompson, a big eCommerce party across the globe but also here in the Netherlands. And we made a blueprint of their development environment the way they develop application and the way they host applications. So, now they started a new project, 40 developers go to the new big eCommerce application. In the past, everyone had to install their own Intershop environment on their own laptop, Java, Oracle, that kind of stuff. It took me a day and a half. Since we abstracted that into like a simple cell, like you would do in any serverless environment nowadays, they can now simply click on a button. And since they made their laptop or their development environment part of our platform, they can now simply drag and drop the complete initial environment to the laptop and they can send development in 10 minutes instead of a day and a half. That's just the first step that makes their life easier. But also imagine, we have an application up and running for two, three months and our security patch, we all know the trouble of getting a patch installed in production but also then install it into the acceptance environment, test environment, development environment, all those kind of different versions. With our platform, since we have the application in mind, we can, with simple one simple click of the button, we can propagate that security patch across all the different environments. So from a developer point of view, there's no need to have any kind of knowledge of course they need to configure a port or something like that but no need of knowledge of any type of infrastructure anymore. We have made the same blueprint for the complete development environment. So with a single click of the button, they have a complete detail environment, known over the need to go to their infrastructure to get the service to their operating guys, they have them installed, industrial Nexus, very book of repository, all that kind of stuff. It's all within one blueprint. So again, we think that the application should come first. That should be abstracted, and not abstracted just in a single spin up a container or spinning up a VM. Now, the complete business case, application, complete environment should be up and running with a single click of a button. So now they can start if they have a demo tomorrow, for example, and they want to have a demo setup. With a single click, they have a complete environment up and running, instead of having to wait three weeks, four weeks before they can start coding. And the same comes with a production environment. We now have an intelligent proxy in front of it. So they can have three different versions of the same shot in their production environment. And based on business rules, we can spread the load against the different versions of a business application, eCommerce application. We signed a new contract with New Relic last week. And the next thing we're going to do, and it's going to be there in two weeks, is fit New Relic data, I mean, an eCommerce application is about performance. A longer response time of a page page load time will drop your drop your revenue. So what we're going to do with New Relic is feed it's performance data back into that the intelligent proxy in front of their application. So now they're going to drop the new version of their intershop application on a Thursday evening, they go to sleep. Friday morning, they wake up and from the three versions, and the best performing website will be up and running. That's the kind of intelligence and that's the kind of feedback we can put into our platform since we started with applications in mind first. It's getting better quality, because you can do better testing. I mean, we all want to test, but we never want to wait for those different kinds of setups, they want to have fast development cycles. That kind of flexibility where you do the functional deployment, the functional release, not the technical stuff. What we now see in the market is that most people, when they go to the cloud, try to solve the technical release problems of getting the application up and running in a technical way into the production time, we try to focus on the functional level. >> So, William, being data driven, a very important piece of what you talked about there. What I want to help our audience understand is concerns about if you talk about abstractions, or if you want to be able to live across different environments, is can you take advantage of the full capabilities of the underlying platform? Because, that is, one of the reasons we go to cloud isn't just because it's got limitless compute Pricing comes down. But there's only new features coming out, or I want to be able to go to, a cloud provider and take advantage of some specific feature. So help us understand how I can live across these environments, but still take advantage of those cloud native features and innovations as they come out. >> Great. There are actually two ways. For most alternatives, we also have an alternative component in our platform as well. We have complete marketplace with all kinds of functionality like AWS has, but I can imagine that people want to develop an AWS and get our AWS lambda functions or s3 buckets or that that kind of specific functionality. And going back to the Intershop example, they run their application as a CaaS solution on Azure. So when you went to Azure DevOps, or that kind of specific functionality included, our platform connects over 130 different data centers across the globe and Azure and AWS, and Oviedo Digital Ocean are all part of the huge mix of different cloud providers. For every provider, we have what we call gateway components. We deploy natively, mostly bare metal or equivalents of bare metal within those cloud providers. And we made an abstraction layer on the network layer. So now we can include those kind of specific services like they were part of our platform natively. Because if we would have just build a layer and couldn't use the specific components of an AWS or an Azure or that kind of stuff, we would just be another hosting provider. I haven't liked VMware. So that kind of stuff. We want to and we are aware that we need to include a specific stuff, functionality. And what we do with this with what we call gateway components. So we have AWS, gay components, educators, but also for IBM, or Google specific environment. So we can combine the network of AWS, with our specific network. And that's possible, because we made a complete abstraction layer between the network of the infrastructure provider and our network. So we can complete IP subnets DNS resolver as if it was running on their local environment. And thereby, since we have that abstraction layer, we can even move the workloads on AWS to Azure. And since we have the abstraction layer network, we can even make sure that you don't need to reconfigure your application. I think that's the flexibility that people are looking for. And if they have a specific workload and Azure and it's getting too expensive, for the ones that includes AWS stuff, they want to shift the workload to different kind of cloud providers based on the characteristics of a specific worker, or even if you want to have the cheapest option, you can even use your on premise data center. >> William, do that there absolutely is interest in doing that. One of the barriers to being able to just go between environments is of course that the skills required to do this. So, there's something to be said about, if I use a single provider, I understand how to do it, I understand how to optimize it, I understand the finances of it. And while there may be very similar things in another cloud, or in my own data center, the management tools are different and everything. So how do we overcome, that skill set challenge, between different environments. >> We had a different approach the same as we do it on application level, we took it also in data center level, so we're going to handle most cannot say all because there's always specific components. But from our interface, you can simply go to a specific application and select the type of data center you want to run on your application. And if your application is running on an AWS, you get the gateway components with the components, like an s3 bucket or a lambda or an RDS, based on the data center you're running in. So we took that abstraction layer even on that level. But I got to be honest, I think 80% of our customers is not interested in the data center, they run their application in unless they have specific functionality, and which is not available on our platform, or they have a long running application, or use a specific or they bought a specific application. Otherwise, they don't care. Because from a traditional application, there is no difference between running on Azure or Google Cloud or an IBM cloud or whatever. The main difference is that we can make a guarantee about the SLA. I mean, IBM has a better uptime guarantee. A better performance and a better network compared to let's say, digitalocean. Kind of set this up. But there is a huge difference. But it's more like the guarantee that we can give them. So we have this abstraction layers, and we try to put as many as possible as much as possible into our portal interface. There will no way that we're going to redesign and we work about the complete AWS interface, or we're not going to include 100% of their functionality. That's not possible. We're, small company. AWS is somewhat more developers in place. But the main components and people are asking for like RDS or these kind of specific setups, that's where we have the gateway components for available and they can include them into their own application. But we also going to advise them why they were looking for those specific AWS components. Is it within the application architecture or is it something gauges right? Isn't there a better solution or an other solution? And I think, since we have that objection that one of the biggest benefits is, and what we see our customers also do is we incorporate that data center into our platform. And we have one huge network across all the cloud providers and including their own data center. So in the past, they had to have two different development teams, one specialized in AWS development, with all that kind of specific stuff. And all one development team which had more like a traditional point of view, because their internal system and data which was not allowed to go outside the company or had to stay within the firewall. And since we have now one big network, which is transparent to them, we can make sure that their code for their internal systems stays internal and is running on internal systems. But we could still use some kind of functionality from the outside. We do it all unencrypted today, and we have one big platform available. So with our gateway components, we can make sure that that data and application data is really staying internally. And only is allowed to grow internal data access and that kind of stuff, but still use external functionality or price. But again, I would say 80% of our customers, they don't care because they just want to get rid of the burden. I think going back to what we think cloud native means is just getting rid of the burden. And you shouldn't be concerned about what type of cloud we're actually using. >> Absolutely, William, the goal of infrastructure support, my applications and my data and we want companies to be able to focus on what is important for the business and not get bogged down and certain technical arguments introduction. So William, thank you so much for joining us. Really great to hear about Delta blue. Looking forward to hearing more in the future. >> Thank you. >> I'm Stu Miniman. And look forward to hearing more of your cloud native insights.

Published Date : Jul 17 2020

SUMMARY :

leaders around the globe, and the rest of the organization saw Glad to be on the show, because of some of the early and focusing on the things you love to do. and rather than in the past it was about, and all the stuff that's needs to be done to hear how that happens and that's the kind of feedback we can put one of the reasons we go to cloud of the huge mix of One of the barriers to and select the type of is important for the business And look forward to hearing

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
WilliamPERSON

0.99+

IBMORGANIZATION

0.99+

William JanssenPERSON

0.99+

Joep PiscaerPERSON

0.99+

twoQUANTITY

0.99+

EuropeLOCATION

0.99+

100%QUANTITY

0.99+

AWSORGANIZATION

0.99+

three weeksQUANTITY

0.99+

Palo AltoLOCATION

0.99+

DeltaBlueORGANIZATION

0.99+

80%QUANTITY

0.99+

New RelicORGANIZATION

0.99+

20 yearsQUANTITY

0.99+

10 minutesQUANTITY

0.99+

Stu MinimanPERSON

0.99+

Friday morningDATE

0.99+

Delta blueORGANIZATION

0.99+

last weekDATE

0.99+

Thursday eveningDATE

0.99+

GoogleORGANIZATION

0.99+

40 developersQUANTITY

0.99+

a day and a halfQUANTITY

0.99+

two waysQUANTITY

0.99+

three monthsQUANTITY

0.99+

first stepQUANTITY

0.99+

NetherlandsLOCATION

0.99+

four weeksQUANTITY

0.99+

Cloud Native InsightsTITLE

0.99+

two weeksQUANTITY

0.99+

oneQUANTITY

0.99+

TodayDATE

0.99+

first interviewQUANTITY

0.99+

10 different pointsQUANTITY

0.99+

10 different typesQUANTITY

0.99+

one big platformQUANTITY

0.98+

tomorrowDATE

0.98+

three versionsQUANTITY

0.98+

Oviedo Digital OceanORGANIZATION

0.97+

first timeQUANTITY

0.97+

BostonLOCATION

0.97+

over 130 different data centersQUANTITY

0.97+

OracleORGANIZATION

0.96+

todayDATE

0.96+

Azure DevOpsTITLE

0.96+

single providerQUANTITY

0.96+

StuPERSON

0.96+

firstQUANTITY

0.95+

KubernetesTITLE

0.95+

theCUBEORGANIZATION

0.95+

WundermanORGANIZATION

0.95+

JavaTITLE

0.95+

singleQUANTITY

0.95+

two different development teamsQUANTITY

0.95+

10 different acceptance environmentsQUANTITY

0.93+

single clickQUANTITY

0.93+

DevOpsTITLE

0.92+

AzureTITLE

0.88+

one bigQUANTITY

0.88+

one blueprintQUANTITY

0.88+

Sasha Kipervarg, LiveRamp | Cloud Native Insights


 

>> Narrator: From theCUBE studios in Palo Alto in Boston, connecting with thought leaders around the globe, these are Cloud Native Insights. >> Hi, and welcome to another episode of Cloud Native Insights. I'm your host, Stu Miniman. And when we talk about Cloud Native of course, it's not just moving to the cloud as a location, but how do we take advantage of what's happened in the cloud of the changes that need to happen. And this is not only from a technology standpoint, it's an organizational standpoint. And we're also going to touch on the financial implications and something you've probably heard about FinOps, relatively new last couple of years as a term. Of course, the financial engineering cloud has been around for many years and how that ties into DevOps and to help us understand this movement, what's going on really thrilled that we have a practitioner in this space. I want to welcome Sasha Kipervarg. He's a head, the head of Global Cloud Operations in special projects with LiveRamp. Sasha, thanks so much for joining us. >> Thanks very much too, happy to be here. >> All right, so why don't we start off first for those that don't know LiveRamp, I'm sorry, you're in the ad tech space. Maybe just give us a little bit about, you know, the organization and what your team does there? >> Sure, so LiveRamp is in the advertising technology space, and we help connect companies to their customers and send targeted advertising to them. We're based in San Francisco and have engineering teams across the globe, primarily New York, London, China, all over the map, really. And we're a fast growing company, we've gone from perhaps 400 to maybe 12, 1300 employees over the last year and a half. >> Well, you know that whole space is a whole separate discussion. I like when I looked up a little bit about LiveRamp the discussion point is, you know, cookies for eating not for following you, in looking where are you going all over the company. So your role inside LiveRamp, though. Tell us a little bit... You know, we're cloud bits in New York? >> Sure, so I'm responsible for the engineering teams that help other development teams operate in the cloud. So whereas on premise, it would have been a traditional operations team in the cloud. It's basically an engineering team that are experts in all the different areas that other engineering teams need us to be in so that we can express good practices and help them deliver products. >> Great, you actually had a real forcing function for cloud. You know, right now during the global pandemic we've seen lots of acceleration of people looking at cloud, if you could briefly just bring us back as to one of the things that helped push LiveRamp, you know, to go much heavier into cloud. >> Yeah, so we had some initial plans and we were exploring. But what really pushed us over the edge was we had a three to four day outage at our data center here in San Francisco during a heatwave. And during that time, the data center couldn't control their temperature. We had unusually warm temperatures in San Francisco, they weren't that warm. It was like maybe in the, you know, mid 90s. But for the Bay Area in the summertime, you know, where it's usually 70, it was a big deal. And so we had racks of servers going down because it was too hot. And so if we weren't quite convinced before that we certainly were after that, and that made us realize that there were lots of good reasons to be in the cloud. And so we did it. We put together a migration and over the course of a year, we not only containerized but we migrated our environment into GCP. >> I wonder if you could just bring us inside a little bit that move to the cloud, you talk about adopting containerization. You know, your applications, you know, how much of it did you just kind of move there? How much did you build new? Where there some things that you just said, hey, I can kind of, you know, adopt a SAS equivalent, you know, how did your application portfolio look? >> Yeah, so it's probably good to think of them in terms of the infrastructure services that we use in the cloud, and then the customer facing applications themselves. And what we try to do is essentially containerize all of our infrastructure applications. Actually, let me rephrase that. We took the customer facing applications, and we containerize those. Now the applications themselves, did not change but they swapped out their underlying infrastructure for containers, running on the GCP native container service. On the back end of things we use the native services in GCP up as much as possible. So if we were using a database on premise, we tried to use the native database service in the Cloud with Google. I think the one interesting exception to that which we're changing now, in fact, was we decided to run our hundred petabyte Hadoop cluster in the Cloud using our own native service because of some price concerns. Those price concerns have gotten better since time and we're now migrating to Dataproc, which is Google's native Hadoop service. >> Yeah, it's fascinating when you think about just how fast things change in the cloud, new services can become available and as you're alluding to the finances can change significantly over you know, a couple of months or a quarter. Overall, how's the experience been? You know, moving to cloud, though? >> Well, it's been fantastic in some ways, painful in others because, you know, you discover and maybe this is begin to touch on the FinOp stuff like, you discover that you've gone from quarterly planning cycles where you opt to purchase a whole rack of servers, and you implement them over the next quarter or something like that, to making by the second decisions, to spin up resources via command line by developer and spend unlimitless operating expenses. So, it's quite a big shift. And I think a lot of companies are caught, you know, flat footed by it. We certainly work for a little bit. And there's some financial pain that gets expressed. And you know, the question that I would pose to the audience when they think about the cloud is, you know, we think of the migrations and we only think about their technical success, but if you migrate to the cloud and you do it technically and you containerize and it's on schedule, but then you blow your budget, was it really a success? Because ultimately, you know the business needs to be profitable in order for things to work. >> Yeah, absolutely Sasha. So what I've heard you talk about this before is in the pre-cloud model, you met with the budget team quarterly, and it was mostly a look back function. And of course, when you think about leveraging the cloud, things are changing on a fairly regular basis. And are you able to understand what decisions you're making and what the impact will be on you know, next month and next quarters, billing? So bring us inside a little bit as to, you know, that interaction and what that meant to your teams and how they had to think about you know, engineering and finance together? >> Yeah, it's a fantastic question. So, I guess the first thing is, let me let me zoom out for a moment and just make sure that the audience understands that you know, typically it's just engineering leadership, and a fairly small number of maybe high level developers, maybe an architect that get together with finance once a quarter and have a conversation about what they want to spend and how much they want to spend, and where it should be implemented. And that is a fairly regular thing that's been going on for many years. When you move to the cloud, all of a sudden that decision needs to happen on a real time basis. And typically, companies are not set up for that kind of a conversation. There's usually like a large wall between finance and engineering. And it's because you want the engineering teams to be engineers and the finance folks to be doing finance related things. And the two don't really mix all that often. But when you give a developer an API to spend money essentially right, that's what you've done. They don't just spend up resources, they spend money by API. You need to have a real time conversation where they can make trade offs, where you can track the budget, and those expenses shift from something called CapEx to OpEx. And that's treated in a very different way, on the books. Where we are today is we've created what a team, we call it a FinOps practice. But it's a team that's cross functional by nature that sits within engineering that's made up of a FinOps practitioner, person dedicated to the role. And then members of the finance team. And then many other members of engineer and they work together to first, express the cost by helping developers understand what they're actually spending and where they're spending it. And then the system also makes, recommendations about how to optimize and then the developers absorb that information and figure out what they should optimize, do that work. And then the system re-represents the information for them, and lets them know that their optimizations make sense or not from a financial perspective. The way that we've talked to developers, we've discovered that they care about efficiency. They care about efficiency in different ways. They care about CPU efficiency, they care about RAM efficiency. And it turns out, they care about how efficient their application is from a cost perspective to, right? And you can either tell them directly to care about it, or help them become aware. Or you can use proxies, like what I just mentioned about CPU, RAM, disk, network. If they understand how efficient their application is. They have a natural instinct to want to make it better on a daily and weekly basis. It's just sort of baked into their deep engineering persona. And we try to harness that. We try to position things in such a way that they can do the right thing, because most developers want to do the right. >> Yeah, it's really interesting to me Sasha I remember back, you know you go back seven, eight years ago and I looked at cloud models, and how cloud providers were trying to give more visibility and even give guidance to customers as to how they could adjust things to make them more financially reasonable. I've come from the infrastructure side, when I think about you know, deployments in a data center. It was very well understood you had systems engineer work with a customer, they deploy something, they understand what the growth of is expected to be, and if you needed more, more computer, more storage, what the cost of that would be, you understand the you know, how many years you will be writing that off for, but everything's well understood, and as you said, like developers often they've got, n minus one technology, okay, here's some gear you could work on. But finances were clearly written, they were put into some spreadsheet or understood as opposed to the cloud. There is much more burden on the user to understand what they're doing. Because you have that limitless capability as opposed to some fixed asset that you're writing it off. We're huge proponents of ledger than the cloud. And often there are, cost savings by going to the cloud. But it feels like they're also some of this overhead of having to do the financial engineering is an overhead cost that might not be considered in the overall movement to the cloud. >> Yeah, and maybe now is a good time to swing back to the concept of DevOps, right? Because I want to frame FinOps in this concept of having the budget overhead and I want to link it to the Agile, okay. So, part of the reason we moved to DevOps which is an Agile movement that essentially, puts the responsibility of owning infrastructure and deploying it into the hands of the engineers themselves. The reason that it existed was because we had a problem deploying, we had two different teams typically operations and engineering. And one of them would write the code, and they would throw it over the wall to the operations team that will deploy the code. And because they were two different teams, and they didn't necessarily sit together or sometimes even report into the same leadership, they had different goals, right. And when there was a problem, the problem had to cross both of the team boundaries. And so it was slower to resolve issues. And so, people had the bright idea to essentially put the teams together, right. And allow the developers themselves to deploy the code. And of course, depending on the size of the company was structured--or it is structured slightly differently this idea of DevOps. And, essentially what you had was a situation that worked beautifully because if you had two separate teams that all of a sudden became one team that was fully responsible for writing the code, writing the tests and deploying the code, they saw each other's pain, they understood the problem really well. And it was an opportunity for them to go faster, and they could see the powerful thing. And I think that's essentially what made the DevOps movement incredibly successful. It was the opportunity to be able to control their own destiny, and move faster that made it successful. I view FinOps in a similar fashion. It is an opportunity for developers to understand their cost efficiency and deploy in the cloud by API, and do it in a fully responsible way. Everything that we've been talking about related to DevOps, there is a higher goal here. And that is the goal of unit economics, which is figuring out precisely what your application actually costs being deployed and used by the consumer on a unit basis, right. And that is the thing we're all trying to get to. And this FinOps gets us one step closer to that sort of financial nirvana. Now if you can achieve it, or even if you can achieve the basics of it. You can structure your contracts in a different way, you can create products that take better advantage of your financial model. You can destroy certain products that you have, that don't really make sense to operate in the cloud. You can fire customers. You can do a whole variety of things, if you know what your full costs are, and FinOps allows us to do that. And FinOps allows developers to think of their applications in a way that perhaps they never have in a fully transparent, holistic way. Like there's no sense to build a Ferrari, if it costs too much to operate, right. And FinOps helps you get there. >> It's such an important point Sasha. I'm so glad you brought that up, back in the traditional infrastructure data center world, we spent decades talking about Showback and Chargeback and what visibility you had? And of course for the most part, it was, oh well you know, that sunk costs or something that facilities takes care of. I'm not going to work at it and therefore, we did not have a clear picture of IT and how it really impacted the bottom line of business. So FinOps as you said, help move us towards that ultimate goal that we know we've had for years. I want to tease on that thing that you mentioned there, speed. We understand that, absolutely speed is one of the most important things, how do we react to the business? How to react to the customer, as close to real time as possible? How do you make sure that FinOps doesn't slow things down? If I'm an engineer, and I need to think about oh, wait. I've been told that, the best code to write is no code. But, I have to constantly think about, am I being financially sound? Am I doing that? How do we make sure that this movement doesn't slow me down, but actually enables me to move forward faster? >> Yeah I mean, let me mention a couple of things there. The first is that, what I alluded to before, which is that if you don't think about this as a developer, it's possible that the finance folks in the company could decide well hey, operating the cloud doesn't make financial sense for us. And so we're not going to do it and we're going to go back to data center and you maybe that's the right business move for some businesses who aren't growing rapidly, for whom speed and flexibility isn't as important. Maybe they stay in the data center or they go back to a data center. And so like, I would think a developer has stakes in the game, if they want to be flexible, if they want to continue to be flexible. And from a company perspective, like we... You know, this idea still being sort of fleshed out and even within the FinOps movement, like there is a question of how much time should a developer spend thinking about costs stuff? I'll tell you what my answer is, and perhaps I can touch on what other people think about it as well. My answer is that it's best to be transparent with developers as much as possible and share with them as much data as we possibly can, the right kind of data, right? Not overwhelm them with statistics, that help them understand their applications and applications efficiency. And if when you are implementing a FinOps practice within your org, if you get the sense that people are very touchy, and they're not used to this idea of talking about cost directly, you can talk about it in terms of proxies, right. And as I mentioned before, CPU, RAM, disk, network. Those are all good proxies for cost. So if you tell them hey, your application is efficient or inefficient on these different dimensions, go do something about it, right. Like, when you build your next architecture for your application, incorporate efficiencies across these particular dimensions. That will resonate and that will ensure that developers don't feel like it's hampering their speed. I think the cultural shift that FinOps emphasizes is key. This, helping developers get the high level understanding of why we're doing what we're doing and why it's important and embedding it into their not only their architectural design, but their daily operations. That is the key, like FinOps has multiple pieces to it. I think it's successful because it emphasizes a system that's made up of governance practices, rules that tell you how you should behave within the system. Tools like a CMP, and we can talk about that in a bit. But essentially, it's a cost management platform which is a tool that is designed to figure out what you're spending and express it back to you. It's designed to create anomalies and there's a whole segment in the marketplace of these different kinds of tools. And then of course, the cultural shift. If you can do all three at your organization whether you want to call it a FinOps or not, you're going to be set up for success and it will solve that problem for you. >> So Sasha, one of the things I've really enjoyed the last decade or so is it used to be that IT organizations thought what they were doing was, the differentiator and therefore, they were a bit guarded about what they would share. And of course, these days leveraging cloud leveraging open source, there is much more collaboration out there. And LiveRamp, not only is using FinOps, but you're a member of the FinOps Foundation, which has over 1500, individual members participating in that oversaw by the Linux Foundation, maybe bring us in a little bit as to, why LiveRamp decided to join this group. And, for final word on really kind of the mission of the FinOps Foundation. >> Yeah, I mean as members of the audience might know, the FinOps Foundation recently moved to the Linux Foundation, and I think part of that move was to express the independence of the FinOps Foundation, it was connected to a company in a CMP space before and I think J.R and the team made a wonderful decision in doing so. And I wanted to give a shout out to them. I'm very excited about the shift, and we look forward to contributing to the codebase and all the conversations. In terms of how we discovered it. I was feeling the pain of all these different problems of being, over my budget in the cloud. And, I had arrived at like this idea of like, I needed a dedicated person, a dedicated team that was cross-functional in order to solve the problem. But, on a whim, I attended a FinOps course at a conference and Mike Fuller, who was the author or one of the authors of the FinOps book, along with J.R. was teaching it and I spent eight hours just in like, in literal wonder thinking holy crap this guy and whoever came up with this concept put together and synthesized all of the pain that I had felt and all the different things I thought about in order to solve the problem in a beautiful, holistic manner. And they were just presenting it back to me on a platter, back to everyone on a platter and I thought that was beautiful. And the week that I got back to work from the conference, I put together a presentation for the executives to position a FinOps practice as the solution for LiveRamps budgetary cloud pain. We went for it, and we... It's helped us, it's helped lots of other companies. And, I'm here today partly because I want to give back because there's so much that I learned from being in the Slack channel. There's so much that I learned by reading the book, things that I hadn't thought of that I hadn't experienced yet. So I didn't have the pain. But you know, J.R and Mike, they had all interviewed, hundreds of different folks for the book, got lots of input, and they were talking about things that I hadn't experienced yet, that I was going to. And so I want to give back, they clearly want to give back. And I think it's, a wonderful, a wonderful practice, a wonderful book, a wonderful Slack channel. I would recommend that anyone facing the budgetary challenge in the cloud, join the organization There is a monthly conversation, where someone presents and you learn a lot from doing it. You learn problems and solutions that you perhaps wouldn't have thought of, so I would highly recommend it. >> All right, well Sasha thank you so much for sharing your story with our community and everything that you've learned and best of luck going forward. >> Thanks very much Stu. It's great to talk. >> Alright, and if you want to learn more about what Sasha was talking about, Linux Foundation it is this finops.org is their website. Linux Foundation, of course theCUBE. Cloud Native, big piece of what happens and what we're doing will be at theCUBEcon, CloudNativeCon shows this year. Look for more interviews in this space. I'm Stu Miniman. And look forward to hearing more about your Cloud Native Insights. (upbeat music)

Published Date : Jul 9 2020

SUMMARY :

leaders around the globe, of the changes that need to happen. and what your team does there? and send targeted advertising to them. you know, cookies for eating in all the different areas that you know, to go much heavier into cloud. and over the course of a year, bit that move to the cloud, and we containerize those. you know, a couple of months or a quarter. and maybe this is begin to and how they had to think about and just make sure that the in the overall movement to the cloud. And that is the goal of unit economics, and what visibility you had? and express it back to you. of the FinOps Foundation. and solutions that you perhaps and everything that you've learned It's great to talk. Alright, and if you

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
SashaPERSON

0.99+

Sasha KipervargPERSON

0.99+

Mike FullerPERSON

0.99+

J.R.PERSON

0.99+

Stu MinimanPERSON

0.99+

San FranciscoLOCATION

0.99+

FinOps FoundationORGANIZATION

0.99+

Palo AltoLOCATION

0.99+

New YorkLOCATION

0.99+

LondonLOCATION

0.99+

MikePERSON

0.99+

GoogleORGANIZATION

0.99+

Linux FoundationORGANIZATION

0.99+

J.RPERSON

0.99+

oneQUANTITY

0.99+

one teamQUANTITY

0.99+

LiveRampORGANIZATION

0.99+

FerrariORGANIZATION

0.99+

eight hoursQUANTITY

0.99+

San FranciscoLOCATION

0.99+

ChinaLOCATION

0.99+

threeQUANTITY

0.99+

two separate teamsQUANTITY

0.99+

Cloud Native InsightsTITLE

0.99+

400QUANTITY

0.99+

Bay AreaLOCATION

0.99+

firstQUANTITY

0.99+

bothQUANTITY

0.99+

four dayQUANTITY

0.99+

two different teamsQUANTITY

0.99+

BostonLOCATION

0.99+

twoQUANTITY

0.98+

todayDATE

0.98+

70QUANTITY

0.98+

Cloud NativeTITLE

0.98+

sevenDATE

0.98+

hundredsQUANTITY

0.98+

DevOpsTITLE

0.98+

mid 90sDATE

0.98+

hundred petabyteQUANTITY

0.98+

over 1500QUANTITY

0.98+

CloudNativeConEVENT

0.98+

second decisionsQUANTITY

0.97+

next monthDATE

0.97+

FinOpsTITLE

0.97+

DataprocORGANIZATION

0.96+

eight years agoDATE

0.96+

first thingQUANTITY

0.95+

Global Cloud OperationsORGANIZATION

0.95+

once a quarterQUANTITY

0.94+

theCUBEORGANIZATION

0.94+

LiveRampTITLE

0.93+

last year and a halfDATE

0.93+

SlackORGANIZATION

0.92+

StuPERSON

0.92+

CapExTITLE

0.91+

next quartersDATE

0.9+

one stepQUANTITY

0.9+

this yearDATE

0.89+

theCUBEconEVENT

0.89+

FinOpsORGANIZATION

0.89+

Dr. Tim Wagner & Shruthi Rao | Cloud Native Insights


 

(upbeat electronic music) >> Narrator: From theCUBE studios in Palo Alto and Boston, connecting with thought leaders all around the world, this is a CUBE conversation! >> Hi, I'm Stu Miniman, your host for Cloud Native Insight. When we launched this series, one of the things we wanted to talk about was that we're not just using cloud as a destination, but really enabling new ways of thinking, being able to use the innovations underneath the cloud, and that if you use services in the cloud, that you're not necessarily locked into a solution or can't move forward. And that's why I'm really excited to help welcome to the program, I have the co-founders of Vendia. First we have Dr. Tim Wagner, he is the co-founder and CEO of the company, as well as generally known in the industry as the father of Serverless from the AWS Lambda, and his co-founder, Shruthi Rao, she is the chief business officer at Vendia, also came from AWS where she worked on blockchain solutions. Tim, Shruthi, thanks so much for joining us. >> Thanks for having us in here, Stu. Great to join the show. >> All right, so Shruthi, actually if we could start with you because before we get into Vendia, coming out of stealth, you know, really interesting technology space, you and Tim both learned a lot from working with customers in your previous jobs, why don't we start from you. Block chain of course had a lot of learnings, a lot of things that people don't understand about what it is and what it isn't, so give us a little bit about what you've learned and how that lead towards what you and Tim and the team are doing with Vendia. >> Yeah, absolutely, Stu! One, the most important thing that we've all heard of was this great gravitational pull towards blockchain in 2018 and 2019. Well, I was one of the founders and early adopters of blockchain from Bitcoin and Ethereum space, all the way back from 2011 and onwards. And at AWS I started the Amazon Managed Blockchain and launched Quantum Ledger Database, two services in the block chain category. What I learned there was, no surprise, there was a gold rush to blockchain from many customers. We, I personally talked to over 1,092 customers when I ran Amazon Managed Blockchain for the last two years. And I found that customers were looking at solving this dispersed data problem. Most of my customers had invested in IoT and edge devices, and these devices were gathering massive amounts of data, and on the flip side they also had invested quite a bit of effort in AI and ML and analytics to crunch this data, give them intelligence. But guess what, this data existed in multiple parties, in multiple clouds, in multiple technology stacks, and they needed a mechanism to get this data from wherever they were into one place so they could the AI, ML, analytics investment, and they wanted all of this to be done in real time, and to gravitated towards blockchain. But blockchain had quite a bit of limitations, it was not scalable, it didn't work with the existing stack that you had. It forced enterprises to adopt this new technology and entirely new type of infrastructure. It didn't work cross-cloud unless you hired expensive consultants or did it yourself, and required these specialized developers. For all of these reasons, we've seen many POCs, majority of POCs just dying on the vine and not ever reaching the production potential. So, that is when I realized that what the problem to be solved was not a trust problem, the problem was dispersed data in multiple clouds and multiple stacks problem. Sometimes multiple parties, even, problem. And that's when Tim and I started talking about, about how can we bring all of the nascent qualities of Lambda and Serverless and use all of the features of blockchain and build something together? And he has an interesting story on his own, right. >> Yeah. Yeah, Shruthi, if I could, I'd like to get a little bit of that. So, first of all for our audience, if you're watching this on the minute, probably want to hit pause, you know, go search Tim, go watch a video, read his Medium post, about the past, present, and future of Serverless. But Tim, I'm excited. You and I have talked in the past, but finally getting you on theCUBE program. >> Yeah! >> You know, I've looked through my career, and my background is infrastructure, and the role of infrastructure we know is always just to support the applications and the data that run business, that's what is important! Even when you talk about cloud, it is the applications, you know, the code, and the data that are important. So, it's not that, you know, okay I've got near infinite compute capacity, it's the new things that I can do with it. That's a comment I heard in one of your sessions. You talked about one of the most fascinating things about Serverless was just the new creativity that it inspired people to do, and I loved it wasn't just unlocking developers to say, okay I have new ways to write things, but even people that weren't traditional coders, like lots of people in marketing that were like, "I can start with this and build something new." So, I guess the question I have for you is, you know we had this idea of Platform as a Service, or even when things like containers launched, it was, we were trying to get close to that atomic unit of the application, and often it was talked about, well, do I want it for portability? Is it for ease of use? So, you've been wrangling and looking at this (Tim laughing) from a lot of different ways. So, is that as a starting point, you know, what did you see the last few years with Lambda, and you know, help connect this up to where Shruthi just left off her bit of the story. >> Absolutely. You know, the great story, the great success of the cloud is this elimination of undifferentiated heavy lifting, you know, from getting rid of having to build out a data center, to all the complexity of managing hardware. And that first wave of cloud adoption was just phenomenally successful at that. But as you say, the real thing businesses wrestle with are applications, right? It's ultimately about the business solution, not the hardware and software on which it runs. So, the very first time I sat down with Andy Jassy to talk about what eventually become Lambda, you know, one of the things I said was, look, if we want to get 10x the number of people to come and, you know, and be in the cloud and be successful it has to be 10 times simpler than it is today. You know, if step one is hire an amazing team of distributed engineers to turn a server into a full tolerance, scalable, reliable business solution, now that's going to be fundamentally limiting. We have to find a way to put that in a box, give that capability, you know, to people, without having them go hire that and build that out in the first place. And so that kind of started this journey for, for compute, we're trying to solve the problem of making compute as easy to use as possible. You know, take some code, as you said, even if you're not a diehard programmer or backend engineer, maybe you're just a full-stack engineer who loves working on the front-end, but the backend isn't your focus, turn that into something that is as scalable, as robust, as secure as somebody who has spent their entire career working on that. And that was the promise of Serverless, you know, outside of the specifics of any one cloud. Now, the challenge of course when you talk to customers, you know, is that you always heard the same two considerations. One is, I love the idea of Lamdba, but it's AWS, maybe I have multiple departments or business partners, or need to kind of work on multiple clouds. The other challenge is fantastic for compute, what about data? You know, you've kind of left me with, you're giving me sort of half the solution, you've made my compute super easy to use, can you make my data equally easy to use? And so you know, obviously the part of the genesis of Vendia is going and tackling those pieces of this, giving all that promise and ease of use of Serverless, now with a model for replicated state and data, and one that can cross accounts, machines, departments, clouds, companies, as easily as it scales on a single cloud today. >> Okay, so you covered quite a bit of ground there Tim, if you could just unpack that a little bit, because you're talking about state, cutting across environments. What is it that Vendia is bringing, how does that tie into solutions like, you know, Lamdba as you mentioned, but other clouds or even potentially on premises solutions? So, what is, you know, the IP, the code, the solution that Vendia's offering? >> Happy to! So, let's start with the customer problem here. The thing that every enterprise, every company, frankly, wrestles with is in the modern world they're producing more data than ever, IMT, digital journeys, you know, mobile, edge devices. More data coming in than ever before, at the same time, more data getting consumed than ever before with deep analytics, supply chain optimization, AI, ML. So, even more consumers of ever more data. The challenge, of course, is that data isn't always inside a company's four walls. In fact, we've heard 80% or more of that data actually lives outside of a company's control. So, step one to doing something like AI, ML, isn't even just picking a product or selecting a technology, it's getting all of your data back together again, so that's the problem that we set out to solve with Vendia, and we realized that, you know, and kind of part of the genesis for the name here, you know, Vendia comes from Venn Diagram. So, part of that need to bring code and data together across companies, across tech stacks, means the ability to solve some of these long-standing challenges. And we looked at the two sort of big movements out there. Two of them, you know, we've obviously both been involved in, one of them was Serverless, which amazing ability to scale, but single account, single cloud, single company. The other one is blockchain and distributed ledgers, manages to run more across parties, across clouds, across tech stacks, but doesn't have a great mechanism for scalability, it's really a single box deployment model, and obviously there are a lot of limitations with that. So, our technology, and kind of our insight and breakthrough here was bringing those two things together by solving the problems in each of them with the best parts of the other. So, reimagine the blockchain as a cloud data implementation built entirely out of Serverless components that have all of the scale, the cost efficiencies, the high utilization, like all of the ease of deployment that something like Lambda has today, and at the same time, you know, bring state to Serverless. Give things like Lambda and the equivalent of other clouds a simple, easy, built-in model so that applications can have multicloud, multi-account state at all times, rather than turning that into a complicated DIY project. So, that was our insight here, you know and frankly where a lot of the interesting technology for us is in turning those centralized services, a centralized version of Serverless Compute or Serverless Database into a multi-account, multicloud experience. And so that's where we spent a lot of time and energy trying to build something that gives customers a great experience. >> Yeah, so I've got plenty of background in customers that, you know, have the "information silos", if you will, so we know, when the unstructured data, you know so much of it is not searchable, I can't leverage it. Shruthi, but maybe it might make sense, you know, what is, would you say some of the top things some of your early customers are saying? You know, I have this pain point, that's pointing me in your direction, what was leading them to you? And how does the solution help them solve that problem? >> Yeah, absolutely! One of our design partners, our lead design partners is this automotive company, they're a premier automotive company, they want, their end goal is to track car parts for warranty recall issues. So, they want to track every single part that goes into a particular car, so they're about 30 to 35,000 parts in each of these cars, and then all the way from manufacturing floor to when the car is sold, and when that particular part is replaced eventually, towards the end of the lifecycle of that part. So for this, they have put together a small test group of their partners, a couple of the parts manufacturers, they're second care partners, National Highway Safety Administration is part of this group, also a couple of dealers and service centers. Now, if you just look at this group of partners, you will see some of these parties have high technology, technology backgrounds, just like the auto manufacturers themselves or the part manufacturers. Low modality or low IT-competency partners such as the service centers, for them desktop PCs are literally the IT competency, and so does the service centers. Now, most of, majority of these are on multiple clouds. This particular auto customer is on AWS and manufactures on Azure, another one is on GCP. Now, they all have to share these large files between each other, making sure that there are some transparency and business rules applicable. For example, two partners who make the same parts or similar parts cannot see each other's data. Most of the participants cannot see the PII data that are not applicable, only the service center can see that. National Highway Safety Administration has read access, not write access. A lot of that needed to be done, and their alternatives before they started using Vendia was either use point-to-point APIs, which was very expensive, very cumbersome, it works for a finite small set of parties, it does not scale, as in when you add more participants into this particular network. And the second option for them was blockchain, which they did use, and used Hyperledger Fabric, they used Ethereum Private to see how this works, but the scalability, with Ethereum Private, it's about 14 to 15 transactions per second, with Hyperledger Fabric it taps out at 100, or 150 on a good day, transaction through, but it's not just useful. All of these are always-on systems, they're not Serverless, so just provisioning capacity, our customers said it took them two to three weeks per participant. So, it's just not a scalable solution. With Vendia, what we delivered to them was this virtual data lake, where the sources of this data are on multiple clouds, are on multiple accounts owned by multiple parties, but all of that data is shared on a virtual data lake with all of the permissions, with all of the logging, with all of the security, PII, and compliance. Now, this particular auto manufacturer and the National Highway Safety Administration can run their ML algorithms to gain intelligence off of it, and start to understand patterns, so when certain parts go bad, or what's the propensity of a certain manufacturing unit producing faulty parts, and so on, and so forth. This really shows you this concept of unstructured data being shared between parties that are not, you know, connected with each other, when there are data silos. But I'd love to follow this up with another example of, you know, the democratization, democratization is very important to Vendia. When Tim launched Lambda and founded the AWS Serverless movement as a whole, and at AWS, one thing, very important thing happened, it lowered the barrier to entry for a new wave of businesses that could just experiment, try out new things, if it failed, they scrap it, if it worked, they could scale it out. And that was possible because of the entry point, because of the paper used, and the architecture itself, and we are, our vision and mission for Vendia is that Vendia fuels the next generation of multi-party connected distributed applications. My second design partner is actually a non-profit that, in the animal welfare industry. Their mission is to maintain a no-kill for dogs and cats in the United States. And the number one reason for over populations of dogs and cats in the shelters is dogs lost, dogs and cats lost during natural disasters, like the hurricane season. And when that happens, and when, let's say your dogs get lost, and you want to find a dog, the ID or the chip-reading is not reliable, they want to search this through pictures. But we also know that if you look at a picture of a dog, four people can come up with four different breed names, and this particular non-profit has 2,500 plus partners across the U.S., and they're all low to no IT modalities, some of them have higher IT competency, and a huge turnover because of volunteer employees. So, what we did for them was came up with a mechanism where they could connect with all 2,500 of these participants very easily in a very cost-effective way and get all of the pictures of all of the dogs in all these repositories into one data lake so they can run some kind of a dog facial recognition algorithm on it and identify where my lost dog is in minutes as opposed to days it used to take before. So, you see a very large customer with very sophisticated IT competency use this, also a non-profit being able to use this. And they were both able to get to this outcome in days, not months or years, as, blockchain, but just under a few days, so we're very excited about that. >> Thank you so much for the examples. All right, Tim, before we get to the end, I wonder if you could take us under the hood a little bit here. My understanding, the solution that you talk about, it's universal apps, or what you call "unis" -- >> Tim: Unis? (laughs) >> I believe, so if I saw that right, give me a little bit of compare and contrast, if you will. Obviously there's been a lot of interest in what Kubernetes has been doing. We've been watching closely, you know there's connections between what Kubernetes is doing and Serverless with the Knative project. When I saw the first video talking about Vendia, you said, "We're serverless, and we're containerless underneath." So, help us understand, because at, you know, a super high level, some of the multicloud and making things very flexible sound very similar. So you know, how is Vendia different, and why do you feel your architecture helps solve this really challenging problem? >> Sure, sure, awesome! You know, look, one of the tenets that we had here was that things have to be as easy as possible for customers, and if you think about the way somebody walks up today to an existing database system, right? They say, "Look, I've got a schema, I know the shape of my data." And a few minutes later I can get a production database, now it's single user, single cloud, single consumer there, but it's a very fast, simple process that doesn't require having code, hiring a team, et cetera, and we wanted Vendia to work the same way. Somebody can walk up with a JSON schema, hand it to us, five minutes later they have a database, only now it's a multiparty database that's decentralized, so runs across multiple platforms, multiple clouds, you know, multiple technology stacks instead of being single user. So, that's kind of goal one, is like make that as easy to use as possible. The other key tenet though is we don't want to be the least common denominator of the cloud. One of the challenges with saying everyone's going to deploy their own servers, they're going to run all their own software, they're going to build, you know, they're all going to co-deploy a Kubernetes cluster, one of the challenges with that is that, as Shruthi was saying, first, anyone for whom that's a challenge, if you don't have a whole IT department wrapped around you that's a difficult proposition to get started on no matter how amazing that technology might be. The other challenge with it though is that it locks you out, sort of the universe of a lock-in process, right, is the lock-out process. It locks you out of some of the best and brightest things the public cloud providers have come up with, and we wanted to empower customers, you know, to pick the best degree. Maybe they want to go use IBM Watson, maybe they want to use a database on Google, and at the same time they want to ingest IoT on AWS, and they wanted all to work together, and want all of that to be seamless, not something where they have to recreate an experience over, and over, and over again on three different clouds. So, that was our goal here in producing this. What we designed as an architecture was decentralized data storage at the core of it. So, think about all the precepts you hear with blockchain, they're all there, they all just look different. So, we use a no SQL database to store data so that we can scale that easily. We still have a consensus algorithm, only now it's a high speed serverless and cloud function based mechanism. You know, instead of smart contracts, you write things in a cloud function like Lambda instead, so no more learning Solidity, now you can use any language you want. So, we changed how we think about that architecture, but many of those ideas about people, really excited about blockchain and its capabilities and the vision for the future are still alive and well, they've just been implemented in a way that's far more practical and effective for the enterprise. >> All right, so what environments can I use today for your solution, Shruthi talked about customers spanning across some of the cloud, so what's available kind of today, what's on the roadmap in the future? Will this include beyond, you know, maybe the top five or six hyper scalers? Can I do, does it just require Serverless underneath? So, will things that are in a customer's own data center eventually support that. >> Absolutely. So, what we're doing right now is having people sign up for our preview release, so in the next few weeks, we're going to start turning that on for early access to developers. That'll be, the early access program, will be multi-account, focused on AWS, and then end of summer, well be doing our GA release, which will be multicloud, so we'll actually be able to operate across multiple clouds, multiple cloud services, on different platforms. But even from day one, we'll have API support in there. So, if you got a service, could even be running on a mainframe, could be on-prem, if it's API based you can still interact with the data, and still get the benefits of the system. So, developers, please start signing up, you can go find more information on vendia.net, and we're really looking forward to getting some of that early feedback and hear more from the people that we're the most excited to have start building these projects. >> Excellent, what a great call to action to get the developers and users in there. Shruthi, if you could just give us the last bit, you know, the thing that's been fascinating, Tim, when I look at the Serverless movement, you know, I've talked to some amazing companies that were two or three people (Tim laughing) and out of their basement, and they created a business, and they're like, "Oh my gosh, I got VC funding, and it's usually sub $10,000,000. So, I look at your team, I'd heard, Tim, you're the primary coder on the team. (Tim laughing) And when it comes to the seed funding it's, you know, compared to many startups, it's a small number. So, Shruthi, give us a little bit if you could the speeds and feeds of the company, your funding, and any places that you're hiring. Yeah, we are definitely hiring, lets me start from there! (Tim laughing) We're hiring for developers, and we are also hiring for solution architects, so please go to vendia.net, we have all the roles listed there, we would love to hear from you! And the second one, funding, yes. Tim is our main developer and solutions architect here, and look, the Serverless movement really helped quite a few companies, including us, to build this, bring this to market in record speeds, and we're very thankful that Tim and AWS started taking the stands, you know back in 2014, 2013, to bring this to market and democratize this. I think when we brought this new concept to our investors, they saw what this could be. It's not an easy concept to understand in the first wave, but when you understand the problem space, you see that the opportunity is pretty endless. And I'll say this for our investors, on behalf of our investors, that they saw a real founder market-fit between us. We're literally the two people who have launched and ran businesses for both Serverless and blockchain at scale, so that's what they thought was very attractive to them, and then look, it's Tim and I, and we're looking to hire 8 to 10 folks, and I think we have gotten to a space where we're making a meaningful difference to the world, and we would love for more people to join us, join this movement and democratize this big dispersed data problem and solve for this. And help us create more meanings to the data that our customers and companies worldwide are creating. We're very excited, and we're very thankful for all of our investors to be deeply committed to us and having conviction on us. >> Well, Shruthi and Tim, first of all, congratulations -- >> Thank you, thank you. >> Absolutely looking forward to, you know, watching the progress going forward. Thanks so much for joining us. >> Thank you, Stu, thank you. >> Thanks, Stu! >> All right, and definitely tune in to our regular conversations on Cloud Native Insights. I'm your host Stu Miniman, and looking forward to hearing more about your Cloud Native Insights! (upbeat electronic music)

Published Date : Jul 2 2020

SUMMARY :

and CEO of the company, Great to join the show. and how that lead towards what you and Tim and on the flip side You and I have talked in the past, it is the applications, you know, and build that out in the first place. So, what is, you know, the and at the same time, you know, And how does the solution and get all of the solution that you talk about, and why do you feel your architecture and at the same time they Will this include beyond, you know, and hear more from the people and look, the Serverless forward to, you know, and looking forward to hearing more

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
ShruthiPERSON

0.99+

TimPERSON

0.99+

AWSORGANIZATION

0.99+

2018DATE

0.99+

2014DATE

0.99+

twoQUANTITY

0.99+

TwoQUANTITY

0.99+

80%QUANTITY

0.99+

Shruthi RaoPERSON

0.99+

2019DATE

0.99+

National Highway Safety AdministrationORGANIZATION

0.99+

two partnersQUANTITY

0.99+

National Highway Safety AdministrationORGANIZATION

0.99+

2011DATE

0.99+

2013DATE

0.99+

8QUANTITY

0.99+

BostonLOCATION

0.99+

second optionQUANTITY

0.99+

10 timesQUANTITY

0.99+

StuPERSON

0.99+

VendiaORGANIZATION

0.99+

Stu MinimanPERSON

0.99+

Palo AltoLOCATION

0.99+

Andy JassyPERSON

0.99+

United StatesLOCATION

0.99+

U.S.LOCATION

0.99+

10xQUANTITY

0.99+

oneQUANTITY

0.99+

GoogleORGANIZATION

0.99+

Tim WagnerPERSON

0.99+

two peopleQUANTITY

0.99+

vendia.netOTHER

0.99+

two servicesQUANTITY

0.99+

first videoQUANTITY

0.99+

OneQUANTITY

0.99+

2,500 plus partnersQUANTITY

0.99+

eachQUANTITY

0.99+

firstQUANTITY

0.99+

bothQUANTITY

0.99+

five minutes laterDATE

0.99+

todayDATE

0.98+

100QUANTITY

0.98+

IBMORGANIZATION

0.98+

FirstQUANTITY

0.98+

over 1,092 customersQUANTITY

0.98+

three peopleQUANTITY

0.98+

two thingsQUANTITY

0.98+

AmazonORGANIZATION

0.98+

150QUANTITY

0.98+

AWS LambdaORGANIZATION

0.98+