BJ Jenkins, Palo Alto Networks | Palo Alto Networks Ignite22
>> TheCUBE presents Ignite 22 brought to you by Palo Alto Networks. >> Welcome back to Las Vegas, everyone. We're glad you're with us. This is theCUBE live at Palo Alto Ignite 22 at the MGM Grant in Las Vegas. Lisa Martin here with Dave Vellante, day one of our coverage. We've had great conversations. The cybersecurity landscape is so interesting Dave, it's such a challenging problem to solve but it's so diverse and dynamic at the same time. >> You know, Lisa theCUBE started in May of 2010 in Boston. We called it the chowder event, chowder and Lobster. It was a EMC world, 2010. BJ Jenkins, who's here, of course, was a longtime friend of theCUBE and made the, made the transition into from, well, it's still data, data to, to cyber. So >> True. And BJ is back with us. BJ Jenkins, president Palo Alto Networks great to have you back on theCUBE. >> It is great to be here in person on theCube >> Isn't it great? >> In Vegas. It's awesome. >> And we can tell by your voice will be, will be gentle. You, you've been in Vegas typical Vegas occupational hazard of losing the voice. >> Yeah. It was one of the benefits of Covid. I didn't lose my voice at home sitting talking to a TV. You lose it when you come to Vegas. >> Exactly. >> But it's a small price to pay. >> So things kick off yesterday with the partner summit. You had a keynote then, you had a customer, a CISO on stage. You had a keynote today, which we didn't get to see. But talk to us a little bit about the lay of the land. What are you hearing from CISOs, from CIOs as we know security is a board level conversation. >> Yeah, I, you know it's been an interesting three or four months here. Let me start with that. I think, cybersecurity in general is still front and center on CIOs and CISO's minds. It has to be, if you saw Wendy's presentation today and the threats out there companies have to have it front and center. I do think it's been interesting though with the macro uncertainty. We've taken to calling this year the revenge of the CFO and you know these deals in cybersecurity are still a top priority but they're getting finance and procurements, scrutiny which I think in this environment is a necessity but it's still a, you know, number one number two imperative no matter who you talked to, in my mind >> It was interesting what Nikesh was saying in the last conference call that, hey we just have to get more approvals. We know this. We're, we're bringing more go-to-market people on board. We, we have, we're filling the pipeline 'cause we know they're going to split up deals big deals go into smaller chunks. So the question I have for you is is how are you able to successfully integrate those people so that you can get ahead of that sort of macro transition? >> Yeah I, you know, I think there's two things I'd say about uncertain macro situations and Dave, you know how old I am. I'm pretty old. I've been through a lot of cycles. And in those cycles I've always found stronger companies with stronger value proposition separate themselves actually in uncertain, economic times. And so I think there's actually an opportunity here. The message tilts a little bit though where it's been about innovation and new threat vectors to one of you have 20, 30, 40 vendors you can consolidate become more effective in your security posture and save money on your TCOs. So one of the things as we bring people on board it's training them on that business value proposition. How do you take a customer who's got 20 or 30 tools take 'em down to 5 or 10 where Palo is more central and strategic and be able to demonstrate that value. So we do that through, we're making a huge investment in our people but macroeconomic times also puts some stronger people back on the market and we're able to incorporate them into the business. >> What are the conditions that are necessary for that consolidation? Like I would imagine if you're, if you're a big customer of a big, you know, competitor of yours that that migration is going to be harder than if you're dealing with lots of little point tools. Do those, do those point tools, are they sort of is it the end of the subscription? Is it just stuff that's off the books now? What's, the condition that is ripe for that kind of consolidation? >> Look, I think the challenge coming into this year was skills. And so customers had all of these point products. It required a lot more human intervention as Nikesh was talking about to integrate them or make them work. And as all of us know finding people with cybersecurity skills over the last 12 months has been incredibly hard. That drove, if you know, if you think about that a CIO and a CISO sitting there going, I have all all this investment in tools. I don't have the people to operate 'em. What do I need to do? What we tried to do is elevate that conversation because in a customer, everybody who's bought one of those, they they bought it to solve a problem. And there's people with affinity for that tool. They're not just going to say I want to get consolidated and give up my tool. They're going to wrap their arms around it. And so what we needed to do and this changed our ecosystem strategy too how we leverage partners. We needed to get into the CIO and CISO and say look at this chaos you have here and the challenges around people that it's, it's presenting you. We can help solve that by, by standardizing, consolidating taking that integration away from you as Nikesh talked about, and making it easier for your your high skill people to work on high skill, you know high challenges in there. >> Let chaos reign, and then reign in the chaos. >> Yes. >> Andy Grove. >> I was looking at some stats that there's 26 million developers but less than 3 million cybersecurity professionals. >> Talked about that skills gap and what CISOs and CIOs are facing is do you consider from a value prop perspective Palo Alto Networks to be a, a facilitator of helping organizations deal with that skills gap? >> I think there's a short term and a long term. I think Nikesh today talked about the long term that we'll never win this battle with human beings. We're going to have to win it with automation. That, that's the long term the short term right here and now is that people need people with cybersecurity skills. Now what we're trying to do, you know, is multifaceted. We work with universities to standardize programs to develop skills that people can come into the marketplace with. We run our own programs inside the company. We have a cloud academy program now where we take people high aptitude for sales and technical aptitude and we will put them through a six month boot camp on cloud and they'll come out of that ready to really work with the leading experts in cloud security. The third angle is partners, right, there are partners in the marketplace who want to drive their business into high services areas. They have people, they know how to train. We give them, we partner with them to give them training. Hopefully that helps solve some of the short-term gaps that are out there today. >> So you made the jump from data storage to security and >> Yeah. >> You know, network security, all kinds of security. What was that like? What you must have learned a lot in the last better part of a decade? >> Yeah. >> Take us through that. >> You know, so the first jump was from EMC. I was 15 years there to be CEO of Barracuda. And you know, it was interesting because EMC was, you know large enterprise for the most part. At Barracuda we had, you know 250,000 small and mid-size enterprises. And it was, it's interesting to get into security in small and mid-size businesses because, you know Wendy today was talking about nation states. For small and mid-size business, it's common thievery right? It's ransomware, it's, and, those customers don't have, you know, the human and financial resources to keep up with the threat factor. So, you know, Nikesh talked about how it's taken 'em four and a half years to get into cybersecurity. I remember my first week at Barracuda, I was talking with a customer who had, you know, breached data shut down. There wasn't much bitcoin back then so it was just a pure ransom. And I'm like, wow, this is, you know, incredible industry. So it's been a good, you know, transition for me. I still think data is at the heart of all of this. Right? And I have always believed there's a strong connection between the things I learned growing up at EMC and what I put into practice today at Palo Alto Networks. >> And how about a culture because I, you know I know have observed the EMC culture >> Yeah. >> And you were there in really the heyday. >> Yeah. >> Right? Which was an awesome place. And it seems like Palo Alto obviously, different times but you know, similar like laser focus on solving problems, you know, obviously great, you know value sellers, you know, you guys aren't the commodity >> Yeah. For Product. But there seemed to be some similarities from afar. I don't know Palo Alto as well as I know EMC. >> I think there's a lot. When I joined EMC, it was about, it was 2 billion in in revenue and I think when I left it was over 20, 20, 21. And, you know, we're at, you know hopefully 5, 5 5 in revenue. I feel like it's this very similar, there's a sense of urgency, there's an incredible focus on the customer. you know, Near and Moche are definitely different individuals but the both same kind of disruptive, Israeli force out there driving the business. There are a lot of similarities. I, you know, the passion, I feel privileged as a, you know go to market person that I have this incredible portfolio to go, you know, work with customers on. It's a lucky position to be in, but very I feel like it is a movie I've seen before. >> Yeah. And but, and the course, the challenges from the, the target that you're disrupting is different. It was, you know, EMC had a lot of big, you know IBM obviously was, you know, bigger target whereas you got thousands of, you know, smaller companies. >> Yes. >> And, and so that's a different dynamic but that's why the consolidation play is so important. >> Look at, that's why I joined Palo Alto Networks when I was at Barracuda for nine years. It just fascinated me, that there was 3000 plus players in security and why didn't security evolve like the storage market did or the server market or network where working >> Yeah, right. >> You know, two or three big gorillas came to, to dominate those markets. And it's, I think it's what Nikesh talked about today. There was a new problem in best of breed. It was always best of breed. You can never in security go in and, you know, say, Hey it's good I saved us some money but I got the third best product in the marketplace. And there was that kind of gap between products. I, believe in why I joined here I think this is my last gig is we have a chance to change that. And this is the first company as I look from the outside in that had best of breed as, you know Nikesh said 13 categories. >> Yeah. >> And you know, we're in the leaders quadrant and it's a conversation I have with customers. You don't have to sacrifice best of breed but get the benefits of a platform. And I, think that resonates today. I think we have a chance to change the industry from that viewpoint. >> Give us a little view of the voice of the customer. You had, was it Sabre? >> Yeah. >> That was on >> Scott Moser, The CISO from Sabre. >> Give us a view, what are you hearing from the voice of the customer? Obviously they're quite a successful customer but challenges, concerns, the partnership. >> Yeah. Look, I think security is similar to industries where we come up with magic marketing phrases and, you know, things to you know, make you want to procure our solutions. You know, zero trust is one. And you know, you'll talk to customers and they're like, okay, yes. And you know, the government, right? Joe, Joe Biden's putting out zero trust executive orders. And the, the problem is if you talk to customers, it's a journey. They have legacy infrastructure they have business drivers that you know they just don't deal with us. They've got to deal with the business side who's trying to make the money that keeps the, the company going. it's really helped them draw a map from where they're at today to zero trust or to a better security architecture. Or, you know, they're moving their apps into the cloud. How am I going to migrate? Right? Again, that discussion three years ago was around lift and shift, right? Today it's about, well, no I need cloud native developed apps to service the business the way I want to, I want to service it. How do I, so I, I think there's this element of a trusted partner and relationship. And again, I think this is why you can't have 40 or 50 of those. You got to start narrowing it down if you want to be able to meet and beat the threats that are out there for you. So I, you know, the customers, I see a lot of 'em. It's, here's where I'm at help me get here to a better position. And they know it's, you know Scott said in our keynote today, you don't just, you know have layer three firewall policies and decide, okay tomorrow I'm going to go to layer seven. That, that's not how it works. Right? There's, and, and by the way these things are a mission critical type areas. So there's got to be a game plan that you help customers go through to get there. >> Definitely. Last question, my last question for you is, is security being a board level conversation I was reading some stats from a survey I think it was the what's new in Cypress survey that that Palo Alto released today that showed that while significant numbers of organizations think they've got a cyber resiliency playbook, there's a lot of disconnect or lack of alignment at the boardroom. Are you in those conversations? How can you help facilitate that alignment between the executive team and the board when it comes to security being so foundational to any business? >> Yeah, it's, I've been on three, four public company boards. I'm on, I'm on two today. I would say four years ago, this was a almost a taboo topic. It was a, put your head in the sand and pray to God nothing happened. And you know, the world has changed significantly. And because of the number of breaches the impact it's had on brand, boards have to think about this in duty of care and their fiduciary duty. Okay. So then you start with a board that may not have the technical skills. The first problem the security industry had is how do I explain your risk profile in a way you can understand it. I'm, I'm on the board of Generac that makes home generators. It's a manufacturing, you know, company but they put Wifi modules in their boxes so that the dealers could help do the maintenance on 'em. And all of a sudden these things were getting attacked. Right? And they're being used for bot attacks. >> Yeah. >> Everybody on their board had a manufacturing background. >> Ah. >> So how do you help that board understand the risk they have that's what's changed over the last four years. It's a constant discussion. It's one I have with CISOs where they're like help us put it in layman's terms so they understand they know what we're doing and they feel confident but at the same time understand the marketplace better. And that's a journey for us. >> That Generac example is a great one because, you know, think about IOT Technologies. They've historically been air gaped >> Yes. >> By design. And all of a sudden the business comes in and says, "Hey we can put wifi in there", you know >> Connect it to a home Wifi system that >> Make our lives so much easier. Next thing you know, it's being used to attack. >> Yeah. >> So that's why, as you go around the world are you discerning, I know you were just in Japan are you discerning significant differences in sort of attitudes toward, towards cyber? Whether it's public policy, you know things like regulation where you, they don't want you sharing data, but as as a cyber company, you want to share that data with you know, public and private? >> Look it, I, I think around the world we see incredible government activity first of all. And I think given the position we're in we get to have some unique conversations there. I would say worldwide security is an imperative. I, no matter where I go, you know it's in front of everybody's mind. The, on the, the governance side, it's really what do we need to adapt to make sure we meet local regulations. And I, and I would just tell you Dave there's ways when you do that, and we talk with governments that because of how they want to do it reduce our ability to give them full insight into all the threats and how we can help them. And I do think over time governments understand that we can anonymize the data. There's, but that, that's a work in process. Definitely there is a balance. We need to have privacy, we need to have, you know personal security for people. But there's ways to collect that data in an anonymous way and give better security insight back into the architectures that are out there. >> All right. A little shift the gears here. A little sports question. We've had some great Boston's sports guests on theCUBE right? I mean, Randy Seidel, we were talking about him. Peter McKay, Snyk, I guess he's a competitor now but you know, there's no question got >> He got a little funding today. I saw that. >> Down round. But they still got a lot of money. Not of a down round, but they were, but yeah, but actually, you know, he was on several years ago and it was around the time they were talking about trading Brady. He said Never trade Brady. And he got that right. We, I think we can agree Brady's the goat. >> Yes. >> The big question I have for you is, Belichick. Do you ever question Has your belief in him as the greatest coach of all time wavered, you know, now that- No. Okay. >> Never. >> Weigh in on that. >> Never, he says >> Still the Goat. >> I'll give you my best. You know, never In Bill we trust. >> Okay. Still. >> All right >> I, you know, the NFL is a unique property that's designed for parody and is designed, I mean actively designed to not let Mr. Craft and Bill Belichick do what they do every year. I feel privileged as a Boston sports fan that in our worst years we're in the seventh playoff spot. And I have a lot of family in Chicago who would kill for that position, by the way. And you know, they're in perpetual rebuilding. And so look, and I think he, you know the way he's been able to manage the cap and the skill levels, I think we have a top five defense. There's different ways to win titles. And if I, you know, remember in Brady's last title with Boston, the defense won us that Super Bowl. >> Well thanks for weighing in on that because there's a lot of crazy talk going on. Like, 'Hey, if he doesn't beat Arizona, he's got to go.' I'm like, what? So, okay, I'm sometimes it takes a good good loyal fan who's maybe, you know, has >> The good news in Boston is we're emotional fans too so I understand you got to keep the long term long term in mind. And we're, we're in a privileged position in Boston. We've got Celtics, we've got Bruins we've got the Patriots right on the edge of the playoffs and we need the Red Sox to get to work. >> Yeah, no, you know they were last, last year so maybe they're going to win it all like they usually do. So >> Fingers crossed. >> Crazy worst to first. >> Exactly. Well you said, in Bill we trust it sounds like from our conversation in BJ we trust from the customers, the partners. >> I hope so. >> Thank you so much BJ, for coming back on theCUBE giving us the lay of the land, what's new, the voice of the customer and how Palo Alto was really differentiated in the market. We always appreciate your, coming on the show you >> Honor and privilege seeing you here. Thanks. >> You may be thinking that you were watching ESPN just now but you know, we call ourselves the ESPN at Tech News. This is Lisa Martin for Dave Vellante and our guest. You're watching theCUBE, the Leader and live emerging in enterprise tech coverage. (upbeat music)
SUMMARY :
brought to you by Palo Alto Networks. Alto Ignite 22 at the MGM Grant We called it the chowder great to have you back on theCUBE. It's awesome. hazard of losing the voice. You lose it when you come to Vegas. You had a keynote then, you had the revenge of the CFO and you know So the question I have for you is Yeah I, you know, I think of a big, you know, competitor of yours I don't have the people to operate 'em. Let chaos reign, and I was looking at some stats you know, is multifaceted. What you must have learned a lot And you know, it was interesting And you were there but you know, similar like laser focus there seemed to be some portfolio to go, you know, a lot of big, you know And, and so that's a different dynamic like the storage market did in and, you know, say, Hey And you know, we're the voice of the customer. Give us a view, what are you hearing And you know, the government, right? How can you help facilitate that alignment And you know, the world Everybody on their but at the same time understand you know, think about IOT Technologies. we can put wifi in there", you know Next thing you know, it's we need to have, you know but you know, there's no question got I saw that. but actually, you know, he was of all time wavered, you I'll give you my best. And if I, you know, remember good loyal fan who's maybe, you know, has so I understand you got Yeah, no, you know they worst to first. Well you coming on the show you Honor and privilege seeing you here. but you know, we call ourselves
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Dave Vellante | PERSON | 0.99+ |
Randy Seidel | PERSON | 0.99+ |
BJ Jenkins | PERSON | 0.99+ |
Bill Belichick | PERSON | 0.99+ |
Red Sox | ORGANIZATION | 0.99+ |
BJ | PERSON | 0.99+ |
Vegas | LOCATION | 0.99+ |
Lisa Martin | PERSON | 0.99+ |
Brady | PERSON | 0.99+ |
20 | QUANTITY | 0.99+ |
40 | QUANTITY | 0.99+ |
Scott | PERSON | 0.99+ |
EMC | ORGANIZATION | 0.99+ |
Dave | PERSON | 0.99+ |
Joe | PERSON | 0.99+ |
Chicago | LOCATION | 0.99+ |
Patriots | ORGANIZATION | 0.99+ |
Boston | LOCATION | 0.99+ |
Scott Moser | PERSON | 0.99+ |
50 | QUANTITY | 0.99+ |
Palo Alto Networks | ORGANIZATION | 0.99+ |
Celtics | ORGANIZATION | 0.99+ |
IBM | ORGANIZATION | 0.99+ |
two | QUANTITY | 0.99+ |
May of 2010 | DATE | 0.99+ |
Andy Grove | PERSON | 0.99+ |
Las Vegas | LOCATION | 0.99+ |
Barracuda | ORGANIZATION | 0.99+ |
three | QUANTITY | 0.99+ |
Joe Biden | PERSON | 0.99+ |
2010 | DATE | 0.99+ |
Sabre | ORGANIZATION | 0.99+ |
250,000 | QUANTITY | 0.99+ |
tomorrow | DATE | 0.99+ |
last year | DATE | 0.99+ |
2 billion | QUANTITY | 0.99+ |
thousands | QUANTITY | 0.99+ |
15 years | QUANTITY | 0.99+ |
nine years | QUANTITY | 0.99+ |
six month | QUANTITY | 0.99+ |
today | DATE | 0.99+ |
30 | QUANTITY | 0.99+ |
Generac | ORGANIZATION | 0.99+ |
Belichick | PERSON | 0.99+ |
Japan | LOCATION | 0.99+ |
Wendy | PERSON | 0.99+ |
yesterday | DATE | 0.99+ |
Peter McKay | PERSON | 0.99+ |
Nikesh | ORGANIZATION | 0.99+ |
Today | DATE | 0.99+ |
21 | QUANTITY | 0.99+ |
13 categories | QUANTITY | 0.99+ |
Super Bowl | EVENT | 0.99+ |
Craft | PERSON | 0.99+ |
ESPN | ORGANIZATION | 0.99+ |
Palo Alto | ORGANIZATION | 0.99+ |
two things | QUANTITY | 0.99+ |
four and a half years | QUANTITY | 0.99+ |
Palo Alto | LOCATION | 0.99+ |
four months | QUANTITY | 0.99+ |
Boston | ORGANIZATION | 0.99+ |
third angle | QUANTITY | 0.98+ |
Arizona | ORGANIZATION | 0.98+ |
30 tools | QUANTITY | 0.98+ |
one | QUANTITY | 0.98+ |
BJ Jenkins, Barracuda Networks | Microsoft Ignite 2019
>>Live from Orlando, Florida. It's the cube covering Microsoft ignite brought to you by Cohesity. >>Good afternoon everyone and welcome back to the cubes live coverage of Microsoft ignite. We are wrapping up three days of wall to wall coverage. Back to back interviews. I'm your host Rebecca Knight, alongside my cohost Stu Miniman. We have saved the best for last. We have BJ Jenkins, president and CEO of Barracuda networks. Thank you so much for coming on the cube. Feel a lot of pressure on internet. It's going to be great. Why don't you start by Barracuda. I think of that heartsong tell our viewers a little bit about, about your business, what you do. >>Yeah. Um, Barracuda is a company focused in the security industry, primarily on email security and network and application security. Uh, we have over 220,000 customers, uh, since we were founded a little over 15 years ago. And um, you know, we have a passion for making our customers secure and safe and being able to run their business. And we're a great partner in Microsoft, so, uh, they really help us drive our business. >>Yeah. So, so much to catch up, PJ, since it's been many years since you've been on the program, you were new in the role, but let's start with that Microsoft relationship here. We've been spending all week talking through all of the various environments. Talk about a little bit about your joint customers, the relationship and what's happening there. >>Yeah. I joined Barracuda seven years ago. Yesterday was my anniversary. And um, when I came into Barracuda, it was primarily at the time focused on a kind of small and midsize businesses. And most of those businesses ran Microsoft exchange or ran some form of Microsoft applications. And really that was the start of our partnership, realizing how important Microsoft was and it's grown. We were the first, uh, security company to put our firewalls in Azure. And that was over five years ago. And I think being first with a partner like Microsoft who is really at that point trying to catch up with Amazon and you know, Satya was, we're starting to drive the business in that direction. Uh, it gave us a unique vantage point in the partnership and it's grown from there. We were, uh, the Azure partner the year in 2016, uh, across their business. Um, we do joint development with them. We do joint go to market activities. And when you look around and you see 30,000 customers here, it's a, it's a good, good place to focus for a company like ourselves. >>Yeah. Well the, the, the changes in Microsoft business has had a ripple effect in the ecosystem, not only the launch of Azure, but I mean a big push office three 65 you talk about there's gotta be a difference between I'm rolling out exchange servers and well, it's all in the cloud. We know that customers still need to think sick as strong about security when they go to SAS Deere. If your customers figured that out yet. >>Yeah. I think, um, the trends that played out on prom play out in the cloud, um, how am I gonna secure my applications? How am I going to secure my data, my network? Um, and then the individuals that are using that cause at the end of the day, the individuals tend to be the weakest link in the security chain. And, um, you know, Mike, what I like is Microsoft has done a really good job improving their security posture, the base level that they provide to their customers every single day improves. And our job is to innovate on top of that and make them even safer. And, um, Microsoft's position in the industry too has been one where they want to be a ecosystem. They want to partner with third parties to help their customers move from on prem into Azure. And they know they're not gonna be able to do it on their own. >>So they've upped their game. We've got to up our game and we do it jointly, which is the nice thing. I, I joke with people. When I was at EMC and I used to go to Redmond, I'd go with battle armor on because there was not gonna be a fun meeting, uh, who's going to be, how Microsoft was going to hurt our business. And now I go to Redmond and you're embraced as a partner. They want to understand what customers and partners are thinking. They jointly plan with you. It's a completely different tone and tenor, which has been nice for us. >>So it is a scary world out there. And as we know that the threat environment is changing, hackers are becoming more sophisticated. I wonder if you could just set the scene for our viewers and just talk about security challenges in general and then we'll get into the specifics of the new solutions that you've announced here. >>Yeah, it's, threats come from everywhere and I think it's hard to boil it down and make it simple at times. But one of the stories I tell, uh, investors and customers about how fast the world is changing, uh, when I came on board, CEO's are obviously targets for hackers and the types of phishing mails I would get at that point. Um, and they would be very obvious. I've gone by BJ my entire life. On the website it says William Jenkins. And so the phishing emails would come in and say, you know, today fog, no, Hey, can you wire money here, William? Right. And so there was just base level intelligence. Nowadays they use LinkedIn, they use fee, they create social graphs. They study your communication forms, they look, they know how you're organized and they target the people. It will have, I always signed my emails past comma, BJ, the best fishing males have that in there. >>They've discovered that they've incorporated that they, so the, just the level of intelligence, the sophistication of what hackers do today, uh, has exponentially changed. And, you know, we're fortunate you can, we have more computing power. We have more artificial intelligence that we can apply to stop them. But the game just keeps getting escalated. And it's a, it's why the security industry has been strong. It's why there's so many companies out there. We've got to keep getting better. Um, but it's, it's a scary world. It's, it's, you know, you can never, never rest and never think you're ahead. You always gotta keep attacking it. >>So BJ, you had a number of announcements. Barracuda did, not nearly as many as Microsoft did, but give us the highlights if you would. >>Yeah. Um, so a number number of things announced here. Uh, first we're part of, uh, Misa, the Microsoft intelligence security association. So we're proud, proud to be a part of that. At launch. Um, we announced, uh, the cloud application platform security platform and the big announcement for us around that was our launch of as a service, uh, that's run on Azure. And, uh, we've always had a strong application approach. We've got integrated, um, detection, DDoSs uh, the O OS top 20 are all in Kurt corporate into our platform. What we've done is really leveraged Microsoft scale to run a very easy, simple to deploy a web application security platform, uh, that takes advantage of Microsoft scale and resiliency and brings that to our customers. Uh, we did a study, you know, only 10% of the websites in the world today are protected. So 90% of the web sites and web applications in the world today run on protected. >>We think this is a great way to go out and, um, help protect more of those. And then finally, um, you know, we announced Microsoft announced their V land solution and we have done joint development with them. We'll continue to innovate here, but we announced obviously our solution that we'll run, uh, with Microsoft's B when we're the only ones who can provide a customer really with multiple lengths run on Microsoft backbone, they can really run their data center. Now the corporate data center out of Azure, uh, we give them traffic prioritization, fail over resiliency that customers need when they're making those types of decisions. So there was more than that, but that was a lot of good stuff for us. We're excited about it. >>What does the recent announcement that Microsoft has won the Jetta contract, does that have any impact on Barracuda's business? Is that, >>well, I think anytime Microsoft wins business, it's a good thing because we're partnering with them. That contract is so big and, uh, has a lot of different elements and, and certainly security is a part of it. So we think there's aspects where we can play. I did hear, I think, um, Oracle was suing and I think AWS, so this may have a lot of legs before it becomes real. But it, I, you know, I think it continues to show that customers want to utilize, um, the scale breadth and depth of solutions that the cloud companies are bringing. And, you know, we view that as opportunity because security is an important element to making that work for those customers. >>So PJ, one to put aside the Microsoft stuff for a second here, since last we talk barracudas gone private and the security industry feels like it just growing so fast. You know, every week we're getting approached by new startups, heavy investment and the like, give us a little bit about your position has a CIO and CEO in this space. Uh, and you know, the love, a little bit of a note. We know it happened a few years back now, but going private when so many companies have, >>yeah, they're, you know, obviously there's a lot of funded companies in the security market. You know, we were in, uh, we had been public for, for four years. Um, a company that's been around 15 years where we were a profitable security company to, we were unique. We weren't, uh, the high flyer growth, but we were growing, you know, kind of, uh, low double digits with profitability, but there were investments that needed to be made in the business. Uh, we were running our transaction system on code, the founder wrote. Um, so there were investments we really needed to make to go from, you know, the 400, 500 million Mark to 1 billion mark. And so going private with a partner like Thoma Bravo, um, who really understands this industry has allowed us to reset the strategy and focus on, uh, the highest growth areas for us, which are email and network and application security. >>Um, they've helped us, we've invested over 20 million in internal systems, um, modern systems, Salesforce, NetSuite, uh, that we think give us the foundational elements to scale to $1 billion. And, um, you know, they combine that with operational expertise that they bring in to help us get more customers to the 220,000. Uh, one of the other interesting things for us too is, um, well we have 220,000 customers. We have 50 of the fortune 100. We have 250 of the fortune 1000 and as the movement, as, as customers have move to cloud, our solutions have become more relevant for customers of scale. And so they've given us the backing really to make that transition into that. So I liked not having to go on public conference calls every quarter. That's been a really nice thing. Um, but they've been a great partner for us. So we've, I think what you can think of us as we focused on areas that we think are the highest priority to our customers. >>Yeah, PJ, it also, we talked about there's so many startups in this space out there. The profile security keeps getting raised. Pat Gelsinger, VMware, you know, pounding the table saying that security needs to do over the, he just purchased black Boston based company that was public. You know, I talked to my friends that had been deep in the security industry and they scoff a little bit about, you know, we've been doing this for a long time. Barracuda is a company that has been around for quite a number of years. How's the industry doing? What do we need to do better? And how do you look at that landscape? >>Yeah, I, you know, I love pats energy and vigor, but there's no silver bullet that's gonna solve every problem out there. I do think, uh, where the industry is getting better is one on sharing information. You can see alliances, associations that have been formed. Um, you know, even with the cloud providers, we're actively sharing information and sharing of that information. We'll make more robust solutions first. Um, second you're seeing vendors go more towards platform where they're offering a larger, so the, the quality of solutions are getting better. And I do think there's consolidation happening where there, there are going to be certain segments of the market where you don't need 15 solutions. You really need, you know, one not from a particular player. So I think you'll see more, uh, consolidation occur around that. And you know, certainly that's been a trend we've been on in terms of integrating our solutions, making them easier to deploy and use for the customers. And then, you know, I think the last part of this is regulation is really a, it's still behind, but it's finally catching up and there's an interest in it. And I think in partnership with the industry, we can get our customers in a better position, a better security posture. So, you know, I, um, there will be consolidation over over time. Uh, you know, I've seen a map, I think there's 3000 security companies in all different segments that won't last forever. And, uh, it'll get easier for customers over time, is my belief. >>So with regulation, do you want to work in partnership with regulators? I mean, how do you, to help them understand the industry first of all and understand the dangers and the risks? I mean, how do you see the future of regulation for this industry? >>First of all, there's a large education process for legislators in general. You have to look no further than when Mark Zuckerberg got questioned by Congress. And the questions he were getting asked were not the best questions. Um, but you do have people who understand this industry and you can look at regulations like GDPR. You know, California's coming out data privacy law now and they're never perfect, but they're good foundational elements to start. And they're helping customers, um, get more aware of what they have to do to be secure and they're helping us explain to customers the things you can do to be in a better security posture. And so there's a continuum around this. We're in the early days, I, there's still a lot of education that has to go on, but when you see, >>start getting passed, it's a good step in the right direction. And by my estimation, BJ, we did save the best for last. Thank you so much for coming on the cube. That was terrific. Sorry it took so long. I'm Rebecca and I first two minutes and that wraps up three days of coverage at Microsoft ignite at the cube. Thank you so much for tuning in and we will see you next time.
SUMMARY :
Microsoft ignite brought to you by Cohesity. Thank you so much for coming on the cube. And um, you know, we have a passion for you were new in the role, but let's start with that Microsoft relationship here. like Microsoft who is really at that point trying to catch up with Amazon and you know, not only the launch of Azure, but I mean a big push office three 65 you talk about there's gotta And, um, you know, Mike, what I like is Microsoft And now I go to Redmond and you're embraced as a partner. I wonder if you could just set the scene for our viewers and just talk And so the phishing emails would come in and say, you know, today fog, And, you know, we're fortunate you can, So BJ, you had a number of announcements. Uh, we did a study, you know, only 10% of the websites in the world today are protected. And then finally, um, you know, we announced Microsoft announced their V land solution And, you know, we view that as opportunity Uh, and you know, the love, needed to make to go from, you know, the 400, 500 million Mark And, um, you know, in the security industry and they scoff a little bit about, you know, we've been doing this for a long time. And then, you know, I think the last part of this is regulation is really a, there's still a lot of education that has to go on, but when you see, Thank you so much for coming on the cube.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Rebecca Knight | PERSON | 0.99+ |
Microsoft | ORGANIZATION | 0.99+ |
BJ Jenkins | PERSON | 0.99+ |
Amazon | ORGANIZATION | 0.99+ |
Rebecca | PERSON | 0.99+ |
Mark Zuckerberg | PERSON | 0.99+ |
AWS | ORGANIZATION | 0.99+ |
2016 | DATE | 0.99+ |
$1 billion | QUANTITY | 0.99+ |
50 | QUANTITY | 0.99+ |
Pat Gelsinger | PERSON | 0.99+ |
Congress | ORGANIZATION | 0.99+ |
Oracle | ORGANIZATION | 0.99+ |
90% | QUANTITY | 0.99+ |
Mike | PERSON | 0.99+ |
William | PERSON | 0.99+ |
BJ | PERSON | 0.99+ |
15 solutions | QUANTITY | 0.99+ |
30,000 customers | QUANTITY | 0.99+ |
Orlando, Florida | LOCATION | 0.99+ |
250 | QUANTITY | 0.99+ |
first | QUANTITY | 0.99+ |
Stu Miniman | PERSON | 0.99+ |
four years | QUANTITY | 0.99+ |
Barracuda | ORGANIZATION | 0.99+ |
VMware | ORGANIZATION | 0.99+ |
over 220,000 customers | QUANTITY | 0.99+ |
10% | QUANTITY | 0.99+ |
three days | QUANTITY | 0.99+ |
Yesterday | DATE | 0.99+ |
GDPR | TITLE | 0.99+ |
220,000 customers | QUANTITY | 0.99+ |
1 billion | QUANTITY | 0.99+ |
ORGANIZATION | 0.98+ | |
seven years ago | DATE | 0.98+ |
today | DATE | 0.98+ |
Barracuda Networks | ORGANIZATION | 0.98+ |
William Jenkins | PERSON | 0.98+ |
Redmond | LOCATION | 0.98+ |
over 20 million | QUANTITY | 0.98+ |
Misa | ORGANIZATION | 0.97+ |
one | QUANTITY | 0.97+ |
first two minutes | QUANTITY | 0.96+ |
Satya | PERSON | 0.96+ |
220,000 | QUANTITY | 0.96+ |
First | QUANTITY | 0.96+ |
Boston | LOCATION | 0.95+ |
around 15 years | QUANTITY | 0.94+ |
over 15 years ago | DATE | 0.94+ |
Azure | TITLE | 0.93+ |
Bravo | PERSON | 0.93+ |
3000 security companies | QUANTITY | 0.92+ |
Jetta | ORGANIZATION | 0.9+ |
Microsoft intelligence | ORGANIZATION | 0.9+ |
NetSuite | ORGANIZATION | 0.88+ |
PJ | PERSON | 0.87+ |
over five years ago | DATE | 0.87+ |
EMC | ORGANIZATION | 0.87+ |
20 | QUANTITY | 0.86+ |
400, 500 million Mark | QUANTITY | 0.84+ |
Katie Jenkins, Liberty Mutual | AWS re:Inforce 2019
>> live from Boston, Massachusetts. It's the Cube covering A W s reinforce 2019 brought to you by Amazon Web service is and its ecosystem partners. >> Welcome back to the cubes. Live coverage here in Boston, Massachusetts, for AWS reinforce Amazon web services. First inaugural conference around Cloud Security. I'm John for your Michael's Day. Volante, our next Katie Jenkins s V P. C. Vice President. See? So, Chief Information Security officer with Liberty Mutual Big Company, Lot of activity insurance. Lot of probably a lot of action on your side. Welcome to the Cube. Thanks. Thanks for coming on. So you've been in this job for about a year. Tell us about what's going on in Libya. Means you guys have a large company. 100 plus years old. You're see. So you're in charge. You're running everything. We're gonna security conference. Tell us the reality. What's going on in the real world? >> Yeah, well, this is super exciting. That reinforce, of course, is in Boston. This is Liberty Mutual's hometown assed. You mentioned 107 year old security, not security company >> insurance company. But we're >> doing really cool things in technology and security. Specifically, um, I would say to kind of bring this gathering together. We have a really rich pool of security talent of security and innovators. It really matches up with what what we're doing. So Liberty Mutual has made a very significant commitment to moving to the public cloud for our technology and computing needs. We're in about your three of that journey, maybe 25% of our workload in the public cloud. It's really been a catalyst for not just transforming our technology organisation but transforming the way security does its work in the way security engages with our development community. >> While you're the head honchos, they say there's a C so but you had 20 plus years in cyber security. This is now kind of a new category with reinforced being a branded show over AWS. I see this deserves its own conversation, and industry is a lot of action going on. What is cloud security mean to you? Because this is the focus of this show. It's not just pure clouds, a lot on premise and on cloud interactions with hybrid etcetera. You guys have been doing tons of I t over the generations with Liberty Mutual, but cloud security is the focus. What does that mean? Thio to? You guys have a cyber security standpoint? >> Yeah, um, in a word. Enablement, um, I think that the public cloud offers us, um, really interesting opportunity to reinvent security. Right? So if you think about all of the technologies and processes and many of which were manual over the years, I think we have an opportunity to leverage automation to make our work easier in some ways to to, um, avoid the situation where we have air oversight. Gosh, we encrypted everything, but you know, this set of assets over here, So through using automation and enforcement, it's a new, exciting opportunity to further develop our security capabilities. But also, you know, cloud security at cloud in general has bred a transformation of the way that are practitioners do work through agile. And it means that security has toe no work with our technologists in a different way. >> So you've had a really interesting background. Um you work for a company that does audits. I can infer from that. You've worked for service is company. You work for a technology vendor. You worked as a practitioner. So you've seen it all sides and you know Amazon. It made some comments yesterday that said, Look, the narrative in the security industry has always been fear, fear, fear. And we'd like to put forth forth the narrative. That is about Listen, the state of security is really good and strong. The union is strong and we're gonna work together in a positive message. So my question is, are you an optimist? >> Ah, a reluctant activist. Um, I think the days of having security be something that's fearful, uh are just not not doing us any any any justice in that area. I mean, security is an area of partnership. There's very little of what we do. Insecurity. It's just done by security practitioners. We need asset managers. We need compliance people. We need the privacy team. We need our auditors way. Need procurement. I mean, there's just so many different parties involved in security that if we're just instilling fear and everyone, I think it'll be difficult for us tow. Get that partnership and we need Thio. Empower people, right. We need Thio. Both empower our developers to do their work in a secure manner and we have to empower our whole workforce and our trusted third parties to make good decisions. We're educating them on how to prevent phishing attacks were doing all sorts of kind of culture based initiatives, recognizing that if it's just the security folks doing security, we're gonna have a big gap. >> One of the things that we were discussing a lot of other C. So So we've been talking privately. Off the record in the hallways and private briefings is the common theme of integration as a big part of dealing with ecosystem, either suppliers and or different teams within their different pillars of how they're organized internally and externally, and then also reducing the number of security vendors that they've been buying products from to get some also in house coding, teams working more closely on the use cases that matter. So this has become kind of ah, see, So a conversation where what? What is that criteria? How do you figure out who to have a suppliers who's gonna be around for the long haul? We're gonna be that a partnership for the enablement. So rather than having hundreds of vendors, we want to get him down to a handful. Is that something that you think about or is it a trend that you see it's happening now? >> Uh, it is a trend. I think it starts at how we even procure in select our suppliers. I mean, we're really giving a lot of thought to the area of third party risk management. And do we understand not just the elements of cyber risk and engaging with 1/3 party? But but privacy and continuity kind of risk, too. So it starts there. I don't have a sort of fabricated number in terms of I'm trying to go from X number of vendors down toe Why? But I think that there's a very purposeful thought process that we're undergoing to say, Yeah, we recognize and for certain technologies, we want to have different providers to provide some of that redundancy. Let's be smart about them. Let's make sure we really understand where those overlapping capabilities are because we don't want to be wasteful either. Right >> on the span, the question comes up to around Devil's because what we're seeing is the devil ops and security paradigms kind of coming together in terms of the concepts agility. You could do some prototyping, a hackathon do some things and then ultimately trying to get into production or two different animals. So that enablement of doing innovative things, his agility, that that's been a key theme, a positive theme. And the question is, is there a funding model? Doesn't automatically get security funding. And where's the spin that you're spending going up? So all the monetary spend questions come up. >> How do you >> deal with that ballistically? And how do you think about, you know, spend conversation? >> Yeah, um, >> it's a really interesting one, because, of course, expense >> pressures. I'm not immune to those. But I >> also think that we're in a position where, um, our executive leadership team understands the value of the work that we're doing understands the important to our policy holders. So it's less often a need to justify why we need more spend. It's a demonstration of using that spend responsibly and understanding where we might have an uplift from something that we automated to say. Well, now we have these resource is that could be doing something else. >> There's >> always something else and security, right? So if we're committed to re Skilling and making sure that people are evolving the work that they do in the talents that they have to adjust a different kind of >> no rule of thumb per se. It's more of your management recognizes the criticality of it. Therefore, you could make those calls on your own building built in building, >> project tough questions and making >> responsible decisions. But I think it comes down and knowing your technology, >> so the skills gap, obviously a huge challenge in your industry would talk to somebody else, they said. We just can't find people, so we have to bring him in and train them ourselves. We have the homegrown and take the long view. Amazon talks about the shared responsibility model, and a lot of small companies don't really understand that things misunderstood. Obviously, Liberty Mutual gets it. My question is, as you see Amazon focusing on compute in the storage and data base layer, and you guys have the opportunity to focus on other areas that are your responsibility that shared responsibility model. Have you been able to shift? Resource is how have you handled that you retrain people? Has it freed up, not freed up time to do some of those more strategic things that you want to do maybe respond more quickly. Prioritized, better automate, etcetera, etcetera. Can you talk about that from your perspective? >> Yeah. So the shared responsibility model is, uh, you know, I think that's video unimportant speaking point of this whole ecosystem. At the end of the day, Liberty Mutual. Our duty is to protect policyholder data. It doesn't matter. It's in the cloud. If it's in our data, Southers, we have that duty. It's >> on you. >> So I think a lot about the skills that we will need in the future. So I've referenced sort of vaguely that yet. Compliance area is a particularly interesting area where we have opportunities to able to more easily Bingley produced artifacts on our auditors need to really bring automation to a process that just has a very steep history and being manual in nature. So, yeah, I understand that tomorrow we're not gonna ask everyone to make a big switch and I'll become developers. But way do you know plenty of people to this conference and they are participating in the tracks on how to bring of automation to compliance. And I think that's pretty heavily in training opportunities for people. >> How do you look about the vendor lock in conversation because of cloud. The value proposition certainly shifts in the old model was, Oh, you by event supplier and you're in, You're locked in with database or whatever with Cloud. There's a lot of switching costs, opportunities to move around. But people generally settling in on one main cloud and having this may be a hybrid backup cloud or the cloud is the secondary is the focus of the team's How do you view, um, lock And when you deal with suppliers because you don't want to be stuck with once a fire? If you have the need to be agile, you want to have options. How do you guys think about that? Because being in agility is key for you guys to be successful. Not someone's just dealing with the vendors. >> Um, >> it does come down to balance. We do leverage multiple cloud providers, right? I think that, um, if we're too focused on making sure that we have that portability, and we could quickly move from one to another than we miss an opportunity to kind of deeply leverage. Some of the service is, for example, that the eight of us provides, but we also, you know, you've been around the block of >> your first rodeo. Exactly. >> And I think that it's important to have that perspective and prepare for the future. >> Do you, um, attend board meetings regularly? >> I do. I do for sent out to our board of directors. >> Is that a sort of frequent thing? And once a year, once 1/4 of interested in what the board conversation is like with >> it happens in a couple different context, whether it's specific to sort of an audit readout or sort of a general state of State of Security type A report out. But yeah, we have a really engaged board that asked great questions about our partners, right about things that are more culture base in terms of how we're doing with our anti phishing protection. And we talk about technology architectures, too, in the work that we're doing to make sure that we're being more fine grain in the way that we're authenticating users and devices, no matter where they work in a more secure way. They're they're interested in that. So I feel pretty lucky. Thio both have the opportunity and get deeply. Would >> you say the conversation is more of a strategic nature with the board. Is it more tactic? You just mentioned some tactical items. Is it more metrics driven or a sort of a combination of all three? >> It's a It's a combination right? I think they want to see demonstrated progress against areas that we have self identified Azarias that we'd like to prove improve. But they're also looking to see that I have a vision for where we're going to fully cognizant of the work that we've done in the public cloud and want to understand that the level of trust and they had in their security programme on premise will perpetuate and advance into the cloud. So >> when you look at clouds, security and now security, you guys have you had a perspective on full sides and clouds certainly accelerating involving fast when you find a legacy app that you're working with. We've heard other seasons. We've talked us who have had frank conversations, that look, we're deciding whether we lift and shifted more rebuild on. So there's been some visibility into when it's great to have lifted shifts and when it's great to rebuild. So that's been a conversation that I don't think been fully baked out yet. In the full narrative in the industry, it's one people are talking about. What's your view on when you have a legacy app, you want a lift and shifted or rebuild it? What goes through your mind? What's a conversation like? >> It's a conversation that we have. We have legacy. I won't hide behind behind that. But it's not a conversation in a decision that's just made by technologists, right? I think we have to articulate what the options are, and that has to be a joint decision with our business partners. I think generally I'm not preferring a lift and shift because I think that we are may be overlooking some of the opportunities to make similar security improvements that I see. But when we can get an application that's using our software development pipelines that we have embedded security controls, we have better visibility. We have better enforcement, ensuring what we know that we know what's going into. The cloud has met, you know, a number of our security standards, so to speak, that's a much better position. >> So the destruction of multiple clouds I'm interested in how you handle that you take separate teams is the same team, sort of handling everything, and it's sort of a follow up on that is I'm interested in your relationship with AWS and how that's affected your business. >> Yeah, so the security team does not. Oh, the cloud environment, so to speak. That's that's, Ah Secure Dev Ops team within our infrastructure organization. And they're very close partner of ours, right? So, yes, I do have a resource. Is that our specialist in AWS versus other clouds and others that are identity and access management specialists are able to work on the development of those patterns across different cloud environments. Right. You know, I there's nothing bad that I could say about the relationship with our AWS partners that we felt very supported and understanding what we're trying to do introduce us to new service is and introduced it probably most importantly, introducing us to other customers that have but you know, are a little bit ahead of us in their journey. So weaken, hopefully not repeat, >> not helping you with security pieces. Well, I'm that's something that they with shared responsibility there are there working with you on this securing those workloads as you move. Glad >> be Definitely leverage their expertise. >> And you mentioned that you guys kind of made a decision a few years ago. Toe go all in on the cloud. How has that affected your business? What kind of results have you seen? A zit met expectations. Is it exceeded? You know, I >> mean, is I mentioned we do still have, Ah, a lot of a lot of our technology on premise, but for the use cases that have really seen that rapid acceleration of agile practices allowed teams to develop code so much more quickly. I think the business is generally delighted that their needs are being far more quickly met. Then >> I could ask you, there's a perpetual line in the men's room. It's quite long. So what's it like to be long? And the lady I was going to say? I don't think it is because I would say the proportion of women here is actually lower than even the industry and most conferences that we attend. So what's it like being a woman in this male dominated security business? >> I been in it so on, but I certainly have. You're in a little bit of custom toe, but not so accustomed that I'm not motivated on a daily basis to bring more women in. I think that security just has tremendous opportunities and, you know, certainly the marketing of security professionals is hoody wearing white male kind of persona. Just >> their opportunity. What some of those opportunities for women who are stem science, they might your daughters all stem love public policy, the sociology impact side. The impact that's here is a lot of range of skills. What are some of those that you would inspire someone >> I studied? Math is an undergrad. We didn't have security >> back then and since got a Masters >> degree in cyber security. So that's cool. But, you know, I think a great security professional is a great communicator, a great collaborator. I need technologists. I need developers. I need process experts. I need people that think you know very deeply about assurance type control so way have tried to attract people out of other technology round. >> And it's just not just math and computer science is creativity involved. There's a lot of things that that blend sells all kinds of diversity. >> There is, you know, you think about human psychology, right? We just totally transformed one of the systems that we use for approving for managers to approve the access of their people. Right Past system was ugly. People didn't know how to interact with it. I mean, that user experience expertise that over laid and how we developed our new platform just makes all the difference to make sure that it's actually invaluable process. Now, like I'm so frustrated. I'm just gonna sign off on this because I I give up >> really interesting because you spend a lot of time and effort and money on things that drive revenue. But this drives so much productivity in business value that, you know he's not maybe direct dollars, but clearly there. I have a question. When you recruit people, presumably you tap your network. And it's not just the good old boys network your women. Are you able to successfully find women or young women in particular that you can attract and recruit into your business as security practitioners? They had much success there. >> Yeah, so we definitely are outpacing industry numbers in terms of women and security. We have a long way to go, you know, historically excluded people right? Not just women people of color. I mean, we just have a long ways to go, right. And I think it takes more than sitting back and waiting for a recruiter to bring recruiter to bring me a slate of candidates to say no. I know people. I know people that know people. And I really have toe invest myself and make sure that my leaders know that that's my expectation of them, right? I mean, I think that way feel that diversity of thought, no matter how that diversity is expressed, is really important doing the work. >> Let us know how we could help in Silicon Valley days here in Boston as well. Love help get the word out. So anything you need for muscle now. Okay. Thanks so much for his great insights. Love to have you on the cube again sometime. Thanks. Coming on S V p. C. So at Liberty Mutual here in the cube, extracting the signal, sharing the reality of what's going on in the security equation for cloud security. I'm John for Dave. A lot. Right back after this short break
SUMMARY :
W s reinforce 2019 brought to you by Amazon Web service is and Means you guys have a large company. This is Liberty Mutual's hometown But we're the public cloud for our technology and computing needs. What is cloud security mean to you? Gosh, we encrypted everything, but you know, this set of assets over here, So my question is, are you an optimist? I think it'll be difficult for us tow. One of the things that we were discussing a lot of other C. So So we've been talking privately. I think it starts at how we even procure So all the monetary spend questions come up. But I the important to our policy holders. Therefore, you could make those calls on your own building built in building, But I think it comes down and knowing your technology, and you guys have the opportunity to focus on other areas that are your responsibility that shared responsibility model. It's in the cloud. So I think a lot about the skills that we will need in the future. of the team's How do you view, um, lock And when you deal with suppliers we also, you know, you've been around the block of your first rodeo. I do for sent out to our board of directors. Thio both have the opportunity and get deeply. you say the conversation is more of a strategic nature with the board. of the work that we've done in the public cloud and want to understand that the level of trust when you look at clouds, security and now security, you guys have you had a perspective on full sides and I think we have to articulate what the options are, and that has to be a joint decision with So the destruction of multiple clouds I'm interested in how you handle that you take separate teams Oh, the cloud environment, so to speak. Well, I'm that's something that they with shared responsibility there are there working with you And you mentioned that you guys kind of made a decision a few years ago. I think the business is I don't think it is because I would but not so accustomed that I'm not motivated on a daily basis to bring more women in. What are some of those that you would inspire someone I studied? I need people that think There's a lot of things that that There is, you know, you think about human psychology, right? particular that you can attract and recruit into your business as security practitioners? We have a long way to go, you know, historically excluded Love to have you on the
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
AWS | ORGANIZATION | 0.99+ |
Amazon | ORGANIZATION | 0.99+ |
Katie Jenkins | PERSON | 0.99+ |
Boston | LOCATION | 0.99+ |
Liberty Mutual | ORGANIZATION | 0.99+ |
Libya | LOCATION | 0.99+ |
Liberty Mutual Big Company | ORGANIZATION | 0.99+ |
25% | QUANTITY | 0.99+ |
Dave | PERSON | 0.99+ |
yesterday | DATE | 0.99+ |
20 plus years | QUANTITY | 0.99+ |
John | PERSON | 0.99+ |
eight | QUANTITY | 0.99+ |
Boston, Massachusetts | LOCATION | 0.99+ |
Both | QUANTITY | 0.99+ |
Silicon Valley | LOCATION | 0.99+ |
hundreds | QUANTITY | 0.98+ |
both | QUANTITY | 0.98+ |
Michael's Day | EVENT | 0.98+ |
One | QUANTITY | 0.98+ |
tomorrow | DATE | 0.98+ |
2019 | DATE | 0.97+ |
once a year | QUANTITY | 0.96+ |
three | QUANTITY | 0.96+ |
Thio | PERSON | 0.95+ |
two different animals | QUANTITY | 0.95+ |
about a year | QUANTITY | 0.95+ |
one | QUANTITY | 0.93+ |
Ah Secure Dev Ops | ORGANIZATION | 0.92+ |
Amazon Web | ORGANIZATION | 0.91+ |
few years ago | DATE | 0.91+ |
100 plus years old | QUANTITY | 0.9+ |
one main | QUANTITY | 0.89+ |
Azarias | ORGANIZATION | 0.83+ |
107 year old | QUANTITY | 0.82+ |
Vice President | PERSON | 0.81+ |
one people | QUANTITY | 0.79+ |
Gosh | PERSON | 0.79+ |
Amazon web | ORGANIZATION | 0.79+ |
First inaugural conference | QUANTITY | 0.78+ |
Chief | PERSON | 0.77+ |
once | QUANTITY | 0.74+ |
1/4 | QUANTITY | 0.72+ |
first rodeo | QUANTITY | 0.72+ |
Bingley | ORGANIZATION | 0.71+ |
Security | PERSON | 0.69+ |
Southers | ORGANIZATION | 0.68+ |
agile | TITLE | 0.66+ |
secondary | QUANTITY | 0.62+ |
Volante | PERSON | 0.43+ |
P. | TITLE | 0.38+ |
Sally Jenkins, Informatica | Informatica World 2019
[Narrator] Live from Las Vegas! It's theCUBE covering Informatica World 2019. Brought to you by Informatica. >> Welcome back, everyone to theCUBE's live coverage of Informatica World, here in Las Vegas. I'm your host, Rebecca Knight, along with my co-host, John Furrier. We're joined by Sally Jenkins. She is the executive vice president and CMO here at Informatica. Thank you so much for coming on theCUBE, Sally. >> Oh you're welcome, thank you for having me. Its nice to see you all again. >> So congrats on a great show, we're going to get to the stats of the show, but the framework of Informatica World is built around these four customer journeys. Next Gen analytics, Cloud Hybrid, 360 engagement, Data Governance and Privacy. Can you tell our viewers a little bit about how this framework reflects what you're hearing from customers and their priorities >> Yes absolutely, Rebecca and yes, you got the right and in the right order, thank you. So, we started this journey with our customers and trying to understand how do they want to be spoken to. What business problems are they solving? And how do they categorize them, if you will. And so, we've been validating these are the right journeys with our customers over the past few years. So everything that you see here at Informatica World is centered around those journeys. The breakouts, our keynotes, all the signage here in our solutions expo. So, its all in validation of how our customers think, and those business problems they're solving. >> So the show, 2600 attendees from 44 countries, 1200 sessions. What's new, what's new and exciting. >> Oh, gosh, there's so many things that are new this year. And one other stat you forgot, 92 customers presenting in our Breakouts. So our customers love to hear from other customers. As to what journeys they're on, what problems their solving. Those are record numbers for us. Record number of partners sponsoring. We've got AWS, we've got Google, we've got Microsoft, we've got the up and comers, that we're calling in the Cloud and AI Innovation zone. So people like DataBricks and Snowflake. We wanted to highlight these up and comer partners, what we call our ecosystem partners. Along with the big guys. You know, we're the Switzerland of data. We play with everybody. We play nicely with everybody. A lot of new things there. A few other things that are new, direct feedback from our customers last year. They said we want you to tell us which breakouts we should go to. Or what work shops should we attend. So we rolled out two things this year. One's called the Intelligent Scheduler. That's where we ask customers what journey are they on. What do they want to learn about. And then we make a smart recommendation to them about what their agenda should look like while they're here. >> You're using the data. >> Yes, AI, we're involving AI, and making the recommendations out to our customers. In addition, our customers said we want to connect with other customers that are like us, on their journeys, so we can learn from them. So we launched we called the Intelligent Connect and again this is part of our app. Which, our app's not new, but what we've done with our app this year is new. We've added gamification, in fact as part of the AI and Cloud Innovation zone, we are asking our customers and all of our attendees to vote on who they think is the one with the best innovation. They're using our app to use voting. They can win things, so there's lots of gaming. There's social that's involved in that, so the app's new. We're taking adavantage of day four. We usually end around lunchtime on day four, this year we're going all in, all day workshops, so that our practitioners can actually roll up their sleeves and get started working with our software. And our ecosystem partners are also leading a lot of those workshops. So a lot that's new this year. And as I mentioned, the Cloud and AI Innovation zone, that's new it's like a booth within a booth here on the solutions expo floor. So this is the year of new, for sure. >> You know one of the things that's been impressive, I was talking with Anil and also Bruce Chizen, who is a board member, The bets you guys have made is impressive. You look back, and this our tenth year in theCUBE, so we go to a lot of events, 100s events in a year, over 100 events over 10 years. We've seen this story with you guys, this is now our fourth year doing theCUBE here. And the story has not changed, its been early moves, big bets. Cloud, early. Going private to see this next big wave. AI, early before everyone else. This is really kind of showing, and I think the ecosystem part is on stage with Databricks, with Snowflake. Really kind of point to a new cast of characters in the ecosystem. >> That's right. >> You're seeing not just the classic enterprise, 'cause you guys have great big, large enterprises that you do business with. That want to be SAS like, they want the agility, they want all those great things but now you have Cloud. The markets seems to have changed. This is an ecosystem opportunity. >> That's right. >> Can you share what's new? Because you see Amazon, Google and Azure, at the cloud, you got On-Premise, you now Edge and IoT, everything's happening with data. Hard, complex, what's new, what's the ecosystem benefit? Can you just share some color commentary around how you guys view that as a company. >> Yeah, thanks, John, and that's a good question. I'm glad you're pointing out that our whole go to market motion is evolving. It's not changing it's evolving because we want to work with our customers in whatever environment they want to work in. So if they're working in a cloud environment, we want to make sure we're there with our cloud ecosystem partners. And it doesn't matter who, cause like I said, we work with everybody, we work nicely with everybody. So we are tying in our cloud ecosystem partners as it makes sense based on what our customer needs are. As well as our GSI partners. So we've got Accentra's here. They brought 35 people to Informatica World this year. We play nicely with Accentra, Deloitte, Cognizant, Capgemini so we really are wanting to make sure that we're doing what makes sense with our customer and working with those partners that our customers want to work with. >> Well I think one of the observations we've made on theCUBE and we said in our opening editorial segment this morning, and we're asking the question about the skill gaps, which we'll get into with you in second, but these big partners from the Global System Integraters to even indirect channel partners, whether they're software developers and or channel partners. They all are now enabled and are mandated to create value. >> Yes, that's right. >> And if they can't get to the value, those projects aren't going to get funded and they're not going to get renewed And so we've seen with the Hadoop cycle of just standing up infrastructure for infrastructure sake isn't going to fly. You got to get to the value. And data, the business that you're in, is the heart of it. >> Well, data's at the heart of it. That's why we're sitting at a really nice sweet spot, because data will always be relevant. And the theme of the conference here is data needs AI and AI needs data. So we're always going to be around. But like I said, I feel like we're sitting right in the middle of it. And we're helping our customers solve really complex problems. And again, like I said if we need to pull in a GSI partner for implementation, we'll do that we've got close to 400,000 people around the world, trained on how to use Informatica solutions. So we're poised and we are ready to go. >> We were talking before we came on camera. We were sitting there catching up, Sally. And I always make these weird metaphors and references, but I think you guys are in an enabling business. It reminds me of VMware, when virtualization came in. Because what that did was, it changed the game on what servers were from a physical footprint, but also changed the economics and change the development landscape. This seems to be the same kind of pattern we're seeing in data where you guys are providing an operational model with technical capabilities. Ecosystem lift, different economics. So kind of similar, and VMware had a good run. >> We'll take that analogy, John, thank you. >> What's your reaction? Do you see it that way? >> Yeah I do, and it all comes back to the journeys that we talk about right. Because our customers, they're never on just one journey. Most of them are on multiple journeys, that they are deploying at the same time. And so as they uncover insights around one journey, it could lead them to the next. So it really comes back to that and data is at the center of all that. >> I want to ask about the skills gap. And this is a problem that the technology industry is facing on a lot of different levels I want to hear about Informatica's thoughts on this. And what you're doing to tackle this problem. And also what kinds of initiatives you're starting around this. >> Well, I'm glad you asked because it's actually top of mind for us. So Informatica is taking a stance in managing the future, so that we can get rid of the skills gap in the future. And last year we launched a program we call the Next 25. That's where we are investing in middle school aged students for the next seven years. Its starts in 6th grade and takes them all the way through high school. They are part of a STEM program, in fact we partnered with Akash middle school here in Las Vegas. Cause we wanted to give back to the local communities since we spend so much time here. And so these kids who are part of the STEM program take part in what we call the Next 25. Where we help them understand beyond academics what they need to learn about in order to be ready for college. Whether that's social skills, or teamwork, or just how do we help them build the self confidence, so it goes beyond the academics. But one of the things that we're talking about tomorrow, is what's next as part of STEM. Cause we all know they're very good at STEM. And so we've engaged with one of the professors at UNLV to talk about what does she see as a gap when she sees middle school students and high school students coming to college and so that's where she recognizes that coding is so important. So we've got a big announcement that we're making tomorrow for the Next 25 kids around coding. >> Its interesting, cause we could talk about this all day, cause my daughter just graduated from Cal, so its fresh in my mind, but I was pointed out at the graduation ceremony on Saturday that the first ever class at University of California Berkley, graduated a data science, they graduated their inaugural class. That goes to show you how early it is. The other thing we're hearing also on these interviews as well as others, that the aperture or the surface area for opportunities isn't just technical. >> Right >> You could be pre med and study machine learning and computer science. There's so much more to it. What do you see just anecdotally or from a personal standpoint and professional, key skills that you think people should hone in on? What dials should they turn? More math, more coding, more cognitive, more social emotional, What do you see as skills they can tailor up for their-- >> Well so let's just start with the data scientist. We know LinkedIn has identified that there are 150,000 job openings just for data scientist in the US alone. So what's more interesting than that, is four times that are available for data engineers. And for the first time ever, data engineers' starting salaries are paying more than starting salaries on Wall Street. So, there's a huge opportunity, just in the data engineering area and the data scientist area. Now you can take that any which way you want. I'm in marketing and we use data all day long to make decisions. You don't have to be, you don't have to go down the engineering path. But you definitely have to have a good understanding of data and how data drives your next decisions, no matter what field you're in. >> And its also those others skills that you were talking about, particularly with those middle school kids, it is the collaboration and the team work and all of those too. >> It does, again, it goes beyond academics. These kids are brilliant. Most of them are 7th or 8th grade. But nothing holds them back, and that's exactly what we're trying to inspire within. So we have them solving big global problems. And you'll hear as they talk about how they're approaching this. They work in teams of five. And they realize to solve huge problems they need to start small and local. So some of these big global problems they're working on, like eradicating poverty, they're starting at the local shelters here in Las Vegas to see how they can start small and make a difference. And this is all on their own, I have folks on my team who are junior genius counselors with them, but that is really to foster some of the conversations. All the new ideas are coming directly from the kids. >> My final question is obviously for the folks who couldn't make it here, watching, know you guys, what's the theme of the show because the news right out of the gate is obviously the big cloud players. That's the key. And the new breed of partners, Snowflake, Databricks as an example. Hallway conversations that I'm hearing, can kind of be geeky and customer focused around "where do I store my data?" so you're seeing a range of conversations. What is the theme this year? What's different this year, or what more the same? Where are you doubling down? What's going on here for the show? What's the main content? >> Well so this is our 20th Informatica World if you can believe that. We've been around for 26 years, but this is our 20th Informatica World. And several years ago we started with the disruptive power of data. Then last year we talked about how we help our customers disrupt intelligently. And this year the theme is around ClAIrity Unleashed. You can tell the theme has been that we've been talking about for the past three years is all underpinned with AI. So it is all about how AI needs data and data needs AI. And how we help bring clarity to our customer's problems through data. >> And a play on words, ClAIr, your AI to clarity. >> Exactly, AI is at the center of our Intelligent data platform. So it is a play on AI but that is where ClAIrity Unleashed comes from. >> Terrific, thank you so much for coming on theCube, Sally. Its great having you. >> Great, thanks Rebecca. Thanks, John. >> Thank you. >> Nice to see you all. >> I'm Rebecca Knight for John Furrier. We will have more from Informatica World, stay tuned. (upbeat pop outro)
SUMMARY :
Brought to you by Informatica. She is the executive vice president Its nice to see you all again. but the framework of Informatica World is built around And how do they categorize them, if you will. So the show, 2600 attendees They said we want you to tell us and making the recommendations out to our customers. We've seen this story with you guys, they want all those great things but now you have Cloud. at the cloud, you got On-Premise, you now Edge and IoT, that we're doing what makes sense with our customer which we'll get into with you in second, And if they can't get to the value, And the theme of the conference here is data needs AI and change the development landscape. to the journeys that we talk about right. And what you're doing to tackle this problem. And so we've engaged with one of the professors at UNLV That goes to show you how early it is. key skills that you think people should hone in on? And for the first time ever, data engineers' it is the collaboration and the team work And they realize to solve huge problems And the new breed of partners, And how we help bring clarity Exactly, AI is at the center Terrific, thank you so much I'm Rebecca Knight for John Furrier.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Rebecca | PERSON | 0.99+ |
John | PERSON | 0.99+ |
Rebecca Knight | PERSON | 0.99+ |
Bruce Chizen | PERSON | 0.99+ |
John Furrier | PERSON | 0.99+ |
Deloitte | ORGANIZATION | 0.99+ |
Microsoft | ORGANIZATION | 0.99+ |
Sally Jenkins | PERSON | 0.99+ |
Amazon | ORGANIZATION | 0.99+ |
Sally | PERSON | 0.99+ |
ORGANIZATION | 0.99+ | |
Informatica | ORGANIZATION | 0.99+ |
Informatica World | ORGANIZATION | 0.99+ |
Saturday | DATE | 0.99+ |
Accentra | ORGANIZATION | 0.99+ |
last year | DATE | 0.99+ |
US | LOCATION | 0.99+ |
Las Vegas | LOCATION | 0.99+ |
AWS | ORGANIZATION | 0.99+ |
ORGANIZATION | 0.99+ | |
first | QUANTITY | 0.99+ |
Capgemini | ORGANIZATION | 0.99+ |
1200 sessions | QUANTITY | 0.99+ |
this year | DATE | 0.99+ |
tenth year | QUANTITY | 0.99+ |
92 customers | QUANTITY | 0.99+ |
Anil | PERSON | 0.99+ |
Cognizant | ORGANIZATION | 0.99+ |
fourth year | QUANTITY | 0.99+ |
7th | QUANTITY | 0.99+ |
Snowflake | ORGANIZATION | 0.99+ |
44 countries | QUANTITY | 0.99+ |
Databricks | ORGANIZATION | 0.99+ |
150,000 job | QUANTITY | 0.99+ |
35 people | QUANTITY | 0.99+ |
tomorrow | DATE | 0.99+ |
one | QUANTITY | 0.99+ |
several years ago | DATE | 0.99+ |
first time | QUANTITY | 0.98+ |
second | QUANTITY | 0.98+ |
Wall Street | LOCATION | 0.98+ |
one journey | QUANTITY | 0.98+ |
two things | QUANTITY | 0.98+ |
2600 attendees | QUANTITY | 0.98+ |
Global System Integraters | ORGANIZATION | 0.97+ |
VMware | ORGANIZATION | 0.97+ |
over 100 events | QUANTITY | 0.97+ |
26 years | QUANTITY | 0.96+ |
6th grade | QUANTITY | 0.96+ |
100s events | QUANTITY | 0.96+ |
theCUBE | ORGANIZATION | 0.96+ |
UNLV | ORGANIZATION | 0.95+ |
GSI | ORGANIZATION | 0.95+ |
Azure | ORGANIZATION | 0.94+ |
DataBricks | ORGANIZATION | 0.94+ |
over 10 years | QUANTITY | 0.94+ |
University of California Berkley | ORGANIZATION | 0.93+ |
day four | QUANTITY | 0.93+ |
400,000 people | QUANTITY | 0.92+ |
five | QUANTITY | 0.91+ |
this morning | DATE | 0.9+ |
Bradley Jenkins, MetLife | Adobe Summit 2019
>> Live from Las Vegas. It's the queue covering Adobe Summit twenty nineteen brought to you by Adobe. >> Hello and welcome back to the keeps. Live coverage in Las Vegas for Adobe Summit. Twenty nineteen. I'm John for Jeffrey from the Cube. Our next guest, Bradley Jenkins, was the marketing CEO and vice president. Met Life, part of the global technology and operations group. Innovative title. But thank you, >> Yeah, thank you. Thanks for having me. >> So we're here to do the summit. A lot of things are happening. It's really interesting because you have a convergence of two worlds and it looks like a cloud world. It's it's it's the creative cloud. It's the experience Cloud now called The whole World shares a lot of devil's mindset in there. Got a platform? The whole world's changed. Now marketing has a full blown class, not just marketing class, so it's a whole system. So as a marketing seo, what does that mean? Is now a new role emerging in organizations? Is this where we're team? >> I think it's a It's an emerging role. I think it's one of those things where in the in the market and technology space, the lines are blurring, and part of the role of people like me are the ones you could be the bridge makers between the two functions and bring in products like we see all around us here today. Cloud based Solutions How do we activate marketing tactics faster, quicker on. Then combine things like experiences with tools and technologies in different ways. I think it's a specialty skill, and it's coming out now and emerging >> well. One of the patterns is that marketing departments that have a technical and also a relationship seems to be more agile, transformed faster. This seems to be the same thing you guys are looking at right? >> Exactly. It's all about speed to market. So agility is this one co looking and combining everything from creative to the developers, all in one Teo product resource person all the wine and we get in and try to solve business problems. Fastest possible. But you're almost kind of a personification of the story we hear all the time, which is? CEOs get a seat at the table right now. They're no longer just keeping the lights on in the system's lit. But it's a fundamental way the company goes the business of fundamental way the company interact with their customers. So to actually put a marketing CEO title. That's a pretty unique thing I don't think we've ever had one on. So you come at it, no doubt about it. I'm here about customer engagement, customer experience, not keeping the light on. That's right. That's right. First, one side, like a unicorn. >> How's it been? So tell us some of the things you do. I love how you're part of a global technology and operations group. Noticed the word operations and tech together again, back to this cloud theme of Dev ops, which changed the game on the world >> it has. >> So we're seeing that same thing happening playing out in the creative market, whether it's content for here, same thing. Explain some of the things you're doing. >> It's the same thing, and it is Everything's very cloud based today, obviously. So everything from building out content, platforms and services and kind of services framework switch, which is which is key to what what we want to do but also campaign and analytics and, uh, you know, social and what the emerging capabilities are in social. How do we tie all those together but do in a way, we're capturing data and insights across all of our channels in a more creative, quicker way, then activating that across new new experiences. >> You know, Bradley, one thing I wanted to ask you, And I'm glad you came on because I've been really kind of riffing on this idea and trying to get a date in actual year kind of a before cloud after cloud demarcation line because, you know, we're in Silicon Valley. We cover a lot of startups and literally ones go big or go home is kind of the mantra. But if you were born before Amazon, you're pretty much either aren't around or got acquired. If you're born after Amazon, where clouds scale and all this stuff happened, you tend to thrive in a whole new kind of shift. So in Martek, which is heavily funded, sector on the ecosystem map of pure play applications was pretty dense. >> Is very dense. Yeah. >> Did that live up to its name? Did it shift and shape? What's your thoughts on that mark Tech landscape could? Certainly, it's relevant when you're marking CEO. You want to put technology in place. Has the platform shifted? What's that? What's going on? Tell us. >> Yeah. So you know, I think has it lived up to his name? Uh, yes, and it's created challenges that the same thing at the same time. So what is still in the Martek landscape is seventeen thousand or whatever tens of thousands of products. Now Mr Wescott fingers latest one shows every year it doubles or quadruples in there. And I think one of the biggest challenges we have now is just navigating, never getting the landscape, but then be able to pick out and say, Here are the five things and you focus on Here is how I'm going to tie them together and in great demand. And there's a lot of noise and you have to break through a lot of that to build a craft. These solutions together. So in a lot of ways, I think it's lived up, Uh, a lot of ways. I think it's create a lot of new challenges that things like markets he has you to think about. Be aware of the bread, the people that are out there. But that's just the capabilities. How do you stitch them together and you become more of a weaver? Then thin a specific domain >> class early adopter proves the model. And now reality as operational izing things becomes clear. The wheat from the chaff, as they say, kind of get figured out >> exactly friendly. I want to get your kind of thoughts on a CZ. The relationship between the company and the customer has shifted from sitting down with an agent or maybe talking to it. Agent on the phone to really Elektronik means how you've been able to kind of continue a certain type of brand experience. And I'm also just curious your feedback on the theme here where it's not really the transaction. It's the experience of which the transaction is a piece of How are you seeing that play out in the way that you guys interact with your customers? Yeah, and I think for us we're in evolving state to we have agencies and brokers that we worked through, and so it's a bit of the model in some cases, in some cases it turns, and we're about to see targeting >> B to B >> group customers as an example, and so the experience is very a bit so for us, it's experience of the customer, and how do we service some? How do we treat them. What's the purchasing servicing capabilities look like? What's our customer service look like? But also the experience of agents and brokers. And are we providing the right service and products to them to build equipped them to go help in resell product? So we look at it from a couple different angles and depends a lot on context and where we're operating in product and servicing products at Is it easy to maintain kind of the voice of the brand, if you will, through these alternate channels or, you know, how do you kind of stay true to the brand? Yet go to market through these. He's a myriad of channels. Yeah, it's no Isaac, a question that we're really working through the same kind of things now of what can we What can we help provide agents and brokers with, and that helps with our brand? Our friend promised up. Some sell better. That it's it's a work in progress, but technical challenge? Yeah, I don't >> really have >> all the answers. >> Take a minute to explain the MetLife transformation. What you guys have done. Where are you now? In the jury? Your journey will be customer. You're here at their event. Where are you on that Progress bar? How far along are you? It seems to be a theme of transforming. Continue to transform is what successful company doing. Our iterating are raising the bar. Whatever term used where you guys at, Can you take us through? >> Yeah. So a few years ago, we we refreshed our enterprise strategy. We placed a customer in digital on data at the center of our enterprise strategy. And we have pillars around different transformation aspects that we're working on everything from customer service too. Right? Products simplifying our product messaging the way we talked about product specially in insurance can be complicated. And so we're trying to get a little a little more concise and clear and package things differently. But But at the core, our strategy now is placing digital placing diddle data at the center of it. Uh and then how do we enact data and new and different ways Everything from not only knowing customers, but how do we use data to great better and smarter products or even the risk different products that we have waken me price competitive in certain market areas. >> So Data's lifeblood of your transformation. It is. What's the strategy? How you guys enabling that internally? What some of the results will take us through experiences, zealously numbers. But I'm sure it's helping. If you do it right. It's challenging, though it's not easy. >> It is. Yeah, it's challenging, and it will take a while to sort it out. So we'LL say we've solved everything. Uh, but But I think we look at a few different things. What one is knowing the customer? And so you know, we're investing heavily and try and doing things like customer profile and a customer. Three sixty. Whatever you want to call it different in different, different areas. Uh, but how do we know them? And then how do we then act? There's the data's insights into different channels. So we've had a lot of a lot of good successes in there, in particular markets on creating more engaging experiences and lifting customer retention and loyalty. So we have good, good insights there. We're planets in different areas, so things like we go to bid for new products and or new new customers around a new product area. What can we do it for our pricing models on. How do we love its data around Where is geographic or whatever it might be? Or demographics and fly it to be more price competitive? And we're starting to see a lot of fruition there and how it gets applied. Tto win New business >> One of the things that we've been talking about on the Q through got a lot of events, and the theme that comes up all the time when you have these new shifts is new. Things are emerging. New capabilities, different economic points, scales different. So all good. Now the hard part is making it work. Operationalize ing Something new is a huge challenge. It is. Did you share your view on that? And reaction to that because this is seems to be not about the tech about either skills, gaps or culture gap. There's a lot of things in the way of operational izing, something new. What's what people do to operationalize something? >> Yeah, no, it's a good question. I'm glad you brought it up because that's actually one of the things that I have a caper. A lot is a lot of times we lead with the tech and then we place it And then we say, Well, now what? And then everything you know is what it comes to a standstill. And, yeah, you have to leave with people. Process so again in for a transformation, understand exactly what it is you're trying to solve. How are you going to solve it afterwards? Do you have the skill sets and place to do it and then follow up with the tech? And then I think a lot of a lot of companies do a little bit reverse where they go in acquiring, like we're going to solve this and bring the cheque in and in your little literally left standing at the end of day of How do you have the operational ises? So something we focus on a lot is it is the people process piece of enablement training, the skills that are required. How do you turn it into a machine after you bring the tech in to really start pumping up? Whether it's a growth objective or call status, I've never where the object it might be. But you have to you have to almost produce this into ah life machine of its own that cannon live and breathe after you bring the second. >> What should more marketing CEOs as it becomes a price? I think it will be. In my opinion, I think it will be a roll because it's really critical because of the opportunity. What should they be doing? That's this New persona evolves. You're pioneering it. What is the job function? What does it do in your opinion? Has this take shape? >> Yeah, I think Number one. Learn the business. And I think you have to speak the same language. And that's one of the biggest challenges translating so different languages across different groups. In the first thing, any market so you could do is go learn the business, speak the same language, then what company you know. We're in insurance company and a risk management companies. So understanding, finance, understanding, mark objectives. Your customer detectives is key and then figure out how to start mapping the solutions in. But, yeah, I think it's it's It's a fridge, a role. We have to be able to be a navigator in away across solution options, but always in context of understand the business and how you confessed, apply, and in a specific way, >> Data wrangler of course, because you're wrangling a lot >> of data. If I don't have a lot of intersection with, you know, kind of actuarial side of the house, which is, you know, kind of always been data driven, right since the early earliest days. But I mean, are you seeing you know, kind of that side of the house? Kayla, you know, can we get we get some of these new tools? Could we get some of these kind of new ways to approach the data problem than we historically did? I think now, now? Yes. I think it has been an evolution. I think in the early days of data, it was a bit more of a scary thing. And so I feel like we're, you know, as advocates in the sea of space that we were pushing a little more than, you know, being pulled in. And I think I think lately in the last couple of years. But I know at least until we've seen a shift of demand side of requests coming in, saying we need to partner way ideas of how to accelerate and be competitive, which is great. Now it's almost become a supply demand trick. Where you just can't keep up. Because the level of segmentation on kind of classy the insurance, you know, kind of breakdown is really high, right? Sex age, you know, a couple other factors. But you know, now that the amount of data that's available, that amount of real time data, it's available on changing, they've got to be going bananas over on that side. >> You know, one of the things that we've been seeing on the side again. I want to bring a question in the marking CEO piece is on. We've had many CEOs talk about this on the Cuba and direct interviews is they've outsourced everything, and they really had no core competency, had all the big size running stuff you had global outsourcing development. And as cloud became important, they had the build applications internally, didn't have the skills, so they had to quickly reset and rebuild and in house capability. And the result of that is ongoing and seen. The ones who've done that well with cloud are doing great. They still use outsourced off. Now, on the marketing side, you saw that same thing happen where agencies run everything. The agency does this, you got the creative agency, you got a PR firm, you all these things going on and some say that marketing has been outsource a lot. And so the question is, what mix of in house skill, an agency relationships? Because now you're gonna see that application developer. No problem. But core competency becomes a super important question. Yeah, And how are you funding it And what should be in house on what should be outsourced. >> Yeah. Yeah, and we have We're going to the same evolution. We had a position than a few years ago where it was almost entirely outsourced, and we in sourced a bunch of it. And now we're right sizing what's unsourced and not in sources. So I think one is Think about, uh, what your differentiation is. And how do you want to be competitively different competitively and having create advantage and then in source those things. And then you had to find a way. That's one thing. I think every year you talk to Rick Wright size and reassess. And so for us, we insourced a lot of things around. Um, first around, build side, so platforms being cloud. But then how do you enact and activate them? So we've brought some of those inside internally on we started marrying those up with creativity. This is just the last words of the great, But we were married them up and get these, uh, you know, more agile lean teams cross blended skill sets and go on, go to market quicker with new experiences. I think over time we'LL see a start and sourcing more of the agency side, maybe shedding some of the you know, the left side as we started becoming more pattern base and whatnot. So I think it's one of those things that you evolve every year as the right size. But the key is trying to tie it back to you. How do you wantto create differentiation? What, you're competitive advantage and then make sure that you have that internal first and foremost. And don't outsource here, your smarts to >> another. I think the key point is by re factoring or Ria's re sizing. That's the interest generation that you get with cloud and scale. If you don't do that, scale can also hurt. You >> can yeah, yeah, >> comes come back and impression. It's right, really. Thanks for coming on. Appreciate the insights from great to hear from Practitioner Love the new child. I think it's a game changer. I think it's going to be a standard final question to end the segment learnings over the over the past couple of years. What some key learnings that you take away from the process that you're going to carry forward. >> Yeah, I think one one is as a company being being a blend roll between marketing the technology. One is, uh, be willing to change and adapt and be willing to bring the rest of the company with you could You can't do everything yourself. So I think you have to be a change agent for the company. I figure out that that everybody is in the journey with you and then how do you create that scale to get the get the mass moving? Because it takes it takes a village thing. Get things done. >> Bradley. Jake is making history on the Cuba's, the first marketing CIA we've interviewed super excited, great insights. This is going to be a position we think's going around for a while, of course. The Cube coverage here on Adobe Summit. Jeffery, Jeffery Thanks for watching Stay with us from or Day one of two day coverage here in Las Vegas. After this short break
SUMMARY :
It's the queue covering I'm John for Jeffrey from the Cube. Yeah, thank you. It's really interesting because you have a convergence of the lines are blurring, and part of the role of people like me are the ones you could be the bridge makers between the two This seems to be the same thing you guys are looking at right? of the story we hear all the time, which is? So tell us some of the things you do. Explain some of the things you're doing. but also campaign and analytics and, uh, you know, social and what the emerging capabilities is kind of the mantra. Is very dense. Has the platform shifted? never getting the landscape, but then be able to pick out and say, Here are the five things and you focus on Here is how I'm going class early adopter proves the model. is a piece of How are you seeing that play out in the way that you guys interact with your customers? But also the experience of agents and brokers. What you guys have done. Products simplifying our product messaging the way we talked about product specially in insurance What some of the results will take us through experiences, zealously numbers. And so you know, we're investing heavily and try and doing things like customer profile and a customer. One of the things that we've been talking about on the Q through got a lot of events, and the theme that comes up all the time at the end of day of How do you have the operational ises? of the opportunity. In the first thing, any market so you could do is go learn the business, speak the same language, then what company you on kind of classy the insurance, you know, kind of breakdown is really high, Now, on the marketing side, you saw that same thing happen side, maybe shedding some of the you know, the left side as we started becoming more pattern base and whatnot. that you get with cloud and scale. What some key learnings that you take away from the process that you're going to carry is in the journey with you and then how do you create that scale to get the get the mass moving? Jake is making history on the Cuba's, the first marketing CIA we've interviewed super
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Rick Wright | PERSON | 0.99+ |
Bradley Jenkins | PERSON | 0.99+ |
Kayla | PERSON | 0.99+ |
Wescott | PERSON | 0.99+ |
Bradley | PERSON | 0.99+ |
Jeffery | PERSON | 0.99+ |
Las Vegas | LOCATION | 0.99+ |
Adobe | ORGANIZATION | 0.99+ |
Amazon | ORGANIZATION | 0.99+ |
Jake | PERSON | 0.99+ |
Silicon Valley | LOCATION | 0.99+ |
seventeen thousand | QUANTITY | 0.99+ |
One | QUANTITY | 0.99+ |
John | PERSON | 0.99+ |
First | QUANTITY | 0.99+ |
five things | QUANTITY | 0.99+ |
Jeffrey | PERSON | 0.99+ |
Isaac | PERSON | 0.99+ |
two functions | QUANTITY | 0.99+ |
Adobe Summit | EVENT | 0.99+ |
one | QUANTITY | 0.99+ |
two worlds | QUANTITY | 0.98+ |
MetLife | ORGANIZATION | 0.98+ |
CIA | ORGANIZATION | 0.98+ |
first | QUANTITY | 0.98+ |
Cuba | LOCATION | 0.97+ |
two day | QUANTITY | 0.97+ |
first thing | QUANTITY | 0.97+ |
today | DATE | 0.96+ |
tens of thousands | QUANTITY | 0.95+ |
Adobe Summit 2019 | EVENT | 0.94+ |
Day one | QUANTITY | 0.93+ |
Martek | ORGANIZATION | 0.91+ |
one side | QUANTITY | 0.89+ |
few years ago | DATE | 0.87+ |
one thing | QUANTITY | 0.85+ |
Ria | ORGANIZATION | 0.84+ |
Twenty nineteen | QUANTITY | 0.83+ |
Three sixty | QUANTITY | 0.82+ |
one shows | QUANTITY | 0.81+ |
second | QUANTITY | 0.8+ |
Martek | LOCATION | 0.79+ |
couple | QUANTITY | 0.78+ |
Adobe Summit twenty nineteen | EVENT | 0.77+ |
last couple of years | DATE | 0.71+ |
Life | PERSON | 0.68+ |
Teo | ORGANIZATION | 0.62+ |
past couple of years | DATE | 0.59+ |
Cube | ORGANIZATION | 0.58+ |
things | QUANTITY | 0.55+ |
products | QUANTITY | 0.5+ |
Cube | TITLE | 0.37+ |
Sally Jenkins, Informatica | Informatica World 2018
>> Narrator: Live from Las Vegas, it's theCUBE, covering Informatica World 2018. Brought to you by Informatica. >> Okay, welcome back, everyone. Live here in Las Vegas at the Venetian, this is Informatica World 2018, CUBE's exclusive coverage. It's our fourth year covering Informatica World, and boy, what a transition; it's been fun to watch. I'm John Furrier, the co-host of theCUBE, with Peter Burris, Head of Research for Wikibon, SiliconANGLE, and theCUBE. Our next guest is Sally Jenkins, Executive Vice President, Chief Marketing Officer at Informatica. Welcome back, good to see you. >> Thank you, John, it's nice to see you too. >> Very comfortable here, you guys having a great event, congratulations. It's crowded, but it doesn't feel crowded. A lot of sessions are going on. What's going on with the event? Give us some stats, you've got a lot of partners here. >> Yeah, so we are very happy to be back in Las Vegas, and we are taking this up a whole notch a bit, if you can notice. We've got close to 4,000 folks who saw the Opening General Session this morning. For the first time ever, we're live streaming, and sent out a note that we were live streaming to over 250,000 customers, so I'm real happy about that. Because, as you know, with the rebrand last year, it was all about getting our message out and upleveling our message, so we're really happy that our message is getting out there, with everything that came from General Session this morning, and then, tomorrow with Closing General Session. >> Just gets bigger every year, so congratulations. >> Thank you. >> Great to see that everything comes in. Of course, the products are just right in line. The timing couldn't have been better. Multi-cloud, everything's kind of clicking. GDPR over the top, little push there for all the international customers. But the big story that we see is the journeys that are happening. You guys have been on a journey as your own company, digital disruption, digital transformation. But there's multiple journeys. Can you just take us through the vision of how you guys see the journeys, and how does Informatica fit into the customers, 'cause your customers are also changing? >> Sally: Yes, that's right. >> Do you change your business model? Anil laid it out, customers have this journey. What's the four journies? >> Yes, that's a great question, John. So we have, of course, been customer-centric ourselves. We've adapted our journeys to accommodate the journeys that we know our customers are on. And this whole conference is centered around those four journeys, so hybrid cloud, next-gen analytics, 360 engagement, and data governance and compliance. So that's what we've heard our customers deal with day in and day out, in their data-centric initiatives, and so we wanted to encapsulate that into the entire conference. So that's what it's all about, and that's an extension of our messaging that we laid out last year. So you'll see that again and again and again in a consistent fashion. >> "Disrupt Intelligently", I saw the messaging. First of all, great artwork, great branding, a lot of the images; what does that mean? 'Cause you've got all kinds of great imagery, people on the move, mobile, data's involved, obviously, the center of it. >> Well, that and data is the critical foundation for what we call "Intelligent Disruptive". So disruption with a purpose is intelligent. And we believe, with our technology, that our customers can then unleash the power of their data to create what we call their next intelligent disruption. So we were very thoughtful about the choice of words there, 'cause disruption can be considered a negative, but we see it as very much a positive, and a way for customers to leapfrog the competition, and set the tone for their markets. >> This is an interesting concept. We were talking with a lot of the customers you've had on; we've had Toyota on, and they said, quote, these testimonials just kind of pop out, "We knew we had the data; we had all these problems "we hadn't connected, but we actually had the data "when they actually connected us, and said, "we could have foreseen this." >> Sally: That's right. >> So they were disrupted in a negative way, the fact that they were trying to connect, now they're set up. And then he used an example, once they got set up, that they didn't predict that all this inbound data from the cars were coming in. So again, that's a disruption, but now they've handled it. Is that kind of where you guys were kind of connecting the dots on the intelligent piece? >> Yeah, that's right, we're helping our customers understand what to do with the data, right? So they know the data exists, but we need to help them turn it into actionable insights that leads to their next disruption, and again and again and again with their different projects. And so those are the conversations that we've been having with our customers. Just helping them, we say, unleash the power of their data. The data's there, we need to make it useful and valuable to them. >> And competitive advantage, obviously, seeing data, ease of use as a competitive strategy. Now the Microsoft announcement was interesting, because you can see that you can take an on-prem dataset, go through the Azure portal in their console, which is very cloud-native, you know, press a few buttons, connect to Informatica's intelligent cloud service, and move data. >> Sally: That's right. >> I mean, it's not like there's someone behind the curtain; it's actually a working product. >> No, it's real, it's real and it's available for preview, and if you saw the keynote this morning, you heard from Scott Guthrie. He said this whole partnership between Informatica and Microsoft, and I quote, "A match made in heaven". So there's something real there. Microsoft and their customers see the value in partnering with us, so we were really pleased to announce that today. >> I'm going to check the Internet, but I think this might be the first iPaaS integration into Azure at this level. 'Cause it's pretty deep with these guys. So that's going to certainly set up hybrid cloud instantly. >> That's right, that's right. And scale, right, we're enterprise-scale to begin with, obviously, so is Microsoft. So it's a good partnership. >> Okay, from the branding piece, I got to ask you, you guys did the rebranding, what's your one-year review, if you have to give yourself a report card, check, check, check, straight As, perfect score? If you could go back and do- >> Well, I'd like to say that we were in the honor roll. And we measure ourselves based on what our customers tell us, so we were very deliberate in choosing a few areas of which we wanted to see progress, and that is, the first one is, were people aware that we're a cloud company? And I'm delighted to say that, yes, we've absolutely moved the needle on that, so they associate Informatica with cloud, as you know, we're the number one in enterprise cloud data management. That's what we kicked off last year. And so you'll see a continued investment around the globe in the brand. We believe that good brand health is what leaders do, in terms of setting the pace for their industry. And that's exactly what we're doing. So, one year into it, we feel really good. We did what we set out, and we delivered on what we said we were going to do. And if you all remember last year's part of the rebrand, as soon as we went external, then we needed to shift our focus back internally, and think about what does this mean to our employees, and how do we leverage the culture that we already had inside Informatica and build upon that? And that's exactly what we've been working on. So we rolled out a new set of values in January. To no surprise, they're called We-DATA. And DATA stands for Do Good, Act as One Team, Think Customer First, and Aspire for the Future. And so that's what we're doing right now, is rolling that out around the world to our employees. And that was based on employee feedback, as well. >> That's bottoms up, that's good organic listening. I got to talk about branding, 'cause this is something that we're seeing a lot of. We're seeing a lot of shifts going on. When you have these shifts you mentioned earlier, about getting a competitive advantage, a leg up on the competition, you guys had that same opportunity. Because the brand, pecking order of companies is going to change with these new waves coming. With data, certainly, so it's a huge opportunity. Do you guys talk about that when you're in the brand meetings, and you're talking about with the execs, the power of the brand, and building the brand? >> Sally: Absolutely. >> And what are some of the things you're focused on to help continue to build that brand? >> Well, I think where you're going with this is what's the financial impact or value that the brand has? And everybody, from our industry analysts, to the financial analysts, to our customers, partners, they put a value on the brand. So if you don't define who you are in the market, then you let everybody else define you, and then there's no value in that. So that's really what we set out to do last year, is we wanted to define who we were, and be proud of it, and take ownership of it. >> Put a stake in the ground. >> Yeah, and then continue to invest in that. So when I say we'll continue to invest in the brand, that is about our messaging, and making sure that we are very clear as to who we are, as I said, 'cause we're setting the pace for this industry. >> And the brand promise real quick, just to summarize, if you had to kind of sum up the bumper sticker for Informatica, Disrupt Intelligently, kind of add to that, what would be the brand promise to your customers? >> Yeah, so it's the Disruptive Power of Data. And then what falls out of that is Unleashing the Power of Data, right? So that's our brand promise to our customers, is that's what we were talking about earlier, that's exactly what we do for them with our technology, and how can we help them stay ahead of their competition? >> That's great, look at the trends too. Look at what GDPR's doing, and some of the block chain stuff that's kind of emerging, it's power to the people. People want to have control of the data. >> Sally: That's right, putting the control back in their hands. >> Great stuff, so thanks for coming on theCUBE. Appreciate it, great to see you, congratulations. >> Thanks, John. >> And great to have our fourth year, our fifth year with Anil, we saw him at Amazon re:Invent in 2014, so great to continue to watch you guys grow. It's been fun to watch. >> Great, good, well stay tuned, there's more to come for sure. >> Right, can't wait to hear. It's theCUBE live here at Informatica World, two days of coverage here. We're getting down to the second day. We've got more action coming; stay here with us. I'm John Furrier, Peter Buriss, we'll be back after this short break.
SUMMARY :
Brought to you by Informatica. I'm John Furrier, the co-host of theCUBE, nice to see you too. you guys having a great and we are taking this year, so congratulations. But the big story that we see What's the four journies? the journeys that we know a lot of the images; what does that mean? and set the tone for their markets. a lot of the customers the fact that they were trying to connect, that leads to their next disruption, Now the Microsoft behind the curtain; it's and if you saw the keynote this morning, So that's going to certainly to begin with, obviously, so is Microsoft. and that is, the first one is, and building the brand? So that's really what we the pace for this industry. Yeah, so it's the That's great, look at the trends too. putting the control back in their hands. Appreciate it, great to to watch you guys grow. there's more to come for sure. We're getting down to the second day.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
John | PERSON | 0.99+ |
Sally | PERSON | 0.99+ |
Microsoft | ORGANIZATION | 0.99+ |
Sally Jenkins | PERSON | 0.99+ |
Informatica | ORGANIZATION | 0.99+ |
Peter Burris | PERSON | 0.99+ |
January | DATE | 0.99+ |
Las Vegas | LOCATION | 0.99+ |
John Furrier | PERSON | 0.99+ |
Peter Buriss | PERSON | 0.99+ |
last year | DATE | 0.99+ |
fourth year | QUANTITY | 0.99+ |
one-year | QUANTITY | 0.99+ |
Scott Guthrie | PERSON | 0.99+ |
fifth year | QUANTITY | 0.99+ |
two days | QUANTITY | 0.99+ |
Toyota | ORGANIZATION | 0.99+ |
last year | DATE | 0.99+ |
tomorrow | DATE | 0.99+ |
CUBE | ORGANIZATION | 0.99+ |
SiliconANGLE | ORGANIZATION | 0.99+ |
Wikibon | ORGANIZATION | 0.99+ |
second day | QUANTITY | 0.99+ |
over 250,000 customers | QUANTITY | 0.99+ |
first time | QUANTITY | 0.98+ |
Informatica World 2018 | EVENT | 0.98+ |
theCUBE | ORGANIZATION | 0.98+ |
four journies | QUANTITY | 0.98+ |
today | DATE | 0.98+ |
Anil | PERSON | 0.97+ |
GDPR | TITLE | 0.97+ |
this morning | DATE | 0.97+ |
first | QUANTITY | 0.96+ |
Venetian | LOCATION | 0.96+ |
first one | QUANTITY | 0.95+ |
iPaaS | TITLE | 0.95+ |
Azure | TITLE | 0.94+ |
One Team | QUANTITY | 0.91+ |
one year | QUANTITY | 0.9+ |
Informatica World | EVENT | 0.9+ |
360 engagement | QUANTITY | 0.88+ |
Informatica World | ORGANIZATION | 0.85+ |
4,000 folks | QUANTITY | 0.79+ |
DATA | ORGANIZATION | 0.79+ |
Think | ORGANIZATION | 0.79+ |
2018 | DATE | 0.76+ |
Narrator | TITLE | 0.74+ |
Amazon re:Invent in 2014 | EVENT | 0.74+ |
General Session | EVENT | 0.74+ |
Executive Vice President | PERSON | 0.73+ |
four journeys | QUANTITY | 0.67+ |
First | QUANTITY | 0.64+ |
year | QUANTITY | 0.56+ |
Aspire for the Future | ORGANIZATION | 0.54+ |
We-DATA | ORGANIZATION | 0.45+ |
Customer | TITLE | 0.41+ |
Bill Jenkins, Intel | Super Computing 2017
>> Narrator: From Denver, Colorado, it's theCUBE. Covering Super Computing 17. Brought to you by Intel. (techno music) Hey, welcome back, everybody. Jeff Frick here with theCUBE. We're in Denver, Colorado at the Super Computing Conference 2017. About 12 thousand people, talking about the outer edges of computing. It's pretty amazing. The keynote was huge. The square kilometer array, a new vocabulary word I learned today. It's pretty exciting times, and we're excited to have our next guest. He's Bill Jenkins. He's a Product Line Manager for AI on FPGAs at Intel. Bill, welcome. Thank you very much for having me. Nice to meet you, and nice to talk to you today. So you're right in the middle of this machine-learning AI storm, which we keep hearing more and more about. Kind of the next generation of big data, if you will. That's right. It's the most dynamic industry I've seen since the telecom industry back in the 90s. It's evolving every day, every month. Intel's been making some announcements. Using this combination of software programming and FPGAs on the acceleration stack to get more performance out of the data center. Did I get that right? Sure, yeah, yeah. Pretty exciting. The use of both hardware, as well as software on top of it, to open up the solution stack, open up the ecosystem. What of those things are you working on specifically? I really build first the enabling technology that brings the FPGA into that Intel ecosystem. Where Intel is trying to provide that solution from top to bottom to deliver AI products. >> Jeff: Right. Into that market. FPGAs are a key piece of that because we provide a different way to accelerate those machine-learning and AI workloads. Where we can be an offload engine to a CPU. We can be inline analytics to offload the system, and get higher performance that way. We tie into that overall Intel ecosystem of tools and products. Right. So that's a pretty interesting piece because the real-time streaming data is all the rage now, right? Not in batch. You want to get it now. So how do you get it in? How do you get it written to the database? How do you get it into the micro-processor? That's a really, really important piece. That's different than even two years ago. You didn't really hear much about real-time. I think it's, like I said, it's evolving quite a bit. Now, a lot of people deal with training. It's the science behind it. The data scientists work to figure out what topologies they want to deploy and how they want to deploy 'em. But now, people are building products around it. >> Jeff: Right. And once they start deploying these technologies into products, they realize that they don't want to compensate for limitations in hardware. They want to work around them. A lot of this evolution that we're building is to try to find ways to more efficiently do that compute. What we call inferencing, the actual deployed machine-learning scoring, as they will. >> Jeff: Right. In a product, it's all about how quickly can I get the data out. It's not about waiting two seconds to start the processing. You know, in an autonomous-driven car where someone's crossing the road, I'm not waiting two seconds to figure out it's a person. Right, right. I need it right away. So I need to be able to do that with video feeds, right off a disk drive, from the ethernet data coming in. I want to do that directly in line, so that my processor can do what it's good at, and we offload that processor to get better system performance. Right. And then on the machine-learning specifically, 'cause that is all the rage. And it is learning. So there is a real-time aspect to it. You talked about autonomous vehicles. But there's also continuous learning over time, that's not necessarily dependent on learning immediately. Right. But continuous improvement over time. What are some of the unique challenges in machine-learning? And what are some of the ways that you guys are trying to address those? Once you've trained the network, people always have to go back and retrain. They say okay, I've got a good accuracy, but I want better performance. Then they start lowering the precision, and they say well, today we're at 32-bit, maybe 16-bit. Then they start looking into eight. But the problem is, their accuracy drops. So they retrain that into eight topology, that network, to get the performance benefit, but with the higher accuracy. The flexibility of FPGA actually allows people to take that network at 32-bit, with the 32-bit trained weights, but deploy it in lower precision. So we can abstract away the fact that the hardware's so flexible, we can do what we call floating point 11-bit floating point. Or even 8-bit floating point. Even here today at the show, we've got a binary and ternary demo, showcasing the flexibility that the FPGA can provide today with that building block piece of hardware that the FPGA can be. And really provide, not only the topologies that people are trying to build today, but tomorrow. >> Jeff: Right. Future proofing their hardware. But then the precisions that they may want to do. So that they don't have to retrain. They can get less than a 1% accuracy loss, but they can lower that precision to get all the performance benefits of that data scientist's work to come up with a new architecture. Right. But it's interesting 'cause there's trade-offs, right? >> Bill: Sure. There's no optimum solution. It's optimum as to what you're trying to optimize for. >> Bill: Right. So really, the ability to change the ability to continue to work on those learning algorithms, to be able to change your priority, is pretty key. Yeah, a lot of times today, you want this. So this has been the mantra of the FPGA for 30 plus years. You deploy it today, and it works fine. Maybe you build an ASIC out of it. But what you want tomorrow is going to be different. So maybe if it's changing so rapidly, you build the ASIC because there's runway to that. But if there isn't, you may just say, I have the FPGA, I can just reprogram it to do what's the next architecture, the next methodology. Right. So it gives you that future proofing. That capability to sustain different topologies. Different architectures, different precisions. To kind of keep people going with the same piece of hardware. Without having to say, spin up a new ASIC every year. >> Jeff: Right, right. Which, even then, it's so dynamic it's probably faster then, every year, the way things are going today. So the other thing you mentioned is topography, and it's not the same topography you mentioned, but this whole idea of edge. Sure. So moving more and more compute, and store, and smarts to the edge. 'Cause there's just not going to be time, you mentioned autonomous vehicles, a lot of applications to get everything back up into the cloud. Back into the data center. You guys are pushing this technology, not only in the data center, but progressively closer and closer to the edge. Absolutely. The data center has a need. It's always going to be there, but they're getting big. The amount of data that we're trying to process every day is growing. I always say that the telecom industry started the Information Age. Well, the Information Age has done a great job of collecting a lot of data. We have to process that. If you think about where, maybe I'll allude back to autonomous vehicles. You're talking about thousands of gigabytes, per day, of data generated. Smart factories. Exabytes of data generated a day. What are you going to do with all that? It has to be processed. We need that compute in the data center. But we have to start pushing it out into the edge, where I start thinking, well even a show like this, I want security. So, I want to do real-time weapons detection, right? Security prevention. I want to do smart city applications. Just monitoring how traffic moves through a mall, so that I can control lighting and heating. All of these things at the edge, in the camera, that's deployed on the street. In the camera that's deployed in a mall. All of that, we want to make those smarter, so that we can do more compute. To offload the amount of data that needs to be sent back to the data center. >> Jeff: Right. As much as possible. Relevant data gets sent back. No shortage of demand for compute store networking, is there? No, no. It's really a heterogeneous world, right? We need all the different compute. We need all the different aspects of transmission of the data with 5G. We need disk space to store it. >> Jeff: Right. We need cooling to cool it. It's really becoming a heterogeneous world. All right, well, I'm going to give you the last word. I can't believe we're in November of 2017. Yeah. Which is bananas. What are you working on for 2018? What are some of your priorities? If we talk a year from now, what are we going to be talking about? Intel's acquired a lot of companies over the past couple years now on AI. You're seeing a lot of merging of the FPGA into that ecosystem. We've got the Nervana. We've got Movidius. We've got Mobileye acquisitions. Saffron Technologies. All of these things, when the FPGA is kind of a key piece of that because it gives you that flexibility of the hardware, to extend those pieces. You're going to see a lot more stuff in the cloud. A lot more stuff with partners next year. And really enabling that edge to data center compute, with things like binary neural networks, ternary neural networks. All the different next generation of topologies to kind of keep that leading edge flexibility that the FPGA can provide for people's products tomorrow. >> Jeff: Exciting times. Yeah, great. All right, Bill Jenkins. There's a lot going on in computing. If you're not getting your computer science degree, kids, think about it again. He's Bill Jenkins. I'm Jeff Frick. You're watching theCUBE from Super Computing 2017. Thanks for watching. Thank you. (techno music)
SUMMARY :
Kind of the next generation of big data, if you will. We can be inline analytics to offload the system, A lot of this evolution that we're building is to try to of hardware that the FPGA can be. So that they don't have to retrain. It's optimum as to what you're trying to optimize for. So really, the ability to change the ability to continue We need that compute in the data center. We need all the different aspects of of the hardware, to extend those pieces. There's a lot going on in computing.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Jeff | PERSON | 0.99+ |
Jeff Frick | PERSON | 0.99+ |
Bill Jenkins | PERSON | 0.99+ |
two seconds | QUANTITY | 0.99+ |
2018 | DATE | 0.99+ |
November of 2017 | DATE | 0.99+ |
8-bit | QUANTITY | 0.99+ |
16-bit | QUANTITY | 0.99+ |
32-bit | QUANTITY | 0.99+ |
today | DATE | 0.99+ |
next year | DATE | 0.99+ |
Bill | PERSON | 0.99+ |
30 plus years | QUANTITY | 0.99+ |
11-bit | QUANTITY | 0.99+ |
tomorrow | DATE | 0.99+ |
Denver, Colorado | LOCATION | 0.99+ |
Intel | ORGANIZATION | 0.98+ |
eight | QUANTITY | 0.98+ |
Movidius | ORGANIZATION | 0.98+ |
Super Computing Conference 2017 | EVENT | 0.98+ |
a day | QUANTITY | 0.96+ |
Saffron Technologies | ORGANIZATION | 0.96+ |
thousands of gigabytes | QUANTITY | 0.95+ |
Mobileye | ORGANIZATION | 0.95+ |
About 12 thousand people | QUANTITY | 0.95+ |
two years ago | DATE | 0.95+ |
90s | DATE | 0.94+ |
less than a 1% | QUANTITY | 0.94+ |
Nervana | PERSON | 0.94+ |
FPGA | ORGANIZATION | 0.9+ |
both hardware | QUANTITY | 0.89+ |
first | QUANTITY | 0.84+ |
Exabytes of data | QUANTITY | 0.76+ |
Super Computing 2017 | EVENT | 0.75+ |
past couple years | DATE | 0.73+ |
every year | QUANTITY | 0.69+ |
year | QUANTITY | 0.69+ |
per day | QUANTITY | 0.6+ |
5G | QUANTITY | 0.58+ |
Super Computing 17 | EVENT | 0.55+ |
theCUBE | ORGANIZATION | 0.52+ |
FPGA | TITLE | 0.42+ |
Sally Jenkins, Informatica - Informatica World 2017 - #INFA17 - #theCUBE
>> Narrator: Live from San Francisco, it's The Cube. Covering Informatica World 2017. Brought to you by Informatica. >> Okay, welcome back, everyone. We're live in San Francisco, this the Cube's exclusive coverage of Informatica World 2017. It's the Cube, our flagship program. We go out to the events and extract the signal from the noise. I'm John Furrier with SiliconANGLE on the Cube. My co-host Peter Burris, Head of Research for SiliconANGLE Media, as well as General Manager at Wikibon.com research. Our next guest is Sally Jenkins, who's the Executive Vice President and Chief Marketing Officer. New to Informatica, not new to the industry, but certainly put her mark on the show, with the new branding. Sally, welcome to the Cube. Great to have you. >> Thank you. >> John: I know you must be exhausted, all the work you've done. >> Thank you. We're running on adrenaline, I can tell you that. But it's all good. We feel really good about it. >> John: So this is our third year following Informatica. We know a lot of the folks from other companies, see some Symantec product guys now running the show at Informatica. Always had great product shops, but with this industry transformation with the cloud, just in the past three or four years, there's been a massive shift and wave. And the pecking order of winners is changing pretty quickly. Informatica went private, kind of like what Dell did, Dell Computer, now Dell Technologies, and re-tooled. Now, you're going to be doing the brand reboot, which we can see behind us. >> Sally: Right. >> You've done that in three months. Take us through that, because this is an interesting story. You're now going to bring the brand perspective to Informatica. What's the strategy? What's your plan? How did you get all this done in three months? >> Yes, no, it's been an incredible journey, but you know, I was just made this enormous offer as a marketer. You couldn't dream for a better challenge than what we had at Informatica. So when I came in, what I recognized is, looking all around and trying to understand our strengths and our weaknesses, and what were the opportunities. We have everything in place. So, as I mentioned in my keynote yesterday, our brand is having to catch up with the business. So the business is there, we've got great products. The leadership that we hold, with all of the Gartner Magic Quadrants, you know, leadership in the six categories that we say that matter, we have a tremendous backing to come out with a new story, and that's exactly what we needed to do. It wasn't just about the logo. In fact, the logo was the last thing that we looked at. It was about, what's our strategy? What's our vision, our mission? What's the story we want to tell with our customers? And we were hearing from our customers, as well, that they wanted us to change, because they're going through transformations. So that was kind of the backdrop for how we got started on this, and so we went right off the bat, trying to nail down our messaging, and reviewing that with customers and partners. I mean, our new partner community is a big part of this, so we did our due diligence that led up to this unveiling. >> We're always kind of complimentary of you guys. Some critical. We had some critical analysis yesterday in the wrap-up session. Minor relative to the big bets. These guys have product shops. They always have had good product shops, and with going private, they've done a lot of re-tooling, a lot of change in the past year. And they talk about that. I'm going to see... We had Amit on, we're going to have Neil on earlier, but I've got to ask you the question, as the new exec. What does the brand stand for? Because the products change, the customers, they have some legacy customers that are growing with them and transforming. What does the brand stand for, from your perspective. And what is that story? >> Well, the brand stands for unleashing the power of data. And I think, as you've probably heard throughout this conference, that our whole stance on this is understanding what the destructive power of data holds for you as a customer. Because, as our customers are transforming, we are also recognizing that we have to transform, too. And our customers are moving from on-prem to cloud. They want to use our products on subscription versus perpetual license. So we're going through this massive change right alongside our customers, and so our brand had to support that. And our brand was, quite frankly, left behind. And so that was the opportunity for us to think differently about, what is that story that's in support of what our customers want? >> The promises you want to make to customers. >> That's right. >> So next for you, you're going to take a vacation. >> (laughs) I get Friday off. (laughter) >> Work from home, basically. >> Then you're going to start applying yourself to the challenges of using data within marketing, to improve Informatica's performance to customers. >> Sally: Absolutely. >> Talk about the transformation that you think your function's going to go through, as you use Informatica to be a better Informatica. >> Yeah, that's a great question. In fact, I talked about this also in our keynote yesterday, because I was talking about a little bit outside-in, and then I flipped and said let's talk inside-out, and I was explaining how my job is to deliver the best customer experience to our customers and our partners. And in order to do that, I need to have those unique insights that I gather from all the data that I'm collecting on our customers and our partners, to make sure that they're getting the right information at the right time to make those right decisions. And so I'm using our own internal intelligent data lake to create what we call our marketing data lake, and that gives me-- First of all, it gives me the whole perspective of the customer and what they're doing and where they're coming from, so that then I can turn that around and make that a unique experience for our customers. So I shared that, because I wanted our customers to understand that I'm going through the same thing that they're going through. In fact, if you've seen some of the quotes that are hanging around here at Informatica World. Jewelry, TV, AWS, they're all talking about delivering the best customer experience for their customers. So, I feel like I'm going through this just as well as our customers are. >> So what's the marketing perspective? Because now you have to sell to the customers. You're listening, so digital's going to be a big part of it. We're in a digital transformation, so we're here at a physical event, we're broadcasting digitally live, and all these assets are flying around. There's a lot of data out there. (laughs) How are you harnessing that data? What's your vision on how you're going to bring Informatica to that digital role, for listening to the customers, engaging with them-- >> Sally: That's right, that's right. >> And creating a touchpoint, digitally. >> Well, and that's-- Digital is a big part of what I'm responsible for, and we oftentimes talk about what's the digital journey our customers go on? And that gets back to, I'm needing to understand where they're coming from, what device are they coming to me from? What kind of information do they want back from me to help them make the right decisions for their company? And quite frankly, bring ideas back to their C-Suite. So, that's all right in my wheelhouse, and that's actually what I'll be turning my attention to post-Informatica World, is really getting deep under, having a better understanding of what that buyer's journey looks like. And it's all digital. I mean, these days, everything we do in marketing starts with digital. >> John: And in some cases, the moment of truth to the beginning of a journey is all digital. >> Yeah. >> John: Analog is kind of-- Is self-service, if you will. >> Peter: Well, except for those customers, except for those customers that you currently have, who you're trying to expand and develop. >> Of course, yeah. >> And help them as well, obviously. But this is... One of the things I find especially interesting about marketing, and I want to test you on this, is that in many respects marketing has been under-appreciated, because the output of marketing has been very information oriented, and the value of the information that the marketing has generated. While we're now starting to recognize how unbelievably valuable it is, historically it's been under-appreciated. >> Sally: That's right, that's right. >> So how are you bringing the story, marrying the ability to tool things, but also to better define... What's the value of a brand? >> That's right. >> Peter: We have no idea. It's goodwill on a balance sheet. >> Yeah, yeah. Well, that's a great question. This is a testament to the belief that our board and our executive team has around the power of a brand. This is why they're investing. They realize that they've invested, and done, and delivered in every facet across Informatica, and the last place that they needed to invest in is in marketing, because they realize the power of the brand in that story. And look, everybody's talking about us. I mean, if you've talked to any of our customers here at Informatica World, they're like, this is unexpected. We haven't seen this from Informatica. They've been hungry for this from Informatica. And so we're really putting our money where our mouth is on the brand this year. So you'll see it all come together. And I have to say, as a marketer, I mean there's nothing more special than the company realizing that they need to get behind the brand. >> John: You've got a great mandate, and you've got a good product behind you. I think that's going to be impressive. The question I want to ask you is twofold. One is, with the rebranding experience, you mentioned you went through digital transformation, a lot of your customers are going through he same thing. What experiences did you learn from that? If you could share some insight, whether it's personal or business, anecdotally, or specifically, quantitatively, what you learned from the rebranding experience. And then, the second part of the question is the brand-building process, how do you envision that road map? >> So, it's interesting. So, I actually brought a best practice in order to get this done in three months, honestly. This is normally like a nine month process. I use this rubric where we start with understanding what's our overall vision and mission, and what's the market opportunity? So, enterprise cloud data management. We're the leaders in that. We've never said that. And so understanding each of the bits and pieces that make up the entire story, before you get to the brand identity, that's actually a best practice that we've employed now, here at Informatica. And that was something that was foreign, just because they hadn't taken the time to focus on that. So that was, not necessarily learning a best practice, but deploying a best practice here at Informatica. And now, we need to turn back inside and change the culture. So we just rolled this out with the Informatica employee base last week, and they're all excited. And I said okay, we'll tune in once we get past Informatica World. So now the employees are excited to understand, how can they help tell the message, get the story out there? How can we change the culture so they understand who we are? You know, we've had many messages in the marketplace, so there's a little bit of confusion. And now we have one story. And now we need... Our employees are our best salespeople, so we need to engage them, and arm them with a story. >> I can just see people watching this video. Give me the rubric, where do I find that rubric? >> Oh, it's posted. It's on our intranet, absolutely. >> John: Interesting, so it's on a public blog? >> It's on our intranet inside, yeah. >> John: Oh, intranet, so it's not for the general public. >> Yes, yeah. >> John: I'm sure they're dying to find out the secret rubric. >> It's a guide to help them under-- Because everyone says, oh what's your new logo? And I'm like, we have a lot to do before we talk about colors and all of that, and so we wanted to make sure our employees understood the messaging, and what was behind that, so that when we got to the logo, they could understand how everything was unfolding. >> John: So what's going to iterate? So, you know, we see this digital transformation, whether it's deploying cloud. You get some structure, a rubric as a guidepost to kind of get the hard work done, foundationally. But then iterating and being agile with the brand. Do you have a philosophy on what points of the brand you're going to be iterating on, and what are the key areas that you see some evolution on the brand side? >> Yeah, well it's definitely that reiteration of our leadership stance that we have on the marketplace. You know, we've been humble, and there's nothing wrong with humble, but we also can be proud, and we can be proud to be proud. >> John: Yeah. >> So you'll be seeing a lot more from us around our leadership that we have in the marketplace, and we're going to be taking that on the road. So what you see here this week at Informatica World, then we roll them out all around the rest of the world through our Informatica World Tours. So we'll package up the story, we'll package up the look and feel, and we'll take that out so that our customers around the world can experience what we're experiencing this week. >> Take us through... I always love to ask this question for new folks, and I did this with Jeremy Burton when he joined EMC, now he's CMO of the Dell Technologies. >> Mm-hmm. >> Because you're new. You see everything fresh, with the fresh eyes. And of course, you've got to come in a little skeptical. Wait a minute, is this going to be a good opportunity? So when you were assessing the jewels, if you will, inside Informatica, what are some of the things that jumped out at you, that you could share? What's the coolest thing you saw? What motivated you? What was the tipping point? Was there a moment when you go, okay, go the next level? >> Yeah. >> John: Was it just a sustained, hmm. Or was there one-- >> No, there were a couple of things. I mean, first and foremost, our leadership. I mean, you guys... There's no other company, I'm sure you can validate this. There's no other company who has leadership in six-- Not just in leader quadrant, but the leader, in the leadership quadrant, in six categories. That's unheard of, and it's something that we need to be proud of. We don't ever talk about that. So that was the first thing. I said okay, we'll check that box. That's really good. Second thing is this interest in investment in the brand. And I thought okay, I've heard that before, but let's see if we're serious about it. >> John: Test that. You had to test that. >> And I've tested it, I've proven it, we've delivered it, and everybody's proud. And so I think those two things combined, our leadership and the fact that we actually can get behind the story, and we have one story, that's the momentum we've needed. So, that's just validation itself. >> Jerry Held, who's a board member, was on yesterday, is very proud of the work you've done, and he's excited. So he's pumped up. You've got one board member on your side. >> Sally: Great, yeah. >> We'll get to see what Bruce thinks this afternoon. >> Board members, we've got our channel partners. I mean look, our channel, for us, is our mouthpiece. And we needed to provide them the story, too. So the channel's engaged, and more excited than ever. Our sales teams are engaged. I mean, they've needed this story. So, you know, it was just guide rails that we needed to bring to the company, and I think this just solidifies that. >> John: You have the wind at your back. Certainly we heard from the channel, sales are up. Certainly the product's doing good. Looking at over a billion dollars in revenue. Great pre-IPO. I mean it's pretty obvious-- >> Sally: Hottest pre-IPO out there. >> Okay, we're going to evaluate that, but we think it's pretty hot right now. Is it the hottest? Mm, I think so. But what are you worried about? Because with all that pressure, being aggressive on the marketing side, you've got to be... You have the wind at your back. What are you worried about, if anything? >> It all comes down to execution, right? So, we've done the heavy lifting to get us here, but as I've said to executive staff and the board, this is our starting line, it's not our finish line. And so the rest of this year, and of course going into 2018, it's all about execution. And I feel really good about that, because you can't execute without a great strategy, and we have a great strategy. And we have a great story to tell. >> And a great management team. I mentioned it earlier, and John and I talked about it last night on the wrap-up, Informatica has a track record of making promises, big promises, and at least recently, keeping them. >> Sally: That's right. >> So you have a track record of executing. Customers are able to bank in you. So going back to kind of why this might be a great opportunity is, from our perspective, you've got good products, you've got good management, you've got a good customer base, you've got a good financial position. Marketing can make a big difference. >> That's right. Now we have a good story, and we have a great brand, and we've got investment, so we'll be out there. I mean, this is our year. I hope you all see that this is our year. >> We'll be watching. You've got a lot of air cover coming in for the folks to try more business and customer satisfaction. >> Yeah. >> What are we going to be talking about next year? (laughs) >> Wait and see. Wait and see. There's more in store. >> Tell us about your first 100 days. (laughter) >> No, no, no, no, no. >> Oh, I rebranded the company. (laughs) We'll just leave it at that. >> Sally Jenkins, Executive Vice President, Chief Marketing Officer, changing the brand, building the brand for Informatica. Wind at her back. Congratulations, great to have you on the Cube. >> John: Thanks for supporting the Cube, being on the Cube. >> Thank you. Exclusive coverage here from Informatica World, I'm John Furrier with Peter Burris. Stay with us more after this short break. (electronic music)
SUMMARY :
Brought to you by Informatica. put her mark on the show, with the new branding. all the work you've done. We're running on adrenaline, I can tell you that. And the pecking order of winners is changing pretty quickly. What's the strategy? What's the story we want to tell with our customers? but I've got to ask you the question, as the new exec. And our customers are moving from on-prem to cloud. (laughs) I get Friday off. to the challenges of using data within marketing, Talk about the transformation that you think your at the right time to make those right decisions. You're listening, so digital's going to be a big part of it. And quite frankly, bring ideas back to their C-Suite. John: And in some cases, the moment of truth Is self-service, if you will. except for those customers that you currently have, that the marketing has generated. marrying the ability to tool things, Peter: We have no idea. And I have to say, as a marketer, I think that's going to be impressive. So now the employees are excited to understand, Give me the rubric, where do I find that rubric? It's on our intranet, absolutely. to find out the secret rubric. And I'm like, we have a lot to do that you see some evolution on the brand side? of our leadership stance that we have on the marketplace. so that our customers around the world now he's CMO of the Dell Technologies. What's the coolest thing you saw? John: Was it just a sustained, hmm. that we need to be proud of. You had to test that. our leadership and the fact that we actually So he's pumped up. So the channel's engaged, and more excited than ever. John: You have the wind at your back. You have the wind at your back. And so the rest of this year, and of course about it last night on the wrap-up, Informatica So going back to kind of why this I hope you all see that this is our year. You've got a lot of air cover coming in for the folks Wait and see. Tell us about your first 100 days. Oh, I rebranded the company. Congratulations, great to have you on the Cube. I'm John Furrier with Peter Burris.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Sally | PERSON | 0.99+ |
John | PERSON | 0.99+ |
Jeremy Burton | PERSON | 0.99+ |
Informatica | ORGANIZATION | 0.99+ |
Jerry Held | PERSON | 0.99+ |
Peter Burris | PERSON | 0.99+ |
Peter | PERSON | 0.99+ |
Sally Jenkins | PERSON | 0.99+ |
2018 | DATE | 0.99+ |
John Furrier | PERSON | 0.99+ |
first | QUANTITY | 0.99+ |
Dell | ORGANIZATION | 0.99+ |
Bruce | PERSON | 0.99+ |
Symantec | ORGANIZATION | 0.99+ |
nine month | QUANTITY | 0.99+ |
San Francisco | LOCATION | 0.99+ |
yesterday | DATE | 0.99+ |
six | QUANTITY | 0.99+ |
second part | QUANTITY | 0.99+ |
next year | DATE | 0.99+ |
AWS | ORGANIZATION | 0.99+ |
Informatica World | ORGANIZATION | 0.99+ |
six categories | QUANTITY | 0.99+ |
Neil | PERSON | 0.99+ |
three months | QUANTITY | 0.99+ |
SiliconANGLE | ORGANIZATION | 0.99+ |
third year | QUANTITY | 0.99+ |
EMC | ORGANIZATION | 0.99+ |
one story | QUANTITY | 0.99+ |
One | QUANTITY | 0.99+ |
Gartner | ORGANIZATION | 0.99+ |
last week | DATE | 0.99+ |
Friday | DATE | 0.98+ |
Dell Technologies | ORGANIZATION | 0.98+ |
Wikibon.com | ORGANIZATION | 0.98+ |
SiliconANGLE Media | ORGANIZATION | 0.98+ |
this year | DATE | 0.98+ |
this week | DATE | 0.98+ |
first 100 days | QUANTITY | 0.98+ |
#INFA17 | EVENT | 0.97+ |
last night | DATE | 0.97+ |
one board member | QUANTITY | 0.94+ |
Unpacking Palo Alto Networks Ignite22 | Palo Alto Networks Ignite22
>> Announcer: TheCUBE presents Ignite '22, brought to you by Palo Alto Networks. >> Welcome back to Las Vegas. It's theCUBE covering Palo Alto Networks '22, from the MGM Grand, Lisa Martin with Dave Vellante. Dave, we are going to unpack in the next few minutes what we heard and saw at day one of Palo Alto Networks, Ignite. A lot of great conversations, some great guests on the program today. >> Yeah last event, CUBE event of the year. Probably last major tech event of the year. It's kind of an interesting choice of timing, two weeks after reInvent. But you know, this crowd is it's a lot of like network engineers, SecOps pros. There's not a lot of suits here. I think they were here yesterday, all the partners. >> Yeah. >> We talked to Carl Sunderland about, Hey, these, these guys want to know how do I grow my business? You know, so it was a lot of C level executives talking about their business, and how they partner with Palo Alto to grow. The crowd today is really, you know hardcore security professionals. >> Yeah. >> So we're hearing a story of consolidation. >> Yes. >> No surprise. We've talked about that and reported on it, you know, quite extensively. The one big takeaway, and I want, I came in, as you know, wanting to understand, okay, can you through m and a maintain, you know, build a suite of great, big portfolio and at the same time maintain best of breed? And the answer was consistent. We heard it from Nikesh, we heard it from Nir Zuk. The answer was you can't be best of breed without having that large portfolio, single data lake, you know? Single version of the truth, of there is such a thing. That was interesting, that in security, you have to have that visibility. I would imagine, that's true for a lot of things. Data, see what Snowflake and Databricks are both trying to do, now AWS. So to join, we heard that last week, so that was one of the big takeaways. What were your, some of your thoughts? >> Just impressed with the level of threat intelligence that Unit 42 has done. I mean, we had Wendy Whitmer on, and she was one of the alumni, great guest. The landscape has changed so dramatically. Every business, in any industry, nobody's safe. They have such great intelligence on what's going on with malware, with ransomware, with Smishing, that they're able to get, help organizations on their way to becoming cyber resilient. You know, we've been talking a lot about cyber resiliency lately. I always want to understand, well what does it mean? How do different organizations and customers define it? Can they actually really get there? And Wendy talked about yes, it is a journey, but organizations can achieve cyber resiliency. But they need to partner with Palo Alto Networks to be able to understand the landscape and ensure that they've got security established across their organization, as it's now growingly Multicloud. >> Yeah, she's a blonde-haired Wonder Woman, superhero. I always ask security pros that question. But you know, when you talk to people like Wendy Whitmore, Kevin Mandy is somebody else. And the people at AWS, or the big cloud companies, who are on the inside, looking at the threat intelligence. They have so much data, and they have so much knowledge. They can, they analyze, they could identify the fingerprints of nation states, different, you know, criminal organizations. And the the one thing, I think it was Wendy who said, maybe it was somebody else, I think it was Wendy, that they're they're tearing down and reforming, right? >> Yes. >> After they're discovered. Okay, they pack up and leave. They're like, you know, Oceans 11. >> Yep. >> Okay. And then they recruit them and bring them back in. So that was really fascinating. Nir Zuk, we'd never had him on theCUBE before. He was tremendous founder and and CTO of Palo Alto Networks, very opinionated. You know, very clear thinker, basically saying, look you're SOC is going to be run by AI >> Yeah. >> within the next five years. And machines are going to do things that humans can't do at scale, is really what he was saying. And then they're going to get better at that, and they're going to do other things that you have done well that they haven't done well, and then they're going to do well. And so, this is an interesting discussion about you know, I remember, you know we had an event with MIT. Eric Brynjolfsson and Andy McAfee, they wrote the book "Second Machine Age." And they made the point, machines have always replaced humans. This is the first time ever that machines are replacing humans in cognitive functions. So what does that mean? That means that humans have to rely on, you know, creativity. There's got to be new training, new thinking. So it's not like you're going to be out of a job, you're just going to be doing a different job. >> Right. I thought Nir Zuk did a great job of explaining that. We often hear people that are concerned with machines taking jobs. He did a great job of, and you did a great recap, of articulating the value that both bring, and the opportunities to the humans that the machines actually deliver as well. >> Yeah so, you know, we didn't, we didn't get deep into the products today. Tomorrow we're going to have a little bit more deep dive on products. We did, we had some partners on, AWS came on, talked about their ecosystem. BJ Jenkins so, you know, BJ Jenkins again I mean super senior executive. And if I were Nikesh, he's doing exactly what I would do. Putting him on a plane and saying, go meet with customers, go make rain, right? And that's what he's doing is, he's an individual who really knows how to interact with the C-suite, has driven value, you know, over the years. So they've got that angle goin', they're driving go to market. They've got the technology piece and they've, they got to build out the ecosystem. That I think is the big opportunity for them. You know, if they're going to double as a company, this ecosystem has to quadruple. >> Yeah, yeah. >> In my opinion. And I, we saw the same thing at CrowdStrike. We said the same thing about Service Now in 2013. And so, what's happened is the GSIs, the global system integrators start to get involved. They start to partner with them and then they get to get that flywheel effect. And then there's a supercloud, I think that, you know I think Nir Zuk said, Hey, we are basically building out that, he didn't use the term supercloud. But, we're building out that cross cloud capability. You don't need another stove pipe for the edge. You know, so they got on-prem, they got AWS, Azure, you said you have to, absolutely have to run on Microsoft. 'Cause I don't believe today, right? Today they run on, I heard somebody say they run on AWS and Google. >> Yeah. >> I haven't heard much about Microsoft. >> Right. >> Both AWS and Google are here. Microsoft, the bigger competitor in security, but Nir Zuk was unequivocal. Yes, of course you have to run, you got to run it on an Alibaba cloud. He didn't say that, but if you want to secure the China cloud, you got to run on Alibaba. >> Absolutely. >> And Oracle he said. Didn't mention IBM, but no reason they can't run on IBM's cloud. But unless IBM doesn't want 'em to. >> Well they're very customer focused and customer first. So it'll be interesting to see if customers take them in that direction. >> Well it's a good point, right? If customers say, Hey we want you running in this cloud, they will. And, but he did call out Oracle, which I thought was interesting. And so, Oracle's all about mission critical data, mission critical apps. So, you know, that's a good sign. You know, I mean there's so much opportunity in cyber, but so much confusion. You know, sneak had a raise today. It was a down round, no surprise there. But you know, these companies are going to start getting tight on cash, and you've seen layoffs, right? And so, I dunno who said it, I think it was Carl at the end said in a downturn, the strongest companies come out stronger. And that's generally, generally been the case. That kind of rich get richer. We see that in the last downturn? Yes and no, to a certain extent. It's still all about execution. I mean I think about EMC coming out of the last downturn. They did come out stronger and then they started to rocket, but then look what happened. They couldn't remain independent. They were just using m and a as a technique to hide the warts. You know so, what Nir Zuk said that was most interesting to me is when we acquire, we acquire with the intent of integrating. ServiceNow has a similar philosophy. I think that's why they've been somewhat successful. And Oracle, for sure, has had a similar philosophy. So, and that idea of shifting labor into vendor R and D has always been a winning formula. >> I think we heard that today. Excited for day two tomorrow. We've got some great conversations. We're going to be able to talk with some customers, the chief product officer is on. So we have more great content coming from our last live show over the year. Dave, it's been great co-hosting day one with you. Look forward to doing it tomorrow. >> Yeah, thanks for doing this. >> All right. >> All right. For Dave Vellante, I'm Lisa Martin. You've been watching theCUBE, the leader in live enterprise and emerging tech coverage. See you tomorrow. (gentle music fades)
SUMMARY :
brought to you by Palo Alto Networks. in the next few minutes CUBE event of the year. We talked to Carl Sunderland So we're hearing a And the answer was consistent. that they're able to But you know, when you talk to people They're like, you know, Oceans 11. And then they recruit them and then they're going to do well. and the opportunities to the humans You know, if they're going to double I think that, you know Yes, of course you have to run, And Oracle he said. So it'll be interesting to see We see that in the last downturn? I think we heard that today. See you tomorrow.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Lisa Martin | PERSON | 0.99+ |
BJ Jenkins | PERSON | 0.99+ |
IBM | ORGANIZATION | 0.99+ |
Microsoft | ORGANIZATION | 0.99+ |
Dave Vellante | PERSON | 0.99+ |
Carl Sunderland | PERSON | 0.99+ |
Kevin Mandy | PERSON | 0.99+ |
Oracle | ORGANIZATION | 0.99+ |
Wendy Whitmore | PERSON | 0.99+ |
Eric Brynjolfsson | PERSON | 0.99+ |
ORGANIZATION | 0.99+ | |
2013 | DATE | 0.99+ |
Nir Zuk | PERSON | 0.99+ |
Andy McAfee | PERSON | 0.99+ |
Palo Alto Networks | ORGANIZATION | 0.99+ |
AWS | ORGANIZATION | 0.99+ |
Wendy | PERSON | 0.99+ |
Dave | PERSON | 0.99+ |
Alibaba | ORGANIZATION | 0.99+ |
Today | DATE | 0.99+ |
Las Vegas | LOCATION | 0.99+ |
today | DATE | 0.99+ |
MIT | ORGANIZATION | 0.99+ |
Tomorrow | DATE | 0.99+ |
Lisa Martin | PERSON | 0.99+ |
EMC | ORGANIZATION | 0.99+ |
tomorrow | DATE | 0.99+ |
last week | DATE | 0.99+ |
Second Machine Age | TITLE | 0.99+ |
one | QUANTITY | 0.99+ |
yesterday | DATE | 0.99+ |
CrowdStrike | ORGANIZATION | 0.99+ |
Snowflake | ORGANIZATION | 0.98+ |
Wendy Whitmer | PERSON | 0.98+ |
TheCUBE | ORGANIZATION | 0.98+ |
Wonder Woman | PERSON | 0.98+ |
Both | QUANTITY | 0.98+ |
both | QUANTITY | 0.98+ |
ServiceNow | ORGANIZATION | 0.98+ |
Multicloud | ORGANIZATION | 0.97+ |
Databricks | ORGANIZATION | 0.97+ |
Oceans 11 | ORGANIZATION | 0.97+ |
Ignite '22 | EVENT | 0.97+ |
Unit 42 | ORGANIZATION | 0.96+ |
MGM Grand | ORGANIZATION | 0.95+ |
China | LOCATION | 0.95+ |
Single | QUANTITY | 0.92+ |
day two | QUANTITY | 0.91+ |
Carl | PERSON | 0.91+ |
one thing | QUANTITY | 0.87+ |
day one | QUANTITY | 0.87+ |
CUBE | ORGANIZATION | 0.86+ |
Azure | ORGANIZATION | 0.85+ |
first | QUANTITY | 0.85+ |
Palo Alto | ORGANIZATION | 0.8+ |
single data | QUANTITY | 0.78+ |
Ignite | ORGANIZATION | 0.77+ |
theCUBE | ORGANIZATION | 0.77+ |
Palo Alto Networks '22 | EVENT | 0.75+ |
next five years | DATE | 0.72+ |
Breaking Analysis: How Palo Alto Networks Became the Gold Standard of Cybersecurity
>> From "theCube" Studios in Palo Alto in Boston bringing you data-driven insights from "theCube" and ETR. This is "Breaking Analysis" with Dave Vellante. >> As an independent pure play company, Palo Alto Networks has earned its status as the leader in security. You can measure this in a variety of ways. Revenue, market cap, execution, ethos, and most importantly, conversations with customers generally. In CISO specifically, who consistently affirm this position. The company's on track to double its revenues in fiscal year 23 relative to fiscal year 2020. Despite macro headwinds, which are likely to carry through next year, Palo Alto owes its position to a clarity of vision and strong execution on a TAM expansion strategy through acquisitions and integration into its cloud and SaaS offerings. Hello and welcome to this week's "Wikibon Cube Insights" powered by ETR and this breaking analysis and ahead of Palo Alto Ignite the company's user conference, we bring you the next chapter on top of the last week's cybersecurity update. We're going to dig into the ETR data on Palo Alto Networks as we promised and provide a glimpse of what we're going to look for at "Ignite" and posit what Palo Alto needs to do to stay on top of the hill. Now, the challenges for cybersecurity professionals. Dead simple to understand. Solving it, not so much. This is a taxonomic eye test, if you will, from Optiv. It's one of our favorite artifacts to make the point the cybersecurity landscape is a mosaic of stovepipes. Security professionals have to work with dozens of tools many legacy combined with shiny new toys to try and keep up with the relentless pace of innovation catalyzed by the incredibly capable well-funded and motivated adversaries. Cybersecurity is an anomalous market in that the leaders have low single digit market shares. Think about that. Cisco at one point held 60% market share in the networking business and it's still deep into the 40s. Oracle captures around 30% of database market revenue. EMC and storage at its peak had more than 30% of that market. Even Dell's PC market shares, you know, in the mid 20s or even over that from a revenue standpoint. So cybersecurity from a market share standpoint is even more fragmented perhaps than the software industry. Okay, you get the point. So despite its position as the number one player Palo Alto might have maybe three maybe 4% of the total market, depending on what you use as your denominator, but just a tiny slice. So how is it that we can sit here and declare Palo Alto as the undisputed leader? Well, we probably wouldn't go that far. They probably have quite a bit of competition. But this CISO from a recent ETR round table discussion with our friend Eric Bradley, summed up Palo Alto's allure. We thought pretty well. The question was why Palo Alto Networks? Here's the answer. Because of its completeness as a platform, its ability to integrate with its own products or they acquire, integrate then rebrand them as their own. We've looked at other vendors we just didn't think they were as mature and we already had implemented some of the Palo Alto tools like the firewalls and stuff and we thought why not go holistically with the vendor a single throat to choke, if you will, if stuff goes wrong. And I think that was probably the primary driver and familiarity with the tools and the resources that they provided. Now here's another stat from ETR's Eric Bradley. He gave us a glimpse of the January survey that's in the field now. The percent of IT buyers stating that they plan to consolidate redundant vendors, it went from 34% in the October survey and now stands at 44%. So we fo we feel this bodes well for consolidators like Palo Alto networks. And the same is true from Microsoft's kind of good enough approach. It should also be true for CrowdStrike although last quarter we saw softness reported on in their SMB market, whereas interestingly MongoDB actually saw consistent strength from its SMB and its self-serve. So that's something that we're watching very closely. Now, Palo Alto Networks has held up better than most of its peers in the stock market. So let's take a look at that real quick. This chart gives you a sense of how well. It's a one year comparison of Palo Alto with the bug ETF. That's the cyber basket that we like to compare often CrowdStrike, Zscaler, and Okta. Now remember Palo Alto, they didn't run up as much as CrowdStrike, ZS and Okta during the pandemic but you can see it's now down unquote only 9% for the year. Whereas the cyber basket ETF is off 27% roughly in line with the NASDAQ. We're not showing that CrowdStrike down 44%, Zscaler down 61% and Okta off a whopping 72% in the past 12 months. Now as we've indicated, Palo Alto is making a strong case for consolidating point tools and we think it will have a much harder time getting customers to switch off of big platforms like Cisco who's another leader in network security. But based on the fragmentation in the market there's plenty of room to grow in our view. We asked breaking analysis contributor Chip Simington for his take on the technicals of the stock and he said that despite Palo Alto's leadership position it doesn't seem to make much difference these days. It's all about interest rates. And even though this name has performed better than its peers, it looks like the stock wants to keep testing its 52 week lows, but he thinks Palo Alto got oversold during the last big selloff. And the fact that the company's free cash flow is so strong probably keeps it at the one 50 level or above maybe bouncing around there for a while. If it breaks through that under to the downside it's ne next test is at that low of around one 40 level. So thanks for that, Chip. Now having get that out of the way as we said on the previous chart Palo Alto has strong opinions, it's founder and CTO, Nir Zuk, is extremely clear on that point of view. So let's take a look at how Palo Alto got to where it is today and how we think you should think about his future. The company was founded around 18 years ago as a network security company focused on what they called NextGen firewalls. Now, what Palo Alto did was different. They didn't try to stuff a bunch of functionality inside of a hardware box. Rather they layered network security functions on top of its firewalls and delivered value as a service through software running at the time in its own cloud. So pretty obvious today, but forward thinking for the time and now they've moved to a more true cloud native platform and much more activity in the public cloud. In February, 2020, right before the pandemic we reported on the divergence in market values between Palo Alto and Fort Net and we cited some challenges that Palo Alto was happening having transitioning to a cloud native model. And at the time we said we were confident that Palo Alto would make it through the knot hole. And you could see from the previous chart that it has. So the company's architectural approach was to do the heavy lifting in the cloud. And this eliminates the need for customers to deploy sensors on prem or proxies on prem or sandboxes on prem sandboxes, you know for instance are vulnerable to overwhelming attacks. Think about it, if you're a sandbox is on prem you're not going to be updating that every day. No way. You're probably not going to updated even every week or every month. And if the capacity of your sandbox is let's say 20,000 files an hour you know a hacker's just going to turn up the volume, it'll overwhelm you. They'll send a hundred thousand emails attachments into your sandbox and they'll choke you out and then they'll have the run of the house while you're trying to recover. Now the cloud doesn't completely prevent that but what it does, it definitely increases the hacker's cost. So they're going to probably hit some easier targets and that's kind of the objective of security firms. You know, increase the denominator on the ROI. All right, the next thing that Palo Alto did is start acquiring aggressively, I think we counted 17 or 18 acquisitions to expand the TAM beyond network security into endpoint CASB, PaaS security, IaaS security, container security, serverless security, incident response, SD WAN, CICD pipeline security, attack service management, supply chain security. Just recently with the acquisition of Cider Security and Palo Alto by all accounts takes the time to integrate into its cloud and SaaS platform called Prisma. Unlike many acquisitive companies in the past EMC was a really good example where you ended up with a kind of a Franken portfolio. Now all this leads us to believe that Palo Alto wants to be the consolidator and is in a good position to do so. But beyond that, as multi-cloud becomes more prevalent and more of a strategy customers tell us they want a consistent experience across clouds. And is going to be the same by the way with IoT. So of the next wave here. Customers don't want another stove pipe. So we think Palo Alto is in a good position to build what we call the security super cloud that layer above the clouds that brings a common experience for devs and operational teams. So of course the obvious question is this, can Palo Alto networks continue on this path of acquire and integrate and still maintain best of breed status? Can it? Will it? Does it even have to? As Holger Mueller of Constellation Research and I talk about all the time integrated suites seem to always beat best of breed in the long run. We'll come back to that. Now, this next graphic that we're going to show you underscores this question about portfolio. Here's a picture and I don't expect you to digest it all but it's a screen grab of Palo Alto's product and solutions portfolios, network cloud, network security rather, cloud security, Sassy, CNAP, endpoint unit 42 which is their threat intelligence platform and every imaginable security service and solution for customers. Well, maybe not every, I'm sure there's more to come like supply chain with the recent Cider acquisition and maybe more IoT beyond ZingBox and earlier acquisition but we're sure there will be more in the future both organic and inorganic. Okay, let's bring in more of the ETR survey data. For those of you who don't know ETR, they are the number one enterprise data platform surveying thousands of end customers every quarter with additional drill down surveys and customer round tables just an awesome SaaS enabled platform. And here's a view that shows net score or spending momentum on the vertical axis in provision or presence within the ETR data set on the horizontal axis. You see that red dotted line at 40%. Anything at or over that indicates a highly elevated net score. And as you can see Palo Alto is right on that line just under. And I'll give you another glimpse it looks like Palo Alto despite the macro may even just edge up a bit in the next survey based on the glimpse that Eric gave us. Now those colored bars in the bottom right corner they show the breakdown of Palo Alto's net score and underscore the methodology that ETR uses. The lime green is new customer adoptions, that's 7%. The forest green at 38% represents the percent of customers that are spending 6% or more on Palo Alto solutions. The gray is at that 40 or 8% that's flat spending plus or minus 5%. The pinkish at 5% is spending is down on Palo Alto network products by 6% or worse. And the bright red at only 2% is churn or defections. Very low single digit numbers for Palo Alto, that's a real positive. What you do is you subtract the red from the green and you get a net score of 38% which is very good for a company of Palo Alto size. And we'll note this is based on just under 400 responses in the ETR survey that are Palo Alto customers out of around 1300 in the total survey. It's a really good representation of Palo Alto. And you can see the other leading companies like CrowdStrike, Okta, Zscaler, Forte, Cisco they loom large with similar aspirations. Well maybe not so much Okta. They don't necessarily rule want to rule the world. They want to rule identity and of course the ever ubiquitous Microsoft in the upper right. Now drilling deeper into the ETR data, let's look at how Palo Alto has progressed over the last three surveys in terms of market presence in the survey. This view of the data shows provision in the data going back to October, 2021, that's the gray bars. The blue is July 22 and the yellow is the latest survey from October, 2022. Remember, the January survey is currently in the field. Now the leftmost set of data there show size a company. The middle set of data shows the industry for a select number of industries in the right most shows, geographic region. Notice anything, yes, Palo Alto up across the board relative to both this past summer and last fall. So that's pretty impressive. Palo Alto network CEO, Nikesh Aurora, stressed on the last earnings call that the company is seeing somewhat elongated deal approvals and sometimes splitting up size of deals. He's stressed that certain industries like energy, government and financial services continue to spend. But we would expect even a pullback there as companies get more conservative. But the point is that Nikesh talked about how they're hiring more sales pros to work the pipeline because they understand that they have to work harder to pull deals forward 'cause they got to get more approvals and they got to increase the volume that's coming through the pipeline to account for the possibility that certain companies are going to split up the deals, you know, large deals they want to split into to smaller bite size chunks. So they're really going hard after they go to market expansion to account for that. All right, so we're going to wrap by sharing what we expect and what we're going to probe for at Palo Alto Ignite next week, Lisa Martin and I will be hosting "theCube" and here's what we'll be looking for. First, it's a four day event at the MGM with the meat of the program on days two and three. That's day two was the big keynote. That's when we'll start our broadcasting, we're going for two days. Now our understanding is we've never done Palo Alto Ignite before but our understanding it's a pretty technically oriented crowd that's going to be eager to hear what CTO and founder Nir Zuk has to say. And as well CEO Nikesh Aurora and as in addition to longtime friend of "theCube" and current president, BJ Jenkins, he's going to be speaking. Wendy Whitmore runs Unit 42 and is going to be several other high profile Palo Alto execs, as well, Thomas Kurian from Google is a featured speaker. Lee Claridge, who is Palo Alto's, chief product officer we think is going to be giving the audience heavy doses of Prisma Cloud and Cortex enhancements. Now, Cortex, you might remember, came from an acquisition and does threat detection and attack surface management. And we're going to hear a lot about we think about security automation. So we'll be listening for how Cortex has been integrated and what kind of uptake that it's getting. We've done some, you know, modeling in from the ETR. Guys have done some modeling of cortex, you know looks like it's got a lot of upside and through the Palo Alto go to market machine, you know could really pick up momentum. That's something that we'll be probing for. Now, one of the other things that we'll be watching is pricing. We want to talk to customers about their spend optimization, their spending patterns, their vendor consolidation strategies. Look, Palo Alto is a premium offering. It charges for value. It's expensive. So we also want to understand what kind of switching costs are customers willing to absorb and how onerous they are and what's the business case look like? How are they thinking about that business case. We also want to understand and really probe on how will Palo Alto maintain best of breed as it continues to acquire and integrate to expand its TAM and appeal as that one-stop shop. You know, can it do that as we talked about before. And will it do that? There's also an interesting tension going on sort of changing subjects here in security. There's a guy named Edward Hellekey who's been in "theCube" before. He hasn't been in "theCube" in a while but he's a security pro who has educated us on the nuances of protecting data privacy, public policy, how it varies by region and how complicated it is relative to security. Because securities you technically you have to show a chain of custody that proves unequivocally, for example that data has been deleted or scrubbed or that metadata does. It doesn't include any residual private data that violates the laws, the local laws. And the tension is this, you need good data and lots of it to have good security, really the more the better. But government policy is often at odds in a major blocker to sharing data and it's getting more so. So we want to understand this tension and how companies like Palo Alto are dealing with it. Our customers testing public policy in courts we think not quite yet, our government's making exceptions and policies like GDPR that favor security over data privacy. What are the trade-offs there? And finally, one theme of this breaking analysis is what does Palo Alto have to do to stay on top? And we would sum it up with three words. Ecosystem, ecosystem, ecosystem. And we said this at CrowdStrike Falcon in September that the one concern we had was the pace of ecosystem development for CrowdStrike. Is collaboration possible with competitors? Is being adopted aggressively? Is Palo Alto being adopted aggressively by global system integrators? What's the uptake there? What about developers? Look, the hallmark of a cloud company which Palo Alto is a cloud security company is a thriving ecosystem that has entries into and exits from its platform. So we'll be looking at what that ecosystem looks like how vibrant and inclusive it is where the public clouds fit and whether Palo Alto Networks can really become the security super cloud. Okay, that's a wrap stop by next week. If you're in Vegas, say hello to "theCube" team. We have an unbelievable lineup on the program. Now if you're not there, check out our coverage on theCube.net. I want to thank Eric Bradley for sharing a glimpse on short notice of the upcoming survey from ETR and his thoughts. And as always, thanks to Chip Symington for his sharp comments. Want to thank Alex Morrison, who's on production and manages the podcast Ken Schiffman as well in our Boston studio, Kristen Martin and Cheryl Knight they help get the word out on social and of course in our newsletters, Rob Hoof, is our editor in chief over at Silicon Angle who does some awesome editing, thank you to all. Remember all these episodes they're available as podcasts. Wherever you listen, all you got to do is search "Breaking Analysis" podcasts. I publish each week on wikibon.com and silicon angle.com where you can email me at david.valante@siliconangle.com or dm me at D Valante or comment on our LinkedIn post. And please do check out etr.ai. They've got the best survey data in the enterprise tech business. This is Dave Valante for "theCube" Insights powered by ETR. Thanks for watching. We'll see you next week on "Ignite" or next time on "Breaking Analysis". (upbeat music)
SUMMARY :
bringing you data-driven and of course the ever
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Alex Morrison | PERSON | 0.99+ |
Edward Hellekey | PERSON | 0.99+ |
Eric Bradley | PERSON | 0.99+ |
Lisa Martin | PERSON | 0.99+ |
Cisco | ORGANIZATION | 0.99+ |
Thomas Kurian | PERSON | 0.99+ |
Dave Vellante | PERSON | 0.99+ |
Lee Claridge | PERSON | 0.99+ |
Rob Hoof | PERSON | 0.99+ |
17 | QUANTITY | 0.99+ |
October, 2021 | DATE | 0.99+ |
Palo Alto | ORGANIZATION | 0.99+ |
February, 2020 | DATE | 0.99+ |
October, 2022 | DATE | 0.99+ |
40 | QUANTITY | 0.99+ |
Microsoft | ORGANIZATION | 0.99+ |
Dave Valante | PERSON | 0.99+ |
Wendy Whitmore | PERSON | 0.99+ |
September | DATE | 0.99+ |
October | DATE | 0.99+ |
January | DATE | 0.99+ |
Zscaler | ORGANIZATION | 0.99+ |
Okta | ORGANIZATION | 0.99+ |
Forte | ORGANIZATION | 0.99+ |
CrowdStrike | ORGANIZATION | 0.99+ |
Chip Simington | PERSON | 0.99+ |
52 week | QUANTITY | 0.99+ |
Palo Alto | ORGANIZATION | 0.99+ |
Cheryl Knight | PERSON | 0.99+ |
BJ Jenkins | PERSON | 0.99+ |
Dell | ORGANIZATION | 0.99+ |
July 22 | DATE | 0.99+ |
6% | QUANTITY | 0.99+ |
Eric | PERSON | 0.99+ |
Vegas | LOCATION | 0.99+ |
Palo Alto | LOCATION | 0.99+ |
two days | QUANTITY | 0.99+ |
one year | QUANTITY | 0.99+ |
34% | QUANTITY | 0.99+ |
Chip Symington | PERSON | 0.99+ |
Kristen Martin | PERSON | 0.99+ |
7% | QUANTITY | 0.99+ |
40% | QUANTITY | 0.99+ |
27% | QUANTITY | 0.99+ |
44% | QUANTITY | 0.99+ |
61% | QUANTITY | 0.99+ |
38% | QUANTITY | 0.99+ |
Palo Alto Networks | ORGANIZATION | 0.99+ |
Nir Zuk | PERSON | 0.99+ |
72% | QUANTITY | 0.99+ |
5% | QUANTITY | 0.99+ |
4% | QUANTITY | 0.99+ |
next week | DATE | 0.99+ |
Constellation Research | ORGANIZATION | 0.99+ |
Cider Security | ORGANIZATION | 0.99+ |
four day | QUANTITY | 0.99+ |
fiscal year 23 | DATE | 0.99+ |
8% | QUANTITY | 0.99+ |
last quarter | DATE | 0.99+ |
david.valante@siliconangle.com | OTHER | 0.99+ |
Fort Net | ORGANIZATION | 0.99+ |
ORGANIZATION | 0.99+ | |
First | QUANTITY | 0.99+ |
Ken Schiffman | PERSON | 0.99+ |
GDPR | TITLE | 0.99+ |
last fall | DATE | 0.99+ |
NASDAQ | ORGANIZATION | 0.99+ |
fiscal year 2020 | DATE | 0.99+ |
three | QUANTITY | 0.99+ |
more than 30% | QUANTITY | 0.99+ |
three words | QUANTITY | 0.99+ |
today | DATE | 0.99+ |
Oracle | ORGANIZATION | 0.99+ |
Franken | ORGANIZATION | 0.99+ |
Steve Mullaney, CEO, Aviatrix | AWS re:Invent 2022
(upbeat music) >> You got it, it's theCUBE. We are in Vegas. This is the Cube's live coverage day one of the full event coverage of AWS reInvent '22 from the Venetian Expo Center. Lisa Martin here with Dave Vellante. We love being in Vegas, Dave. >> Well, you know, this is where Super Cloud sort of was born. >> It is. >> Last year, just about a year ago. Steve Mullaney, CEO of of Aviatrix, you know, kind of helped us think it through. And we got some fun stories around. It's happening, but... >> It is happening. We're going to be talking about Super Cloud guys. >> I guess I just did the intro, Steve Mullaney >> You did my intro, don't do it again. >> Sorry I stole that from you, yeah. >> Steve Mullaney, joined just once again, one of our alumni. Steve, great to have you back on the program. >> Thanks for having me back. >> Dave: It's happening. >> It is happening. >> Dave: We talked about a year ago. Net Studio was right there. >> That was two years. Was that year ago, that was a year ago. >> Dave: It was last year. >> Yeah, I leaned over >> What's happening? >> so it's happening. It's happening. You know what, the thing I noticed what's happening now is the maturity of the cloud, right? So, if you think about this whole journey to cloud that has been, what, AWS 12 years. But really over the last few years is when enterprises have really kind of joined that journey. And three or four years ago, and this is why I came out of retirement and went to Aviatrix, was they all said, okay, now we're going to do cloud. You fast forward now three, four years from now, all of a sudden those five-year plans of evacuating the data center, they got one year left, two year left, and they're going, oh crap, we don't have five years anymore. We're, now the maturity's starting to say, we're starting to put more apps into the cloud. We're starting to put business critical apps like SAP into the cloud. This is not just like the low-hanging fruit anymore. So what's happening now is the business criticality, the scale, the maturity. And they're all now starting to hit a lot of limits that have been put into the CSPs that you never used to hit when you didn't have business critical and you didn't have that scale. They were always there. The rocks were always there. Just it was, you never hit 'em. People are starting to hit 'em now. So what's happening now is people are realizing, and I'm going to jump the gun, you asked me for my bumper sticker. The bumper sticker for Aviatrix is, "Good enough is no longer good enough." Now it's funny, it came in a keynote today, but what we see from our customers is it's time to upgrade the native constructs of networking and network security to be enterprise-grade now. It's no longer good enough to just use the native constructs because of a lack of visibility, the lack of controls, the lack of troubleshooting capabilities, all these things. "I now need enterprise grade networking." >> Let me ask you a question 'cause you got a good historical perspective on the industry. When you think about when Maritz was running VMWare. He was like any app, he said basically we're building a software mainframe. And they kind of did that, right? But then they, you know, hit the issue with scale, right? And they can't replicate the cloud. Are there things that we can draw from that experience and apply that to the cloud? What's the same, what's different? >> Oh yeah. So, 1992, do you remember what happened in 1992? I do this, weird German software company called SAP >> Yeah, R3. announced a release as R/3. Which was their first three-tier client-server application of SAP. Before that it ran on mainframes, TCP/IP. Remember that Protocol War? Guess what happened post-1992, everybody goes up like this. Infrastructure completely changes. Cisco, EMC, you name it, builds out these PCE client-server architectures. The WAN changes, MPLS, the campus, everything's home running back to that data center running SAP. That was the last 30 years ago. Great transformation of SAP. They've did it again. It's called S/4Hana. And now it's running and people are switching to S/4Hana and they're moving to the cloud. It's just starting. And that is going to alter how you build infrastructure. And so when you have that, being able to troubleshoot in hours versus minutes is a big deal. This is business critical, millions of dollars. This is not fun and games. So again, back to my, what was good enough for the last three or four years for enterprises no longer good enough, now I'm running business critical apps like SAP, and it's going to completely change infrastructure. That's happening in the cloud right now. And that's obviously a significant seismic shift, but what are some of the barriers that customers have been able to eliminate in order to get there? Or is it just good enough isn't good enough anymore? >> Barriers in terms of, well, I mean >> Lisa: The adoption. Yeah well, I mean, I think it's all the things that they go to cloud is, you know, the complexity, really, it's the agility, right? So the barrier that they have to get over is how do I keep the developer happy because the developer went to the cloud in the first place, why? Swipe the credit card because IT wasn't doing their job, 'cause every time I asked them for something, they said no. So I went around 'em. We need that. That's what they have to overcome in the move to the cloud. That is the obstacle is how do I deliver that visibility, that control, the enterprise, great functionality, but yet give the developer what they want. Because the minute I stop giving them that swipe the card operational model, what do you think they're going to do? They're going to go around me again and I can't, and the enterprise can't have that. >> That's a cultural shift. >> That's the main barrier they've got to overcome. >> Let me ask you another question. Is what we think of as mission critical, the definition changing? I mean, you mentioned SAP, obviously that's mission critical for operations, but you're also seeing new applications being developed in the cloud. >> I would say anything that's, I call business critical, same thing, but it's, business critical is internal to me, like SAP, but also anything customer-facing. That's business critical to me. If that app goes down or it has a problem, I'm not collecting revenue. So, you know, back 30 years ago, we didn't have a lot of customer-facing apps, right? It really was just SAP. I mean there wasn't a heck of a lot of cust- There were customer-facing things. But you didn't have all the digitalization that we have now, like the digital economy, where that's where the real explosion has come, is you think about all the customer-facing applications. And now every enterprise is what? A technology, digital company with a customer-facing and you're trying to get closer and closer to who? The consumer. >> Yeah, self-service. >> Self-service, B2C, everybody wants to do that. Get out of the middle man. And those are business critical applications for people. >> So what's needed under the covers to make all this happen? Give us a little double click on where you guys fit. >> You need consistent architecture. Obviously not just for one cloud, but for any cloud. But even within one cloud, forget multicloud, it gets worst with multicloud. You need a consistent architecture, right? That is automated, that is as code. I can't have the human involved. These are all, this is the API generation, you've got to be able to use automation, Terraform. And all the way from the application development platform you know, through Jenkins and all other software, through CICD pipeline and Terraform, when you, when that developer says, I want infrastructure, it has to go build that infrastructure in real time. And then when it says, I don't need it anymore it's got to take it away. And you cannot have a human involved in that process. That's what's completely changed. And that's what's giving the agility. And that's kind of a cloud model, right? Use software. >> Well, okay, so isn't that what serverless does, right? >> That's part of it. Absolutely. >> But I might still want control sometimes over the runtime if I'm running those mission critical applications. Everything in enterprise is a heterogeneous thing. It's like people, people say, well there's going to, the people going to repatriate back to on-prem, they are not repatriating back to on-prem. >> We were just talking about that, I'm like- >> Steve: It's not going to happen, right? >> It's a myth, it's a myth. >> And there's things that maybe shouldn't have ever gone into the cloud, I get that. Look, do people still have mainframes? Of course. There's certain things that you just, doesn't make sense to move to the new generation. There were things, certain applications that are very static, they weren't dynamic. You know what, keeping it on-prem it's, probably makes sense. So some of those things maybe will go back, but they never should have gone. But we are not repatriating ever, you know, that's not going to happen. >> No I agree. I mean, you know, there was an interesting paper by Andreessen, >> Yeah. >> But, I mean- >> Steve: Yeah it was a little self-serving for some company that need more funding, yeah. You look at the numbers. >> Steve: Yeah. >> It tells the story. It's just not happening. >> No. And the reason is, it's that agility, right? And so that's what people, I would say that what you need to do is, and in order to get that agility, you have to have that consistency. You have to have automation, you have to get these people out of the way. You have to use software, right? So it's that you have that swipe the card operational model for the developers. They don't want to hear the word no. >> Lisa: Right. >> What do you think is going to happen with AWS? Because we heard, I don't know if you heard Selipsky's keynote this morning, but you've probably heard the hallway talk. >> Steve: I did, yeah. >> Okay. You did. So, you know, connecting the dots, you know doubling down on all the primitives, that we expected. We kind of expected more of the higher level stuff, which really didn't see much of that, a little bit. >> Steve: Yeah. So, you know, there's a whole thing about, okay, does the cloud get commoditized? Does it not? I think the secret weapon's the ecosystem, right? Because they're able to sell through with guys like you. Make great margins on that. >> Steve: Yeah, well, yeah. >> What are your thoughts though on the future of AWS? >> IAS is going to get commoditized. So this is the fallacy that a lot of the CSPs have, is they thought that they were going to commoditize enterprise. It never happens that way. What's going to happen is infrastructure as a service, the lower level, which is why you see all the CSPs talking about what? Oracle Cloud, industry cloud. >> Well, sure, absolutely, yeah. >> We got to get to the apps, we got to get to SAP, we got to get to all that, because that's not going to get commoditized, right. But all the infrastructural service where AWS is king that is going to get commoditized, absolutely. >> Okay, so, but historically, you know Cisco's still got 60% plus gross margins. EMC always had good margin. How pure is the lone survivor in Flash? They got 70% gross margins. So infrastructure actually has always been a pretty good business. >> Yeah that's true. But it's a hell of a lot easier, particularly with people like Aviatrix and others that are building these common architectural things that create simplicity and abstract the way the complexities of underneath such that we allow your network to run an AWS, Azure, Google, Oracle, whatever, exactly the same. So it makes it a hell of a lot easier >> Dave: Super cloud. >> to go move. >> But I want to tap your brain because you have a good perspective of this because servers used to be a great margin business too on-prem and now it's not. It's a low margin business 'cause all the margin went to Intel. >> Yeah. But the cloud guys, you know, AWS in particular, makes a ton of dough on servers, so, or compute. So it's going to be interesting to see over time if that gets com- that's why they're going so hard after silicon. >> I think if they can, I think if you can capture the workload. So AWS and everyone else, as another example, this SAP, they call that a gravity workload. You know what gravity workload is? It's a black hole. It drags everything else with it. If you get SAP or Oracle or a mainframe app, it ain't going anywhere. And then what's going to happen is all your other apps are going to follow it. So that's what they're all going to fight for, is type of app. >> You said something earlier about, forget multicloud, for a moment, but, that idea of the super cloud, this abstraction layer, I mean, is that a real business value for customers other than, oh I got all these clouds, I need 'em to work together. You know, from your perspective from Aviatrix perspective, is it an opportunity for you to build on top of that? Or are you just looking at, look, I'm going to do really good work in AWS, in Azure? Now we're making the same experience. >> I hear this every single day from our customers is they look and they say, good enough isn't good enough. I've now hit the point, I'm hitting route limitations. I'm hitting, I'm doing things manually, and that's fine when I don't have that many applications or I don't have mission critical. The dogs are eating the dog food, we're going into the cloud and they're looking and then saying this is not an operational model for me. I've hit the point where I can't keep doing this, I can't throw bodies at this, I need software. And that's the opportunity for us, is they look and they say, I'm doing it in one cloud, but, and there's zero chance I'm going to be able to figure that out in the two or three other clouds. Every enterprise I talk to says multicloud is inevitable. Whether they're in it now, they all know they're going to go, because it's the business units that demand it. It's not the IT teams that demand it, it's the line of business that says, I like GCP for this reason. >> The driver's functionality that they're getting. >> It's the app teams that say, I have this service and GCP's better at it than AWS. >> Yeah, so it's not so much a cost game or the end all coffee mug, right? >> No, no. >> Google does this better than Microsoft, or better than- >> If you asked an IT person, they would rather not have multicloud. They actually tried to fight it. No, why would you want to support four clouds when you could support one right? That's insane. >> Dave and Lisa: Right. If they didn't have a choice and, and so it, the decision was made without them, and actually they weren't even notified until day before. They said, oh, good news, we're going to GCP tomorrow. Well, why wasn't I notified? Well, we're notifying you now. >> Yeah, you would've said, no. >> Steve: This is cloud bottle, let's go. >> Super cloud again. Did you see the Berkeley paper, sky computing I think they call it? Down at Berkeley, yep Dave Linthicum from Deloitte. He's talking about, I think he calls it meta cloud. It's happening. >> Yeah, yeah, yeah. >> It's happening. >> No, and because customers, customers want that. They... >> And talk about some customer example or two that you think really articulates the value of why it's happening and the outcomes that it's generating. >> I mean, I was just talking to Lamb Weston last night. So we had a reception, Lamb Weston, huge, frozen potatoes. They serve like, I dunno, some ungodly percentage of all the french fries to all the fast food. It's unbelievable what they do. Do you know, they have special chemicals they put on the french fries. So when you get your DoorDash, they stay crispy longer. They've invented that patented it. But anyway, it's all these businesses you've never heard of and they do all the, and again, they're moving to SAP or they're actually SAP in the cloud, they're one of the first ones. They did it through Accenture. They're pulling it back off from Accenture. They're not happy with the service they're getting. They're going to use us for their networking and network security because they're going to get that visibility and control back. And they're going to repatriate it back from a managed service and bring it back and run it in-house. And the SAP basis engineers want it to happen because they see the visibility and control that the infrastructure guy's going to get because of us, which leads to, all they care about is uptime and performance. That's it. And they're going to say the infrastructure team's going to lead to better uptime and better performance if it's running on Aviatrix. >> And business performance and uptime, business critical >> That is the business. That is the business. >> It is. So what are some of the things next coming down the pike from Aviatrix? Any secret sauce you can share? >> Lot of secrets. So, two secrets. One, the next thing people really want to do, embedded network security into the network. We've kind of talked about this. You're going to be seeing some things from us. Where does network security belong? In the network. Embedded in the fabric of the network, not as this dumb device called the next-gen firewall that you steer traffic to. It has to be into the fabric of what we do, what we call airspace. You're going to see us talk about that. And then the next thing, back to the maturity of the cloud, as they build out the core, guess what they're doing? It's this thing called edge, Dave, right? And guess what they're going to do? It's not about connecting the cloud to the edge to the cloud with dumb things like SD-WAN, right? Or SaaS. It's actually the other way around. Go into the cloud, turn around, look out at the edge and say, how do I extend the cloud out to the edge, and make it look like a VPC. That's what people are doing. Why, 'cause I want the operational model. I want all the things that I can do in the cloud out at the edge. And everyone knows it's been in networking. I've been in networking for 37 years. He who wins the core does what? Wins the edge, 'cause that's what happens. You do it first in the core and then you want one architecture, one common architecture, one consistent way of doing everything. And that's going to go out to the edge and it's going to look like a VPC from an operational model. >> And Amazon's going to support that, no doubt. >> Yeah, I mean every, you know, every, and then it's just how do you want to go do that? And us as the networking and network security provider, we're getting dragged to the edge by our customer. Because you're my networking provider. And that means, end to end. And they're trying to drag us into on-prem too, yeah. >> Lot's going on, you're going to have to come back- >> Because they want one networking vendor. >> But wait, and you say what? >> We will never do like switches and any of the keep Arista, the Cisco, and all that kind of stuff. But we will start sucking in net flow. We will start doing, from an operational perspective, we will integrate a lot of the things that are happening in on-prem into our- >> No halfway house. >> Copilot. >> No halfway house, no two architectures. But you'll take the data in. >> You want one architecture. >> Yeah. >> Yeah, totally. >> Right play. >> Amazing stuff. >> And he who wins the core, guess what's more strategic to them? What's more strategic on-prem or cloud? Cloud. >> It flipped three years ago. >> Dave: Yeah. >> So he who wins in the clouds going to win everywhere. >> Got it, We'll keep our eyes on that. >> Steve: Cause and effect. >> Thank you so much for joining us. We've got your bumper sticker already. It's been a great pleasure having you on the program. You got to come back, there's so, we've- >> You posting the bumper sticker somewhere? >> Lisa: It's going to be our Instagram. >> Oh really, okay. >> And an Instagram sto- This is new for you guys. Always coming up with new ideas. >> Raising the bar. >> It is, it is. >> Me advance, I mean, come on. >> I love it. >> All right, for our guest Steve Mullaney and Dave Vellante, I'm Lisa Martin. You're watching theCUBE, the leader in live enterprise and emerging tech coverage.
SUMMARY :
This is the Cube's live coverage day one Well, you know, this is where you know, kind of helped We're going to be talking don't do it again. I stole that from you, yeah. Steve, great to have you Dave: We talked about Was that year ago, that was a year ago. We're, now the maturity's starting to say, and apply that to the cloud? 1992, do you remember And that is going to alter in the move to the cloud. That's the main barrier being developed in the cloud. like the digital economy, Get out of the middle man. covers to make all this happen? And all the way from the That's part of it. the people going to into the cloud, I get that. I mean, you know, there You look at the numbers. It tells the story. and in order to get that agility, going to happen with AWS? of the higher level stuff, does the cloud get commoditized? a lot of the CSPs have, that is going to get How pure is the lone survivor in Flash? and abstract the way 'cause all the margin went to Intel. But the cloud guys, you capture the workload. of the super cloud, this And that's the opportunity that they're getting. It's the app teams that say, to support four clouds the decision was made without them, Did you see the Berkeley paper, No, and that you think really that the infrastructure guy's That is the business. coming down the pike from Aviatrix? It's not about connecting the cloud to And Amazon's going to And that means, end to end. Because they want and any of the keep Arista, the Cisco, But you'll take the data in. And he who wins the core, clouds going to win everywhere. You got to come back, there's so, we've- This is new for you guys. the leader in live enterprise
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Steve | PERSON | 0.99+ |
Lisa Martin | PERSON | 0.99+ |
Dave Vellante | PERSON | 0.99+ |
Steve Mullaney | PERSON | 0.99+ |
Cisco | ORGANIZATION | 0.99+ |
AWS | ORGANIZATION | 0.99+ |
Dave Vellante | PERSON | 0.99+ |
Vegas | LOCATION | 0.99+ |
Dave | PERSON | 0.99+ |
Lisa | PERSON | 0.99+ |
60% | QUANTITY | 0.99+ |
Amazon | ORGANIZATION | 0.99+ |
Dave Linthicum | PERSON | 0.99+ |
two | QUANTITY | 0.99+ |
70% | QUANTITY | 0.99+ |
Microsoft | ORGANIZATION | 0.99+ |
37 years | QUANTITY | 0.99+ |
Aviatrix | ORGANIZATION | 0.99+ |
EMC | ORGANIZATION | 0.99+ |
five-year | QUANTITY | 0.99+ |
1992 | DATE | 0.99+ |
Deloitte | ORGANIZATION | 0.99+ |
ORGANIZATION | 0.99+ | |
five years | QUANTITY | 0.99+ |
Last year | DATE | 0.99+ |
Accenture | ORGANIZATION | 0.99+ |
Oracle | ORGANIZATION | 0.99+ |
a year ago | DATE | 0.99+ |
Andreessen | PERSON | 0.99+ |
Arista | ORGANIZATION | 0.99+ |
Lamb Weston | ORGANIZATION | 0.99+ |
three | DATE | 0.99+ |
tomorrow | DATE | 0.99+ |
Net Studio | ORGANIZATION | 0.99+ |
one | QUANTITY | 0.99+ |
One | QUANTITY | 0.98+ |
last year | DATE | 0.98+ |
SAP | ORGANIZATION | 0.98+ |
today | DATE | 0.98+ |
Lamb Weston | ORGANIZATION | 0.98+ |
last night | DATE | 0.98+ |
Berkeley | ORGANIZATION | 0.98+ |
one cloud | QUANTITY | 0.98+ |
one cloud | QUANTITY | 0.98+ |
two secrets | QUANTITY | 0.97+ |
two architectures | QUANTITY | 0.97+ |
last 30 years ago | DATE | 0.97+ |
12 years | QUANTITY | 0.97+ |
zero chance | QUANTITY | 0.97+ |
three years ago | DATE | 0.97+ |
Venetian Expo Center | LOCATION | 0.97+ |
Stephen Chin, JFrog | KubeCon + CloudNativeCon NA 2022
>>Good afternoon, brilliant humans, and welcome back to the Cube. We're live in Detroit, Michigan at Cub Con, and I'm joined by John Furrier. John three exciting days buzzing. How you doing? >>That's great. I mean, we're coming down to the third day. We're keeping the energy going, but this segment's gonna be awesome. The CD foundation's doing amazing work. Developers are gonna be running businesses and workflows are changing. Productivity's the top conversation, and you're gonna start to see a coalescing of the communities who are continuous delivery, and it's gonna be awesome. >>And, and our next guess is an outstanding person to talk about this. We are joined by Stephen Chin, the chair of the CD Foundation. Steven, thanks so much for being here. >>No, no, my pleasure. I mean, this has been an amazing week quote that CubeCon with all of the announcements, all of the people who came out here to Detroit and, you know, fantastic. Like just walking around, you bump into all the right people here. Plus we held a CD summit zero day events, and had a lot of really exciting announcements this week. >>Gotta love the shirt. I gotta say, it's one of my favorites. Love the logos. Love the love the branding. That project got traction. What's the news in the CD foundation? I tried to sneak in the back. I got a little laid into your co-located event. It was packed. Everyone's engaged. It was really looked, look really cool. Give us the update. >>What's the news? Yeah, I know. So we, we had a really, really powerful event. All the key practitioners, the open source leads and folks were there. And one of, one of the things which I think we've done a really good job in the past six months with the CD foundation is getting back to the roots and focusing on technical innovation, right? This is what drives foundations, having strong projects, having people who are building innovation, and also bringing in a new innovation. So one of the projects which we added to the CD foundation this week is called Persia. So it's a, it's a decentralized package repository for getting open source libraries. And it solves a lot of the problems which you get when you have centralized infrastructure. You don't have the right security certificates, you don't have the right verification libraries. And these, these are all things which large companies provision and build out inside of their infrastructure. But the open source communities don't have the benefit of the same sort of really, really strong architecture. A lot of, a lot of the systems we depend upon. It's >>A good point, yeah. >>Yeah. I mean, if you think about the systems that developers depend upon, we depend upon, you know, npm, ruby Gems, Mayn Central, and these systems been around for a while. Like they serve the community well, right? They're, they're well supported by the companies and it's, it's, it's really a great contribution that they give us. But every time there's an outage or there's a security issue, guess, guess how many security issues that our, our research team found at npm? Just ballpark. >>74. >>So there're >>It's gotta be thousands. I mean, it's gotta be a lot of tons >>Of Yeah, >>They, they're currently up to 60,000 >>Whoa. >>Vulnerable, malicious packages in NPM and >>Oh my gosh. So that's a super, that's a jar number even. I know it was gonna be huge, but Holy mo. >>Yeah. So that's a software supply chain in actually right there. So that's, that's open source. Everything's out there. What's, how do, how does, how do you guys fix that? >>Yeah, so per peria kind of shifts the whole model. So when, when you think about a system that can be sustained, it has to be something which, which is not just one company. It has to be a, a, a set of companies, be vendor neutral and be decentralized. So that's why we donated it to the Continuous Delivery Foundation. So that can be that governance body, which, which makes sure it's not a single company, it is to use modern technologies. So you, you, you just need something which is immutable, so it can't be changed. So you can rely on it. It has to have a strong transaction ledger so you can see all of the history of it. You can build up your software, build materials off of it, and it, it has to have a strong peer-to-peer architecture, so it can be sustained long term. >>Steven, you mentioned something I want to just get back to. You mentioned outages and disruption. I, you didn't, you didn't say just the outages, but this whole disruption angle is interesting if something happens. Talk about the impact of the developer. They stalled, inefficiencies create basically disruption. >>No, I mean, if, if, so, so if you think about most DevOps teams in big companies, they support hundreds or thousands of teams and an hour of outage. All those developers, they, they can't program, they can't work. And that's, that's a huge loss of productivity for the company. Now, if you, if you take that up a level when MPM goes down for an hour, how many millions of man hours are wasted by not being able to get your builds working by not being able to get your codes to compile. Like it's, it's >>Like, yeah, I mean, it's almost hard to fathom. I mean, everyone's, It's stopped. Exactly. It's literally like having the plug pulled >>Exactly on whenever you're working on, That's, that's the fundamental problem we're trying to solve. Is it, it needs to be on a, like a well supported, well architected peer to peer network with some strong backing from big companies. So the company is working on Persia, include J Frog, which who I work for, Docker, Oracle. We have Deploy hub, Huawei, a whole bunch of other folks who are also helping out. And when you look at all of those folks, they all have different interests, but it's designed in a way where no single party has control over the network. So really it's, it's a system system. You, you're not relying upon one company or one logo. You're relying upon a well-architected open source implementation that everyone can rely >>On. That's shared software, but it's kind of a fault tolerant feature too. It's like, okay, if something happens here, you have a distributed piece of it, decentralized, you're not gonna go down. You can remediate. All right, so where's this go next? I mean, cuz we've been talking about the role of developer. This needs to be a modern, I won't say modern upgrade, but like a modern workflow or value chain. What's your vision? How do you see that? Cuz you're the center of the CD foundation coming together. People are gonna be coalescing multiple groups. Yeah. >>What's the, No, I think this is a good point. So there, there's a, a lot of different continuous delivery, continuous integration technologies. We're actually, from a Linux Foundation standpoint, we're coalescing all the continued delivery events into one big conference >>Next. You just made an announcement about this earlier this week. Tell us about CD events. What's going on, what's in, what's in the cooker? >>Yeah, and I think one of the big announcements we had was the 0.1 release of CD events. And CD events allows you to take all these systems and connect them in an event scalable, event oriented architecture. The first integration is between Tecton and Capin. So now you can get CD events flowing cleanly between your, your continuous delivery and your observability. And this extends through your entire DevOps pipeline. We all, we all need a standards based framework Yep. For how we get all the disparate continuous integration, continuous delivery, observability systems to, to work together. That's also high performance. It scales with our needs and it, it kind of gives you a future architecture to build on top of. So a lot of the companies I was talking with at the CD summit Yeah. They were very excited about not only using this with the projects we announced, but using this internally as an architecture to build their own DevOps pipelines on. >>I bet that feels good to hear. >>Yeah, absolutely. Yeah. >>Yeah. You mentioned Teton, they just graduated. I saw how many projects have graduated? >>So we have two graduated projects right now. We have Jenkins, which is the first graduated project. Now Tecton is also graduated. And I think this shows that for Tecton it was, it was time, the very mature project, great support, getting a lot of users and having them join the set of graduated projects. And the continuous delivery foundation is a really strong portfolio. And we have a bunch of other projects which also are on their way towards graduation. >>Feels like a moment of social proof I bet. >>For you all. Yeah, yeah. Yeah. No, it's really good. Yeah. >>How long has the CD Foundation been around? >>The CD foundation has been around for, i, I won't wanna say the exact number of years, a few years now. >>Okay. >>But I, I think that it, it was formed because what we wanted is we wanted a foundation which was purpose built. So CNCF is a great foundation. It has a very large umbrella of projects and it takes kind of that big umbrella approach where a lot of different efforts are joining it, a lot of things are happening and you can get good traction, but it produces its own bottlenecks in process. Having a foundation which is just about continuous delivery caters to more of a DevOps, professional DevOps audience. I think this, this gives a good platform for best practices. We're working on a new CDF best practices Yeah. Guide. We're working when use cases with all the member companies. And it, it gives that thought leadership platform for continuous delivery, which you need to be an expert in that area >>And the best practices too. And to identify the issues. Because at the end of the day, with the big thing that's coming out of this is velocity and more developers coming on board. I mean, this is the big thing. More people doing more. Yeah. Well yeah, I mean you take this open source continuous thunder away, you have more developers coming in, they be more productive and then people are gonna even either on the DevOps side or on the straight AP upside. And this is gonna be a huge issue. And the other thing that comes out that I wanna get your thoughts on is the supply chain issue you talked about is hot verifications and certifications of code is such big issue. Can you share your thoughts on that? Because Yeah, this is become, I won't say a business model for some companies, but it's also becoming critical for security that codes verified. >>Yeah. Okay. So I, I think one of, one of the things which we're specifically doing with the Peria project, which is unique, is rather than distributing, for example, libraries that you developed on your laptop and compiled there, or maybe they were built on, you know, a runner somewhere like Travis CI or GitHub actions, all the libraries being distributed on Persia are built by the authorized nodes in the network. And then they're, they're verified across all of the authorized nodes. So you nice, you have a, a gar, the basic guarantee we're giving you is when you download something from the Peria network, you'll get exactly the same binary as if you built it yourself from source. >>So there's a lot of trust >>And, and transparency. Yeah, exactly. And if you remember back to like kind of the seminal project, which kicked off this whole supply chain security like, like whirlwind it was SolarWinds. Yeah. Yeah. And the exact problem they hit was the build ran, it produced a result, they modified the code of the bill of the resulting binary and then they signed it. So if you built with the same source and then you went through that same process a second time, you would've gotten a different result, which was a malicious pre right. Yeah. And it's very hard to risk take, to take a binary file Yep. And determine if there's malicious code in it. Cuz it's not like source code. You can't inspect it, you can't do a code audit. It's totally different. So I think we're solving a key part of this with Persia, where you're freeing open source projects from the possibility of having their binaries, their packages, their end reduces, tampered with. And also upstream from this, you do want to have verification of prs, people doing code reviews, making sure that they're looking at the source code. And I think there's a lot of good efforts going on in the open source security foundation. So I'm also on the governing board of Open ssf >>To Do you sleep? You have three jobs you've said on camera? No, I can't even imagine. Yeah. Didn't >>You just spin that out from this open source security? Is that the new one they >>Spun out? Yeah, So the Open Source Security foundation is one of the new Linux Foundation projects. They, they have been around for a couple years, but they did a big reboot last year around this time. And I think what they really did a good job of now is bringing all the industry players to the table, having dialogue with government agencies, figuring out like, what do we need to do to support open source projects? Is it more investment in memory, safe languages? Do we need to have more investment in, in code audits or like security reviews of opensource projects. Lot of things. And all of those things require money investments. And that's what all the companies, including Jay Frogger doing to advance open source supply chain security. I >>Mean, it's, it's really kind of interesting to watch some different demographics of the developers and the vendors and the customers. On one hand, if you're a hardware person company, you have, you talk zero trust your software, your top trust, so your trusted code, and you got zero trust. It's interesting, depending on where you're coming from, they're all trying to achieve the same thing. It means zero trust. Makes sense. But then also I got code, I I want trust. Trust and verified. So security is in everything now. So code. So how do you see that traversing over? Is it just semantics or what's your view on that? >>The, the right way of looking at security is from the standpoint of the hacker, because they're always looking for >>Well said, very well said, New >>Loop, hope, new loopholes, new exploits. And they're, they're very, very smart people. And I think when you, when you look some >>Of the smartest >>Yeah, yeah, yeah. I, I, I work with, well former hackers now, security researchers, >>They converted, they're >>Recruited. But when you look at them, there's like two main classes of like, like types of exploits. So some, some attacker groups. What they're looking for is they're looking for pulse zero days, CVEs, like existing vulnerabilities that they can exploit to break into systems. But there's an increasing number of attackers who are now on the opposite end of the spectrum. And what they're doing is they're creating their own exploits. So, oh, they're for example, putting malicious code into open source projects. Little >>Trojan horse status. Yeah. >>They're they're getting their little Trojan horses in. Yeah. Or they're finding supply chain attacks by maybe uploading a malicious library to NPM or to pii. And by creating these attacks, especially ones that start at the top of the supply chain, you have such a large reach. >>I was just gonna say, it could be a whole, almost gives me chills as we're talking about it, the systemic, So this is this >>Gnarly nation state attackers, like people who wanted serious >>Damages. Engineered hack just said they're high, highly funded. Highly skilled. Exactly. Highly agile, highly focused. >>Yes. >>Teams, team. Not in the teams. >>Yeah. And so, so one, one example of this, which actually netted quite a lot of money for the, for the hacker who exposed it was, you guys probably heard about this, but it was a, an attack where they uploaded a malicious library to npm with the same exact namespace as a corporate library and clever, >>Creepy. >>It's called a dependency injection attack. And what happens is if you, if you don't have the right sort of security package management guidelines inside your company, and it's just looking for the latest version of merging multiple repositories as like a, like a single view. A lot of companies were accidentally picking up the latest version, which was out in npm uploaded by Alex Spearson was the one who did the, the attack. And he simultaneously reported bug bounties on like a dozen different companies and netted 130 k. Wow. So like these sort of attacks that they're real Yep. They're exploitable. And the, the hackers >>Complex >>Are finding these sort of attacks now in our supply chain are the ones who really are the most dangerous. That's the biggest threat to us. >>Yeah. And we have stacker ones out there. You got a bunch of other services, the white hat hackers get the bounties. That's really important. All right. What's next? What's your vision of this show as we end Coan? What's the most important story coming outta Coan in your opinion? And what are you guys doing next? >>Well, I, I actually think this is, this is probably not what most hooks would say is the most exciting story to con, but I find this personally the best is >>I can't wait for this now. >>So, on, on Sunday, the CNCF ran the first kids' day. >>Oh. >>And so they had a, a free kids workshop for, you know, underprivileged kids for >>About, That's >>Detroit area. It was, it was taught by some of the folks from the CNCF community. So Arro, Eric hen my, my older daughter, Cassandra's also an instructor. So she also was teaching a raspberry pie workshop. >>Amazing. And she's >>Here and Yeah, Yeah. She's also here at the show. And when you think about it, you know, there's always, there's, there's, you know, hundreds of announcements this week, A lot of exciting technologies, some of which we've talked about. Yeah. But it's, it's really what matters is the community. >>It this is a community first event >>And the people, and like, if we're giving back to the community and helping Detroit's kids to get better at technology, to get educated, I think that it's a worthwhile for all of us to be here. >>What a beautiful way to close it. That is such, I'm so glad you brought that up and brought that to our attention. I wasn't aware of that. Did you know that was >>Happening, John? No, I know about that. Yeah. No, that was, And that's next generation too. And what we need, we need to get down into the elementary schools. We gotta get to the kids. They're all doing robotics club anyway in high school. Computer science is now, now a >>Sport, in my opinion. Well, I think that if you're in a privileged community, though, I don't think that every school's doing robotics. And >>That's why Well, Cal Poly, Cal Poly and the universities are stepping up and I think CNCF leadership is amazing here. And we need more of it. I mean, I'm, I'm bullish on this. I love it. And I think that's a really great story. No, >>I, I am. Absolutely. And, and it just goes to show how committed CNF is to community, Putting community first and Detroit. There has been such a celebration of Detroit this whole week. Stephen, thank you so much for joining us on the show. Best Wishes with the CD Foundation. John, thanks for the banter as always. And thank you for tuning in to us here live on the cube in Detroit, Michigan. I'm Savannah Peterson and we are having the best day. I hope you are too.
SUMMARY :
How you doing? We're keeping the energy going, but this segment's gonna be awesome. the chair of the CD Foundation. of the announcements, all of the people who came out here to Detroit and, you know, What's the news in the CD foundation? You don't have the right security certificates, you don't have the right verification libraries. you know, npm, ruby Gems, Mayn Central, I mean, it's gotta be a lot of tons So that's a super, that's a jar number even. What's, how do, how does, how do you guys fix that? It has to have a strong transaction ledger so you can see all of the history of it. Talk about the impact of the developer. No, I mean, if, if, so, so if you think about most DevOps teams It's literally like having the plug pulled And when you look at all of those folks, they all have different interests, you have a distributed piece of it, decentralized, you're not gonna go down. What's the, No, I think this is a good point. What's going on, what's in, what's in the cooker? And CD events allows you to take all these systems and connect them Yeah. I saw how many projects have graduated? And the continuous delivery foundation is a really strong portfolio. For you all. The CD foundation has been around for, i, I won't wanna say the exact number of years, it gives that thought leadership platform for continuous delivery, which you need to be an expert in And the other thing that comes out that I wanna get your thoughts on is So you nice, you have a, a gar, the basic guarantee And the exact problem they hit was the build ran, To Do you sleep? And I think what they really did a good job of now is bringing all the industry players to So how do you see that traversing over? And I think when you, when you look some Yeah, yeah, yeah. But when you look at them, there's like two main classes of like, like types Yeah. the supply chain, you have such a large reach. Engineered hack just said they're high, highly funded. Not in the teams. the same exact namespace as a corporate library the latest version, which was out in npm uploaded by Alex Spearson That's the biggest threat to us. And what are you guys doing next? the CNCF community. And she's And when you think about it, And the people, and like, if we're giving back to the community and helping Detroit's kids to get better That is such, I'm so glad you brought that up and brought that to our attention. into the elementary schools. And And I think that's a really great story. And thank you for tuning in to us here live
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Steven | PERSON | 0.99+ |
Stephen Chin | PERSON | 0.99+ |
Alex Spearson | PERSON | 0.99+ |
Stephen | PERSON | 0.99+ |
Continuous Delivery Foundation | ORGANIZATION | 0.99+ |
Cal Poly | ORGANIZATION | 0.99+ |
Detroit | LOCATION | 0.99+ |
Oracle | ORGANIZATION | 0.99+ |
John | PERSON | 0.99+ |
Cassandra | PERSON | 0.99+ |
Huawei | ORGANIZATION | 0.99+ |
130 k. | QUANTITY | 0.99+ |
Savannah Peterson | PERSON | 0.99+ |
hundreds | QUANTITY | 0.99+ |
John Furrier | PERSON | 0.99+ |
one | QUANTITY | 0.99+ |
Jay Frogger | PERSON | 0.99+ |
Mayn Central | ORGANIZATION | 0.99+ |
CNCF | ORGANIZATION | 0.99+ |
Tecton | ORGANIZATION | 0.99+ |
CD Foundation | ORGANIZATION | 0.99+ |
last year | DATE | 0.99+ |
Sunday | DATE | 0.99+ |
Docker | ORGANIZATION | 0.99+ |
Detroit, Michigan | LOCATION | 0.99+ |
Detroit, Michigan | LOCATION | 0.99+ |
thousands | QUANTITY | 0.99+ |
third day | QUANTITY | 0.99+ |
first event | QUANTITY | 0.99+ |
Linux Foundation | ORGANIZATION | 0.99+ |
Open Source Security | ORGANIZATION | 0.99+ |
one company | QUANTITY | 0.99+ |
KubeCon | EVENT | 0.99+ |
this week | DATE | 0.98+ |
CD foundation | ORGANIZATION | 0.98+ |
CNF | ORGANIZATION | 0.98+ |
one logo | QUANTITY | 0.98+ |
millions | QUANTITY | 0.98+ |
earlier this week | DATE | 0.98+ |
JFrog | PERSON | 0.98+ |
second time | QUANTITY | 0.98+ |
Teton | ORGANIZATION | 0.98+ |
J Frog | ORGANIZATION | 0.97+ |
Arro | PERSON | 0.97+ |
CloudNativeCon | EVENT | 0.97+ |
npm | ORGANIZATION | 0.97+ |
first integration | QUANTITY | 0.97+ |
GitHub | ORGANIZATION | 0.96+ |
an hour | QUANTITY | 0.96+ |
two main classes | QUANTITY | 0.96+ |
Persia | ORGANIZATION | 0.95+ |
up to 60,000 | QUANTITY | 0.95+ |
Capin | ORGANIZATION | 0.95+ |
hundreds of announcements | QUANTITY | 0.94+ |
zero days | QUANTITY | 0.94+ |
zero trust | QUANTITY | 0.94+ |
three jobs | QUANTITY | 0.93+ |
single company | QUANTITY | 0.92+ |
Cube | ORGANIZATION | 0.91+ |
single view | QUANTITY | 0.91+ |
Deploy hub | ORGANIZATION | 0.9+ |
past six months | DATE | 0.9+ |
CD | ORGANIZATION | 0.9+ |
ruby Gems | ORGANIZATION | 0.89+ |
NA 2022 | EVENT | 0.89+ |
Eric hen | PERSON | 0.87+ |
zero day | QUANTITY | 0.86+ |
single party | QUANTITY | 0.86+ |
Breaking Analysis: We Have the Data…What Private Tech Companies Don’t Tell you About Their Business
>> From The Cube Studios in Palo Alto and Boston, bringing you data driven insights from The Cube at ETR. This is "Breaking Analysis" with Dave Vellante. >> The reverse momentum in tech stocks caused by rising interest rates, less attractive discounted cash flow models, and more tepid forward guidance, can be easily measured by public market valuations. And while there's lots of discussion about the impact on private companies and cash runway and 409A valuations, measuring the performance of non-public companies isn't as easy. IPOs have dried up and public statements by private companies, of course, they accentuate the good and they kind of hide the bad. Real data, unless you're an insider, is hard to find. Hello and welcome to this week's "Wikibon Cube Insights" powered by ETR. In this "Breaking Analysis", we unlock some of the secrets that non-public, emerging tech companies may or may not be sharing. And we do this by introducing you to a capability from ETR that we've not exposed you to over the past couple of years, it's called the Emerging Technologies Survey, and it is packed with sentiment data and performance data based on surveys of more than a thousand CIOs and IT buyers covering more than 400 companies. And we've invited back our colleague, Erik Bradley of ETR to help explain the survey and the data that we're going to cover today. Erik, this survey is something that I've not personally spent much time on, but I'm blown away at the data. It's really unique and detailed. First of all, welcome. Good to see you again. >> Great to see you too, Dave, and I'm really happy to be talking about the ETS or the Emerging Technology Survey. Even our own clients of constituents probably don't spend as much time in here as they should. >> Yeah, because there's so much in the mainstream, but let's pull up a slide to bring out the survey composition. Tell us about the study. How often do you run it? What's the background and the methodology? >> Yeah, you were just spot on the way you were talking about the private tech companies out there. So what we did is we decided to take all the vendors that we track that are not yet public and move 'em over to the ETS. And there isn't a lot of information out there. If you're not in Silicon (indistinct), you're not going to get this stuff. So PitchBook and Tech Crunch are two out there that gives some data on these guys. But what we really wanted to do was go out to our community. We have 6,000, ITDMs in our community. We wanted to ask them, "Are you aware of these companies? And if so, are you allocating any resources to them? Are you planning to evaluate them," and really just kind of figure out what we can do. So this particular survey, as you can see, 1000 plus responses, over 450 vendors that we track. And essentially what we're trying to do here is talk about your evaluation and awareness of these companies and also your utilization. And also if you're not utilizing 'em, then we can also figure out your sales conversion or churn. So this is interesting, not only for the ITDMs themselves to figure out what their peers are evaluating and what they should put in POCs against the big guys when contracts come up. But it's also really interesting for the tech vendors themselves to see how they're performing. >> And you can see 2/3 of the respondents are director level of above. You got 28% is C-suite. There is of course a North America bias, 70, 75% is North America. But these smaller companies, you know, that's when they start doing business. So, okay. We're going to do a couple of things here today. First, we're going to give you the big picture across the sectors that ETR covers within the ETS survey. And then we're going to look at the high and low sentiment for the larger private companies. And then we're going to do the same for the smaller private companies, the ones that don't have as much mindshare. And then I'm going to put those two groups together and we're going to look at two dimensions, actually three dimensions, which companies are being evaluated the most. Second, companies are getting the most usage and adoption of their offerings. And then third, which companies are seeing the highest churn rates, which of course is a silent killer of companies. And then finally, we're going to look at the sentiment and mindshare for two key areas that we like to cover often here on "Breaking Analysis", security and data. And data comprises database, including data warehousing, and then big data analytics is the second part of data. And then machine learning and AI is the third section within data that we're going to look at. Now, one other thing before we get into it, ETR very often will include open source offerings in the mix, even though they're not companies like TensorFlow or Kubernetes, for example. And we'll call that out during this discussion. The reason this is done is for context, because everyone is using open source. It is the heart of innovation and many business models are super glued to an open source offering, like take MariaDB, for example. There's the foundation and then there's with the open source code and then there, of course, the company that sells services around the offering. Okay, so let's first look at the highest and lowest sentiment among these private firms, the ones that have the highest mindshare. So they're naturally going to be somewhat larger. And we do this on two dimensions, sentiment on the vertical axis and mindshare on the horizontal axis and note the open source tool, see Kubernetes, Postgres, Kafka, TensorFlow, Jenkins, Grafana, et cetera. So Erik, please explain what we're looking at here, how it's derived and what the data tells us. >> Certainly, so there is a lot here, so we're going to break it down first of all by explaining just what mindshare and net sentiment is. You explain the axis. We have so many evaluation metrics, but we need to aggregate them into one so that way we can rank against each other. Net sentiment is really the aggregation of all the positive and subtracting out the negative. So the net sentiment is a very quick way of looking at where these companies stand versus their peers in their sectors and sub sectors. Mindshare is basically the awareness of them, which is good for very early stage companies. And you'll see some names on here that are obviously been around for a very long time. And they're clearly be the bigger on the axis on the outside. Kubernetes, for instance, as you mentioned, is open source. This de facto standard for all container orchestration, and it should be that far up into the right, because that's what everyone's using. In fact, the open source leaders are so prevalent in the emerging technology survey that we break them out later in our analysis, 'cause it's really not fair to include them and compare them to the actual companies that are providing the support and the security around that open source technology. But no survey, no analysis, no research would be complete without including these open source tech. So what we're looking at here, if I can just get away from the open source names, we see other things like Databricks and OneTrust . They're repeating as top net sentiment performers here. And then also the design vendors. People don't spend a lot of time on 'em, but Miro and Figma. This is their third survey in a row where they're just dominating that sentiment overall. And Adobe should probably take note of that because they're really coming after them. But Databricks, we all know probably would've been a public company by now if the market hadn't turned, but you can see just how dominant they are in a survey of nothing but private companies. And we'll see that again when we talk about the database later. >> And I'll just add, so you see automation anywhere on there, the big UiPath competitor company that was not able to get to the public markets. They've been trying. Snyk, Peter McKay's company, they've raised a bunch of money, big security player. They're doing some really interesting things in developer security, helping developers secure the data flow, H2O.ai, Dataiku AI company. We saw them at the Snowflake Summit. Redis Labs, Netskope and security. So a lot of names that we know that ultimately we think are probably going to be hitting the public market. Okay, here's the same view for private companies with less mindshare, Erik. Take us through this one. >> On the previous slide too real quickly, I wanted to pull that security scorecard and we'll get back into it. But this is a newcomer, that I couldn't believe how strong their data was, but we'll bring that up in a second. Now, when we go to the ones of lower mindshare, it's interesting to talk about open source, right? Kubernetes was all the way on the top right. Everyone uses containers. Here we see Istio up there. Not everyone is using service mesh as much. And that's why Istio is in the smaller breakout. But still when you talk about net sentiment, it's about the leader, it's the highest one there is. So really interesting to point out. Then we see other names like Collibra in the data side really performing well. And again, as always security, very well represented here. We have Aqua, Wiz, Armis, which is a standout in this survey this time around. They do IoT security. I hadn't even heard of them until I started digging into the data here. And I couldn't believe how well they were doing. And then of course you have AnyScale, which is doing a second best in this and the best name in the survey Hugging Face, which is a machine learning AI tool. Also doing really well on a net sentiment, but they're not as far along on that access of mindshare just yet. So these are again, emerging companies that might not be as well represented in the enterprise as they will be in a couple of years. >> Hugging Face sounds like something you do with your two year old. Like you said, you see high performers, AnyScale do machine learning and you mentioned them. They came out of Berkeley. Collibra Governance, InfluxData is on there. InfluxDB's a time series database. And yeah, of course, Alex, if you bring that back up, you get a big group of red dots, right? That's the bad zone, I guess, which Sisense does vis, Yellowbrick Data is a NPP database. How should we interpret the red dots, Erik? I mean, is it necessarily a bad thing? Could it be misinterpreted? What's your take on that? >> Sure, well, let me just explain the definition of it first from a data science perspective, right? We're a data company first. So the gray dots that you're seeing that aren't named, that's the mean that's the average. So in order for you to be on this chart, you have to be at least one standard deviation above or below that average. So that gray is where we're saying, "Hey, this is where the lump of average comes in. This is where everyone normally stands." So you either have to be an outperformer or an underperformer to even show up in this analysis. So by definition, yes, the red dots are bad. You're at least one standard deviation below the average of your peers. It's not where you want to be. And if you're on the lower left, not only are you not performing well from a utilization or an actual usage rate, but people don't even know who you are. So that's a problem, obviously. And the VCs and the PEs out there that are backing these companies, they're the ones who mostly are interested in this data. >> Yeah. Oh, that's great explanation. Thank you for that. No, nice benchmarking there and yeah, you don't want to be in the red. All right, let's get into the next segment here. Here going to look at evaluation rates, adoption and the all important churn. First new evaluations. Let's bring up that slide. And Erik, take us through this. >> So essentially I just want to explain what evaluation means is that people will cite that they either plan to evaluate the company or they're currently evaluating. So that means we're aware of 'em and we are choosing to do a POC of them. And then we'll see later how that turns into utilization, which is what a company wants to see, awareness, evaluation, and then actually utilizing them. That's sort of the life cycle for these emerging companies. So what we're seeing here, again, with very high evaluation rates. H2O, we mentioned. SecurityScorecard jumped up again. Chargebee, Snyk, Salt Security, Armis. A lot of security names are up here, Aqua, Netskope, which God has been around forever. I still can't believe it's in an Emerging Technology Survey But so many of these names fall in data and security again, which is why we decided to pick those out Dave. And on the lower side, Vena, Acton, those unfortunately took the dubious award of the lowest evaluations in our survey, but I prefer to focus on the positive. So SecurityScorecard, again, real standout in this one, they're in a security assessment space, basically. They'll come in and assess for you how your security hygiene is. And it's an area of a real interest right now amongst our ITDM community. >> Yeah, I mean, I think those, and then Arctic Wolf is up there too. They're doing managed services. You had mentioned Netskope. Yeah, okay. All right, let's look at now adoption. These are the companies whose offerings are being used the most and are above that standard deviation in the green. Take us through this, Erik. >> Sure, yet again, what we're looking at is, okay, we went from awareness, we went to evaluation. Now it's about utilization, which means a survey respondent's going to state "Yes, we evaluated and we plan to utilize it" or "It's already in our enterprise and we're actually allocating further resources to it." Not surprising, again, a lot of open source, the reason why, it's free. So it's really easy to grow your utilization on something that's free. But as you and I both know, as Red Hat proved, there's a lot of money to be made once the open source is adopted, right? You need the governance, you need the security, you need the support wrapped around it. So here we're seeing Kubernetes, Postgres, Apache Kafka, Jenkins, Grafana. These are all open source based names. But if we're looking at names that are non open source, we're going to see Databricks, Automation Anywhere, Rubrik all have the highest mindshare. So these are the names, not surprisingly, all names that probably should have been public by now. Everyone's expecting an IPO imminently. These are the names that have the highest mindshare. If we talk about the highest utilization rates, again, Miro and Figma pop up, and I know they're not household names, but they are just dominant in this survey. These are applications that are meant for design software and, again, they're going after an Autodesk or a CAD or Adobe type of thing. It is just dominant how high the utilization rates are here, which again is something Adobe should be paying attention to. And then you'll see a little bit lower, but also interesting, we see Collibra again, we see Hugging Face again. And these are names that are obviously in the data governance, ML, AI side. So we're seeing a ton of data, a ton of security and Rubrik was interesting in this one, too, high utilization and high mindshare. We know how pervasive they are in the enterprise already. >> Erik, Alex, keep that up for a second, if you would. So yeah, you mentioned Rubrik. Cohesity's not on there. They're sort of the big one. We're going to talk about them in a moment. Puppet is interesting to me because you remember the early days of that sort of space, you had Puppet and Chef and then you had Ansible. Red Hat bought Ansible and then Ansible really took off. So it's interesting to see Puppet on there as well. Okay. So now let's look at the churn because this one is where you don't want to be. It's, of course, all red 'cause churn is bad. Take us through this, Erik. >> Yeah, definitely don't want to be here and I don't love to dwell on the negative. So we won't spend as much time. But to your point, there's one thing I want to point out that think it's important. So you see Rubrik in the same spot, but Rubrik has so many citations in our survey that it actually would make sense that they're both being high utilization and churn just because they're so well represented. They have such a high overall representation in our survey. And the reason I call that out is Cohesity. Cohesity has an extremely high churn rate here about 17% and unlike Rubrik, they were not on the utilization side. So Rubrik is seeing both, Cohesity is not. It's not being utilized, but it's seeing a high churn. So that's the way you can look at this data and say, "Hm." Same thing with Puppet. You noticed that it was on the other slide. It's also on this one. So basically what it means is a lot of people are giving Puppet a shot, but it's starting to churn, which means it's not as sticky as we would like. One that was surprising on here for me was Tanium. It's kind of jumbled in there. It's hard to see in the middle, but Tanium, I was very surprised to see as high of a churn because what I do hear from our end user community is that people that use it, like it. It really kind of spreads into not only vulnerability management, but also that endpoint detection and response side. So I was surprised by that one, mostly to see Tanium in here. Mural, again, was another one of those application design softwares that's seeing a very high churn as well. >> So you're saying if you're in both... Alex, bring that back up if you would. So if you're in both like MariaDB is for example, I think, yeah, they're in both. They're both green in the previous one and red here, that's not as bad. You mentioned Rubrik is going to be in both. Cohesity is a bit of a concern. Cohesity just brought on Sanjay Poonen. So this could be a go to market issue, right? I mean, 'cause Cohesity has got a great product and they got really happy customers. So they're just maybe having to figure out, okay, what's the right ideal customer profile and Sanjay Poonen, I guarantee, is going to have that company cranking. I mean they had been doing very well on the surveys and had fallen off of a bit. The other interesting things wondering the previous survey I saw Cvent, which is an event platform. My only reason I pay attention to that is 'cause we actually have an event platform. We don't sell it separately. We bundle it as part of our offerings. And you see Hopin on here. Hopin raised a billion dollars during the pandemic. And we were like, "Wow, that's going to blow up." And so you see Hopin on the churn and you didn't see 'em in the previous chart, but that's sort of interesting. Like you said, let's not kind of dwell on the negative, but you really don't. You know, churn is a real big concern. Okay, now we're going to drill down into two sectors, security and data. Where data comprises three areas, database and data warehousing, machine learning and AI and big data analytics. So first let's take a look at the security sector. Now this is interesting because not only is it a sector drill down, but also gives an indicator of how much money the firm has raised, which is the size of that bubble. And to tell us if a company is punching above its weight and efficiently using its venture capital. Erik, take us through this slide. Explain the dots, the size of the dots. Set this up please. >> Yeah. So again, the axis is still the same, net sentiment and mindshare, but what we've done this time is we've taken publicly available information on how much capital company is raised and that'll be the size of the circle you see around the name. And then whether it's green or red is basically saying relative to the amount of money they've raised, how are they doing in our data? So when you see a Netskope, which has been around forever, raised a lot of money, that's why you're going to see them more leading towards red, 'cause it's just been around forever and kind of would expect it. Versus a name like SecurityScorecard, which is only raised a little bit of money and it's actually performing just as well, if not better than a name, like a Netskope. OneTrust doing absolutely incredible right now. BeyondTrust. We've seen the issues with Okta, right. So those are two names that play in that space that obviously are probably getting some looks about what's going on right now. Wiz, we've all heard about right? So raised a ton of money. It's doing well on net sentiment, but the mindshare isn't as well as you'd want, which is why you're going to see a little bit of that red versus a name like Aqua, which is doing container and application security. And hasn't raised as much money, but is really neck and neck with a name like Wiz. So that is why on a relative basis, you'll see that more green. As we all know, information security is never going away. But as we'll get to later in the program, Dave, I'm not sure in this current market environment, if people are as willing to do POCs and switch away from their security provider, right. There's a little bit of tepidness out there, a little trepidation. So right now we're seeing overall a slight pause, a slight cooling in overall evaluations on the security side versus historical levels a year ago. >> Now let's stay on here for a second. So a couple things I want to point out. So it's interesting. Now Snyk has raised over, I think $800 million but you can see them, they're high on the vertical and the horizontal, but now compare that to Lacework. It's hard to see, but they're kind of buried in the middle there. That's the biggest dot in this whole thing. I think I'm interpreting this correctly. They've raised over a billion dollars. It's a Mike Speiser company. He was the founding investor in Snowflake. So people watch that very closely, but that's an example of where they're not punching above their weight. They recently had a layoff and they got to fine tune things, but I'm still confident they they're going to do well. 'Cause they're approaching security as a data problem, which is probably people having trouble getting their arms around that. And then again, I see Arctic Wolf. They're not red, they're not green, but they've raised fair amount of money, but it's showing up to the right and decent level there. And a couple of the other ones that you mentioned, Netskope. Yeah, they've raised a lot of money, but they're actually performing where you want. What you don't want is where Lacework is, right. They've got some work to do to really take advantage of the money that they raised last November and prior to that. >> Yeah, if you're seeing that more neutral color, like you're calling out with an Arctic Wolf, like that means relative to their peers, this is where they should be. It's when you're seeing that red on a Lacework where we all know, wow, you raised a ton of money and your mindshare isn't where it should be. Your net sentiment is not where it should be comparatively. And then you see these great standouts, like Salt Security and SecurityScorecard and Abnormal. You know they haven't raised that much money yet, but their net sentiment's higher and their mindshare's doing well. So those basically in a nutshell, if you're a PE or a VC and you see a small green circle, then you're doing well, then it means you made a good investment. >> Some of these guys, I don't know, but you see these small green circles. Those are the ones you want to start digging into and maybe help them catch a wave. Okay, let's get into the data discussion. And again, three areas, database slash data warehousing, big data analytics and ML AI. First, we're going to look at the database sector. So Alex, thank you for bringing that up. Alright, take us through this, Erik. Actually, let me just say Postgres SQL. I got to ask you about this. It shows some funding, but that actually could be a mix of EDB, the company that commercializes Postgres and Postgres the open source database, which is a transaction system and kind of an open source Oracle. You see MariaDB is a database, but open source database. But the companies they've raised over $200 million and they filed an S-4. So Erik looks like this might be a little bit of mashup of companies and open source products. Help us understand this. >> Yeah, it's tough when you start dealing with the open source side and I'll be honest with you, there is a little bit of a mashup here. There are certain names here that are a hundred percent for profit companies. And then there are others that are obviously open source based like Redis is open source, but Redis Labs is the one trying to monetize the support around it. So you're a hundred percent accurate on this slide. I think one of the things here that's important to note though, is just how important open source is to data. If you're going to be going to any of these areas, it's going to be open source based to begin with. And Neo4j is one I want to call out here. It's not one everyone's familiar with, but it's basically geographical charting database, which is a name that we're seeing on a net sentiment side actually really, really high. When you think about it's the third overall net sentiment for a niche database play. It's not as big on the mindshare 'cause it's use cases aren't as often, but third biggest play on net sentiment. I found really interesting on this slide. >> And again, so MariaDB, as I said, they filed an S-4 I think $50 million in revenue, that might even be ARR. So they're not huge, but they're getting there. And by the way, MariaDB, if you don't know, was the company that was formed the day that Oracle bought Sun in which they got MySQL and MariaDB has done a really good job of replacing a lot of MySQL instances. Oracle has responded with MySQL HeatWave, which was kind of the Oracle version of MySQL. So there's some interesting battles going on there. If you think about the LAMP stack, the M in the LAMP stack was MySQL. And so now it's all MariaDB replacing that MySQL for a large part. And then you see again, the red, you know, you got to have some concerns about there. Aerospike's been around for a long time. SingleStore changed their name a couple years ago, last year. Yellowbrick Data, Fire Bolt was kind of going after Snowflake for a while, but yeah, you want to get out of that red zone. So they got some work to do. >> And Dave, real quick for the people that aren't aware, I just want to let them know that we can cut this data with the public company data as well. So we can cross over this with that because some of these names are competing with the larger public company names as well. So we can go ahead and cross reference like a MariaDB with a Mongo, for instance, or of something of that nature. So it's not in this slide, but at another point we can certainly explain on a relative basis how these private names are doing compared to the other ones as well. >> All right, let's take a quick look at analytics. Alex, bring that up if you would. Go ahead, Erik. >> Yeah, I mean, essentially here, I can't see it on my screen, my apologies. I just kind of went to blank on that. So gimme one second to catch up. >> So I could set it up while you're doing that. You got Grafana up and to the right. I mean, this is huge right. >> Got it thank you. I lost my screen there for a second. Yep. Again, open source name Grafana, absolutely up and to the right. But as we know, Grafana Labs is actually picking up a lot of speed based on Grafana, of course. And I think we might actually hear some noise from them coming this year. The names that are actually a little bit more disappointing than I want to call out are names like ThoughtSpot. It's been around forever. Their mindshare of course is second best here but based on the amount of time they've been around and the amount of money they've raised, it's not actually outperforming the way it should be. We're seeing Moogsoft obviously make some waves. That's very high net sentiment for that company. It's, you know, what, third, fourth position overall in this entire area, Another name like Fivetran, Matillion is doing well. Fivetran, even though it's got a high net sentiment, again, it's raised so much money that we would've expected a little bit more at this point. I know you know this space extremely well, but basically what we're looking at here and to the bottom left, you're going to see some names with a lot of red, large circles that really just aren't performing that well. InfluxData, however, second highest net sentiment. And it's really pretty early on in this stage and the feedback we're getting on this name is the use cases are great, the efficacy's great. And I think it's one to watch out for. >> InfluxData, time series database. The other interesting things I just noticed here, you got Tamer on here, which is that little small green. Those are the ones we were saying before, look for those guys. They might be some of the interesting companies out there and then observe Jeremy Burton's company. They do observability on top of Snowflake, not green, but kind of in that gray. So that's kind of cool. Monte Carlo is another one, they're sort of slightly green. They are doing some really interesting things in data and data mesh. So yeah, okay. So I can spend all day on this stuff, Erik, phenomenal data. I got to get back and really dig in. Let's end with machine learning and AI. Now this chart it's similar in its dimensions, of course, except for the money raised. We're not showing that size of the bubble, but AI is so hot. We wanted to cover that here, Erik, explain this please. Why TensorFlow is highlighted and walk us through this chart. >> Yeah, it's funny yet again, right? Another open source name, TensorFlow being up there. And I just want to explain, we do break out machine learning, AI is its own sector. A lot of this of course really is intertwined with the data side, but it is on its own area. And one of the things I think that's most important here to break out is Databricks. We started to cover Databricks in machine learning, AI. That company has grown into much, much more than that. So I do want to state to you Dave, and also the audience out there that moving forward, we're going to be moving Databricks out of only the MA/AI into other sectors. So we can kind of value them against their peers a little bit better. But in this instance, you could just see how dominant they are in this area. And one thing that's not here, but I do want to point out is that we have the ability to break this down by industry vertical, organization size. And when I break this down into Fortune 500 and Fortune 1000, both Databricks and Tensorflow are even better than you see here. So it's quite interesting to see that the names that are succeeding are also succeeding with the largest organizations in the world. And as we know, large organizations means large budgets. So this is one area that I just thought was really interesting to point out that as we break it down, the data by vertical, these two names still are the outstanding players. >> I just also want to call it H2O.ai. They're getting a lot of buzz in the marketplace and I'm seeing them a lot more. Anaconda, another one. Dataiku consistently popping up. DataRobot is also interesting because all the kerfuffle that's going on there. The Cube guy, Cube alum, Chris Lynch stepped down as executive chairman. All this stuff came out about how the executives were taking money off the table and didn't allow the employees to participate in that money raising deal. So that's pissed a lot of people off. And so they're now going through some kind of uncomfortable things, which is unfortunate because DataRobot, I noticed, we haven't covered them that much in "Breaking Analysis", but I've noticed them oftentimes, Erik, in the surveys doing really well. So you would think that company has a lot of potential. But yeah, it's an important space that we're going to continue to watch. Let me ask you Erik, can you contextualize this from a time series standpoint? I mean, how is this changed over time? >> Yeah, again, not show here, but in the data. I'm sorry, go ahead. >> No, I'm sorry. What I meant, I should have interjected. In other words, you would think in a downturn that these emerging companies would be less interesting to buyers 'cause they're more risky. What have you seen? >> Yeah, and it was interesting before we went live, you and I were having this conversation about "Is the downturn stopping people from evaluating these private companies or not," right. In a larger sense, that's really what we're doing here. How are these private companies doing when it comes down to the actual practitioners? The people with the budget, the people with the decision making. And so what I did is, we have historical data as you know, I went back to the Emerging Technology Survey we did in November of 21, right at the crest right before the market started to really fall and everything kind of started to fall apart there. And what I noticed is on the security side, very much so, we're seeing less evaluations than we were in November 21. So I broke it down. On cloud security, net sentiment went from 21% to 16% from November '21. That's a pretty big drop. And again, that sentiment is our one aggregate metric for overall positivity, meaning utilization and actual evaluation of the name. Again in database, we saw it drop a little bit from 19% to 13%. However, in analytics we actually saw it stay steady. So it's pretty interesting that yes, cloud security and security in general is always going to be important. But right now we're seeing less overall net sentiment in that space. But within analytics, we're seeing steady with growing mindshare. And also to your point earlier in machine learning, AI, we're seeing steady net sentiment and mindshare has grown a whopping 25% to 30%. So despite the downturn, we're seeing more awareness of these companies in analytics and machine learning and a steady, actual utilization of them. I can't say the same in security and database. They're actually shrinking a little bit since the end of last year. >> You know it's interesting, we were on a round table, Erik does these round tables with CISOs and CIOs, and I remember one time you had asked the question, "How do you think about some of these emerging tech companies?" And one of the executives said, "I always include somebody in the bottom left of the Gartner Magic Quadrant in my RFPs. I think he said, "That's how I found," I don't know, it was Zscaler or something like that years before anybody ever knew of them "Because they're going to help me get to the next level." So it's interesting to see Erik in these sectors, how they're holding up in many cases. >> Yeah. It's a very important part for the actual IT practitioners themselves. There's always contracts coming up and you always have to worry about your next round of negotiations. And that's one of the roles these guys play. You have to do a POC when contracts come up, but it's also their job to stay on top of the new technology. You can't fall behind. Like everyone's a software company. Now everyone's a tech company, no matter what you're doing. So these guys have to stay in on top of it. And that's what this ETS can do. You can go in here and look and say, "All right, I'm going to evaluate their technology," and it could be twofold. It might be that you're ready to upgrade your technology and they're actually pushing the envelope or it simply might be I'm using them as a negotiation ploy. So when I go back to the big guy who I have full intentions of writing that contract to, at least I have some negotiation leverage. >> Erik, we got to leave it there. I could spend all day. I'm going to definitely dig into this on my own time. Thank you for introducing this, really appreciate your time today. >> I always enjoy it, Dave and I hope everyone out there has a great holiday weekend. Enjoy the rest of the summer. And, you know, I love to talk data. So anytime you want, just point the camera on me and I'll start talking data. >> You got it. I also want to thank the team at ETR, not only Erik, but Darren Bramen who's a data scientist, really helped prepare this data, the entire team over at ETR. I cannot tell you how much additional data there is. We are just scratching the surface in this "Breaking Analysis". So great job guys. I want to thank Alex Myerson. Who's on production and he manages the podcast. Ken Shifman as well, who's just coming back from VMware Explore. Kristen Martin and Cheryl Knight help get the word out on social media and in our newsletters. And Rob Hof is our editor in chief over at SiliconANGLE. Does some great editing for us. Thank you. All of you guys. Remember these episodes, they're all available as podcast, wherever you listen. All you got to do is just search "Breaking Analysis" podcast. I publish each week on wikibon.com and siliconangle.com. Or you can email me to get in touch david.vellante@siliconangle.com. You can DM me at dvellante or comment on my LinkedIn posts and please do check out etr.ai for the best survey data in the enterprise tech business. This is Dave Vellante for Erik Bradley and The Cube Insights powered by ETR. Thanks for watching. Be well. And we'll see you next time on "Breaking Analysis". (upbeat music)
SUMMARY :
bringing you data driven it's called the Emerging Great to see you too, Dave, so much in the mainstream, not only for the ITDMs themselves It is the heart of innovation So the net sentiment is a very So a lot of names that we And then of course you have AnyScale, That's the bad zone, I guess, So the gray dots that you're rates, adoption and the all And on the lower side, Vena, Acton, in the green. are in the enterprise already. So now let's look at the churn So that's the way you can look of dwell on the negative, So again, the axis is still the same, And a couple of the other And then you see these great standouts, Those are the ones you want to but Redis Labs is the one And by the way, MariaDB, So it's not in this slide, Alex, bring that up if you would. So gimme one second to catch up. So I could set it up but based on the amount of time Those are the ones we were saying before, And one of the things I think didn't allow the employees to here, but in the data. What have you seen? the market started to really And one of the executives said, And that's one of the Thank you for introducing this, just point the camera on me We are just scratching the surface
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Erik | PERSON | 0.99+ |
Alex Myerson | PERSON | 0.99+ |
Ken Shifman | PERSON | 0.99+ |
Sanjay Poonen | PERSON | 0.99+ |
Dave Vellante | PERSON | 0.99+ |
Dave | PERSON | 0.99+ |
Erik Bradley | PERSON | 0.99+ |
November 21 | DATE | 0.99+ |
Darren Bramen | PERSON | 0.99+ |
Alex | PERSON | 0.99+ |
Cheryl Knight | PERSON | 0.99+ |
Postgres | ORGANIZATION | 0.99+ |
Databricks | ORGANIZATION | 0.99+ |
Netskope | ORGANIZATION | 0.99+ |
Adobe | ORGANIZATION | 0.99+ |
Rob Hof | PERSON | 0.99+ |
Fivetran | ORGANIZATION | 0.99+ |
$50 million | QUANTITY | 0.99+ |
21% | QUANTITY | 0.99+ |
Chris Lynch | PERSON | 0.99+ |
19% | QUANTITY | 0.99+ |
Jeremy Burton | PERSON | 0.99+ |
$800 million | QUANTITY | 0.99+ |
6,000 | QUANTITY | 0.99+ |
Oracle | ORGANIZATION | 0.99+ |
Redis Labs | ORGANIZATION | 0.99+ |
November '21 | DATE | 0.99+ |
ETR | ORGANIZATION | 0.99+ |
First | QUANTITY | 0.99+ |
25% | QUANTITY | 0.99+ |
last year | DATE | 0.99+ |
OneTrust | ORGANIZATION | 0.99+ |
two dimensions | QUANTITY | 0.99+ |
two groups | QUANTITY | 0.99+ |
November of 21 | DATE | 0.99+ |
both | QUANTITY | 0.99+ |
Boston | LOCATION | 0.99+ |
more than 400 companies | QUANTITY | 0.99+ |
Kristen Martin | PERSON | 0.99+ |
MySQL | TITLE | 0.99+ |
Moogsoft | ORGANIZATION | 0.99+ |
The Cube | ORGANIZATION | 0.99+ |
third | QUANTITY | 0.99+ |
Grafana | ORGANIZATION | 0.99+ |
H2O | ORGANIZATION | 0.99+ |
Mike Speiser | PERSON | 0.99+ |
david.vellante@siliconangle.com | OTHER | 0.99+ |
second | QUANTITY | 0.99+ |
two | QUANTITY | 0.99+ |
first | QUANTITY | 0.99+ |
28% | QUANTITY | 0.99+ |
16% | QUANTITY | 0.99+ |
Second | QUANTITY | 0.99+ |
Christian Hernandez, Codefresh | CUBE Conversation
>>And welcome to this cube conversation here in Palo Alto, California. I'm John furrier, host of the cube. We have a great guest coming in remotely from LA Christian Hernandez developer experienced lead at code fresh code fresh IO. Recently they were on our feature at a startup showcase series, season two episode one cloud data innovations, open source innovations, all good stuff, Christian. Thanks for coming on this cube conversation. >>Thank you. Thank you, John. Thank you for having me on, >>You know, I'm I was really impressed with code fresh. My met with the founders on here on the cube because GI ops AI, everything's something ops devs dev sec ops. You've got AI ops. You've got now GI ops, essentially operationalizing the software future is here and software's eating the world is, was written many years ago, but it's open source is now all. So all things software's open source and that's kind of a done deal. It's only getting better and better. Mainstream companies are contributing. You guys are on this wave of, of this open source tsunami and you got cloud scale. Automation's right there, machine learning, all this stuff is now the next gen of, of, of code, right? So you, your code fresh and your title is developer experience lead. What does that mean right now? What does it mean to be a developer experience lead? Like you make sure people having a good experience. Are you developing you figuring out the product? What does that mean? >>Yeah. That's and it's also part of the, the whole Debre explosion that's happening right now. I believe it's, you know, everyone's always asking, well, what, you know, what is developer advocate? What does that mean developer experience? What does that mean? So, so you, you kind of hit the nail on the head a little bit up there in, in the beginning, is that the, the experience of the developer when using a particular platform, right? Especially the code flash platform. That is my responsibility there at code fresh to enable, to enable end users, to enable partners, to enable, you know, anyone that wants to use the code fresh platform for their C I C D and get ops square flows. So that's, that's really my, my corner of the world is to make sure their experience is great. So that's, it's really what, what I'm here to do >>At food fresh. You know, one of the things I can say of my career, you've been kind of become a historian over time. When I was a developer back in the old days, it was simply you compiled stuff, you did QA on it. You packaged it out. You wanted out the door and you know, that was a workflow right now with the cloud. I was talking with your founders, you got new abstraction layers. Cloud has changed again again, open source. So newer things are coming, right? Like, like, like Kubernetes for instance is a great example that came out of the open source kind of the innovations. But that, and Hadoop, we were mentioning before he came on camera from a storage standpoint, kind of didn't make it because it was just too hard. Right. And it made the developer's job harder. And then it made the developer's requirements to be specialized. >>So you had kind of two problems. You had hard to use a lot of friction and then it required certain expertise when the developers just want to code. Right. So, so you have now the motion of, with GI ops, you guys are in the middle of kinda this idea of frictionless based software delivery with the cloud. So what's different now, can you talk about that specific point because no one wants to be, do hard work and have to redo things. Yeah. Shift left and all that good stuff. What's hard now, what do you guys solve? What's the, what's the friction that you're taking out what's to become frictionless. >>Yeah. Yeah. And you, you, you mentioned a very interesting point about how, you know, things that are coming out almost makes it seem harder nowadays to develop an application. You used to have it to where, you know, kind of a, sort of a waterfall sort of workflow where, you know, you develop your code, you know, you compile it. Right. You know, I guess back in the day, Java was king. I think Java still is, has a, is a large footprint out there where you would just compile it, deploy it. If it works, it works. Alright cool. And you have it and you kind of just move it along in its process. Whereas I think the, the whole idea of, I think Netflix came out with like the, the fail often fail fast release often, you know, the whole Atlassian C I C D thing, agile thing came into play. >>Where now it's, it's a little bit more complex to get your code out there delivered to get your code from one environment to the other environment, especially with the, the Avan of Kubernetes and cloud native architecture, where you can deploy and have this imutable infrastructure where you can just deploy and automate so quickly. So often that there needs to be some sort of new process now into place where to have a new process, like GI ops to where it'll, it it's frictionless, meaning that it's, it, it makes it that process a little easier makes that little, that comp that complex process of deploying onto like a cloud native architecture easier. So that way, as you said before, returning the developers to back to what they care about, mot, the most is just code. I just want to code. >>Yeah. You know, the other thing, cool thing, Christian, I wanna bring up and we'll get into some of the specifics around Argo specifically CD is that the community is responding as a kind of, it takes a village kind of mindset. People are getting into this just saying, Hey, if we can get our act together around some de facto workflows and de facto capabilities, everyone wins. It's a rising tide, floats all boats, kind of concept. CNCF certainly has been a big part of that. Even seen some of the big hyper scales getting behind it. But you guys are part of the founding members of the open get ups working group, Amazon Azure, GitHub, red hat Weaveworks and then a ton of contributors. Okay. So this is kind of cool. This means that there's like people behind this thing. Look, we gotta get here faster. What happened at co con this year? You guys had some news around Argo and you had some news around the hosted solution. Can you take a minute to explain two things, one the open community vibe, and then two, what you guys announced at Coon in Spain. >>Yeah. Yeah. So as far as open get ups, that was, you know, as you said before, code fresh was part of that, that founding committee. Right. Of, of group of people trying to figure out, define what get ups is. Right. We're trying to bring it beyond the, you know, the, the hype word, right beyond just like a marketing term to where we actually define what it actually is, because it is actually something that's out there that people are doing. Right. A lot of people, you know, remember that the, the Chick-fil-A story where it's like, they, they are completely doing, you know, this get ops thing, we're just now wanting, putting definition around it. So that was just amazing to see out at there in, in Cuban. And, but like you said, in QAN, we, you know, we're, we're, we're taking some of that, that acceleration that we see in the community to, and we, we announce our, our hosted get ops offering. >>Right. So hosted get ops is something that our customers have been asking for for a while. Many times when, you know, someone wants to use something like Argo CD, the, in, they install it on their cluster, they get up and running. And, but with, with all that comes like the feed and care of that platform, and, you know, not only just keeping the lights on, but also management security, you know, general maintenance, you know, all the things that, that come along with managing a system. And on top of that comes like the scale aspect of it. Right. And so with scale, so a lot of people go with like a hub and spoke others, go with like a fleet design in, in either case, right. There's, there's a challenge for the feet and care of it. Right. And so with code fresh coast of get ups, we take that management headache away. >>Right? So we, we take the, the, the management of, of Argo CD, the management of, of all of that, and kind of just offer Argo CD as a surface, right. Which offers, you know, allows users to, you know, let us take care of all the, of the get offs, runtime. And so they can concentrate on, you know, their application deployments. Right. And you also get things like Dora metrics, right. Integrated with the platform, you have the ability to integrate multiple CI providers, you know, like get hub actions or whatever, existing Jenkins pipelines. And really that, that code fresh platform becomes like your get ops platform becomes like, you know, your, your central view of the world of, of your, you know, get ups processes. >>Yeah. I mean, that whole single source of truth concept is really kind of needed. I gotta ask you though, with the popularity of the Argo CD on get ups internally, right. That's been clear, right. Kubernetes, the way that's going, it's accelerating fast. People want simple it's scaling, you got automation built in all that good stuff. What was the driver behind the hosted get up solution? Was it customer needs? Was it efficiency all the above? What was specifically and, and why would someone want to have the hosted versus say internal? >>Yeah. So it's, it was really driven by, you know, customer need been something that the customers have been asking for. And it's also been something that, you know, you, you, you have a process of developing an application to, you know, you know, a fleet of clusters in a traditional, you know, I keep saying traditional, get outs practice as if get outs are so old. And, you know, in, you know, when, when, when people first start out, they'll start, you know, installing Argo city on all these clusters and trying to manage that at scale it's, it's, it, it seemed like there was, you know, it it'd be nice if we can just like, be able to consume this as a service. So we don't have to like, worry about, you know, you know, best practices. We don't have to worry about security. We don't just, all of that is taken care of and managed by us at code fresh. So this is like something that, you know, has been asked for and, and something that, you know, we believe will accelerate, you know, developers into actually developing their, their applications. They don't have to worry about managing >>The platform. So just getting this right. Hosted, managed service by you guys on this one, >>Correct? Yes. >>Okay. Got it. All right. So let me, let me get in the Argo real quick, just to kind of just level set for the folks that are, are leaning into this and then kicking the tires. Where are we with Argo? What, why was it so popular? What did it do specifically? Did it just make it easier for developers to manage and monitor Kubernetes, keep 'em updated? What was the specific value behind Argo? Where, where, where did it come from and why is it so popular? >>Yeah, so Argo the Argo project, which is made up of, of a few tools, usually when people say Argo, they meet, they they're talking about Argo CD, but there's also Argo workflows, Argo events, Argo notifications. And, and like I said before, CD with that, and that is something that was developed internally at Intuit. Right? So for those of who don't know, Intuit is the company behind turbo tax. So for those, those of us in the us, we, we know, you know, we know that season all too well, the tax season. And so that was a tool that was developed internally. >>And by the way, Intuit we've done many years. They're very huge cloud adopters. They've been on that train from the day one. They've been, they've been driving a lot of cloud scale too. Sorry >>To interrupt. Yeah. And, and, and yeah, no, and, and, and also, you know, they, they were always open source first, right. So they've always had, you know, they developed something internally. They always had the, the intention of opensourcing it. And so it was really a tool that was born internally, and it was a tool that helped them, you know, get stuff done with Kubernetes. And that's kind of like the tagline they use for, for the Argo project is you need to get stuff done. They wanted their developers to focus less on deploying the application and more right. More than on writing the application itself. And so the, and so the Argo project is a suite of tools essentially that helps deploy onto Kubernetes, you know, using get ups as that, you know, that cornerstone in design, right in the design philosophy, it's so popular because of the ease of use and developer friendliness aspect of it. It's, it's, it's, it's meant to be simple right. In and simple in a, in a good sense of getting up and running, which attracted, you know, developers from, you know, all around the world. You know, other companies like red hat got into it as well. BlackRock also is, is a, is a big contributor, thousands of other independent contributors as well to the Argo project. >>Yeah. Christian, if you bring up a good point and I'm gonna go on a little tangent here, but I wanna get your reaction to something that Dave ante and I, and our cube team has been kind of riffing on lately. You mentioned, you know, Netflix earlier, you mentioned Intuit. There's a kind of a story that's been developing and, and with traction and momentum and trajectory over the past, say 10 years, the companies that went on the cloud, like Netflix into it, snowflake, snowflake, not so much now, but in terms of open source, they're all contributing lift. They're all contributing back to open source, but they're not cloud providers. Right. So you're seeing that kind of first generation, I's a massive contribution to open source. So open source been around for a while, remember the early days, and we'd all participate on projects, but now you have real companies building IP going open source first because they're on a hyperscale cloud, but they're not the cloud themselves. They took advantage of that. So there's kind of this cycle of flywheel of cloud to open source, not from the vendors themselves like Amazon, which services or Azure, but the people who rode their CapEx and built on that scale, feeding into the open source. And then coming back, this is kind of an interesting dynamic. What's your reaction to that? Do you see that? Yeah. Super cloud kind of vibe there. >>Yeah. Yeah. Well, and, and also it, it, I think it's, it's a, it's indicative that, you know, open source is not only, you know, a way to develop, you know, applications, a way to engineer, you know, your project, but also kind of like a strategic advantage in, in, in such a way. Right. You know, you, you see, you see companies like, like, like even like Microsoft has been going into, you know, open source, right. They they've been going to open source first. They made a, a huge pivot to, you know, using open source as, you know, like, like a, like a strategic direction for, for the company. And I think that goes back to, you know, a little bit for my roots, you know, I, I, I always, I always talk about, you know, I always talk about red hat, right. I always talk about, you know, I was, I was, I was in red hat previously and, you know, you know, red hat being, you know, the first billion dollar open source company. >>Right. I, we always joke is like, well, you know, internally, like we know you were a billion dollar company that sold free software. How, you know, how, how does that happen? But it's, it's, it's really, you know, built into the, built into being able to tap into those expert resources. Yeah. You know, people love using software. People love the software they love using, and they wanna improve it. Companies are now just getting out of their way. Yeah. You know, companies now, essentially, it's just like, let's just get out of the way. Let's let people work on, you know, what they wanna work on. They love the software. They wanna improve it. Let's let them, >>It's interesting. A lot of people love the clouds have all this power. If you think about what we are just riffing on and what you just said, the economics and the organic self-governing has always been the open source way where commercial value is enabled. If you play ball, right. Like, oh, red hat, for instance. And now you're seeing the community kind of be that arbiter of the cloud. So, Hey, if everyone can create value on say AWS or Azure, bring it to open source, everyone benefits across all clouds hope eventually. So the choice aspect comes in. So this community angle is huge. And I think it's changing a lot for the better. And I think this is where we're seeing a lot of that growth. And you guys have been the middle level with the Argo project and get ups specifically in that, in that sector. How have you seen that growth? What some dynamics have you seen power dynamics, organic? Is it governed well, whats some of the, the successes, what are some of the challenges? Can you share your thoughts on the community's growth around get ops and Argo project? >>Yeah, yeah. Yeah. So I've been, you know, part of some of these communities, right? Like the, the open, get, get ops community, the Argos community pretty much from the beginning and, and seeing it developed from an idea to, you know, having all these contributors, having, you know, the, the, the buzzword come out of it, you know, the get ups and it be that being the, you know, having it, you know, all over the, you know, social media, all over LinkedIn, all over all, all these, all these different channels, you know, I I've seen things like get ops con, right. So, you know, being part of the, get ops open, get ops community, you know, one of the things we did was we did get ops con it started as a meetup, you know, couple years ago. And now, you know, it was a, you know, we had an actual event at Cuan in Los Angeles. >>You know, we had like, you know, about 50 people there, but then, you know, Cuan in Valencia this past Cuan we had over 200 people, it was a second largest co-located events in, at Cuan. So that just, just seeing that community and, you know, from a personal standpoint, you know, be being part of that, that the, the community being the, the event chair, right. Yeah. Being, being one of the co-chairs was a, was a moment of pride for me being able to stand up there and just seeing a sea of people was like, wow, we just started with a handful of people at a meetup. And now, you know, we're actually having conferences and, and, and speaking of conference, like the Argo community as well, we put in, you know, we put on a virtual only event on Argo con last year. We're gonna do it in person today. You know, this year. >>Do you have a date on that? Do you have a date on that Argo con 22? >>Two? Yeah, yeah, yeah. Argo con September 19th, 2022. So, you know, mark your calendars, it it's, you know, it's a multi-day event, you know, it's, it's part of something else that I've seen in the community where, you know, first we're talk talking about these meetups. Now we're doing multi-day events. We're, you know, in talks of the open, get ups, you know, get ups can also make that a multi-day event. There's just so many talks in so many people that want to be involved in network that, you know, we're saying, well, we're gonna need more days because there's just so many people coming to these events, you know, in, in, you know, seeing these communities grow, not just from like the engineering standpoint, but also from the end user standpoint, but also from the people that are actually doing these things. And, you know, seeing some of these use cases, seeing some of the success, seeing some of the failures, right? Like people love listening to those talks about postmortems, I think are part of my favorite talks as well. So seeing that community grow is, is, you know, on a personal level, it's, it's a point >>It's like CSI for software developers. You want to curious about >>Exactly >>What happened. You know, you know, it's interesting, you mentioned about the, the multiple events at Coon. You know, the vibe that's going on is a very festival vibe, right? You have organic groups coming together. I remember when they had just started doing the day zero programs. Now you have like, almost like multiple stages of content at these events. It feels like, like a Coachella vibe or some sort of like festival vibe, like a lot of things going on and you, and if you pick your kind of area, but you can move around, I find that the kind of the format de Azure I think is going well these days. What do you think about that? >>Yeah, yeah. No, for sure. It's and, and, and I love that that analogy of Coachella, it does feel like, you know, it's, there's something for everyone and you can find what you like, and you'll find a little, you know, a little group, right. A little click of, of, of people that's probably the wrong term to use, but you know, you, you find, you know, you, you know, like-minded people and, you know, passionate about the same thing, right? Like the security guys, they, you know, you see them all clump together, right? Like you see like the, the developer C I CD get ops guys, we all kind of clump together and start talking, you know, about everything that we're doing. And it's, that's, that's, I think that's really something special that coupon, you know, some, you know, it's gotten so big that it's almost impossible to fit everything in a, in a week, because unless there's just so much to do. And there's so much that that interests, you know, someone, but it's >>A code, a code party is what we call it. It's a code party. Yeah. >>It's, it's a code party for sure. For >>Sure. Nerd nerd Fest on, on steroids. Hey, I gotta get, I wanna wrap this up and give you the final word, Christian. Thanks for coming on. Great insight, great conversation. There's a huge, you guys are in the middle of a hot area, obviously large scale data growth. Kubernetes is scaling beautifully and making it easier at managed services. What people want machine learning's kicking in and, and you get automation building in all favoring, the developer and C I CD pipeline and all that good stuff. People want to learn more. Can you take a minute to put the plug in for code fresh on the certification? How do I get involved? Where are you? Is there levels if I want to jump in and get trained and get fluent on code fresh, can you share commentary and, and, and what the status is? >>Yeah, yeah, for sure. So code fresh is offering a free certification, right? For get ups or Argo CD and get ops. The first of it's kind for Argo CD, first of it's kind for get ops is you can actually go get certified with Argo CD and get ops. You know, we there level one is out right now. You can go take that code, fresh.io/certification. It's out there, sign up, you know, you, you don't, you don't need to pay anything, right. It's, it's something it's a, of a free course. You could take level two is coming soon. Right? So level two is coming soon in the next few months, I believe I don't wanna quote a specific day, but soon because I, but soon I, it it's soon, soon as in, as in months. Right? So, you know, we're, we're counting that down where you can not only level one cert level certification, but a level, two more advanced certification for those who have been using Argo for a while, they can still, you know, take that and be, you know, be able to get, you know, another level of certification for that. So also, you know, Argo con will be there. We're, we're part of the programming committee for Argo con, right? This is a community driven event, but, you know, code fresh is a proud diamond sponsor. So we'll be there. >>Where's it located up to us except for eptember 19th multiday or one day >>It's a, it's a multi-day event. So Argo con from 19, 19 20 and 21 in a mountain view. So it'll be in mountain view in the bay area. So for those of you who are local, you can just drive in. Great. >>I'm write that down. I'll plug it. I'll put in the show notes. >>Awesome. Awesome. Yeah. And you will be there so you can talk to me, you can talk to anyone else at code, fresh talking about Argo CD, you know, find, find out more about hosted, get ups code, fresh.io. You know, you can find us in the Argo project, open, get ups community, you know, we're, we're, we're deep in the community for both Argo and get ups. So, you know, you can find us there as well. >>Well, let's do a follow up in when you're in town, so's only a couple months away and getting through the summer, it's already, I can't believe events are back. So it's really great to see face to face in the community. And there was responding. I mean, co con in October, I think that was kind of on the, that was a tough call and then get to see your own in Spain. I couldn't make it. Unfortunately, I had got COVID came down with it, but our team was there. Open sources, booming continues to go. The next level, new power dynamics are developing in a great way. Christian. Thanks for coming on, sharing your insights as the developer experience lead at code fresh. Thanks so much. >>Thank you, John. I appreciate it. >>Okay. This is a cube conversation. I'm John feer, host of the cube. Thanks for watching.
SUMMARY :
I'm John furrier, host of the cube. Thank you. Are you developing you figuring out the product? I believe it's, you know, everyone's always asking, well, what, you know, You wanted out the door and you know, that was a workflow right now So, so you have now the motion of, with GI ops, you guys are in the middle of kinda this idea of frictionless workflow where, you know, you develop your code, you know, you compile it. So that way, as you said before, You guys had some news around Argo and you had some news around the hosted solution. A lot of people, you know, remember that the, the Chick-fil-A story where and, you know, not only just keeping the lights on, but also management security, you know, Which offers, you know, allows users to, you know, let us take care of all the, People want simple it's scaling, you got automation built in all that good stuff. you know, we believe will accelerate, you know, developers into actually developing their, Hosted, managed service by you guys on this one, So let me, let me get in the Argo real quick, just to kind of just level set for the folks that So for those, those of us in the us, we, we know, you know, we know that season all too well, the tax And by the way, Intuit we've done many years. and it was a tool that helped them, you know, You mentioned, you know, you know, applications, a way to engineer, you know, your project, but also kind of like I, we always joke is like, well, you know, internally, like we know you were a billion dollar company that And you guys have been the middle level with the Argo project and come out of it, you know, the get ups and it be that being the, you know, You know, we had like, you know, about 50 people there, but then, you know, Cuan in Valencia this you know, it's, it's part of something else that I've seen in the community where, you know, first we're talk talking about these meetups. You want to curious about You know, you know, it's interesting, you mentioned about the, the multiple events at Coon. Like the security guys, they, you know, you see them all clump together, Yeah. It's, it's a code party for sure. Hey, I gotta get, I wanna wrap this up and give you the final word, you know, be able to get, you know, another level of certification So for those of you who are local, I'll put in the show notes. So, you know, you can find us there as well. So it's really great to see face to face in the community. I'm John feer, host of the cube.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Spain | LOCATION | 0.99+ |
John | PERSON | 0.99+ |
October | DATE | 0.99+ |
Valencia | LOCATION | 0.99+ |
Microsoft | ORGANIZATION | 0.99+ |
Intuit | ORGANIZATION | 0.99+ |
Christian Hernandez | PERSON | 0.99+ |
Amazon | ORGANIZATION | 0.99+ |
Palo Alto, California | LOCATION | 0.99+ |
Dave | PERSON | 0.99+ |
two problems | QUANTITY | 0.99+ |
Cuan | LOCATION | 0.99+ |
AWS | ORGANIZATION | 0.99+ |
last year | DATE | 0.99+ |
two things | QUANTITY | 0.99+ |
Argo con | EVENT | 0.99+ |
GitHub | ORGANIZATION | 0.99+ |
two | QUANTITY | 0.99+ |
September 19th, 2022 | DATE | 0.99+ |
Christian | PERSON | 0.99+ |
this year | DATE | 0.99+ |
Netflix | ORGANIZATION | 0.99+ |
LA | LOCATION | 0.98+ |
eptember 19th | DATE | 0.98+ |
ORGANIZATION | 0.98+ | |
one | QUANTITY | 0.98+ |
Argos | ORGANIZATION | 0.98+ |
thousands | QUANTITY | 0.98+ |
one day | QUANTITY | 0.98+ |
first generation | QUANTITY | 0.98+ |
Argo | ORGANIZATION | 0.98+ |
Cuban | LOCATION | 0.98+ |
over 200 people | QUANTITY | 0.98+ |
first | QUANTITY | 0.97+ |
today | DATE | 0.97+ |
couple years ago | DATE | 0.97+ |
both | QUANTITY | 0.97+ |
Coachella | EVENT | 0.97+ |
19 | DATE | 0.97+ |
Two | QUANTITY | 0.96+ |
Argo con 22 | EVENT | 0.96+ |
CNCF | ORGANIZATION | 0.96+ |
Los Angeles | LOCATION | 0.95+ |
Coon | ORGANIZATION | 0.95+ |
Kubernetes | TITLE | 0.95+ |
10 year | QUANTITY | 0.95+ |
first billion dollar | QUANTITY | 0.95+ |
Java | TITLE | 0.94+ |
level one | QUANTITY | 0.94+ |
level two | QUANTITY | 0.93+ |
Argo con | ORGANIZATION | 0.93+ |
21 | DATE | 0.93+ |
about 50 people | QUANTITY | 0.93+ |
C I CD | ORGANIZATION | 0.91+ |
COVID | ORGANIZATION | 0.9+ |
one environment | QUANTITY | 0.9+ |
second largest co | QUANTITY | 0.89+ |
Weaveworks | ORGANIZATION | 0.88+ |
Nerd nerd Fest | EVENT | 0.88+ |
QAN | LOCATION | 0.87+ |
Azure | TITLE | 0.84+ |
billion dollar | QUANTITY | 0.82+ |
season two | QUANTITY | 0.81+ |
Amazon Azure | ORGANIZATION | 0.81+ |
Kapil Thangavelu & Umair Khan, Stacklet | Kubecon + Cloudnativecon Europe 2022
>>The cube presents, Coon and cloud native con Europe, 2022, brought to you by red hat, the cloud native computing foundation and its ecosystem partners. >>Welcome to Valencia Spain in Coon cloud native con Europe, 2022. I'm your host Keith Townsend. And we're continuing the conversation with community, with startups, with people building cloud native, a cube alum joint by a CTO. And not as the CTO advisor. I really appreciate talking to CTOs Capel. Th Lou don't forgive me if I murder the name, that's a tough one. I'm I'm, I'm getting warmed up to the cubey, but don't worry. When we get to the technical parts, it's gonna be fun. And then a cube alum, Umer K director of marketing Capel. You're the CTO. So we we'll start out with you. What's the problem statement? What, what, what are you guys doing? >>So, uh, we're building on top of an open source project podcast, custodian, uh, that is in CNCF. And that I built when I was at capital one and just as they were going, they're taking those first few steps. It's a large regulated enterprise into the cloud. And the challenge that I saw was, you know, how do we enable developers to pick whatever tools and technologies they want, if they wanna use Terraform or cloud formation or Ansible? I mean, the cloud gives us APIs and we wanna be able to enable people to use those APIs through innovative ways. Uh, but at the same time, we wanna make sure that the, regardless of what choices those developers make, that the organization is being is being well managed, that all those resources, all that infrastructure is complying to the organizational's policies. And what we saw at the time was that what we were getting impediments around our velocity into the cloud, because we had to cover off on all of the compliance and regulation aspects. >>And we were doing that them as one offs. And so, uh, taking a step back, I realized that what we really needed was a way to go faster on the compliance side and clock custodian was born out of that effort side of desk that we took through enterprise wide. And it was really about, um, accelerating the velocity around compliance, but doing it in the same way that we do application and infrastructure is code. So doing policy as code in a very simple readable YAML DSL, um, because, you know, PO you have, we, anytime we write code, we're gonna more people are gonna read that code than, than are going to need to be able to write it. And so being able to make it really easy to understand from both the developers that are in the environment from the compliance folks or auditors or security folks that might wanna review it, um, it was super important. And then instead of being at the time, we saw lots of very under products and they were all just big walls of red in somebody's corner office and getting that to actually back the information back in the hands of developers so that they can fix things, um, was problematic. So being able to do time remediation and real time collaboration and communication back to developers, Hey, you put a database on the internet. It's okay. We fixed it for you. And here's the corporate policy on how to do it better in the future. >>So this is a area of focus of mind that people, I think don't get right. A lot, the technology hard enough by itself. The transformation cloud is not just about adopting new technologies, but adopting new processes, the data, and information's there automatically. But when I go to an auditor or, or, uh, compliance and say, Hey, we've changed the process for how do we do change control for our software stack? I get a blank stare. It's what do you mean we've been doing it this way for the past 15, 20 years, that's resistance, it's a pain point and projects fail due to this issue. So talk to me about that initial customer engagement. What's what's that conversation like? >>So we start off by deploying our, our platform on top of buck custodian. Um, and as far as our customers, and we give them a view of all the things that are in their cloud, what is their baseline, so to speak. Um, but I think it's really important. Like I think you bring up a good point, like communication, the challenge, larger challenge for enterprises in the cloud, and especially with grocery compliance is understanding that it is not a steady state. It's always, there's always something new in the backlog. And so being able, and the, one of the challenges for larger orgs is just being able to communicate out what that is. I remember changing a tag policy and spending the next two years, explaining it to people what the actual tag policy was. Um, and so being able to actually inform them, you know, via email, via slack, via, you know, any communication mechanism, uh, as they're doing things is, is so powerful to be able to, to help the organization grow together and move and get an alignment about what, what the, what the new things are. >>And then additionally, you know, from a perspective of, uh, tooling that is built for the real world, like being able to, as those new policies come into play, being able to say, okay, we're going to segment into stopping the bleeding on the net new and being able to then take action on what's already deployed that now needs to become into compliance is, is really important. But coming back to your question on customer engagements, so we'll go in and we'll deploy, uh, a SAC platform for them. We'll basically show them all of the things that are there already and extent. Um, we provide a real time SQL interface that customers can use, um, that is an asset inventory of all their cloud assets. Uh, and then we provide, uh, policy packs that sort of cover off on compliance, security, cost, optimizations, and opportunities for them. Uh, and then we help them through, uh, get ops around those policies, help deploy remediation activities and capabilities for their environment. >>So walk me through some of the detail of, of, of the process and where the software helps and where people need to step in. I'm making I'm, I'm talking to my security auditor, and he's saying, you know what, Keith, I understand that the Aw, that the, uh, VM talking to the application, VM talking to the Oracle database, there is a firewall rule that says that that can happen. Show me that rule in cloud custodian. And you're trying to explain, well, well, there's no longer a firewall. There's a service. And the service is talking to that. And it, it is here and clouds, custodian and St is whether Stant help come to either help with the conversation, or where do I inject more of my experience and my ability to negotiate with the auditor. >>So stalet from the perspective, uh, and if we take a step back, we, we talk about governances code and, and the four pillars around compliance, security, cost, optimization operations, uh, that we help organizations do. But if we take a step back, what is cloud custodian? Cloud custodian is really a cloud orchestrator, a resource orchestrator. What <inaudible> provides on top of that is UI UX, um, policy packs at scale execution, across thousands of accounts, but in the context of an auditor, what we're really providing is here's the policy that we're enforcing. And here's the evidence, the attestation over time. And here's the resource database with history that shows how we, how we got here, where we compliant last year to this policy that we just wrote today. >>So shifting the conversation, you just mentioned operations. One of the larger conversations that I have with CIOs and CTOs is where do I put my people? Like this is a really tough challenge. When you look at moving to something like a SRE model, or, uh, let's say, even focus on the SRE, like what, where does the SRE sit in an organization? How does stack, like if at all, help me make those types of strategic decisions if I'm talking about governance overall. So, >>So I think in terms of personas, if you look at there's a cloud engineer, then SRE, I think that what at its core Stackler and cloud custodian does is a centralized engine, right? So your cost policies, your compliance policies, your security policies are not in a silo anymore. It's one tool. It's one repository that everyone can collaborate on as well. And even engineering, a lot of engineering teams run custodian and, and adopt custodian as well. So in terms of persona stack, it really helps bring it together. All teams have the same simple YAML DSL file that they can write their policies, share their policies and communicate and collaborate better as well. >>Yeah. So I mean, cloud transformation for an enterprise is a deeper topic. Like I think, you know, there's a lot of good breast practices establishing a cloud center of excellence. Um, I, I think, you know, investing in training for people, uh, getting certification so everyone can speak the same language when it comes to cloud is a key aspect. When it comes to the operations aspect, I very much believe that you should have, you know, try to devolve and get the developers writing, uh, some of the DevOps. And so having SREs around for the actual application teams is, is valuable, but you still have a core cloud infrastructure engineering group that's doing potentially any of your core networking, any of your, you know, IM authentication aspects. And so, uh, what we found is that, you know, SLA and cloud custodian get PR primarily get deployed by one of three groups. >>The, uh, you know, you've got the, the CIO buyer within that cloud infrastructure engineering team. And what we found is that group is because they're working with the application teams in a read right way. Uh, they're very much more, um, uh, used to doing and open to doing remediation in real time. Um, and so, and then we also have the CISO teams that want to get to a secure compliance state, be able to do audit and, and validate that all the environments are, um, you know, secure, frankly. And then we get to the CFO groups. Uh, and so, and this sometimes is part of the cloud center of excellence. And so it, it has to be this cross team collaboration. And they're really focused on the, that, that cost optimization, finding the over provision, underutilized things, establishing workloads for dev environments to turn them off at night. Um, and of course, respective of time zones, cause we're all global these days. Uh, and so those are sort of the three groups that we see that sort of really want to engage with us because we can provide value for them to help their accelerate their business goals. >>So that's an expansive view, cost compliance, security operations. That's a lot, I'm thinking about all the tools, all the information that feeds into that, where does cloud custodians start and stop? Like, am I putting cloud custodian agents on servers or, uh, pods, like how, how am I interacting with this? >>So the core clock suiting is just to see lot it's stateless, it's designed to be operationally simple. Um, and so you can run it in Kubernetes, in Jenkins. We've seen people use GitLab. We've seen people run just as a query interactive tool just from, um, investigations perspective on their laptop. But when you write a policy, a policy really consists of, you know, a couple of core elements. Uh, you identify a resource you want to target say an S3 bucket or, uh, a Google cloud VM. And then you say establishes that a filters. I want to look for all the C two instances that are on public subnets with an IM roll attached that has the ability to, uh, create another IM user. And so that, you know, you filter down, you ask the arbitrary questions to filter to the interesting set of things you want, and then you take a set of actions on them. >>So you might take an action, like stop an C two instance, and you might use it as an incident response. Um, you might, uh, use it for off hours in a, in that type of policy. So you get this library of filters and actions that you can combine to form, you know, millions of different types of policies. Now, we also have this notion of an execution mode. So you might say, uh, let's operate in real time. Whenever someone launches this instance, whenever there's an API call, we want to introspect what that API I call is doing and make sure that it's compliant to policy. Now, when you do that, custo will, when you, and you run it with the COI, cause you will actually provision a Lambda function and hook up the event sources to it. Uh, and sorry, Lambda really the serverless we bind into the serverless native capabilities of the underlying cloud provider. So Google cloud function, Azure serverless functions, uh, and native AWS Lambda native us. And so now that policy is effectively hermetically sealed, running, uh, in the Seus runtime of that cloud and responding to API calls in real time, all with, you know, structured outputs and logs and metrics to the native cloud provider capabilities around those. Um, and that really ensures that, uh, you know, it's effectively becomes operation free from the perspective of the user of having to maintain infrastructure >>For it. So let's talk about >>Agent agent list and API based. >>Let's talk about like the a non-developer use case specifically finance. Absolutely. We, you have to deploy the ability to deploy, uh, um, uh, SAP in a, uh, E C two instance, but it's very expensive. Do it only when you absolutely need to do it, but you have the rights to do it. And I wanna run a, uh, a check to see if anyone's doing it like this is this isn't a colder developer, what is their experience? So, >>So primarily we focus on the infrastructure. So low balancers, VMs, you know, encryption and address on discs. Um, when we get into the application workloads running on those instances, we spend, we don't spend that that's on our target focus area. Mm-hmm <affirmative>, we can do it. Uh, and it really depends on the underlying cloud provider's capabilities. So in Amazon, there's a system called systems manager and it runs, and it's basically running an agent on the box. We're not running the agent, but we can communicate with that agent. We can, I inspect the, the inventory that's running on that box. We can send commands to that box, through those serverless functions and through those policies. And so we see it commonly used for like incident response and a security perspective where you might wanna take a memory snapshot of, of, of the instance before, uh, um, yeah, putting it into a forensic cloud and adding >>To that, like these days we're seeing the emerging personas of a fops engineer or a fops director as well, because cost in cloud is totally different. So what custodian and Stackler allows to do is again, using the simple policy files. Even if they have a non-developer background, they can understand this DSL, they can create policies, they can better, uh, target developers, better get them to take actions on policy as well. If they're overspending in the cloud or underspending in the cloud, uh, especially with St. You get, they get a lot of, out of the box dashboards and policy packs too. So say they can really understand how the cost has been consumed. They can have the developers take actions because a lot of the fops finance people complain like my developers does not understand it. Right. How do we get them to take action and make sure we are not over spending? Right. So with custodian policies, they're able to send them, uh, educational messages on slack or open a J ticket and really enforce them to take action as well and start saving cost. Like >>If you, uh, if you imagine cloud custodian as, um, you know, cleaning staff for, for the, your, your cloud environment, like it, it's, uh, you know, if you go to a typical, you know, cloud account, you're gonna see chairs that are 10 feet tall sitting at the table. You're gonna, because it's been over provision and obviously, you know, one can use it. Um, you're gonna find like the trash is overflowing because no one set up a log retention policy on the log group or set up S3, uh, life cycle rules on their buckets. And so you just have this, um, sort of this, uh, this explosion of things that people now, you know, beyond application functioning, like beyond, you know, getting to, you know, high performance, Dr. Capable, uh, SLAs around your application model, you now have to worry about the life cycle of all those resources and helping people manage that life cycle and making sure that they're using the, the, just the resources and consumption that they need, because we're all utilization based, uh, in the cloud. And so getting that to be more in line with what the application actually needs is really where we can help organizations and the CFO cost context. >>So, Emil, you got 10 seconds to tell me why you brought me a comic book. >><laugh> we created this comic book, uh, to explain the concept of governance scored in a simplified fashion. I know Keith, you like comic books, I believe. Uh, so it's a simple way of describing what we do, why it's important for pH ops for SecOps teams. And it talks about custodian and St. It as well. >>Well, I'm more of an Ironman type of guy or Batman cloud governance or governance cloud native governance is a very tough problem. I can't under emphasize how many projects get stalled or fail from a perception perspective, even if you're technically delivered what you've asked to deliver. That's where a lot of these conversations are going. We're gonna talk to a bunch of startups that are solving these tough problems here from Licia Spain, I'm Keith Townsend, and you're watching the cube, the leader in high tech coverage.
SUMMARY :
The cube presents, Coon and cloud native con Europe, 2022, brought to you by red hat, And not as the CTO advisor. And the challenge that I saw was, you know, how do we enable developers to pick And here's the corporate policy on how to do it better in the future. It's what do you mean we've been Um, and so being able to actually inform them, you know, via email, And then additionally, you know, from a perspective of, uh, And the service is talking to that. So stalet from the perspective, uh, and if we take a step back, So shifting the conversation, you just mentioned operations. So I think in terms of personas, if you look at there's a cloud engineer, then SRE, uh, what we found is that, you know, SLA and cloud custodian get PR primarily get deployed The, uh, you know, you've got the, the CIO buyer within that cloud infrastructure engineering team. all the information that feeds into that, where does cloud custodians And so that, you know, you filter down, you ask the arbitrary questions to filter to Uh, and sorry, Lambda really the serverless we bind into the serverless native capabilities of the underlying cloud So let's talk about to do it, but you have the rights to do it. We're not running the agent, but we can communicate with that agent. they're able to send them, uh, educational messages on slack or open a J ticket and And so getting that to be more in I know Keith, you like comic books, I believe. We're gonna talk to a bunch of startups that are solving
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Laura | PERSON | 0.99+ |
Lisa Martin | PERSON | 0.99+ |
Stu Miniman | PERSON | 0.99+ |
2015 | DATE | 0.99+ |
John Troyer | PERSON | 0.99+ |
Umair Khan | PERSON | 0.99+ |
Laura Dubois | PERSON | 0.99+ |
Keith Townsend | PERSON | 0.99+ |
1965 | DATE | 0.99+ |
Keith | PERSON | 0.99+ |
Laura Dubois | PERSON | 0.99+ |
Dell | ORGANIZATION | 0.99+ |
Emil | PERSON | 0.99+ |
Cloud Native Computing Foundation | ORGANIZATION | 0.99+ |
Fidelity | ORGANIZATION | 0.99+ |
Lisa | PERSON | 0.99+ |
1946 | DATE | 0.99+ |
10 seconds | QUANTITY | 0.99+ |
2020 | DATE | 0.99+ |
2019 | DATE | 0.99+ |
Amr Abdelhalem | PERSON | 0.99+ |
AWS | ORGANIZATION | 0.99+ |
Red Hat | ORGANIZATION | 0.99+ |
Kapil Thangavelu | PERSON | 0.99+ |
Amazon | ORGANIZATION | 0.99+ |
San Diego | LOCATION | 0.99+ |
10 feet | QUANTITY | 0.99+ |
Avamar | ORGANIZATION | 0.99+ |
Amr | PERSON | 0.99+ |
One | QUANTITY | 0.99+ |
San Diego, California | LOCATION | 0.99+ |
12 months | QUANTITY | 0.99+ |
one tool | QUANTITY | 0.99+ |
Fidelity Investments | ORGANIZATION | 0.99+ |
tens of thousands | QUANTITY | 0.99+ |
Oracle | ORGANIZATION | 0.99+ |
thousands | QUANTITY | 0.99+ |
one repository | QUANTITY | 0.99+ |
Lambda | TITLE | 0.99+ |
Dell Technologies | ORGANIZATION | 0.99+ |
Tens of thousands | QUANTITY | 0.99+ |
six month | QUANTITY | 0.99+ |
8000 people | QUANTITY | 0.99+ |
next year | DATE | 0.99+ |
10,000 developers | QUANTITY | 0.99+ |
last year | DATE | 0.99+ |
214 | OTHER | 0.99+ |
six months later | DATE | 0.99+ |
C two | TITLE | 0.99+ |
today | DATE | 0.99+ |
fourth year | QUANTITY | 0.99+ |
three | QUANTITY | 0.99+ |
NoSQL | TITLE | 0.99+ |
CNCF | ORGANIZATION | 0.99+ |
one | QUANTITY | 0.99+ |
150,000 | QUANTITY | 0.99+ |
79% | QUANTITY | 0.99+ |
KubeCon | EVENT | 0.99+ |
2022 | DATE | 0.99+ |
OpenVMS | TITLE | 0.99+ |
Networker | ORGANIZATION | 0.99+ |
GitOps | TITLE | 0.99+ |
DOD | ORGANIZATION | 0.99+ |
Michael Ferranti, Teleport | Kubecon + Cloudnativecon Europe 2022
>>The cube presents Koon and cloud native con Europe, 2022, brought to you by red hat, the cloud native computing foundation and its ecosystem partners. >>Welcome to Valencia Spain and CubeCon cloud native con Europe, 2022 I'm cube Townsend, along with Paul Gill, senior editor, enterprise architecture at Silicon angle. We are talking to some incredible folks this week, continuing the conversation around enabling developers to do their work. Paul you've said that this conference is about developers. What are you finding key as a theme running throughout the show >>That that developers really need a whole set of special tools. You know, it's not the end user, the end user tools, the end user access controls the authentication it's developers need a need their own to live their in their own environment. They need their own workflow tools, their own collaboration and their own security. And that's where teleport comes in. >>So speaking of teleport, we have Michael fork, chief marking our officer at teleport new world role for you. First, tell me about how long have you been at teleport now >>Going on seven or eight months now, >>Seven or eight months in this fast moving market. I'm I'm going to tell you a painful experience I've had in this new world. We've built applications. We've moved fast audits come in. The auditors have come in and they said, you know what, who authorized this change to the cluster? And we'll go into the change ticket and say, this person authorized the changes and the change ticket. And then they'll ask for trace back. Okay. Show me the change. What do it mean? Show you the changes. It just happened. >>Yeah. Check, check GitHub. >>Yeah, check GI, get, see, we, we, we, we said we were gonna make the changes, the change happen. That's not enough. What are CU, how are you helping customers solve this access control and audit problem? >>Yeah, that's a great question. There're kind of, there're kind of two, two sides to the puzzle. And actually I think that the intro hits it. Well, you you've talked about kind of developer experience needing needing tools to more efficiently do the job as a practitioner. And you're coming at it from kind of a security and compliance angle. And there's a tension between both of those teams. It's like, you know, there's, there's a tension between dev and ops before we created DevOps. There's also a tension between kind of security teams and developers. So we've created dev SecOps. What that means is you need an easy way for developers to get access, access to the resources they needed through their jobs. That's, you know, Linux hosts and databases and Kubernetes clusters and, you know, monitoring dashboards and managing all of those credentials is quite cumbersome. If I need to access a dozen systems, then you know, I'm using SSH keys to access this. >>I have admin credentials for my database. I I'm going through a VPN to access an internal dashboard, teleport, consolidates, all of that access into a single login via your identity provider, Okta active directory, but then on the security and compliance side, we make it really easy for that compliance officer. When they say, show me that change, we have all of the audit logs. That's that show exactly what changes Keith made when he logged into, into that system. And in fact, one of the booths behind here is talking about E B P F a modern way to get that kind of kernel level grade granularity. We build all of that observability into teleport to make the security and compliance teams happy. And the engineering teams a lot more productive. >>Where do the, the access control tools like Okta, you mentioned fall short. I mean, why, why is there a need for your level of, of control at the control plane? >>Yeah. When you, when you start to talk about authorization, authentication, audit at the infrastructure level, each of these technologies has its own way of managing what kind of in, in the jargon often and Ze, right? Authentication authorization. So you have SSH for, for Linux. Kubernetes has its own way of doing authorization. All of the database providers have their own way and it's quite complicated, right? It's, it's much different. So, you know, if I'm gonna access office 365 or I'm gonna a access Salesforce, right. I'm really talking about the HTTP protocol. It's relatively trivial to implement single sign on for web-based applications. But when we start talking about things that are happening at the Linux kernel level, or with Kubernetes, it's quite complicated to build those integrations. And that's where teleport extends what you have with your IDP. So for instance, Okta, lots of our customers use Okta as their identity provider, but then teleport takes those roles and applies them and enforces them at the actual infrastructure level. >>So if I'm a lay developer, I'm looking at this thinking, you know, I, I have service mesh, I've implemented link D SEO or something to that level. And I also have Ansible and Ansible has security, etcetera. What, what role, or how does that integrate to all together from a big picture perspective? >>Yeah. So >>What, one of the, kind of the meta themes at teleport is we, we like to, we like to say that we are fighting complexity cuz as we build new technologies, we tend to run the new tech on top of the old tech. Whereas for instance, when you buy a new car, you typically don't, you know, hook the old car to the back and then pull it around with you. Right? We, we replace old technology with new technology, but in infrastructure that doesn't happen as often. And so you end up with kind of layers of complexity with one protocol sitting on top of another protocol on top of another protocol. And what teleport does is for the access control plane, we, we kind of replace the legacy ways of doing authentication authorization and audit with a new modern experience. But we allow you to continue to use the existing tools. >>So we don't replace, for instance, you know, your configuration management system, you can keep using Ansible or, or salt or Jenkins, but teleport now is gonna give those, those scripts or those pipelines in identity that you can define. What, what should Ansible be able to do? Right? If, cuz people are worried about supply chain attacks, if a, if a vulnerable dependency gets introduced into your supply chain pipeline and your kind of Ansible playbook goes crazy and starts deploying that vulnerability everywhere, that's probably something you wanna limit with teleport. You can limit that with an identity, but you can still use the tools that you're, that you're used to. >>So how do I guarantee something like an ex-employee doesn't come in and, and initiate Ansible script that was sitting in the background just waiting to happen until, you know, they left. >>Yeah. Great question. It's there's kind of the, the, the great resignation that's happening. We did a survey where actually we asked the question kind of, you know, can you guarantee that X employees can no longer access your infrastructure? And shockingly like 89% of companies could not guarantee that it's like, wow, that's like that should, that should be a headline somewhere. And we actually just learned that there are on the dark web, there are people that are targeting current employees of Netflix and Uber and trying to buy credentials of those employees to the infrastructure. So it's a big problem with teleport. We solve this in a really easy, transparent way for developers. Everything that we do is based on short lift certificates. So unlike a SSH key, which exists until you decommission it, shortlist certificates by, by default expire. And if you don't reissue them based on a new login based on the identity, then, then you can't do anything. So even a stolen credential kind of the it's value decreases dramatically over time. >>So that statistic or four out of five companies can't guarantee X employees can't access infrastructure. Why is simply removing the employee from the, you know, from the L app or directory decommissioning their login credentials. Why is that not sufficient? >>Well, it, it depends on if everything is integrated into your identity provider and because of the complexities of accessing infrastructure, we know that developers are creative people. And by, by kind of by definition, they're able to create systems to make their lives easier. So one thing that we see developers doing is kind of copying an SSH key to a local notepad on, on their computer. So they essentially can take that credential out of a vault. They can put it somewhere that's easier for them to access. And if you're not rotating that credential, then I can also, you know, copy it to a, to a personal device as well. Same thing for shared admin credentials. So the, the, the issue is that those credentials are not completely managed in a unified way that enables the developer to not go around the system in order to make their lives easier. >>But rather to actually use the system, there's a, there's a market called privilege access management that a lot of enterprises are using to kind of manage credentials for their developers, but it's notoriously disruptive to developer workflows. And so developers kind of go around the system in order to make their jobs easier. What teleport does is we obviate the need to go around the system, cuz the simplest thing is just to come in in the morning, log in one time to my identity provider. And now I have access to all of my servers, all of my databases, all of my Kubernetes clusters with a short lift certificate, that's completely transparent. And does >>This apply to, to your, both your local and your cloud accounts? >>Yes. Yes, exactly. >>So as a security company, what's driving the increase in security breaches. Is it the lack of developer hygiene? Is it this ex-employee great resignation bill. Is it external intruders? What's driving security breaches today. >>Yes. >>It's you know, it's, it's all of those things. I think if I had to put, give you a one word answer, I would say complexity. The systems that we are building are just massively complex, right? Look at how many vendors there are at this show in order to make Kubernetes easy to use, to do what its promises. It's just, we're building very complex systems. When you build complex systems, there's a lot of back doors, we call it kind of a tax surface. And that's why for every new thing that we introduce, we also need to think about how do we remove old layers of the stack so that we can simplify so that we can consolidate and take advantage of the power of something like Kubernetes without introducing security vulnerabilities. >>One of the problems or challenges with security solutions is, you know, you there's this complexity versus flexibility knob that you, you need to be careful of. What's the deployment experience in integration experience for deploying teleport. >>Yeah, it's it, we built it to be cloud native to feel like any other kind of cloud native or Kubernetes like solution. So you basically, you deploy it using helm chart, you deploy it using containers and we take care of all of the auto configuration and auto update. So that it's just, it's, it's part of your stack and you manage it using the same automation that you use to manage everything else. That's a, that's a big kind of installation and developer experience. Part of it. If it's complex to use, then not only are developers not gonna use it. Operations teams are not gonna want to have to deal with it. And then you're left with doing things the old way, which is very unsatisfactory for everybody. >>How does Kubernetes change the security equation? Are there vulnerabilities? It introduces to the, to the stack that maybe companies aren't aware of >>Almost by definition. Yes. Kind of any new technology is gonna introduce new security vulnerabilities. That's the that's that is the result of the complexity, which is, there are things that you just don't know when you introduce new components. I think kind of all of the supply chain vulnerabilities are our way of looking at that, which is we have, you know, Kubernetes is itself built on a lot of dependencies. Those dependencies themselves could have security vulnerabilities. You might have a package that's maintained by one kind of hobbyist developer, but that's actually deployed across hundreds of thousands of applications across, across the internet. So again, it's about one understanding that that complexity exists and then saying, is there a way that we can kind of layer on a solution that provides a common layer to let us kind of avoid that complexity and say, okay, every critical action needs to be authorized with an identity that way if it's automated or if it's human, I have that level of assurance that a hacked Ansible pipeline is not going to be able to introduce vulnerabilities across my entire infrastructure. >>So one of the challenges for CIOs and CTOs, it's the lack of developer resources and another resulting pain point that compounds that issue is rework due to security audits is teleport a source of truth that when a auditor comes in to audit a, a, a, a C I C D pipeline that the developer or, or operations team can just say, Hey, here's, self-service get what you need. And come back to us with any questions or is there a second set of tools we have to use to get that audit and compliance reporting? >>Yeah, it's teleport can be that single source of truth. We can also integrate with your other systems so you can export all of the, what we call access logs. So every, every behavior that took place, every query that was run on a database, every, you know, curl command that was run on a Lennox, host, teleport is creating a log of that. And so you can go in and you can filter and you can view those, those actions within teleport. But we also integrate with other systems that, that people are using, you have its Splunk or Datadog or whatever other tool chain it's really important that we integrate, but you can also use teleport as that single source. So >>You can work with the observability suites that are now being >>Installed. Yeah, there, the, the wonderful thing about kind of an ecosystem like Kubernetes is there's a lot of standardization. You can pick your preferred tool, but under the hood, the protocols for taking a log and putting it in another system are standardized. And so we can integrate with any of the tools that developers are already using. >>So how big is teleport when I'm thinking about a, from a couple of things big as in what's the footprint and then from a developer operations team overhead, is this kind of a set and forget it, how much care feed and maintenance does it >>Need? So it's very lightweight. We basically have kind of two components. There's the, the access proxy that sits in front of your infrastructure. And that's what enables us to, you know, regardless of the complexity that sits across your multi data center footprint, your traditional applications, running on windows, your, your, your modern applications running on, you know, Linux and Kubernetes, we provide seamless access to all of that. And then there's an agent that runs on all of your hosts. And this is the part that can be deployed using yo helm or any other kind of cloud native deployment methodology that enables us to do the, the granular application level audit. For instance, what queries are actually being run on CockroachDB or on, on Postgres, you know, what, what CIS calls are running on Linnux kernel, very lightweight automation can be used to install, manage, upgrade all of it. And so from an operations perspective, kind of bringing in teleport shouldn't be any more complicated than running any application on a container. That's, that's the design goal and what we built for our customers. >>If I'm in a hybrid environment, I'm transitioning, I'm making the migration to teleport. Is this a team? Is this a solution that sits only on the Kubernetes cloud native side? Or is this something that I can trans transition to initially, and then migrate all of my applications to, as I transition to cloud native? >>Yeah. We, there are kind of, no, there are no cloud native dependencies for teleport. Meaning if you are, you're a hundred percent windows shop, then we support for instance, RDP. That's the way in which windows handles room access. If you have some applications that are running on Linux, we can support that as well. If you've got kind of the, you know, the complete opposite in the spectrum, you're doing everything, cloud native containers, Kubernetes, everything. We also support that. >>Well, Michael, I really appreciate you stopping by and sharing the teleport story. Security is becoming an obvious pain point for cloud native and container management. And teleport has a really good story around ensuring compliance and security from Licia Spain. I'm Keith towns, along with Paul Gillon and you're watching the cue, the, the leader, not the, the leader two, the high take tech coverage.
SUMMARY :
The cube presents Koon and cloud native con Europe, 2022, brought to you by red hat, What are you finding key it's developers need a need their own to live their in their own environment. how long have you been at teleport now I'm going to tell you a painful experience I've had in this new world. What are CU, how are you helping customers solve this If I need to access a dozen systems, then you know, I'm using SSH keys to access And in fact, one of the booths behind here is talking about E B P F a modern way you mentioned fall short. And that's where teleport extends what you have with your IDP. you know, I, I have service mesh, I've implemented link D SEO or And so you end up with kind of layers of complexity with one protocol So we don't replace, for instance, you know, your configuration management system, waiting to happen until, you know, they left. a new login based on the identity, then, then you can't do anything. Why is simply removing the employee from the, you know, from the L app or directory decommissioning their you know, copy it to a, to a personal device as well. And so developers kind of go around the system in order to make their jobs easier. Is it the lack of developer hygiene? I think if I had to put, give you a one word answer, One of the problems or challenges with security solutions is, you know, So you basically, you deploy it using helm chart, you deploy it using which is we have, you know, Kubernetes is itself built on a lot of dependencies. the developer or, or operations team can just say, Hey, here's, self-service get what you need. But we also integrate with other systems that, that people are using, you have its Splunk or Datadog or whatever And so we can integrate with any of the tools that developers to, you know, regardless of the complexity that sits across your multi data center footprint, Or is this something that I can trans transition to initially, and then migrate all of my applications the, you know, the complete opposite in the spectrum, you're doing everything, cloud native containers, Kubernetes, Well, Michael, I really appreciate you stopping by and sharing the teleport story.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Michael | PERSON | 0.99+ |
Paul Gill | PERSON | 0.99+ |
Keith | PERSON | 0.99+ |
seven | QUANTITY | 0.99+ |
Paul | PERSON | 0.99+ |
Paul Gillon | PERSON | 0.99+ |
Michael Ferranti | PERSON | 0.99+ |
Netflix | ORGANIZATION | 0.99+ |
Uber | ORGANIZATION | 0.99+ |
89% | QUANTITY | 0.99+ |
Seven | QUANTITY | 0.99+ |
two | QUANTITY | 0.99+ |
First | QUANTITY | 0.99+ |
eight months | QUANTITY | 0.99+ |
five companies | QUANTITY | 0.99+ |
Michael fork | PERSON | 0.99+ |
one | QUANTITY | 0.99+ |
one word | QUANTITY | 0.99+ |
both | QUANTITY | 0.99+ |
two sides | QUANTITY | 0.99+ |
GitHub | ORGANIZATION | 0.99+ |
four | QUANTITY | 0.99+ |
Kubecon | ORGANIZATION | 0.98+ |
Teleport | ORGANIZATION | 0.98+ |
each | QUANTITY | 0.98+ |
one thing | QUANTITY | 0.98+ |
Linux | TITLE | 0.97+ |
Cloudnativecon | ORGANIZATION | 0.97+ |
one time | QUANTITY | 0.97+ |
single | QUANTITY | 0.97+ |
one protocol | QUANTITY | 0.97+ |
second set | QUANTITY | 0.96+ |
two components | QUANTITY | 0.96+ |
Kubernetes | TITLE | 0.96+ |
windows | TITLE | 0.95+ |
single source | QUANTITY | 0.95+ |
this week | DATE | 0.95+ |
One | QUANTITY | 0.95+ |
today | DATE | 0.94+ |
Ansible | ORGANIZATION | 0.94+ |
office 365 | TITLE | 0.94+ |
2022 | DATE | 0.93+ |
Koon | ORGANIZATION | 0.92+ |
a dozen systems | QUANTITY | 0.92+ |
hundreds of thousands of applications | QUANTITY | 0.92+ |
single login | QUANTITY | 0.91+ |
Valencia Spain | LOCATION | 0.91+ |
Postgres | ORGANIZATION | 0.9+ |
Linux kernel | TITLE | 0.89+ |
hundred percent | QUANTITY | 0.87+ |
Europe | LOCATION | 0.85+ |
red hat | ORGANIZATION | 0.85+ |
Okta | ORGANIZATION | 0.84+ |
Lennox | ORGANIZATION | 0.84+ |
CU | ORGANIZATION | 0.84+ |
Jenkins | TITLE | 0.81+ |
Splunk | ORGANIZATION | 0.8+ |
SecOps | TITLE | 0.79+ |
teleport | ORGANIZATION | 0.77+ |
Salesforce | TITLE | 0.75+ |
Ansible | TITLE | 0.73+ |
Datadog | ORGANIZATION | 0.73+ |
HTTP | OTHER | 0.73+ |
CockroachDB | TITLE | 0.69+ |
GI | ORGANIZATION | 0.68+ |
Okta | TITLE | 0.68+ |
Kubernetes | ORGANIZATION | 0.66+ |
E B P F | TITLE | 0.65+ |
cloud native con | EVENT | 0.63+ |
Alexis Richardson, Weaveworks | CUBE Conversation
(bright upbeat music) >> Hey everyone, welcome to theCUBE's AWS startup showcase. This is season two of the startup showcase, episode one. I'm your host, Lisa Martin. Pleased to be welcoming back one of our alumni, Alexis Richardson, the founder >> Hey. >> and CEO of Weaveworks. Alexis, welcome back to the program. >> Thank you so much, Lisa, I'm really happy to be here. Good to see you again. >> Likewise. So it's been a while since we've had Weaveworks on the program. Give the audience an overview of Weaveworks. You were founded in 2014, pioneering getopts, automating Kubernetes across all industries, but help us understand, unpack that a bit. >> Well, so my previous role was at Pivotal, where I was head of application platform and I was responsible for Spring and Vfabric, and some pieces of Cloud Foundry. And you may remember back in those days, everybody wanted to build like a Heroku, but for the enterprise. And so they were asking, how can we build more cloud services? And my team was involved in building out cloud services, but we were running into trouble with the technology that we had. And then when containers appeared, we thought this is the technology for us to roll out cloud services. So with some of my team, we decided to start a new company, Weaveworks, really intending to focus on developers. Because these new containers were pretty cool, but they were really complex operational centric tools, and enterprise developers need simplicity. That's what we'd learned from things like Spring. They want simplicity, productivity, velocity, all of that stuff, they don't want operational complexity. So Weaveworks' mission is to make applications easy for developers with containers. >> Talk to me about how you've accomplished that over the last seven years, and some of the things that you're doing to facilitate a DevOps practice within organizations across any industry? >> Yeah, well, our story is pretty interesting because of course in 2014, all of this was incredibly new. You couldn't even take two containers and put them together into a single application. So forget about enterprise. What we did was we built a network, which gave the company its name, Weave. But then we spent several years building out more and more pieces of the stack. We decided that we should go to market commercially because we're an open source company with a commercial SaaS. And we thought we would be like new Relic, that there'll be lots of customers in the cloud. And, therefore, they would need monitoring and management. And Weave started writing a SaaS based on Kubernetes, which was what we chose as our platform, back in the day, very, very, very early. We were one of the very first companies to start running Kubernetes in production other than Google. And so what we learned was customers didn't want to have management and monitoring for applications in the cloud, based on Kubernetes. Because they were all still struggling to get Docker working, to get basic Kubernetes clusters set up. And they kept saying to us "this is great, we love your tool, but we really need simpler things right now." So what we had done was we'd learned how to operate Kubernetes. And we discovered that we were doing it in this specific way, a way that meant that we could be reliable, we could set things up remotely, we could move things between zones. And so we called this approach getopts. So we've named the practice of getopts, which is really DevOps for Kubernetes. We decided that it was exciting after we had an outage and made a very quick recovery. Told people about it and they said, "well, we can't even Kubernetes started, let alone recover it from a crash." So we started evangelizing getopts and saying to people that we knew how to set up and run Kubernetes as operators for developers of apps, based on this experience. And people said, "well, why don't you help us do that?" So we pivoted the company away from a SaaS business, doing management, and straight back into enterprise software, providing a solution for people to run Kubernetes stacks, deploy applications, detect drifts, and operate them at scale. And we've never looked back. And since then we've built, very successfully, a big business out of telco customers, banks, car companies, really global two thousands. Starting from that open source base, continuing to respect that, but always keeping in mind helping developers build applications at scale. >> So in terms of that pivot that you've made, it sounds like you made that in conjunction with developers across industries to really understand what the right direction is here. What's the approach, what's their appetite? Talk to me about a customer example or two that really you think articulate the value and the right decision that that pivot was and how you're helping customers to really further their DevOps practice. >> Well, one of our first customers was actually Fidelity in this new world. Fidelity has a very advanced technology organization, a very forward thinking CTO, who I seem to recall is, or CEO, who I think is female. Really is into technology as a source of, you know, velocity and business strength. And we were brought to Fidelity by our partner, Amazon. And they said, "look, Fidelity have been using your open source tools, they want to run on Kubernetes, the early EKS service on AWS, but they need help, because what they want is a shared application platform that people can use across Fidelity to deploy and manage apps." So the idea Fidelity had was they're going to split their IT into a platform team, that was going to provide this platform, and a bunch of app teams that were going to write business apps like risk management, other financial processing. Paths, basically. And we came in to help Fidelity. And what we did was help Fidelity rollout, using getopts, a Amazon wide application platform. We also helped them to build, this was very early days for us post pivot, we really helped them to build an add on layer. So you could take any Kubernetes cluster and add other components to it, and then you'd have your platform right there. And the whole stack would be managed by getopts, which nobody had done before. Nobody who'd come up with a way of managing the whole stack, so you could start and stop stacks wherever you wanted, at will, correctly. I mean, if you talk to people about what's hard in IT, they'll tell you shutting down Kubernetes is hard, 'cause I know I'm never going to know how to start it again. So being able to start and stop things, move them around is really crucial. What Fidelity also wanted, which made I think the whole thing even more exciting, was to duplicate this environment on Azure and actually also on-premise later on. So where Fidelity are today is the whole Fidelity platform runs on Microsoft and on Amazon and on-premise, using three different implementations of Kubernetes. But using this platform technology and getopts that we helped Fidelity rollout. And if you want to know a bit about the story, type FIDEKS, F I D E K S into Google and you'll find a video of me three or four years ago on stage at Cube Con talking with a Fidelity chief architect about this story. It's pretty exciting and these are early days for these new Kubernetes platforms. >> Early days, but so transformative. And I can't imagine the events of the last few years without having this capability and this technology to facilitate such pivots and transformation where we would all be. I want to kind of dig into some use cases, 'cause one of the things that you just mentioned with the Fidelity example got me thinking use case of hybrid, multi-cloud, but also continuous app development. Talk to me about some of the key use cases that you work with customers on. >> Well you just named two. So hybrid and multi-cloud is absolutely critical, and also sovereign, which is when you're actually offline and you only update your cloud periodically. That's one of the major use cases for us. And what customers want there is they want consistency. They want a single operating model, across all of these different locations, so that all of their teams can get trained on one set of technologies and then move from place to place. They're not looking for magic, where apps move with the sun or any of that stuff. They just want to know they can base everything on a single, homogeneous skillset and have scale across their teams. Maybe tens of thousands of developers, all who know how to do the same thing. That's a really important use case. You also mentioned continuous delivery. That's probably the second really critical use case for us. People say, "I've got Kubernetes set up now, and I have Jenkins." At JP Morgan once told me they had 40,000 Jenkins servers, or something like that, you know, Jenkins at scale. And they're like, "okay, how do I push changes from Jenkins into the cloud?" So getopts provides a bridge between the world of CI and the runtime of Kubernetes. So one group of our customers is help me to put that middle piece of CD that gets you CI, CD, to Kubernetes, that's a classic. And then what they're looking for is an increase in velocity. And what we typically see is people go from deploying once every six months to deploying once a week, to deploying once a day, to deploying several times a day. And then they split things up into teams and suddenly, wow, that vision of microservices has come and everybody's excited 'cause IT velocity has gone up by two X. Another really >> So, >> Sorry, carry on. >> Go ahead, I was just going to say in terms of IT velocity it sounds like that's a major business outcome that you're enabling for, whether it's teleco, financial services, or whatnot. That velocity is, as you just described, is rapidly accelerating. >> Yeah, if you go to our website, you'll find a bunch of these use cases. And one that I really like is NatWest mettle, which is another financial example. They're not all financial by the way. But there's some metrics in there. We're getting people up to two X productivity, which at scale is huge, really makes a difference. Also, meantime to recovery. If you know the metric space, you'll know these are all DORA metrics. And DORA, which was acquired by Google a couple of years ago, is a really fantastic analyst in the space that came up with a bunch of ways of thinking about how to measure your performance as a business and IT organization. Recovery time and things like this that you really need to focus on if you're in this world. >> Well, from an IT velocity perspective, if I translate that to business outcomes, especially given the dynamics in the market over the last two years, this is transformative and probably helped a lot of organizations to pivot multiple times during the last couple of years. To get to that survival mode and into that thriving mode, enabling organizations to meet customer demand that was changing faster, et cetera. That's a really big imperative that this technology can deliver to the business. >> Yeah, I mean, that's been huge for us. So when the pandemic first began, obviously, we had some road bumps and there were some challenges, but what we found out very quickly was that people were moving into digital much faster. And we've been mostly enabling them, not just in finance, as I said, but also, car companies, utilities, et cetera. The other one, of course, is modern operations. So, everyone's excited about the potential for automation. If I have thousands and thousands of developers and thousands of applications, do I need thousands of operations staff? And the answer is, with Kubernetes in this new era, you can reduce your operational loads. So that actually very few people are needed to keep systems up, to do basic monitoring, to do redeployments and so on, which are all boring infrastructure tasks that no developer wants to do. If we can automate all of that, we can modernize the whole IT space. And that's what I think the promise of Kubernetes that we're also seeing as well. So applications speed first and then operational competence second. >> So you guys had a launch, here we are in early calendar year 2022, you guys had a launch just about six or eight weeks ago in November of 2021, where you were launching announcing the GA of Weave getopts enterprise, which is a licensed product building on the free open source Weave getopts core. Talk to me about that and what the significance of that is. >> Well, this is an enterprise solution that helps customers build these critical use cases, like shared service platform or secure DevOps or multi-cloud, using getopts, which gives them higher security, lower costs of management, and better operations, and higher velocity. And all of it is taking all the best practices that we've learned starting from those days of running our own Kubernetes stack and then through those early customers like Fidelity into the modern era where we have an at-scale platform for these people. And the crucial properties are it provides you with a platform, it provides you with trusted delivery, and it provides you with what we call release orchestration, which is when you deploy things at scale into production, using tools like canaries and other modern practices. So, all of it is enabling what we call the cloud native enterprise, application delivery, modern operations. >> So what's the upgrade path for customers that are using the free open-source tier to the enterprise package, what does that look like? >> The good news is it's an add on. So, I have been in the industry a while and I strongly believe it's really important that if you have an open source product, you shouldn't ask people to delete it or uninstall it to install your enterprise product, unless you really, really, really have to. And I'm not trying to be picky here. Maybe there are cases where it's important, but actually in our case, it's very simple. If you're already using one of our upstream tools, like Flux, for example, then going from Flux to Weave getopts enterprise is an add-on installation. So you don't have to change or take out what you're doing. You might be using Flux without knowing it. You may not be aware of this, but it's also insight as your AKS and ARC, it's inside the Amazon EKS anywhere bundle. It's available on Alibaba, VMware have used it in cartographer and Tanzu application platform. And even Red Hat use it too in some cases. So you may be using it already, from one of the big vendors who are partners of ours, as a precursor to buying Weave getopts enterprise. So, you know, don't be scared. Get in touch is what I would say to people. >> Get in touch. And of course, folks can go to weave.works to learn more about that. And, also we want to watch the Weave.works space, 'cause you have some news coming out relatively soon that sounds pretty exciting, Alexis. >> Well, I mentioned trusted delivery. And I think one of the things with that is no CIO wants to go faster, unless they also have the safety wheels on, let's face it. And the big question we get asked is "I love this getopts stuff, but how can I bring my team with me? How can I introduce change?" I have all of these approvals mechanisms in place, can I move into the world of getopts? And the answer is yes, yes you can because we now support policy engines as baked into our enterprise product. Now, if you don't know what policy is, it's really a way of applying rules to what you're seeing in IT. And you can detect whether something passes or fails conditions, which means that we can detect if something bad is about to happen in a deployment and stop it from happening, this is really critical. It also goes hand in hand with things like supply chain and security, which I'm sure we read about in the news far too much. >> Yeah, pretty much daily supply chain and security >> Pretty much daily. >> is one of those things that we're all in every generation concerned about. Well, Alexis, it's been a pleasure having you back on the program, talking to us about what's new at Weaveworks, the direction that you're going, how you're helping organizations across industries really advance their DevOps practice. And we will check weave.works in the next couple of weeks for more on that news that you started to break a little bit with us today. We appreciate your time, Alexis. >> Thank you very much, indeed, take care. >> Likewise. For Alexis Richardson, I'm Lisa Martin. Keep it right here on theCUBE, your leader in hybrid tech event coverage. (bright music) (music fades)
SUMMARY :
the founder and CEO of Weaveworks. Good to see you again. Weaveworks on the program. And you may remember back in those days, and saying to people that we knew and the right decision that that pivot was and getopts that we And I can't imagine the and then move from place to place. That velocity is, as you just described, And one that I really and into that thriving mode, And the answer is, with Talk to me about that and what And the crucial properties are So, I have been in the industry a while And of course, folks can go to And the answer is yes, yes you can for more on that news that you started your leader in hybrid tech event coverage.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Lisa Martin | PERSON | 0.99+ |
2014 | DATE | 0.99+ |
Amazon | ORGANIZATION | 0.99+ |
Lisa | PERSON | 0.99+ |
Alexis Richardson | PERSON | 0.99+ |
thousands | QUANTITY | 0.99+ |
Fidelity | ORGANIZATION | 0.99+ |
Alexis | PERSON | 0.99+ |
November of 2021 | DATE | 0.99+ |
JP Morgan | ORGANIZATION | 0.99+ |
Microsoft | ORGANIZATION | 0.99+ |
ORGANIZATION | 0.99+ | |
Weaveworks | ORGANIZATION | 0.99+ |
two | QUANTITY | 0.99+ |
second | QUANTITY | 0.99+ |
one | QUANTITY | 0.99+ |
NatWest | ORGANIZATION | 0.99+ |
once a day | QUANTITY | 0.99+ |
40,000 | QUANTITY | 0.99+ |
three | DATE | 0.98+ |
early calendar year 2022 | DATE | 0.98+ |
today | DATE | 0.98+ |
once a week | QUANTITY | 0.98+ |
one set | QUANTITY | 0.98+ |
Alibaba | ORGANIZATION | 0.98+ |
two thousands | QUANTITY | 0.98+ |
Pivotal | ORGANIZATION | 0.98+ |
Weave | ORGANIZATION | 0.98+ |
AWS | ORGANIZATION | 0.98+ |
two containers | QUANTITY | 0.97+ |
Jenkins | TITLE | 0.97+ |
Weaveworks' | ORGANIZATION | 0.97+ |
Flux | TITLE | 0.97+ |
Kubernetes | TITLE | 0.96+ |
single application | QUANTITY | 0.96+ |
weave.works | ORGANIZATION | 0.96+ |
four years ago | DATE | 0.96+ |
Azure | TITLE | 0.95+ |
eight weeks ago | DATE | 0.95+ |
DORA | ORGANIZATION | 0.94+ |
first customers | QUANTITY | 0.93+ |
Relic | ORGANIZATION | 0.92+ |
single | QUANTITY | 0.91+ |
about six | DATE | 0.9+ |
first companies | QUANTITY | 0.9+ |
theCUBE | ORGANIZATION | 0.89+ |
telco | ORGANIZATION | 0.89+ |
Heroku | ORGANIZATION | 0.89+ |
Ben Mappen, Armory & Ian Delahorne, Patreon | CUBE Conversation
>>Welcome to the cube conversation here. I'm Sean ferry with the cube in Palo Alto, California. We've got two great guests here featuring armory who has with them Patrion open-source and talking open source and the enterprise. I'm your host, John ferry with the cube. Thanks for watching guys. Thanks for coming on. Really appreciate. I've got two great guests, Ben mapping, and SVP, a strategic partner in the armory and Ian Della horn, S staff SRE at Patrion gentlemen, you know, open source and enterprise is here and we wouldn't talk about thanks for coming. I appreciate it. >>Yeah. Thank you, John. Really happy to be here. Thank you to the Cuban and your whole crew. I'll start with a quick intro. My name is Ben Mappin, farmers founders, lead strategic partnerships. As John mentioned, you know, it all, it really starts with a premise that traditional businesses, such as hotels, banks, car manufacturers are now acting and behaving much more like software companies than they did in the past. And so if you believe that that's true. What does it mean? It means that these businesses need to get great at delivering their software and specifically to the cloud, like AWS. And that's exactly what armory aims to do for our customers. We're based on opensource Spinnaker, which is a continuous delivery platform. And, and I'm very happy that Ian from Patrion is here to talk about our journey together >>And introduce yourself what you do at Patriot and when Patrion does, and then why you guys together here? What's the, what's the story? >>Absolutely. Hi, John and Ben. Thanks for, thanks for having me. So I am Ian. I am a site reliability engineer at Patrion and Patrion is a membership platform for creators. And what we're our mission is to get creators paid, changing the way the art is valued so that creators can make money by having a membership relationship with, with fans. And we are, we're built on top of AWS and we are using Spinnaker with armory to deploy our applications that, you know, help, help creators get paid. Basically >>Talk about the original story of Ben. How are you guys together? What brought you together? Obviously patron is well-known in the creator circles. Congratulations, by the way, all your success. You've done a great service for the industry and have changed the game you were doing creators before it was fashionable. And also you got some cutting-edge decentralization business models as well. So again, we'll come back to that in a minute, but Ben, talk about how this all comes together. Yeah, >>Yeah. So Ian's got a great kind of origin story on our relationship together. I'll give him a lead in which is, you know, what we've learned over the years from our large customers is that in order to get great at deploying software, it really comes down to three things or at least three things. The first being velocity, you have to ship your software with velocity. So if you're deploying your software once a quarter or even once a year, that does no good to your customers or to your business, like just code sitting in a feature branch on a shelf, more or less not creating any business value. So you have to ship with speed. Second, you have to ship with reliability. So invariably there will be bugs. There will be some outages, but you know, one of the things that armory provides with Spinnaker open sources, the ability to create hardened deployment pipeline so that you're testing the right things at the right times with the right folks involved to do reviews. >>And if there is hopefully not, but if there is a problem in production, you're isolating that problem to a small group of users. And then we call this the progressive deployment or Canary deployment where you're deploying to a small number of users. You measure the results, make sure it's good, expand it and expand it. And so I think, you know, preventing outages is incredibly incredibly important. And then the last thing is being able to deploy multi target multi-cloud. And so in the AWS ecosystem, we're talking about ECS, EKS Lambda. And so I think that these pieces of value or kind of the, the pain points that, that enterprises face can resonate with a lot of companies out there, including ENN Patriot. And so I'll, I'll, I'll let you tell the story. >>Yeah, go ahead. Absolutely. Thanks. Thanks for the intro, man. So background background of our partnership with armory as back in the backend, February of 2019, we had a payments payments slowed down for payments processing, and we were risking not getting creators paid on time, which is a doc great for creators because they rely on us for income to be able to pay themselves, pay their rent or mortgage, but also pay staff because they have video editors, website admins, people that nature work with them. And there were, they're a very, there's a very many root causes to this, to this incident, all kind of culminate at once. One of the things that we saw was that deploying D point fixes to remediate. This took too long or taking at least 45 minutes to deploy a new version of the application. And so we've had continuous delivery before using a custom custom home built, rolling deploy. >>We needed to get that time down. We also needed to be secure in our knowledge of like that deploy was stable. So we had had to place a break in the middle due to various factors that that can happen during the deploy previously, I had used a Spinnaker at previous employers. I have been set it up myself and introduced it. And I knew about, I knew like, oh, this is something we could, this would be great. But the Patriot team, the patron SRE team at that time was two people. So I don't have the ability to manage Spinnaker on my own. It's a complex open-source product. It can do a lot of things. There's a lot of knobs to tweak a lot of various settings and stuff you need to know about tangentially. One of the co-founders of, of armory had been, had to hit, had hit me up earlier. I was like, Hey, have you heard of armory? We're doing this thing, opens our Spinnaker, we're packaging this and managing it, check us out if you want. I kind of like filed it away. Like, okay, well that might be something we can use later. And then like two weeks later, I was like, oh wait, this company that does Spinnaker, I know of them. We should probably have a conversation with them and engage with them. >>And so you hit him up and said, Hey, too many knobs and buttons to push what's the deal. >>Yeah, exactly. Yeah. So I was, I was like, Hey, so by the way, I about that thing, how, how soon can you get someone get someone over here? >>So Ben take us through the progression. Cause that really is how things work in the open source. Open source is really one of those things where a lot of community outreach, a lot of people are literally a one degree or two separation from someone who either wrote the project or is involved in the project. Here's a great example. He saw the need for Spinnaker. The business model was there for him to solve. Okay. Fixes rolling deployments, homegrown all the things, pick your pick, your use case, but he wanted to make it easier. This tends to, this is kind of a pattern. What did you guys do? What's the next step? How did this go from here? >>Yeah. You know, Spinnaker being source is critical to armory's success. Many companies, not just pastry on open source software, I think is not really debatable anymore in terms of being applicable to enterprise companies. But the thing with selling open source software to large companies is that they need a backstop. They need not just enterprise support, but they need features and functionality that enable them to use that software at scale and safely. And so those are really the things that, that we focus on and we use open source as a really, it's a great community to collaborate and to contribute fixes that other companies can use. Other companies contribute fixes and functionality that we then use. But it's, it's really a great place to get feedback and to find new customers that perhaps need that enhanced level of functionality and support. And, and I'm very, very happy that Patrion was one of those companies. >>Okay. So let's talk about the Patrion. Okay. Obviously scaling is a big part of it. You're an SRE site, reliability engineers with folks who don't know what that is, is your, your job is essentially, you know, managing scale. Some say you the dev ops manager, but that's not really right answer. What is the SRE role at patriotics share with folks out there who are either having an SRE. They don't even know it yet or need to have SRS because this is a huge transition that, and new, new and emerging must have role in companies, >>Right? Yeah. We're the history of Patrion covers a lot. We cover a wide swath of a wide swath of, of, of things that we work with and, and areas that we consider to be our, our purview. Not only are we working on working with our AWS environment, but we also are involved in how can we make the site more reliable or performance so that, so that creators fans have a good experience. So we work with our content delivery numbers or caching strategies for caching caching assets. We work inside the application itself for doing performance performance, a hassle. This is also in proving observability with distributed tracing and metrics on a lot of that stuff, but also on the build and deploy side, if we can, if we can get that deploy time faster, like give engineers faster feedback on features that they're working on or bug fixes and also being secure and knowing that the, the code that they're working on it gets delivered reliably. >>Yeah. I think I, you have the continuous delivery is always the, the, the killer killer workflow as both the Spinnaker question here. Well, how has Spinnaker, well, what, how, how does Spinnaker being an open source project help you guys? I mean, obviously open source code is great. How has that been significant and beneficial for both armory and Patrion? >>Yeah, I'll take the first stab at this one. And it starts at the beginning. Spinnaker was created by Netflix and since Netflix open source that four or five years ago, there have been countless and significant contributions from many other companies, including armory, including AWS and those contributions collectively push the industry forward and allow the, the companies that, you know, that use open-source Spinnaker or armory, they can now benefit from all of the collective effort together. So just that community aspect working together is huge. Absolutely huge. And, you know, open source, I guess on the go-to-market side is a big driver for us. You know, there's many, many companies using open-source Spinnaker in production that are not our customers yet. And we, we survey them. We want to know how they're using open-source Spinnaker so that we can then improve open-source Spinnaker, but also build features that are critical for large companies to run at scale, deploy at scale, deploy with velocity and with reliability. >>Yeah. What's your take on, on the benefits of Spinnaker being open source? >>A lot of what Ben, it's been really beneficial to be able to like, be able to go in and look at the source code for components. I've been wondering something like, why is this thing working like this? Or how did they solve this? It's also been useful for, I can go ask the community for, for advice on things. If armory doesn't has the, it doesn't have the time or bandwidth to work on some things I've been able to ask the special interest groups in the source community. Like, can we, can we help improve this or something like that. And I've also been able to commit simple bug fixes for features that I've, that I've needed. I was like, well, I don't need to, I don't need to go engage are very on this. I can just like, I can just write up a simple patch on and have that out for review. >>You know, that's the beautiful thing about open sources. You get the source code and that's, and some people just think it's so easy, Ben, you know, just, Hey, just give me the open source. I'll code it. I got an unlimited resource team. Not, not always the case. So I gotta ask you guys on Patrion. Why use a company like armory, if you have the open source code and armory, why did you build a business on the open source project? Like Spinnaker? >>Yeah. Like I see. Absolutely. Yeah. Like I, like I said earlier, the atrium, the Patrion SRE team was wasn't is fairly small. There's two people. Now we're six. People are still people down. We're six people now. So being sure we could run a Spinnaker on our own if we, if we wanted to. And, but then we'd have no time to do anything else basically. And that's not the best use of our, of our creators money. Our fans, the fans being the creators artists. We have obviously take a percentage on top of that. And we, we need to spend our, that money well, and having armory who's dedicated to the Spinnaker is dedicated, involved the open source project. But also there are experts on this Sunday. It was something that would take me like a week of stumbling around trying to find documentation on how to set this thing up. They done this like 15, 20 times and they can just go, oh yeah, this is what we do for this. And let me go fix it for you >>At score. You know, you've got a teammate. I think that's where, what you're getting at. I got to ask you what other things is that free you up? Because this is the classic business model of life. You know, you have a partner you're moving fast, it slows you down to get into it. Sure. You can do it yourself, but why it's faster to go with it, go together with a partner and a wing man as we will. What things did does that free you up to work on as an SRE? >>Oh, that's freed me up to work on a bigger parts of our build and deploy pipeline. It's freed me up to work on moving from a usage based deploys onto a containerization strategy. It's freed me up to work on more broader observability issues instead of just being laser-focused on running an operating spending. >>Yeah. And that really kind of highlights. I'm glad you said that because it highlights what's going on. You had a lot of speed and velocity. You've got scale, you've got security and you've got new challenges you got to fix in and move fast. It's a whole new world. So again, this is why I love cloud native. Right? So you got open source, you got scale and you guys are applying directly to the, to the infrastructure of the business. So Ben, I got to ask you armory. Co-founder why did you guys build your business on an open source project? Like Spinnaker? What was the mindset? How did you attack this? What did you guys do? Take us through that piece because this is truly a great entrepreneurial story about open source. >>Yeah. Yeah. I'll give you the abridged version, which is that my co-founders and I, we solved the same problem, which is CD at a previous company, but we did it kind of the old fashioned way we home role. We handled it ourselves. We built it on top of Jenkins and it was great for that company, but, and that was kind of the inspiration for us to then ask questions. Hey, is this bigger? We, when at the time we found that Spinnaker had just been, you know, dog food inside of Netflix and they were open sourcing it. And we thought it was a great opportunity for us to partner. But the bigger reason is that Spinnaker is a platform that deploys to other platforms like AWS and Kubernetes and the sheer amount of surface area that's required to build a great product is enormous. And I actually believe that the only way to be successful in this space is to be open source, to have a community of large companies and passionate developers that contribute the roads if you will, to deploy into various targets. >>And so that's the reason, number one for it being open source and us wanting to build our business on top of open source. And then the second reason is because we focus almost exclusively on solving enterprise scale problems. We have a platform that needs to be extensible and open source is by definition extensible. So our customers, I mean, Ian just had a great example, right? Like he needed to fix something he was able to do so solve it in open source. And then, you know, shortly thereafter that that fix in mainline gets into the armory official build and then he can consume his fix. So we see a lot of that from our other customers. And then even, you know, take a very, very large company. They may have custom off that they need to integrate with, but that doesn't, that's not in open-source Spinnaker, but they can go and build that themselves. >>Yeah, it's real. It really is the new modern way to develop. And I, you know, last 80 with startup showcase last season, Emily Freeman gave a talk on, you know, you know, retiring, I call it killing the software, SDLC, the lifecycle of how software was developed in the past. And I got to ask you guys, and, and this cube conversation is that this is kind of like the, the kind of the big wave we're on now is cloud scale, open source, cloud, native data security, all being built in on this in the pipelines to your point is SRS enabling a new infrastructure and a new environment for people to build essentially SAS. So I got to ask you guys as, and you mentioned it Ben, the old way you hand rolled something, Netflix, open source, something, you got to look at Lyft with Envoy. I mean, large-scale comes, are donating their stuff into open source and people getting on top of it and building it. So the world's changed. So we've got to ask you, what's the difference between standing up a SAS application today versus say five to eight years ago, because we all see salesforce.com. You know, they're out there, they built their own data center. Cloud skills changed the dynamics of how software is being built. And with open-source accelerating every quarter, you're seeing more growth in software. How has building a platform for applications changed and how has that changed? How people build SAS applications, Ben, what's your take on this? It's kind of a thought exercise here. >>Yeah. I mean, I wouldn't even call it a thought exercise. We're seeing it firsthand from our customers. And then I'll, you know, I'll, I'll give my answer and you can weigh in on like practical, like what you're actually doing at Patrion with SAS, but the, the costs and the kind of entry fee, if you will, for building a SAS application has tremendously dropped. You don't need to buy servers and put them inside data centers anymore. You just spin up a VM or Kubernetes cluster with AWS. AWS has led the way in public cloud to make this incredible easy. And the tool sets being built around cloud native, like armory and like many other companies in the space are making it even easier. So we're just seeing the proliferation of, of software being developed and, and hopefully, you know, armory is playing a role in, in making it easier and better. >>So before we get to Unum for a second, I just want to just double down on it because there's great conversation that implies that there's going to be a new migration of apps everywhere, right. As tsunami of clutter good or bad, is that good or bad or is it all open source? Is it all good then? >>Absolutely good. For sure. There will be, you know, good stuff developed and not so good stuff developed, but survival of the fittest will hopefully promote those, the best apps with the highest value to the end user and, and society at large and push us all forward. So, >>And what's your take, obviously, Kubernetes, you seeing things like observability talking about how we're managing stateful and services that are being deployed and tear down in real time, automated, all new things are developing. How does building a true scalable SAS application change today versus say five, eight years ago? >>I mean, like you said, there's a, there's a lot, there's a lot of new, both open source. So SAS products available that you can use to build a scale stuff. Like if you're going to need that to build like secure authentication, instead of having to roll that out and you could go with something like Okta raw zero, you can just pull that off the shelf stuff for like managing push notifications before that was like something really hard to really hard to do. Then Firebase came on the scene and also for manic state and application and stuff like that. And also for like being, being able to deliver before >>You had Jenkins, maybe even for that, you didn't really have anything Jenkins came along. And then now you have open-source products like Spinnaker that you can use to deliver. And then you have companies built around that, that you can just go and say, Hey, can you please help us deliver this? Like you just help us, enable us to be able to build, build our products so that we can focus on delivering value to our creators and fans instead of having to focus on, on other things. >>So bill it builds faster. You can compose stuff faster. You don't have to roll your own code. You can just roll your own modules basically, and then exactly what prietary on top of it. Absolutely. Yeah. And that's why commercial open source is booming. Guys. Thank you so much, Ben, congratulations on armory and great to have you on from Patrion well-known success. So we'll accompany you congratulate. If we don't know patriarch, check it out, they have changed the game on creators and leading the industry. Ben. Great, great shot with armory and Spinnaker. Thanks for coming on. Thank you >>So much. Thank you >>So much. Okay. I'm Sean Ferrer here with the cube conversation with Palo Alto. Thanks for watching.
SUMMARY :
horn, S staff SRE at Patrion gentlemen, you know, open source and enterprise is here And so if you believe that that's true. our applications that, you know, help, help creators get paid. the game you were doing creators before it was fashionable. So you have to ship with speed. And so I think, you know, preventing outages is One of the things that we saw was that deploying D So I don't have the ability to manage Spinnaker on my own. how soon can you get someone get someone over here? did you guys do? And so those are really the things that, that we focus on and we use you know, managing scale. So we work with our content delivery numbers or how does Spinnaker being an open source project help you guys? And it starts at the beginning. And I've also been able to commit So I gotta ask you guys on Patrion. And let me go fix it for you I got to ask you what other things is that free you up? It's freed me up to work on moving from a usage So Ben, I got to ask you armory. And I actually believe that the only way to be successful in this space is to And then even, you know, take a very, very large company. And I got to ask you guys, And then I'll, you know, I'll, I'll give my answer and you can weigh in on like practical, So before we get to Unum for a second, I just want to just double down on it because there's great conversation that implies that there's going There will be, you know, good stuff developed and And what's your take, obviously, Kubernetes, you seeing things like observability talking about how we're managing So SAS products available that you can use to build a scale stuff. And then now you have open-source products like Spinnaker that you can use to deliver. congratulations on armory and great to have you on from Patrion well-known success. Thank you Thanks for watching.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Sean Ferrer | PERSON | 0.99+ |
John | PERSON | 0.99+ |
Ben Mappin | PERSON | 0.99+ |
Emily Freeman | PERSON | 0.99+ |
Ian | PERSON | 0.99+ |
February of 2019 | DATE | 0.99+ |
Ian Delahorne | PERSON | 0.99+ |
Ben | PERSON | 0.99+ |
six | QUANTITY | 0.99+ |
Netflix | ORGANIZATION | 0.99+ |
AWS | ORGANIZATION | 0.99+ |
Patrion | ORGANIZATION | 0.99+ |
15 | QUANTITY | 0.99+ |
Ian Della horn | PERSON | 0.99+ |
Ben Mappen | PERSON | 0.99+ |
two people | QUANTITY | 0.99+ |
Palo Alto, California | LOCATION | 0.99+ |
Spinnaker | ORGANIZATION | 0.99+ |
SRE | ORGANIZATION | 0.99+ |
Second | QUANTITY | 0.99+ |
one degree | QUANTITY | 0.99+ |
second reason | QUANTITY | 0.99+ |
two weeks later | DATE | 0.99+ |
Patriot | ORGANIZATION | 0.99+ |
One | QUANTITY | 0.99+ |
two | QUANTITY | 0.99+ |
six people | QUANTITY | 0.99+ |
20 times | QUANTITY | 0.99+ |
both | QUANTITY | 0.99+ |
two great guests | QUANTITY | 0.98+ |
Patreon | ORGANIZATION | 0.98+ |
four | DATE | 0.98+ |
once a year | QUANTITY | 0.98+ |
one | QUANTITY | 0.98+ |
armory | ORGANIZATION | 0.98+ |
once a quarter | QUANTITY | 0.97+ |
SAS | ORGANIZATION | 0.97+ |
first | QUANTITY | 0.97+ |
three things | QUANTITY | 0.96+ |
five years ago | DATE | 0.96+ |
Envoy | ORGANIZATION | 0.96+ |
eight years ago | DATE | 0.95+ |
Lyft | ORGANIZATION | 0.95+ |
five | DATE | 0.94+ |
last 80 | DATE | 0.94+ |
Jenkins | TITLE | 0.94+ |
Sean ferry | PERSON | 0.93+ |
ENN Patriot | ORGANIZATION | 0.91+ |
today | DATE | 0.91+ |
Spinnaker | TITLE | 0.91+ |
salesforce.com | OTHER | 0.91+ |
first stab | QUANTITY | 0.9+ |
Kim Lewandowski and Dan Lorenc, Chainguard, Inc. | KubeCon + CloudNativeCon NA 2021
>>Hello, and welcome back to the cubes coverage of coop con cloud native con 2021. We're here in person at a real event. I'm John farrier host of the cube, but Dave Nicholson, Michael has got great guests here. Two founders of brand new startup, one week old cable on ASCII and Dave Lawrence, uh, with chain guard, former Google employees, open source community members decided to start a company with five other people on total five total. Congratulations. Welcome to the cube. >>Thank you. Thank you for >>Having us. So tell us like a product, you know, we know you don't have a price. So take us through the story because this is one of those rare moments. We got great chance to chat with you guys just a week into the new forms company and the team. What's the focus, what's the vision. >>How far back do you want to go with this story >>And why you left Google? So, you know, we're a gin and tonics. We get a couple of beers I can do that. We can do that. Let's just take over the world. >>Yeah. So we both been at Google, uh, for awhile. Um, the last couple of years we've been really worried about and focused on open-source security risk and supply chain security in general and software. Um, it's been a really interesting time as you probably noticed, uh, to be in that space, but it wasn't that interesting two years ago or even a year and a half ago. Um, so we were doing a bunch of this work at Google and the open source. Nobody really understood it. People kind of looked at us funny at talks and conferences. Um, and then beginning of this year, a bunch of attacks started happening, uh, things in the headlines like solar winds, solar winds attack, like you say, it attack all these different ransomware things happening. Uh, companies and governments are getting hit with supply chain attacks. So overnight people kind of started caring and being really worried about the stuff that we've been doing for a while. So it was a pretty cool thing to be a part of. And it seemed like a good time to start a company and keep your >>Reaction to this startup. How do you honestly feel, I suppose, feeling super excited. Yeah. >>I am really excited. I was in stars before Google. So then I went to Google where there for seven, I guess, Dan, a little bit longer, but I was there for seven years on the product side. And then yeah, we, we, the open source stuff, we were really there for protecting Google and we both came from cloud before that working on enterprise product. So then sorta just saw the opportunity, you know, while these companies trying to scramble and then sort of figure out how to better secure themselves. So it seemed like a perfect, >>The start-up bug and you back in the start up, but it's the timing's perfect. I got to say, this is a big conversation supply chain from whether it's components and software now, huge attack vector, people are taking advantage of it super important. So I'm really glad you're doing it. But first explain to the folks watching what is supply chain software? What's the challenge? What is the, what is the supply chain security challenge or problem? >>Sure. Yeah, it's the metaphor of software supply chain. It's just like physical supply chain. That's where the name came from. And it, it really comes down to how the code gets from your team's keyboard, your team's fingers on those keyboards into your production environment. Um, and that's just the first level of it. Uh, cause nobody writes all of the code. They use themselves. We're here at cloud native con it's hundreds of open source vendors, hundreds of open libraries that people are reusing. So your, your trust, uh, radius and your attack radius extends to not just your own companies, your own developers, but to everyone at this conference. And then everyone that they rely on all the way out. Uh, it's quite terrifying. It's a surface, the surface area explode pretty quickly >>And people are going and the, and the targeting to, because everyone's touching the code, it's open. It's a lot of action going on. How do you solve the problem? What is the approach? What's the mindset? What's the vision on the problems solving solutions? >>Yeah, that's a great question. I mean, I think like you said, the first step is awareness. Like Dan's been laughing, he's been, he felt like a crazy guy in the corner saying, you know, stop building software underneath your desk and you know, getting companies, >>Hey, we didn't do, why don't you tell them? I was telling him for five years. >>Yeah. But, but I think one of his go-to lines was like, would you pick up a thumb drive off the side of the street and plug it into your computer? Probably not. But when you download, you know, an open source package or something, that's actually can give you more privileges and production environments and it's so it's pretty scary. Um, so I think, you know, for the last few years we've been working on a number of open source projects in this space. And so I think that's where we're going to start is we're going to look at those and then try to grow out the community. And we're, we're watching companies, even like solar winds, trying to piece these parts together, um, and really come up with a better solution for themselves. >>Are there existing community initiatives or open source efforts that are underway that you plan to participate in or you chart? Are you thinking of charting a new >>Path? >>Oh, it's that looks like, uh, Thomas. Yeah, the, the SIG store project we kicked off back in March, if you've covered that or familiar with that at all. But we kicked that off back in March of 2021 kind of officially we'd look at code for awhile before then the idea there was to kind of do what let's encrypted, uh, for browsers and Webster, um, security, but for code signing and open source security. So we've always been able to get code signing certificates, but nobody's really using them because they're expensive. They're complicated, just like less encrypted for CAS. They made a free one that was automated and easy to use for developers. And now people do without thinking about it in six stores, we tried to do the same thing for open source and just because of the headlines that were happening and all of the attacks, the momentum has just been incredible. >>Is it a problem that people just have to just get on board with a certain platform or tool or people have too many tools, they abandoned them there, their focus shifts is there. Why what's the, what's the main problem right now? >>Well, I think, you know, part of the problem is just having the tools easy enough for developers are going to want to use them and it's not going to get in our way. I think that's going to be a core piece of our company is really nailing down the developer experience and these toolings and like the co-sign part of SIG store that he was explaining, like it's literally one command line to sign, um, a package, assign a container and then one line to verify on the other side. And then these organizations can put together sort of policies around who they trust and their system like today it's completely black box. They have no idea what they're running and takes a re >>You have to vape to rethink and redo everything pretty much if they want to do it right. If they just kind of fixing the old Europe's sold next solar with basically. >>Yeah. And that's why we're here at cloud native con when people are, you know, the timing is perfect because people are already rethinking how their software gets built as they move it into containers and as they move it into Kubernetes. So it's a perfect opportunity to not just shift to Kubernetes, but to fix the way you build software from this, >>What'd you say is the most prevalent change mindset change of developers. Now, if you had to kind of, kind of look at it and say, okay, current state-of-the-art mindset of a developer versus say a few years ago, is it just that they're doing things modularly with more people? Or is it more new approaches? Is there a, is there a, >>I think it's just paying attention to your building release process and taking it seriously. This has been a theme for, since I've been in software, but you have these very fancy production data centers with physical security and all these levels of, uh, Preston prevention and making sure you can't get in there, but then you've got a Jenkins machine that's three years old under somebody's desk building the code that goes into there. >>It gets socially engineered. It gets at exactly. >>Yeah. It's like the, it's like the movies where they, uh, instead of breaking into jail, they hide in the food delivery truck. And it's, it's that, that's the metaphor that I like perfectly. The fence doesn't work. If your truck, if you open the door once a week, it doesn't matter how big defenses. Yeah. So that's >>Good Dallas funny. >>And I, I think too, like when I used to be an engineer before I joined Google, just like how easy it is to bring in a third party package or something, you know, you need like an image editing software, like just go find one off the internet. And I think, you know, developers are slowly doing a mind shift. They're like, Hey, if I introduce a new dependency, you know, there's going to be, I'm going to have to maintain this thing and understand >>It's a little bit of a decentralized view too. Also, you got a little bit of that. Hey, if you sign it, you own it. If it tracks back to you, okay, you are, your fingerprints are, if you will, or on that chain of >>Custody and custody. >>Exactly. I was going to say, when I saw chain guard at first of course, I thought that my pant leg riding a bike, but then of course the supply chain things coming in, like on a conveyor belt, conveyor, conveyor belt. But that, that whole question of chain of custody, it isn't, it isn't as simple as a process where someone grabs some code, embeds it in, what's going on, pushes it out somewhere else. That's not the final step typically. Yeah. >>So somebody else grabs that one. And does it again, 35 more times, >>The one, how do you verify that? That's yeah, it seems like an obvious issue that needs to be addressed. And yet, apparently from what you're telling us for quite a while, people thought you were a little bit in that, >>And it's not just me. I mean, not so Ken Thompson of bell labs and he wrote the book >>He wrote, yeah, it was a seatbelt that I grew >>Up on in the eighties. He gave a famous lecture called uh, reflections on trusting trust, where he pranked all of his colleagues at bell labs by putting a back door in a compiler. And that put back doors into every program that compiled. And he was so clever. He even put it in, he made that compiler put a backdoor into the disassembler to hide the back door. So he spent weeks and, you know, people just kind of gave up. And I think at that point they were just like, oh, we can't trust any software ever. And just forgot about it and kept going on and living their lives. So this is a 40 year old problem. We only care about it now. >>It's totally true. A lot of these old sacred cows. So I would have done life cycles, not really that relevant anymore because the workflows are changing. These new Bev changes. It's complete dev ops is taken over. Let's just admit it. Right. So if we have ops is taken over now, cloud native apps are hitting the scene. This is where I think there's a structural industry change, not just the community. So with that in mind, how do you guys vector into that in terms of a market entry? What's just thinking around product. Obviously you got a higher, did you guys raise some capital in process? A little bit of a capital raise five, no problem. Todd market, but product wise, you've got to come in, get the beachhead. >>I mean, we're, we're, we're casting a wide net right now and talking to as many customers like we've met a lot of these, these customer potential customers through the communities, you know, that we've been building and we did a supply chain security con helped with that event, this, this Monday to negative one event and solar winds and Citibank were there and talking about their solutions. Um, and so I think, you know, and then we'll narrow it down to like people that would make good partners to work with and figure out how they think they're solving the problem today. And really >>How do you guys feel good? You feel good? Well, we got Jerry Chen coming off from gray lock next round. He would get a term sheet, Jerry, this guy's got some action on it in >>There. Probably didn't reply to him on LinkedIn. >>He's coming out with Kronos for him. He just invested 200 million at CrossFit. So you guys should have a great time. Congratulations on the leap. I know it's comfortable to beat Google, a lot of things to work on. Um, and student startups are super fun too, but not easy. None of the female or, you know, he has done it before, so. Right. Cool. What do you think about today? Did the event here a little bit smaller, more VIP event? What's your takeaway on this? >>It's good to be back in person. Obviously we're meeting, we've been associating with folks over zoom and Google meets for a while now and meeting them in person as I go, Hey, no hard to recognize behind the mask, but yeah, we're just glad to sort of be back out in a little bit of normalization. >>Yeah. How's everything in Austin, everyone everyone's safe and good over there. >>Yeah. It's been a long, long pandemic. Lots of ups and downs, but yeah. >>Got to get the music scene back. Most of these are comes back in the house. Everything's all back to normal. >>Yeah. My hair doesn't normally look like this. I just haven't gotten a haircut since this also >>You're going to do well in this market. You got a term sheet like that. Keep the hair, just to get the money. I think I saw your LinkedIn profile and I was wondering it's like, which version are we going to get? Well, super relevant. Super great topic. Congratulations. Thanks for coming on. Sharing the story. You're in the queue. Great jumper. Dave Nicholson here on the cube date, one of three days we're back in person of course, hybrid event. Cause the cube.net for all more footage and highlights and remote interviews. So stay tuned more coverage after this short break.
SUMMARY :
I'm John farrier host of the cube, but Dave Nicholson, Michael has got great guests here. Thank you for We got great chance to chat with you guys And why you left Google? And it seemed like a good time to start a company and keep your How do you honestly feel, I suppose, feeling super excited. you know, while these companies trying to scramble and then sort of figure out how to better secure themselves. The start-up bug and you back in the start up, but it's the timing's perfect. And it, it really comes down to how the code gets from your team's keyboard, How do you solve the problem? he's been, he felt like a crazy guy in the corner saying, you know, stop building software underneath your desk and Hey, we didn't do, why don't you tell them? Um, so I think, you know, for the last few years we've been working on a number of the headlines that were happening and all of the attacks, the momentum has just been incredible. Is it a problem that people just have to just get on board with a certain platform or tool Well, I think, you know, part of the problem is just having the tools easy enough for developers are going to want to use them the old Europe's sold next solar with basically. So it's a perfect opportunity to not just shift to Kubernetes, but to fix the way you build software from this, What'd you say is the most prevalent change mindset change of developers. and all these levels of, uh, Preston prevention and making sure you can't get in there, but then you've got It gets socially engineered. And it's, it's that, that's the metaphor that I like perfectly. And I think, you know, developers are slowly doing a mind shift. Hey, if you sign it, That's not the final step typically. So somebody else grabs that one. people thought you were a little bit in that, the book a backdoor into the disassembler to hide the back door. So with that in mind, how do you guys vector into that in terms of a market entry? Um, and so I think, you know, and then we'll narrow it down How do you guys feel good? Probably didn't reply to him on LinkedIn. None of the female or, you know, he has done it before, so. It's good to be back in person. Lots of ups and downs, but yeah. Got to get the music scene back. I just haven't gotten a haircut since this also Keep the hair, just to get the money.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Dave Nicholson | PERSON | 0.99+ |
Ken Thompson | PERSON | 0.99+ |
Dan | PERSON | 0.99+ |
March | DATE | 0.99+ |
March of 2021 | DATE | 0.99+ |
Kim Lewandowski | PERSON | 0.99+ |
Dave Lawrence | PERSON | 0.99+ |
Austin | LOCATION | 0.99+ |
seven years | QUANTITY | 0.99+ |
Jerry Chen | PERSON | 0.99+ |
John farrier | PERSON | 0.99+ |
seven | QUANTITY | 0.99+ |
ORGANIZATION | 0.99+ | |
Jerry | PERSON | 0.99+ |
five | QUANTITY | 0.99+ |
Michael | PERSON | 0.99+ |
35 more times | QUANTITY | 0.99+ |
200 million | QUANTITY | 0.99+ |
Citibank | ORGANIZATION | 0.99+ |
CrossFit | ORGANIZATION | 0.99+ |
Dan Lorenc | PERSON | 0.99+ |
six stores | QUANTITY | 0.99+ |
Two founders | QUANTITY | 0.99+ |
Thomas | PERSON | 0.99+ |
first | QUANTITY | 0.98+ |
two years ago | DATE | 0.98+ |
today | DATE | 0.98+ |
a year and a half ago | DATE | 0.98+ |
first step | QUANTITY | 0.98+ |
once a week | QUANTITY | 0.98+ |
ASCII | ORGANIZATION | 0.98+ |
KubeCon | EVENT | 0.98+ |
one line | QUANTITY | 0.98+ |
first level | QUANTITY | 0.98+ |
Chainguard, Inc. | ORGANIZATION | 0.98+ |
ORGANIZATION | 0.98+ | |
five other people | QUANTITY | 0.97+ |
three days | QUANTITY | 0.97+ |
one | QUANTITY | 0.97+ |
both | QUANTITY | 0.97+ |
this year | DATE | 0.97+ |
hundreds of open libraries | QUANTITY | 0.96+ |
cube.net | OTHER | 0.95+ |
one command | QUANTITY | 0.95+ |
eighties | DATE | 0.95+ |
CloudNativeCon | EVENT | 0.94+ |
Europe | LOCATION | 0.94+ |
SIG | ORGANIZATION | 0.92+ |
hundreds of open source vendors | QUANTITY | 0.91+ |
three years old | QUANTITY | 0.91+ |
bell labs | ORGANIZATION | 0.89+ |
few years ago | DATE | 0.89+ |
one week old | QUANTITY | 0.88+ |
40 year old | QUANTITY | 0.88+ |
last couple of years | DATE | 0.82+ |
pandemi | EVENT | 0.81+ |
chain guard | ORGANIZATION | 0.81+ |
Kronos | ORGANIZATION | 0.78+ |
five years | QUANTITY | 0.78+ |
Kubernetes | TITLE | 0.77+ |
NA 2021 | EVENT | 0.77+ |
last few years | DATE | 0.73+ |
this Monday | DATE | 0.72+ |
a week | QUANTITY | 0.7+ |
con | ORGANIZATION | 0.63+ |
many | QUANTITY | 0.54+ |
Bev | ORGANIZATION | 0.53+ |
native con 2021 | EVENT | 0.52+ |
coop con cloud | ORGANIZATION | 0.51+ |
Dallas | TITLE | 0.49+ |
Jenkins | ORGANIZATION | 0.46+ |
Preston | ORGANIZATION | 0.45+ |
Kingdon Barrett, Weaveworks | KubeCon + CloudNativeCon NA 2021
>>Good morning, welcome to the cubes coverage of Qube con and cloud native con 21 live from Los Angeles. Lisa Martin, here with Dave Nicholson. David's great to be in person with other humans at this conference. Finally, I can't believe >>You're arms length away. It's unreal. >>I know, and they checked backs cards. So everybody's here is nice and safe. We're excited to welcome kingdom Barrett to the program, flux, maintainer and open source support engineer at we works. He came to him. Welcome to the program. >>Oh, thank you for having me on today. >>So let's talk about flux. This is a CNCF incubating project. I saw catalyze as adopt talk to us about flux and its evolution. >>Uh, so flex is, uh, uh, just got into its second version a while ago. We've been, uh, working on, um, uh, we're an incubating project and we're going towards graduation at this point. Um, flex has seen a great deal of adoption from, uh, infant cloud infrastructure vendors in particular, uh, like Microsoft and Amazon and VMware, all building products on, um, flux, uh, the latest version of flux. And, uh, we've heard, uh, from companies like Alibaba and state farm. We had a, uh, uh, conference, uh, at a co-hosted event earlier on Tuesday called get-ups con, uh, where we presented all about get ops, which is the technology, uh, guiding, uh, set of principles that underlies flux. And, uh, there are new adopters, um, all, all every day, including, uh, the department of defense, uh, who has a hundred thousand developers. Um, it's, it's, it's very successful project at this point, who are the >>Key users of flux flux? >>Excuse me. The key users of flux are, uh, probably, uh, application developers and infrastructure engineers, and platform support folks. So a pretty broad spectrum of people. >>And you've got some news at the event. >>Yeah, we actually, uh, we have a, uh, ecosystem event that's coming up, um, on October 20th, uh, it's free virtual event. Uh, folks can join us to hear from these companies. We have people from high level, uh, CTOs and GMs, uh, from companies like Microsoft, Amazon VMware, uh, we've worked D two IQ, um, that are, uh, going to be speaking, uh, about their, uh, products that you can buy from their cloud vendor, uh, that, uh, are based on flux. Uh, so, so that's a milestone for us. That's a major milestone. These are large vendors, um, major cloud vendors that have decided that they trust, uh, flux with their customers workloads. And it's, it's the way that they want to push get ups. Great >>Validation. Yeah. >>So give us an example, just digging in a little bit on flux and get ops. What are some of the things that flux either enforces or enables or validates? What, how would you describe the flux get ops relationship? >>So the first to get ops principles is declarative infrastructure and that's, uh, that's something that people who are using Kubernetes are already very familiar with. Um, flux has a basic itself, or, or I guess spawned, uh, maybe is a better way to say it. Uh, this, um, uh, whole get ops working group, that's just defined the principles. There's four of them in the formal definition. That's just been promoted to a 1.0 and, uh, the get ups working group, publish, publish this at, uh, open get-ups dot dev where you can read all four. And, um, it's great copy site. If you're not really familiar with get ops, you can, you can read all four, but, uh, the other, uh, the second one I would have mentioned is, uh, version storage is, is, uh, it's called get ups and get as a version store. So it's a good for, um, disaster recovery. >>Uh, and, uh, if you have an issue with a new release, if you're, uh, pushing changes frequently, that's, you know, more than likely you will have issues from time to time. Uh, you can roll back with, get ups because everything is version. Um, and, uh, you can do those releases rapidly because the deployment is automatic, um, and it's continuously reconciling. So those are the four principles of get ups. Uh, and they're, they're not exactly prescriptive. You don't have to adopt them all at once. You can pick and choose where you want to get started. Um, but that's what, uh, is underneath flux. >>How do you help customers pick and choose based on what are some of the key criteria that you would advise them on? >>We would advise them to try to follow all of those principles, because that's what you get out of the box with fluxes is a solution that does those things. But if there is one of those things that gets in a way, um, there's also the concept of a closed loop that is, um, sometimes debated as whether it should be part of the get ops principles or not. Um, that just means that, uh, when you use get-ups the only changes that go to your infrastructure are coming through get-ups. Uh, so you don't have someone coming in and using the back door. Um, it all goes through get, uh, w when you want to make a change to your cluster or your application, you push it to get the automation takes over from there and, um, and makes, uh, developers and platform engineers jobs a lot easier. And it makes it easier for them to collaborate with each other, >>Of course, productivity. You mentioned AWS, Microsoft, VMware, uh, all working with you to deliver, get ups to enterprise customers. Talk to me about some of the benefits in it for these big guys. I mean, that's great validation, but what's in it for AWS and VMware and Microsoft, for example, business outcome wise. >>Well, uh, one of the things that we've been promoting and since June is a flex has been, uh, uh, there's an API underneath, that's called the get ops toolkit. This is, uh, if you're building a platform for platforms like these cloud vendors are, um, we announced that fluxes APRs are officially stable. So that means that it's safe for them to build on top of, and they can, uh, go ahead and build things and not worry that we're going to pull the rug out from under them. So that's one of the major vendors, uh, one of the major, uh, uh, vendor benefits and, um, uh, we've, we've also added a recent improvement, uh, uh, called service side apply that, uh, will improve performance. Uh, we reduced the number of, um, API calls, but also for, for, uh, users, it makes things a lot easier because they don't have to write explicitly health checks on everything. Uh, it's possible for them to say, we'd like to see everything is healthy, and it's a one-line addition, that's it? >>So, you know, there's been a lot of discussion from a lot of different angles of the subject of security, uh, in this space. Um, how does this, how does this dovetail with that? A lot of discussion specifically about software supply chain security. Now this is more in the operations space. How do, how do those come together? Do you have any thoughts on security? >>Well, flux is built for security first. Um, there are a lot of products out there that, uh, will shell out to other tools and, and that's a potential vulnerability and flux does not do that. Uh, we've recently undergone a security audit, which we're waiting for the results and the report over, but this is part of our progress towards the CNCF graduated status. Um, and, uh, we've, we've liked what we've seen and preliminary results. Uh, we've, we've prepared for the security audit on knowing that it was coming and, uh, uh, flexes, uh, uh, designed for security first. Uh, you're able to verify that the commits that you're applying to your cluster are signed and actually come from a valid author who is, uh, permitted to make changes to the cluster and, uh, get ops itself is, is this, uh, model of operations by poll requests. So, um, you, you have an opportunity to make sure that your changes are, uh, appropriately reviewed before they get applied. >>Got it. So you had a session at coupon this week. Talk to me a little bit about that. What were like the top three takeaways, and maybe even share with us some of the feedback that you got from the audience? >>Um, so, uh, the session was about Jenkins and get ups or Jenkins and flux. And the, um, the main idea is that when you use flux, flux is a tool for delivery. So you've heard maybe of CIC, D C I N C D are separate influx. We consider these as two separate jobs that should not cross over. And, uh, when, when, uh, you do that. So the talk is about Jenkins and flux. Jenkins is a very popular CII solution and the messages, uh, you don't have to abandon, if you've made a large infrastructure investment in a CII solution, you don't have to abandon your Jenkins or your GitHub actions or, or whatever other CII solution you're using to build and test images. Uh, you can take it with you and adopt get ups. >>Um, so there's compatibility there and, and usability familiarity for the audience, the users. Yeah. What was some of the feedback that they provided to you? Um, were they surprised by that? Happy about that? >>Well, and talk to us a little bit fast paced. Uh, we'll put it in the advanced CIC D track. I covered a lot of ground in that talk, and I hope to go back and cover things in a little bit smaller steps. Um, I tried to show as many of the features of Fluxus as I could. Uh, and, and so one of the feedback that I got was actually, it was a little bit difficult to follow up as, so I'm a new presenter. Um, this is my first year we've worked. I've never presented at CubeCon before. Um, I'm really glad I got the opportunity to be here. This is a great, uh, opportunity to collaborate with other open source teams. And, um, that's, that's, uh, that's the takeaway from me? No. >>So you've got to give a shout out to, uh, to weave works. Absolutely. You know, any, any organization that realizes the benefit of having its folks participating in the community, realizing that it, it helps the community, it helps you, it helps them, you know, that's, that's what we love about, about all of this. >>Yeah. We're, uh, we're really excited to grow adoption for, um, Kubernetes and get ops together. So, >>So I've asked a few people this over the last couple of days, where do you think we are in the peak Kubernetes curve? Are we still just at the very beginning stages of this, of this as a, as a movement? >>Um, certainly we're, um, it's, it's, uh, for, for people who are here at CubeCon, I think we see that, you know, uh, a lot of companies are very successful with Kubernetes, but, um, I come from a university, it, uh, background and I haven't seen a lot of adoption, uh, in, in large enterprise, um, more conservative enterprises, at least in, in my personal experience. And I think that, uh, there is a lot for those places to gain, um, through, through, uh, adopting Kubernetes and get ups together. I think get ops is, uh, we'll provide them with the opportunity to, uh, experience Kubernetes in the best way possible. >>We've seen such acceleration in the last 18, 19 months of digital transformation for companies to survive, to pivot during COVID to survive, doubt to thrive. Do you see that influencing the adoption of Kubernetes and maybe different industries getting more comfortable with leveraging it as a platform? >>Sure. Um, a lot of companies see it as a cost center. And so if you can make it easier or possible to do, uh, operations with fewer people in the loop, um, that, that makes it a cost benefit for a lot of people, but also you need to keep people in the loop. You need to keep the people that you have included and, and be transparent about what infrastructure choices and changes you're making. So, uh, that's one of the things that get ups really helps with >>At transparency is key. One more question for you. Can you share a little bit before we wrap here about the project roadmap and some of the things that are coming down the pike? Yeah. >>So I mentioned a graduation. That's the immediate goal that we're working towards? Uh, most directly, uh, we have, um, grown our, uh, number of integrations pretty significantly. We have an operator how entry in red hat, open shift there's operator hub, where you can go and click to install flux. And that's great. Um, and, uh, we looked forward to, uh, making flux more compatible with more of the tools that you find in the CNCF umbrella. Um, that's, that's what our roadmap is for >>Increasing that compatibility. And one more time mentioned the event, October 20th, I believe he said, let folks know where they can go and find it on the web. Yeah. >>If you're interested in the get ups days.com, it's the get-ups one-stop shop and it's, uh, vendors like AWS and Microsoft and VMware detour IQ. And we've worked, we've all built a flux based solutions, um, for, uh, that are available for sale right now. So if you're, uh, trying to use get-ups and you have one of these vendors as your cloud vendor, um, it seems like a natural fit to try the solution that's out of the box. Uh, but if you need convincing, you get Upstate's dot com, you can go find out more about the event and, uh, we'll hope to see you there. >>I get upstairs.com kingdom. Thank you. You're joining Dave and me on the program, talking to us about flux. Congratulations on its evolution. We look forward to hearing more great things as the years unfold. >>Thank you so much for having me on our pleasure >>For Dave Nicholson. I'm Lisa Martin. You're watching the kid live from Los Angeles at CubeCon cloud native con 21 stick around Dave and I, and we'll be right back with our next guest.
SUMMARY :
David's great to be in person with other humans You're arms length away. We're excited to welcome kingdom Barrett to the program, to us about flux and its evolution. Uh, so flex is, uh, uh, just got into its second version a while So a pretty broad spectrum of people. uh, products that you can buy from their cloud vendor, uh, that, uh, are based on flux. Yeah. What, how would you describe the flux get ops and, uh, the get ups working group, publish, publish this at, uh, open get-ups dot dev where you can Uh, and, uh, if you have an issue with a new release, if you're, uh, w when you want to make a change to your cluster or your application, you push it to get the automation uh, all working with you to deliver, get ups to enterprise customers. So that means that it's safe for them to build on top of, and they can, uh, of security, uh, in this space. Um, and, uh, we've, we've liked what we've seen and preliminary results. and maybe even share with us some of the feedback that you got from the audience? And, uh, when, when, uh, you do that. Um, so there's compatibility there and, and usability familiarity for the audience, uh, opportunity to collaborate with other open source teams. it helps the community, it helps you, it helps them, you know, that's, So, I think get ops is, uh, we'll provide them with the opportunity to, Do you see that influencing the adoption of Kubernetes and maybe different So, uh, that's one of the things that get ups really helps with Can you share a little bit before we wrap here about the project roadmap Um, and, uh, we looked forward to, uh, And one more time mentioned the event, October 20th, I believe he said, uh, trying to use get-ups and you have one of these vendors as your cloud vendor, You're joining Dave and me on the program, talking to us about flux. con 21 stick around Dave and I, and we'll be right back with our next guest.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Dave | PERSON | 0.99+ |
Lisa Martin | PERSON | 0.99+ |
Microsoft | ORGANIZATION | 0.99+ |
Dave Nicholson | PERSON | 0.99+ |
Alibaba | ORGANIZATION | 0.99+ |
AWS | ORGANIZATION | 0.99+ |
October 20th | DATE | 0.99+ |
Amazon | ORGANIZATION | 0.99+ |
Los Angeles | LOCATION | 0.99+ |
David | PERSON | 0.99+ |
June | DATE | 0.99+ |
one-line | QUANTITY | 0.99+ |
one | QUANTITY | 0.99+ |
Jenkins | TITLE | 0.99+ |
second version | QUANTITY | 0.98+ |
CNCF | ORGANIZATION | 0.98+ |
flex | ORGANIZATION | 0.98+ |
VMware | ORGANIZATION | 0.98+ |
this week | DATE | 0.98+ |
first year | QUANTITY | 0.98+ |
first | QUANTITY | 0.97+ |
GitHub | ORGANIZATION | 0.97+ |
today | DATE | 0.97+ |
CubeCon | EVENT | 0.96+ |
two separate jobs | QUANTITY | 0.95+ |
Kingdon Barrett | ORGANIZATION | 0.95+ |
udNativeCon NA 2021 | EVENT | 0.95+ |
One more question | QUANTITY | 0.93+ |
Weaveworks | ORGANIZATION | 0.92+ |
second one | QUANTITY | 0.92+ |
CIC | TITLE | 0.92+ |
Upstate | ORGANIZATION | 0.92+ |
Kubernetes | TITLE | 0.92+ |
CubeCon | ORGANIZATION | 0.89+ |
Fluxus | TITLE | 0.87+ |
Qube con | EVENT | 0.86+ |
Kubernetes | ORGANIZATION | 0.85+ |
KubeCon | EVENT | 0.84+ |
ups days.com | OTHER | 0.83+ |
upstairs.com | OTHER | 0.83+ |
four | QUANTITY | 0.82+ |
Barrett | PERSON | 0.81+ |
three takeaways | QUANTITY | 0.8+ |
hundred thousand developers | QUANTITY | 0.79+ |
18 | QUANTITY | 0.75+ |
VMware detour IQ | ORGANIZATION | 0.75+ |
Kubernetes | PERSON | 0.75+ |
one more time | QUANTITY | 0.74+ |
four of them | QUANTITY | 0.71+ |
get | OTHER | 0.7+ |
1.0 | OTHER | 0.7+ |
19 months | QUANTITY | 0.69+ |
CII | TITLE | 0.68+ |
Clo | ORGANIZATION | 0.66+ |
flux | TITLE | 0.64+ |
Tuesday | DATE | 0.64+ |
COVID | TITLE | 0.63+ |
D two IQ | ORGANIZATION | 0.62+ |
con | EVENT | 0.59+ |
con | ORGANIZATION | 0.59+ |
last | DATE | 0.56+ |
21 | QUANTITY | 0.5+ |
cloud | ORGANIZATION | 0.5+ |
VMware | TITLE | 0.37+ |
Pat Conte, Opsani | AWS Startup Showcase
(upbeat music) >> Hello and welcome to this CUBE conversation here presenting the "AWS Startup Showcase: "New Breakthroughs in DevOps, Data Analytics "and Cloud Management Tools" featuring Opsani for the cloud management and migration track here today, I'm your host John Furrier. Today, we're joined by Patrick Conte, Chief Commercial Officer, Opsani. Thanks for coming on. Appreciate you coming on. Future of AI operations. >> Thanks, John. Great to be here. Appreciate being with you. >> So congratulations on all your success being showcased here as part of the Startups Showcase, future of AI operations. You've got the cloud scale happening. A lot of new transitions in this quote digital transformation as cloud scales goes next generation. DevOps revolution as Emily Freeman pointed out in her keynote. What's the problem statement that you guys are focused on? Obviously, AI involves a lot of automation. I can imagine there's a data problem in there somewhere. What's the core problem that you guys are focused on? >> Yeah, it's interesting because there are a lot of companies that focus on trying to help other companies optimize what they're doing in the cloud, whether it's cost or whether it's performance or something else. We felt very strongly that AI was the way to do that. I've got a slide prepared, and maybe we can take a quick look at that, and that'll talk about the three elements or dimensions of the problem. So we think about cloud services and the challenge of delivering cloud services. You've really got three things that customers are trying to solve for. They're trying to solve for performance, they're trying to solve for the best performance, and, ultimately, scalability. I mean, applications are growing really quickly especially in this current timeframe with cloud services and whatnot. They're trying to keep costs under control because certainly, it can get way out of control in the cloud since you don't own the infrastructure, and more importantly than anything else which is why it's at the bottom sort of at the foundation of all this, is they want their applications to be a really a good experience for their customers. So our customer's customer is actually who we're trying to solve this problem for. So what we've done is we've built a platform that uses AI and machine learning to optimize, meaning tune, all of the key parameters of a cloud application. So those are things like the CPU usage, the memory usage, the number of replicas in a Kubernetes or container environment, those kinds of things. It seems like it would be simple just to grab some values and plug 'em in, but it's not. It's actually the combination of them has to be right. Otherwise, you get delays or faults or other problems with the application. >> Andrew, if you can bring that slide back up for a second. I want to just ask one quick question on the problem statement. You got expenditures, performance, customer experience kind of on the sides there. Do you see this tip a certain way depending upon use cases? I mean, is there one thing that jumps out at you, Patrick, from your customer's customer's standpoint? Obviously, customer experience is the outcome. That's the app, whatever. That's whatever we got going on there. >> Sure. >> But is there patterns 'cause you can have good performance, but then budget overruns. Or all of them could be failing. Talk about this dynamic with this triangle. >> Well, without AI, without machine learning, you can solve for one of these, only one, right? So if you want to solve for performance like you said, your costs may overrun, and you're probably not going to have control of the customer experience. If you want to solve for one of the others, you're going to have to sacrifice the other two. With machine learning though, we can actually balance that, and it isn't a perfect balance, and the question you asked is really a great one. Sometimes, you want to over-correct on something. Sometimes, scalability is more important than cost, but what we're going to do because of our machine learning capability, we're going to always make sure that you're never spending more than you should spend, so we're always going to make sure that you have the best cost for whatever the performance and reliability factors that you you want to have are. >> Yeah, I can imagine. Some people leave services on. Happened to us one time. An intern left one of the services on, and like where did that bill come from? So kind of looked back, we had to kind of fix that. There's a ton of action, but I got to ask you, what are customers looking for with you guys? I mean, as they look at Opsani, what you guys are offering, what's different than what other people might be proposing with optimization solutions? >> Sure. Well, why don't we bring up the second slide, and this'll illustrate some of the differences, and we can talk through some of this stuff as well. So really, the area that we play in is called AIOps, and that's sort of a new area, if you will, over the last few years, and really what it means is applying intelligence to your cloud operations, and those cloud operations could be development operations, or they could be production operations. And what this slide is really representing is in the upper slide, that's sort of the way customers experience their DevOps model today. Somebody says we need an application or we need a feature, the developers pull down something from get. They hack an early version of it. They run through some tests. They size it whatever way they know that it won't fail, and then they throw it over to the SREs to try to tune it before they shove it out into production, but nobody really sizes it properly. It's not optimized, and so it's not tuned either. When it goes into production, it's just the first combination of settings that work. So what happens is undoubtedly, there's some type of a problem, a fault or a delay, or you push new code, or there's a change in traffic. Something happens, and then, you've got to figure out what the heck. So what happens then is you use your tools. First thing you do is you over-provision everything. That's what everybody does, they over-provision and try to soak up the problem. But that doesn't solve it because now, your costs are going crazy. You've got to go back and find out and try as best you can to get root cause. You go back to the tests, and you're trying to find something in the test phase that might be an indicator. Eventually your developers have to hack a hot fix, and the conveyor belt sort of keeps on going. We've tested this model on every single customer that we've spoken to, and they've all said this is what they experience on a day-to-day basis. Now, if we can go back to the side, let's talk about the second part which is what we do and what makes us different. So on the bottom of this slide, you'll see it's really a shift-left model. What we do is we plug in in the production phase, and as I mentioned earlier, what we're doing is we're tuning all those cloud parameters. We're tuning the CPU, the memory, the Replicas, all those kinds of things. We're tuning them all in concert, and we're doing it at machine speed, so that's how the customer gets the best performance, the best reliability at the best cost. That's the way we're able to achieve that is because we're iterating this thing in machine speed, but there's one other place where we plug in and we help the whole concept of AIOps and DevOps, and that is we can plug in in the test phase as well. And so if you think about it, the DevOps guy can actually not have to over-provision before he throws it over to the SREs. He can actually optimize and find the right size of the application before he sends it through to the SREs, and what this does is collapses the timeframe because it means the SREs don't have to hunt for a working set of parameters. They get one from the DevOps guys when they send it over, and this is how the future of AIOps is being really affected by optimization and what we call autonomous optimization which means that it's happening without humans having to press a button on it. >> John: Andrew, bring that slide back up. I want to just ask another question. Tuning in concert thing is very interesting to me. So how does that work? Are you telegraphing information to the developer from the autonomous workload tuning engine piece? I mean, how does the developer know the right knobs or where does it get that provisioning information? I see the performance lag. I see where you're solving that problem. >> Sure. >> How does that work? >> Yeah, so actually, if we go to the next slide, I'll show you exactly how it works. Okay, so this slide represents the architecture of a typical application environment that we would find ourselves in, and inside the dotted line is the customer's application namespace. That's where the app is. And so, it's got a bunch of pods. It's got a horizontal pod. It's got something for replication, probably an HPA. And so, what we do is we install inside that namespace two small instances. One is a tuning pod which some people call a canary, and that tuning pod joins the rest of the pods, but it's not part of the application. It's actually separate, but it gets the same traffic. We also install somebody we call Servo which is basically an action engine. What Servo does is Servo takes the metrics from whatever the metric system is is collecting all those different settings and whatnot from the working application. It could be something like Prometheus. It could be an Envoy Sidecar, or more likely, it's something like AppDynamics, or we can even collect metrics off of Nginx which is at the front of the service. We can plug into anywhere where those metrics are. We can pull the metrics forward. Once we see the metrics, we send them to our backend. The Opsani SaaS service is our machine learning backend. That's where all the magic happens, and what happens then is that service sees the settings, sends a recommendation to Servo, Servo sends it to the tuning pod, and we tune until we find optimal. And so, that iteration typically takes about 20 steps. It depends on how big the application is and whatnot, how fast those steps take. It could be anywhere from seconds to minutes to 10 to 20 minutes per step, but typically within about 20 steps, we can find optimal, and then we'll come back and we'll say, "Here's optimal, and do you want to "promote this to production," and the customer says, "Yes, I want to promote it to production "because I'm saving a lot of money or because I've gotten "better performance or better reliability." Then, all he has to do is press a button, and all that stuff gets sent right to the production pods, and all of those settings get put into production, and now he's now he's actually saving the money. So that's basically how it works. >> It's kind of like when I want to go to the beach, I look at the weather.com, I check the forecast, and I decide whether I want to go or not. You're getting the data, so you're getting a good look at the information, and then putting that into a policy standpoint. I get that, makes total sense. Can I ask you, if you don't mind, expanding on the performance and reliability and the cost advantage? You mentioned cost. How is that impacting? Give us an example of some performance impact, reliability, and cost impacts. >> Well, let's talk about what those things mean because like a lot of people might have different ideas about what they think those mean. So from a cost standpoint, we're talking about cloud spend ultimately, but it's represented by the settings themselves, so I'm not talking about what deal you cut with AWS or Azure or Google. I'm talking about whatever deal you cut, we're going to save you 30, 50, 70% off of that. So it doesn't really matter what cost you negotiated. What we're talking about is right-sizing the settings for CPU and memory, Replica. Could be Java. It could be garbage collection, time ratios, or heap sizes or things like that. Those are all the kinds of things that we can tune. The thing is most of those settings have an unlimited number of values, and this is why machine learning is important because, if you think about it, even if they only had eight settings or eight values per setting, now you're talking about literally billions of combinations. So to find optimal, you've got to have machine speed to be able to do it, and you have to iterate very, very quickly to make it happen. So that's basically the thing, and that's really one of the things that makes us different from anybody else, and if you put that last slide back up, the architecture slide, for just a second, there's a couple of key words at the bottom of it that I want to want to focus on, continuous. So continuous really means that we're on all the time. We're not plug us in one time, make a change, and then walk away. We're actually always measuring and adjusting, and the reason why this is important is in the modern DevOps world, your traffic level is going to change. You're going to push new code. Things are going to happen that are going to change the basic nature of the software, and you have to be able to tune for those changes. So continuous is very important. Second thing is autonomous. This is designed to take pressure off of the SREs. It's not designed to replace them, but to take the pressure off of them having to check pager all the time and run in and make adjustments, or try to divine or find an adjustment that might be very, very difficult for them to do so. So we're doing it for them, and that scale means that we can solve this for, let's say, one big monolithic application, or we can solve it for literally hundreds of applications and thousands of microservices that make up those applications and tune them all at the same time. So the same platform can be used for all of those. You originally asked about the parameters and the settings. Did I answer the question there? >> You totally did. I mean, the tuning in concert. You mentioned early as a key point. I mean, you're basically tuning the engine. It's not so much negotiating a purchase SaaS discount. It's essentially cost overruns by the engine, either over burning or heating or whatever you want to call it. I mean, basically inefficiency. You're tuning the core engine. >> Exactly so. So the cost thing is I mentioned is due to right-sizing the settings and the number of Replicas. The performance is typically measured via latency, and the reliability is typically measured via error rates. And there's some other measures as well. We have a whole list of them that are in the application itself, but those are the kinds of things that we look for as results. When we do our tuning, we look for reducing error rates, or we look for holding error rates at zero, for example, even if we improve the performance or we improve the cost. So we're looking for the best result, the best combination result, and then a customer can decide if they want to do so to actually over-correct on something. We have the whole concept of guard rail, so if performance is the most important thing, or maybe some customers, cost is the most important thing, they can actually say, "Well, give us the best cost, "and give us the best performance and the best reliability, "but at this cost," and we can then use that as a service-level objective and tune around it. >> Yeah, it reminds me back in the old days when you had filtering white lists of black lists of addresses that can go through, say, a firewall or a device. You have billions of combinations now with machine learning. It's essentially scaling the same concept to unbelievable. These guardrails are now in place, and that's super cool and I think really relevant call-out point, Patrick, to kind of highlight that. At this kind of scale, you need machine learning, you need the AI to essentially identify quickly the patterns or combinations that are actually happening so a human doesn't have to waste their time that can be filled by basically a bot at that point. >> So John, there's just one other thing I want to mention around this, and that is one of the things that makes us different from other companies that do optimization. Basically, every other company in the optimization space creates a static recommendation, basically their recommendation engines, and what you get out of that is, let's say it's a manifest of changes, and you hand that to the SREs, and they put it into effect. Well, the fact of the matter is is that the traffic could have changed then. It could have spiked up, or it could have dropped below normal. You could have introduced a new feature or some other code change, and at that point in time, you've already instituted these changes. They may be completely out of date. That's why the continuous nature of what we do is important and different. >> It's funny, even the language that we're using here: network, garbage collection. I mean, you're talking about tuning an engine, am operating system. You're talking about stuff that's moving up the stack to the application layer, hence this new kind of eliminating of these kind of siloed waterfall, as you pointed out in your second slide, is kind of one integrated kind of operating environment. So when you have that or think about the data coming in, and you have to think about the automation just like self-correcting, error-correcting, tuning, garbage collection. These are words that we've kind of kicking around, but at the end of the day, it's an operating system. >> Well in the old days of automobiles, which I remember cause I'm I'm an old guy, if you wanted to tune your engine, you would probably rebuild your carburetor and turn some dials to get the air-oxygen-gas mix right. You'd re-gap your spark plugs. You'd probably make sure your points were right. There'd be four or five key things that you would do. You couldn't do them at the same time unless you had a magic wand. So we're the magic wand that basically, or in modern world, we're sort of that thing you plug in that tunes everything at once within that engine which is all now electronically controlled. So that's the big differences as you think about what we used to do manually, and now, can be done with automation. It can be done much, much faster without humans having to get their fingernails greasy, let's say. >> And I think the dynamic versus static is an interesting point. I want to bring up the SRE which has become a role that's becoming very prominent in the DevOps kind of plus world that's happening. You're seeing this new revolution. The role of the SRE is not just to be there to hold down and do the manual configuration. They had a scale. They're a developer, too. So I think this notion of offloading the SRE from doing manual tasks is another big, important point. Can you just react to that and share more about why the SRE role is so important and why automating that away through when you guys have is important? >> The SRE role is becoming more and more important, just as you said, and the reason is because somebody has to get that application ready for production. The DevOps guys don't do it. That's not their job. Their job is to get the code finished and send it through, and the SREs then have to make sure that that code will work, so they have to find a set of settings that will actually work in production. Once they find that set of settings, the first one they find that works, they'll push it through. It's not optimized at that point in time because they don't have time to try to find optimal, and if you think about it, the difference between a machine learning backend and an army of SREs that work 24-by-seven, we're talking about being able to do the work of many, many SREs that never get tired, that never need to go play video games, to unstress or whatever. We're working all the time. We're always measuring, adjusting. A lot of the companies we talked to do a once-a-month adjustment on their software. So they put an application out, and then they send in their SREs once a month to try to tune the application, and maybe they're using some of these other tools, or maybe they're using just their smarts, but they'll do that once a month. Well, gosh, they've pushed code probably four times during the month, and they probably had a bunch of different spikes and drops in traffic and other things that have happened. So we just want to help them spend their time on making sure that the application is ready for production. Want to make sure that all the other parts of the application are where they should be, and let us worry about tuning CPU, memory, Replica, job instances, and things like that so that they can work on making sure that application gets out and that it can scale, which is really important for them, for their companies to make money is for the apps to scale. >> Well, that's a great insight, Patrick. You mentioned you have a lot of great customers, and certainly if you have your customer base are early adopters, pioneers, and grow big companies because they have DevOps. They know that they're seeing a DevOps engineer and an SRE. Some of the other enterprises that are transforming think the DevOps engineer is the SRE person 'cause they're having to get transformed. So you guys are at the high end and getting now the new enterprises as they come on board to cloud scale. You have a huge uptake in Kubernetes, starting to see the standardization of microservices. People are getting it, so I got to ask you can you give us some examples of your customers, how they're organized, some case studies, who uses you guys, and why they love you? >> Sure. Well, let's bring up the next slide. We've got some customer examples here, and your viewers, our viewers, can probably figure out who these guys are. I can't tell them, but if they go on our website, they can sort of put two and two together, but the first one there is a major financial application SaaS provider, and in this particular case, they were having problems that they couldn't diagnose within the stack. Ultimately, they had to apply automation to it, and what we were able to do for them was give them a huge jump in reliability which was actually the biggest problem that they were having. We gave them 5,000 hours back a month in terms of the application. They were they're having pager duty alerts going off all the time. We actually gave them better performance. We gave them a 10% performance boost, and we dropped their cloud spend for that application by 72%. So in fact, it was an 80-plus % price performance or cost performance improvement that we gave them, and essentially, we helped them tune the entire stack. This was a hybrid environment, so this included VMs as well as more modern architecture. Today, I would say the overwhelming majority of our customers have moved off of the VMs and are in a containerized environment, and even more to the point, Kubernetes which we find just a very, very high percentage of our customers have moved to. So most of the work we're doing today with new customers is around that, and if we look at the second and third examples here, those are examples of that. In the second example, that's a company that develops websites. It's one of the big ones out in the marketplace that, let's say, if you were starting a new business and you wanted a website, they would develop that website for you. So their internal infrastructure is all brand new stuff. It's all Kubernetes, and what we were able to do for them is they were actually getting decent performance. We held their performance at their SLO. We achieved a 100% error-free scenario for them at runtime, and we dropped their cost by 80%. So for them, they needed us to hold-serve, if you will, on performance and reliability and get their costs under control because everything in that, that's a cloud native company. Everything there is cloud cost. So the interesting thing is it took us nine steps because nine of our iterations to actually get to optimal. So it was very, very quick, and there was no integration required. In the first case, we actually had to do a custom integration for an underlying platform that was used for CICD, but with the- >> John: Because of the hybrid, right? >> Patrick: Sorry? >> John: Because it was hybrid, right? >> Patrick: Yes, because it was hybrid, exactly. But within the second one, we just plugged right in, and we were able to tune the Kubernetes environment just as I showed in that architecture slide, and then the third one is one of the leading application performance monitoring companies on the market. They have a bunch of their own internal applications and those use a lot of cloud spend. They're actually running Kubernetes on top of VMs, but we don't have to worry about the VM layer. We just worry about the Kubernetes layer for them, and what we did for them was we gave them a 48% performance improvement in terms of latency and throughput. We dropped their error rates by 90% which is pretty substantial to say the least, and we gave them a 50% cost delta from where they had been. So this is the perfect example of actually being able to deliver on all three things which you can't always do. It has to be, sort of all applications are not created equal. This was one where we were able to actually deliver on all three of the key objectives. We were able to set them up in about 25 minutes from the time we got started, no extra integration, and needless to say, it was a big, happy moment for the developers to be able to go back to their bosses and say, "Hey, we have better performance, "better reliability. "Oh, by the way, we saved you half." >> So depending on the stack situation, you got VMs and Kubernetes on the one side, cloud-native, all Kubernetes, that's dream scenario obviously. Not many people like that. All the new stuff's going cloud-native, so that's ideal, and then the mixed ones, Kubernetes, but no VMs, right? >> Yeah, exactly. So Kubernetes with no VMs, no problem. Kubernetes on top of VMs, no problem, but we don't manage the VMs. We don't manage the underlay at all, in fact. And the other thing is we don't have to go back to the slide, but I think everybody will remember the slide that had the architecture, and on one side was our cloud instance. The only data that's going between the application and our cloud instance are the settings, so there's never any data. There's never any customer data, nothing for PCI, nothing for HIPPA, nothing for GDPR or any of those things. So no personal data, no health data. Nothing is passing back and forth. Just the settings of the containers. >> Patrick, while I got you here 'cause you're such a great, insightful guest, thank you for coming on and showcasing your company. Kubernetes real quick. How prevalent is this mainstream trend is because you're seeing such great examples of performance improvements. SLAs being met, SLOs being met. How real is Kubernetes for the mainstream enterprise as they're starting to use containers to tip their legacy and get into the cloud-native and certainly hybrid and soon to be multi-cloud environment? >> Yeah, I would not say it's dominant yet. Of container environments, I would say it's dominant now, but for all environments, it's not. I think the larger legacy companies are still going through that digital transformation, and so what we do is we catch them at that transformation point, and we can help them develop because as we remember from the AIOps slide, we can plug in at that test level and help them sort of pre-optimize as they're coming through. So we can actually help them be more efficient as they're transforming. The other side of it is the cloud-native companies. So you've got the legacy companies, brick and mortar, who are desperately trying to move to digitization. Then, you've got the ones that are born in the cloud. Most of them aren't on VMs at all. Most of them are on containers right from the get-go, but you do have some in the middle who have started to make a transition, and what they've done is they've taken their native VM environment and they've put Kubernetes on top of it so that way, they don't have to scuttle everything underneath it. >> Great. >> So I would say it's mixed at this point. >> Great business model, helping customers today, and being a bridge to the future. Real quick, what licensing models, how to buy, promotions you have for Amazon Web Services customers? How do people get involved? How do you guys charge? >> The product is licensed as a service, and the typical service is an annual. We license it by application, so let's just say you have an application, and it has 10 microservices. That would be a standard application. We'd have an annual cost for optimizing that application over the course of the year. We have a large application pack, if you will, for let's say applications of 20 services, something like that, and then we also have a platform, what we call Opsani platform, and that is for environments where the customer might have hundreds of applications and-or thousands of services, and we can plug into their deployment platform, something like a harness or Spinnaker or Jenkins or something like that, or we can plug into their their cloud Kubernetes orchestrator, and then we can actually discover the apps and optimize them. So we've got environments for both single apps and for many, many apps, and with the same platform. And yes, thanks for reminding me. We do have a promotion for for our AWS viewers. If you reference this presentation, and you look at the URL there which is opsani.com/awsstartupshowcase, can't forget that, you will, number one, get a free trial of our software. If you optimize one of your own applications, we're going to give you an Oculus set of goggles, the augmented reality goggles. And we have one other promotion for your viewers and for our joint customers here, and that is if you buy an annual license, you're going to get actually 15 months. So that's what we're putting on the table. It's actually a pretty good deal. The Oculus isn't contingent. That's a promotion. It's contingent on you actually optimizing one of your own services. So it's not a synthetic app. It's got to be one of your own apps, but that's what we've got on the table here, and I think it's a pretty good deal, and I hope your guys take us up on it. >> All right, great. Get Oculus Rift for optimizing one of your apps and 15 months for the price of 12. Patrick, thank you for coming on and sharing the future of AIOps with you guys. Great product, bridge to the future, solving a lot of problems. A lot of use cases there. Congratulations on your success. Thanks for coming on. >> Thank you so much. This has been excellent, and I really appreciate it. >> Hey, thanks for sharing. I'm John Furrier, your host with theCUBE. Thanks for watching. (upbeat music)
SUMMARY :
for the cloud management and Appreciate being with you. of the Startups Showcase, and that'll talk about the three elements kind of on the sides there. 'cause you can have good performance, and the question you asked An intern left one of the services on, and find the right size I mean, how does the and the customer says, and the cost advantage? and that's really one of the things I mean, the tuning in concert. So the cost thing is I mentioned is due to in the old days when you had and that is one of the things and you have to think about the automation So that's the big differences of offloading the SRE and the SREs then have to make sure and certainly if you So most of the work we're doing today "Oh, by the way, we saved you half." So depending on the stack situation, and our cloud instance are the settings, and get into the cloud-native that are born in the cloud. So I would say it's and being a bridge to the future. and the typical service is an annual. and 15 months for the price of 12. and I really appreciate it. I'm John Furrier, your host with theCUBE.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Emily Freeman | PERSON | 0.99+ |
Patrick | PERSON | 0.99+ |
John | PERSON | 0.99+ |
Andrew | PERSON | 0.99+ |
John Furrier | PERSON | 0.99+ |
Pat Conte | PERSON | 0.99+ |
10% | QUANTITY | 0.99+ |
50% | QUANTITY | 0.99+ |
Patrick Conte | PERSON | 0.99+ |
15 months | QUANTITY | 0.99+ |
second | QUANTITY | 0.99+ |
90% | QUANTITY | 0.99+ |
AWS | ORGANIZATION | 0.99+ |
thousands | QUANTITY | 0.99+ |
four | QUANTITY | 0.99+ |
nine steps | QUANTITY | 0.99+ |
30 | QUANTITY | 0.99+ |
Oculus | ORGANIZATION | 0.99+ |
100% | QUANTITY | 0.99+ |
72% | QUANTITY | 0.99+ |
48% | QUANTITY | 0.99+ |
10 microservices | QUANTITY | 0.99+ |
second part | QUANTITY | 0.99+ |
First | QUANTITY | 0.99+ |
second slide | QUANTITY | 0.99+ |
first case | QUANTITY | 0.99+ |
Today | DATE | 0.99+ |
Amazon Web Services | ORGANIZATION | 0.99+ |
ORGANIZATION | 0.99+ | |
one | QUANTITY | 0.99+ |
20 services | QUANTITY | 0.99+ |
Prometheus | TITLE | 0.99+ |
second example | QUANTITY | 0.99+ |
second one | QUANTITY | 0.99+ |
five key | QUANTITY | 0.99+ |
One | QUANTITY | 0.99+ |
first | QUANTITY | 0.99+ |
third one | QUANTITY | 0.99+ |
80-plus % | QUANTITY | 0.99+ |
eight settings | QUANTITY | 0.99+ |
Opsani | PERSON | 0.99+ |
third examples | QUANTITY | 0.99+ |
two | QUANTITY | 0.99+ |
today | DATE | 0.99+ |
services | QUANTITY | 0.99+ |
50 | QUANTITY | 0.99+ |
eight values | QUANTITY | 0.99+ |
both | QUANTITY | 0.99+ |
nine | QUANTITY | 0.98+ |
three elements | QUANTITY | 0.98+ |
Servo | ORGANIZATION | 0.98+ |
80% | QUANTITY | 0.98+ |
opsani.com/awsstartupshowcase | OTHER | 0.98+ |
first one | QUANTITY | 0.98+ |
two small instances | QUANTITY | 0.98+ |
10 | QUANTITY | 0.97+ |
three things | QUANTITY | 0.97+ |
once a month | QUANTITY | 0.97+ |
one time | QUANTITY | 0.97+ |
70% | QUANTITY | 0.97+ |
GDPR | TITLE | 0.97+ |
zero | QUANTITY | 0.97+ |
Servo | TITLE | 0.97+ |
about 20 steps | QUANTITY | 0.97+ |
12 | QUANTITY | 0.96+ |
Kubernetes | TITLE | 0.96+ |
four times | QUANTITY | 0.96+ |
Sanjeev Mohan, SanjMo & Nong Li, Okera | AWS Startup Showcase
(cheerful music) >> Hello everyone, welcome to today's session of theCUBE's presentation of AWS Startup Showcase, New Breakthroughs in DevOps, Data Analytics, Cloud Management Tools, featuring Okera from the cloud management migration track. I'm John Furrier, your host. We've got two great special guests today, Nong Li, founder and CTO of Okera, and Sanjeev Mohan, principal @SanjMo, and former research vice president of big data and advanced analytics at Gartner. He's a legend, been around the industry for a long time, seen the big data trends from the past, present, and knows the future. Got a great lineup here. Gentlemen, thank you for this, so, life in the trenches, lessons learned across compliance, cloud migration, analytics, and use cases for Fortune 1000s. Thanks for joining us. >> Thanks for having us. >> So Sanjeev, great to see you, I know you've seen this movie, I was saying that in the open, you've at Gartner seen all the visionaries, the leaders, you know everything about this space. It's changing extremely fast, and one of the big topics right out of the gate is not just innovation, we'll get to that, that's the fun part, but it's the regulatory compliance and audit piece of it. It's keeping people up at night, and frankly if not done right, slows things down. This is a big part of the showcase here, is to solve these problems. Share us your thoughts, what's your take on this wide-ranging issue? >> So, thank you, John, for bringing this up, and I'm so happy you mentioned the fact that, there's this notion that it can slow things down. Well I have to say that the old way of doing governance slowed things down, because it was very much about control and command. But the new approach to data governance is actually in my opinion, it's liberating data. If you want to democratize or monetize, whatever you want to call it, you cannot do it 'til you know you can trust said data and it's governed in some ways, so data governance has actually become very interesting, and today if you want to talk about three different areas within compliance regulatory, for example, we all know about the EU GDPR, we know California has CCPA, and in fact California is now getting even a more stringent version called CPRA in a couple of years, which is more aligned to GDPR. That is a first area we know we need to comply to that, we don't have any way out. But then, there are other areas, there is insider trading, there is how you secure the data that comes from third parties, you know, vendors, partners, suppliers, so Nong, I'd love to hand it over to you, and see if you can maybe throw some light into how our customers are handling these use cases. >> Yeah, absolutely, and I love what you said about balancing agility and liberating, in the face of what may be seen as things that slow you down. So we work with customers across verticals with old and new regulations, so you know, you brought up GDPR. One of our clients is using this to great effect to power their ecosystem. They are a very large retail company that has operations and customers across the world, obviously the importance of GDPR, and the regulations that imposes on them are very top of mind, and at the same time, being able to do effective targeting analytics on customer information is equally critical, right? So they're exactly at that spot where they need this customer insight for powering their business, and then the regulatory concerns are extremely prevalent for them. So in the context of GDPR, you'll hear about things like consent management and right to be forgotten, right? I, as a customer of that retailer should say "I don't want my information used for this purpose," right? "Use it for this, but not this." And you can imagine at a very, very large scale, when you have a billion customers, managing that, all the data you've collected over time through all of your devices, all of your telemetry, really, really challenging. And they're leveraging Okera embedded into their analytics platform so they can do both, right? Their data scientists and analysts who need to do everything they're doing to power the business, not have to think about these kind of very granular customer filtering requirements that need to happen, and then they leverage us to do that. So that's kind of new, right, GDPR, relatively new stuff at this point, but we obviously also work with customers that have regulations from a long long time ago, right? So I think you also mentioned insider trading and that supply chain, so we'll talk to customers, and they want really data-driven decisions on their supply chain, everything about their production pipeline, right? They want to understand all of that, and of course that makes sense, whether you're the CFO, if you're going to make business decisions, you need that information readily available, and supply chains as we know get more and more and more complex, we have more and more integrated into manufacturing and other verticals. So that's your, you're a little bit stuck, right? You want to be data-driven on those supply chain analytics, but at the same time, knowing the details of all the supply chain across all of your dependencies exposes your internal team to very high blackout periods or insider trading concerns, right? For example, if you knew Apple was buying a bunch of something, that's maybe information that only a select few people can have, and the way that manifests into data policies, 'cause you need the ability to have very, very scalable, per employee kind of scalable data restriction policies, so they can do their job easier, right? If we talk about speeding things up, instead of a very complex process for them to get approved, and approved on SEC regulations, all that kind of stuff, you can now go give them access to the part of the supply chain that they need, and no more, and limit their exposure and the company's exposure and all of that kind of stuff. So one of our customers able to do this, getting two orders of magnitude, a 100x reduction in the policies to manage the system like that. >> When I hear you talking like that, I think the old days of "Oh yeah, regulatory, it kind of slows down innovation, got to go faster," pretty basic variables, not a lot of combination of things to check. Now with cloud, there seems to be combinations, Sanjeev, because how complicated has the regulatory compliance and audit environment gotten in the past few years, because I hear security in a supply chain, I hear insider threats, I mean these are security channels, not just compliance department G&A kind of functions. You're talking about large-scale, potentially combinations of access, distribution, I mean it seems complicated. How much more complicated is it now, just than it was a few years ago? >> So, you know the way I look at it is, I'm just mentioning these companies just as an example, when PayPal or Ebay, all these companies started, they started in California. Anybody who ever did business on Ebay or PayPal, guess where that data was? In the US in some data center. Today you cannot do it. Today, data residency laws are really tough, and so now these organizations have to really understand what data needs to remain where. On top of that, we now have so many regulations. You know, earlier on if you were healthcare, you needed to be HIPAA compliant, or banking PCI DSS, but today, in the cloud, you really need to know, what data I have, what sensitive data I have, how do I discover it? So that data discovery becomes really important. What roles I have, so for example, let's say I work for a bank in the US, and I decide to move to Germany. Now, the old school is that a new rule will be created for me, because of German... >> John: New email address, all these new things happen, right? >> Right, exactly. So you end up with this really, a mass of rules and... And these are all static. >> Rules and tools, oh my god. >> Yeah. So Okera actually makes a lot of this dynamic, which reduces your cloud migration overhead, and Nong used some great examples, in fact, sorry if I take just a second, without mentioning any names, there's one of the largest banks in the world is going global in the digital space for the first time, and they're taking Okera with them. So... >> But what's the point? This is my next topic in cloud migration, I want to bring this up because, complexity, when you're in that old school kind of data center, waterfall, these old rules and tools, you have to roll this out, and it's a pain in the butt for everybody, it's a hassle, huge hassle. Cloud gives the agility, we know that, and cloud's becoming more secure, and I think now people see the on-premise, certainly things that'd be on-premises for secure things, I get that, but when you start getting into agility, and you now have cloud regions, you can start being more programmatic, so I want to get you guys' thoughts on the cloud migration, how companies who are now lifting and shifting, replatforming, what's the refactoring beyond that, because you can replatform in the cloud, and still some are kind of holding back on that. Then when you're in the cloud, the ones that are winning, the companies that are winning are the ones that are refactoring in the cloud. Doing things different with new services. Sanjeev, you start. >> Yeah, so you know, in fact lot of people tell me, "You know, we are just going to lift and shift into the cloud." But you're literally using cloud as a data center. You still have all the, if I may say, junk you had on-prem, you just moved it into the cloud, and now you're paying for it. In cloud, nothing is free. Every storage, every processing, you're going to pay for it. The most successful companies are the ones that are replatforming, they are taking advantage of the platform as a service or software as a service, so that includes things like, you pay as you go, you pay for exactly the amount you use, so you scale up and scale down or scale out and scale in, pretty quickly, you know? So you're handling that demand, so without replatforming, you are not really utilizing your- >> John: It's just hosting. >> Yeah, you're just hosting. >> It's basically hosting if you're not doing anything right there. >> Right. The reason why people sometimes resist to replatform, is because there's a hidden cost that we don't really talk about, PaaS adds 3x to IaaS cost. So, some organizations that are very mature, and they have a few thousand people in the IT department, for them, they're like "No, we just want to run it in the cloud, we have the expertise, and it's cheaper for us." But in the long run, to get the most benefit, people should think of using cloud as a service. >> Nong what's your take, because you see examples of companies, I'll just call one out, Snowflake for instance, they're essentially a data warehouse in the cloud, they refactored and they replatformed, they have a competitive advantage with the scale, so they have things that others don't have, that just hosting. Or even on-premise. The new model developing where there's real advantages, and how should companies think about this when they have to manage these data lakes, and they have to manage all these new access methods, but they want to maintain that operational stability and control and growth? >> Yeah, so. No? Yeah. >> There's a few topics that are all (indistinct) this topic. (indistinct) enterprises moving to the cloud, they do this maybe for some cost savings, but a ton of it is agility, right? The motor that the business can run at is just so much faster. So we'll work with companies in the context of cloud migration for data, where they might have a data warehouse they've been using for 20 years, and building policies over that time, right? And it's taking a long time to go proof of access and those kind of things, made more sense, right? If it took you months to procure a physical infrastructure, get machines shipped to your data center, then this data access taking so long feels okay, right? That's kind of the same rate that everything is moving. In the cloud, you can spin up new infrastructure instantly, so you don't want approvals for getting policies, creating rules, all that stuff that Sanjeev was talking about, that being slow is a huge, huge problem. So this is a very common environment that we see where they're trying to do that kind of thing. And then, for replatforming, again, they've been building these roles and processes and policies for 20 years. What they don't want to do is take 20 years to go migrate all that stuff into the cloud, right? That's probably an experience nobody wants to repeat, and frankly for many of them, people who did it originally may or may not be involved in this kind of effort. So we work with a lot of companies like that, they have their, they want stability, they got to have the business running as normal, they got to get moving into the new infrastructure, doing it in a new way that, you know, with all the kind of lessons learned, so, as Sanjeev said, one of these big banks that we work with, that classical story of on-premise data warehousing, maybe a little bit of Hadoop, moved onto AWS, S3, Snowflake, that kind of setup, extremely intricate policies, but let's go reimagine how we can do this faster, right? What we like to talk about is, you're an organization, you need a design that, if you onboarded 1000 more data users, that's got to be way, way easier than the first 10 you onboarded, right? You got to get it to be easier over time, in a really, really significant way. >> Talk about the data authorization safety factor, because I can almost imagine all the intricacies of these different tools creates specialism amongst people who operate them. And each one might have their own little authorization nuance. Trend is not to have that siloed mentality. What's your take on clients that want to just "Hey, you know what? I want to have the maximum agility, but I don't want to get caught in the weeds on some of these tripwires around access and authorization." >> Yeah, absolutely, I think it's real important to get the balance of it, right? Because if you are an enterprise, or if you have diversive teams, you want them to have the ability to use tools as best of breed for their purpose, right? But you don't want to have it be so that every tool has its own access and provisioning and whatever, that's definitely going to be a security, or at least, a lot of friction for you to get things going. So we think about that really hard, I think we've seen great success with things like SSO and Okta, right? Unifying authentication. We think there's a very, very similar thing about to happen with authorization. You want that single control plane that can integrate with all the tools, and still get the best of what you need, but it's much, much easier (indistinct). >> Okta's a great example, if people don't want to build their own thing and just go with that, same with what you guys are doing. That seems to be the dots that are connecting you, Sanjeev. The ease of use, but yet the stability factor. >> Right. Yeah, because John, today I may want to bring up a SQL editor to go into Snowflake, just as an example. Tomorrow, I may want to use the Azure Bot, you know? I may not even want to go to Snowflake, I may want to go to an underlying piece of data, or I may use Power BI, you know, for some reason, and come from Azure side, so the point is that, unless we are able to control, in some sort of a centralized manner, we will not get that consistency. And security you know is all or nothing. You cannot say "Well, I secured my Snowflake, but if you come through HTFS, Hadoop, or some, you know, that is outside of my realm, or my scope," what's the point? So that is why it is really important to have a watertight way, in fact I'm using just a few examples, maybe tomorrow I decide to use a data catalog, or I use Denodo as my data virtualization and I run a query. I'm the same identity, but I'm using different tools. I may use it from home, over VPN, or I may use it from the office, so you want this kind of flexibility, all encompassed in a policy, rather than a separate rule if you do this and this, if you do that, because then you end up with literally thousands of rules. >> And it's never going to stop, either, it's like fashion, the next tool's going to come out, it's going to be cool, and people are going to want to use it, again, you don't want to have to then move the train from the compliance side this way or that way, it's a lot of hassle, right? So we have that one capability, you can bring on new things pretty quickly. Nong, am I getting it right, this is kind of like the trend, that you're going to see more and more tools and/or things that are relevant or, certain use cases that might justify it, but yet, AppSec review, compliance review, I mean, good luck with that, right? >> Yeah, absolutely, I mean we certainly expect tools to continue to get more and more diverse, and better, right? Most innovation in the data space, and I think we... This is a great time for that, a lot of things that need to happen, and so on and so forth. So I think one of the early goals of the company, when we were just brainstorming, is we don't want data teams to not be able to use the tools because it doesn't have the right security (indistinct), right? Often those tools may not be focused on that particular area. They're great at what they do, but we want to make sure they're enabled, they do some enterprise investments, they see broader adoption much easier. A lot of those things. >> And I can hear the sirens in the background, that's someone who's not using your platform, they need some help there. But that's the case, I mean if you don't get this right, there are some consequences, and I think one of the things I would like to bring up on next track is, to talk through with you guys is, the persona pigeonhole role, "Oh yeah, a data person, the developer, the DevOps, the SRE," you start to see now, developers and with cloud developers, and data folks, people, however they get pigeonholed, kind of blending in, okay? You got data services, you got analytics, you got data scientists, you got more democratization, all these things are being kicked around, but the notion of a developer now is a data developer, because cloud is about DevOps, data is now a big part of it, it's not just some department, it's actually blending in. Just a cultural shift, can you guys share your thoughts on this trend of data people versus developers now becoming kind of one, do you guys see this happening, and if so, how? >> So when, John, I started my career, I was a DBA, and then a data architect. Today, I think you cannot have a DBA who's not a developer. That's just my opinion. Because there is so much of CICD, DevOps, that happens today, and you know, you write your code in Python, you put it in version control, you deploy using Jenkins, you roll back if there's a problem. And then, you are interacting, you're building your data to be consumed as a service. People in the past, you would have a thick client that would connect to the database over TCP/IP. Today, people don't want to connect over TCP/IP necessarily, they want to go by HTTP. And they want an API gateway in the middle. So, if you're a data architect or DBA, now you have to worry about, "I have a REST API call that's coming in, how am I going to secure that, and make sure that people are allowed to see that?" And that was just yesterday. >> Exactly. Got to build an abstraction layer. You got to build an abstraction layer. The old days, you have to worry about schema, and do all that, it was hard work back then, but now, it's much different. You got serverless, functions are going to show way... It's happening. >> Correct, GraphQL, and semantic layer, that just blows me away because, it used to be, it was all in database, then we took it out of database and we put it in a BI tool. So we said, like BusinessObjects started this whole trend. So we're like "Let's put the semantic layer there," well okay, great, but that was when everything was surrounding BusinessObjects and Oracle Database, or some other database, but today what if somebody brings Power BI or Tableau or Qlik, you know? Now you don't have a semantic layer access. So you cannot have it in the BI layer, so you move it down to its own layer. So now you've got a semantic layer, then where do you store your metrics? Same story repeats, you have a metrics layer, then the data centers want to do feature engineering, where do you store your features? You have a feature store. And before you know, this stack has disaggregated over and over and over, and then you've got layers and layers of specialization that are happening, there's query accelerators like Dremio or Trino, so you've got your data here, which Nong is trying really hard to protect, and then you've got layers and layers and layers of abstraction, and networks are fast, so the end user gets great service, but it's a nightmare for architects to bring all these things together. >> How do you tame the complexity? What's the bottom line? >> Nong? >> Yeah, so, I think... So there's a few things you need to do, right? So, we need to re-think how we express security permanence, right? I think you guys have just maybe in passing (indistinct) talked about creating all these rules and all that kind of stuff, that's been the way we've done things forever. We get to think about policies and mechanisms that are much more dynamic, right? You need to really think about not having to do any additional work, for the new things you add to the system. That's really, really core to solving the complexity problem, right? 'Cause that gets you those orders of magnitude reduction, system's got to be more expressive and map to those policies. That's one. And then second, it's got to be implemented at the right layer, right, to Sanjeev's point, close to the data, and it can service all of those applications and use cases at the same time, and have that uniformity and breadth of support. So those two things have to happen. >> Love this universal data authorization vision that you guys have. Super impressive, we had a CUBE Conversation earlier with Nick Halsey, who's a veteran in the industry, and he likes it. That's a good sign, 'cause he's seen a lot of stuff, too, Sanjeev, like yourself. This is a new thing, you're seeing compliance being addressed, and with programmatic, I'm imagining there's going to be bots someday, very quickly with AI that's going to scale that up, so they kind of don't get in the innovation way, they can still get what they need, and enable innovation. You've got cloud migration, which is only going faster and faster. Nong, you mentioned speed, that's what CloudOps is all about, developers want speed, not things in days or hours, they want it in minutes and seconds. And then finally, ultimately, how's it scale up, how does it scale up for the people operating and/or programming? These are three major pieces. What happens next? Where do we go from here, what's, the customer's sitting there saying "I need help, I need trust, I need scale, I need security." >> So, I just wrote a blog, if I may diverge a bit, on data observability. And you know, so there are a lot of these little topics that are critical, DataOps is one of them, so to me data observability is really having a transparent view of, what is the state of your data in the pipeline, anywhere in the pipeline? So you know, when we talk to these large banks, these banks have like 1000, over 1000 data pipelines working every night, because they've got that hundred, 200 data sources from which they're bringing data in. Then they're doing all kinds of data integration, they have, you know, we talked about Python or Informatica, or whatever data integration, data transformation product you're using, so you're combining this data, writing it into an analytical data store, something's going to break. So, to me, data observability becomes a very critical thing, because it shows me something broke, walk me down the pipeline, so I know where it broke. Maybe the data drifted. And I know Okera does a lot of work in data drift, you know? So this is... Nong, jump in any time, because I know we have use cases for that. >> Nong, before you get in there, I just want to highlight a quick point. I think you're onto something there, Sanjeev, because we've been reporting, and we believe, that data workflows is intellectual property. And has to be protected. Nong, go ahead, your thoughts, go ahead. >> Yeah, I mean, the observability thing is critically important. I would say when you want to think about what's next, I think it's really effectively bridging tools and processes and systems and teams that are focused on data production, with the data analysts, data scientists, that are focused on data consumption, right? I think bridging those two, which cover a lot of the topics we talked about, that's kind of where security almost meets, that's kind of where you got to draw it. I think for observability and pipelines and data movement, understanding that is essential. And I think broadly, on all of these topics, where all of us can be better, is if we're able to close the loop, get the feedback loop of success. So data drift is an example of the loop rarely being closed. It drifts upstream, and downstream users can take forever to figure out what's going on. And we'll have similar examples related to buy-ins, or data quality, all those kind of things, so I think that's really a problem that a lot of us should think about. How do we make sure that loop is closed as quickly as possible? >> Great insight. Quick aside, as the founder CTO, how's life going for you, you feel good? I mean, you started a company, doing great, it's not drifting, it's right in the stream, mainstream, right in the wheelhouse of where the trends are, you guys have a really crosshairs on the real issues, how you feeling, tell us a little bit about how you see the vision. >> Yeah, I obviously feel really good, I mean we started the company a little over five years ago, there are kind of a few things that we bet would happen, and I think those things were out of our control, I don't think we would've predicted GDPR security and those kind of things being as prominent as they are. Those things have really matured, probably as best as we could've hoped, so that feels awesome. Yeah, (indistinct) really expanded in these years, and it feels good. Feels like we're in the right spot. >> Yeah, it's great, data's competitive advantage, and certainly has a lot of issues. It could be a blocker if not done properly, and you're doing great work. Congratulations on your company. Sanjeev, thanks for kind of being my cohost in this segment, great to have you on, been following your work, and you continue to unpack it at your new place that you started. SanjMo, good to see your Twitter handle taking on the name of your new firm, congratulations. Thanks for coming on. >> Thank you so much, such a pleasure. >> Appreciate it. Okay, I'm John Furrier with theCUBE, you're watching today's session presentation of AWS Startup Showcase, featuring Okera, a hot startup, check 'em out, great solution, with a really great concept. Thanks for watching. (calm music)
SUMMARY :
and knows the future. and one of the big topics and I'm so happy you in the policies to manage of things to check. and I decide to move to Germany. So you end up with this really, is going global in the digital and you now have cloud regions, Yeah, so you know, if you're not doing anything right there. But in the long run, to and they have to manage all Yeah, so. In the cloud, you can spin up get caught in the weeds and still get the best of what you need, with what you guys are doing. the Azure Bot, you know? are going to want to use it, a lot of things that need to happen, the SRE," you start to see now, People in the past, you The old days, you have and networks are fast, so the for the new things you add to the system. that you guys have. So you know, when we talk Nong, before you get in there, I would say when you want I mean, you started a and I think those things and you continue to unpack it Thank you so much, of AWS Startup Showcase,
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Nick Halsey | PERSON | 0.99+ |
John | PERSON | 0.99+ |
John Furrier | PERSON | 0.99+ |
California | LOCATION | 0.99+ |
US | LOCATION | 0.99+ |
Nong Li | PERSON | 0.99+ |
Apple | ORGANIZATION | 0.99+ |
Germany | LOCATION | 0.99+ |
Ebay | ORGANIZATION | 0.99+ |
PayPal | ORGANIZATION | 0.99+ |
20 years | QUANTITY | 0.99+ |
Sanjeev | PERSON | 0.99+ |
Tomorrow | DATE | 0.99+ |
two | QUANTITY | 0.99+ |
GDPR | TITLE | 0.99+ |
Sanjeev Mohan | PERSON | 0.99+ |
Today | DATE | 0.99+ |
One | QUANTITY | 0.99+ |
yesterday | DATE | 0.99+ |
Snowflake | TITLE | 0.99+ |
today | DATE | 0.99+ |
Python | TITLE | 0.99+ |
Gartner | ORGANIZATION | 0.99+ |
Tableau | TITLE | 0.99+ |
first time | QUANTITY | 0.99+ |
3x | QUANTITY | 0.99+ |
both | QUANTITY | 0.99+ |
100x | QUANTITY | 0.99+ |
one | QUANTITY | 0.99+ |
Okera | ORGANIZATION | 0.99+ |
Informatica | ORGANIZATION | 0.98+ |
two orders | QUANTITY | 0.98+ |
Nong | ORGANIZATION | 0.98+ |
SanjMo | PERSON | 0.98+ |
second | QUANTITY | 0.98+ |
Power BI | TITLE | 0.98+ |
1000 | QUANTITY | 0.98+ |
tomorrow | DATE | 0.98+ |
two things | QUANTITY | 0.98+ |
Qlik | TITLE | 0.98+ |
each one | QUANTITY | 0.97+ |
thousands of rules | QUANTITY | 0.97+ |
1000 more data users | QUANTITY | 0.96+ |
ORGANIZATION | 0.96+ | |
first 10 | QUANTITY | 0.96+ |
Okera | PERSON | 0.96+ |
AWS | ORGANIZATION | 0.96+ |
hundred, 200 data sources | QUANTITY | 0.95+ |
HIPAA | TITLE | 0.94+ |
EU | ORGANIZATION | 0.94+ |
CCPA | TITLE | 0.94+ |
over 1000 data pipelines | QUANTITY | 0.93+ |
single | QUANTITY | 0.93+ |
first area | QUANTITY | 0.93+ |
two great special guests | QUANTITY | 0.92+ |
BusinessObjects | TITLE | 0.92+ |
Richard Hummel, NETSCOUT | CUBE Conversation, July 2021
(upbeat music) >> Hey, welcome to this Cube conversation with NetScout. I'm Lisa Martin. Excited to talk to you. Richard Hummel, the manager of threat research for Arbor Networks, the security division of NetScout. Richard, welcome to theCube. >> Thanks for having me, Lisa, it's a pleasure to be here. >> We're going to unpack the sixth NetScout Threat Intelligence Report, which is going to be very interesting. But something I wanted to start with is we know that and yes, you're going to tell us, COVID and the pandemic has had a massive impact on DDoS attacks, ransomware. But before we dig into the report, I'd like to just kind of get some stories from you as we saw last year about this time rapid pivot to work from home, rapid pivot to distance learning. Talk to us about some of the attacks that you saw in particular that literally hit close to home. >> Sure and there's one really good prime example that comes to mind because it impacted a lot of people. There was a lot of media sensation around this but if you go and look, just Google it, Miami Dade County and DDoS, you'll see the first articles that pop up is the entire district school network going down because the students did not want to go to school and launched a DDoS attack. There was something upwards of 190,000 individuals that could no longer connect to the school's platform, whether that's a teacher, a student or parents. And so it had a very significant impact. And when you think about this in terms of the digital world, that impacted very severely, a large number of people and you can't really translate that to what would happen in a physical environment because it just doesn't compute. There's two totally different scenarios to talk about here. >> Amazing that a child can decide, "I don't want to go to school today." And as a result of a pandemic take that out for nearly 200,000 folks. So let's dig into, I said this is the sixth NetScout Threat Intelligence Report. One of the global trends and themes that is seen as evidence in what happened last year is up and to the right. Oftentimes when we're talking about technology, you know, with analyst reports up and to the right is a good thing. Not so in this case. We saw huge increases in threat vectors, more vectors weaponized per attack sophistication, expansion of threats and IOT devices. Walk us through the overall key findings from 2020 that this report discovered. >> Absolutely. And if yo glance at your screen there you'll see the key findings here where we talk about record breaking numbers. And just in 2020, we saw over 10 million attacks, which, I mean, this is a 20% increase over 2019. And what's significant about that number is COVID had a huge impact. In fact, if we go all the way back to the beginning, right around mid March, that's when the pandemic was announced, attacks skyrocketed and they didn't stop. They just kept going up and to the right. And that is true through 2021. So far in the first quarter, typically January, February is the down month that we observe in DDoS attacks. Whether this is, you know, kids going back to school from Christmas break, you have their Christmas routines and e-commerce is slowing down. January, February is typically a slow month. That was not true in 2021. In fact, we hit record numbers on a month by month in both January and February. And so not only do we see 2.9 million attacks in the first quarter of 2021, which, I mean, let's do the math here, right? We've got four quarters, you know, we're on track to hit 12 million attacks potentially, if not more. And then you have this normal where we said 800,000 approximately month over month since the pandemic started, we started 2021 at 950,000 plus. That's up and to the right and it's not slowing down. >> It's not slowing down. It's a trend that it shows, you know, significant impact across every industry. And we're going to talk about that but what are some of the new threat vectors that you saw weaponized in the last year? I mean, you talked about the example of the Miami-Dade school district but what were some of those new vectors that were really weaponized and used to help this up and to the right trend? >> So there's four in particular that we were tracking in 2020 and these nets aren't necessarily new vectors. Typically what happens when an adversary starts using this is there's a proof of concept code out there. In fact, a good example of this would be the RDP over UDP. So, I mean, we're all remotely connected, right? We're doing this over a Zoom call. If I want to connect to my organization I'm going to use some sort of remote capability whether that's a VPN or tunneling in, whatever it might be, right? And so remote desktop is something that everybody's using. And we saw actors start to kind of play around with this in mid 2020. And in right around September, November timeframe we saw a sudden spike. And typically when we see spikes in this kind of activity it's because adversaries are taking proof of concept code, that maybe has been around for a period of time, and they're incorporating those into DDoS for hire services. And so any person that wants to launch a DDoS attack can go into underground forums in marketplaces and they can purchase, maybe it's $10 in Bitcoin, and they can purchase an attack. That leverage is a bunch of different DDoS vectors. And so adversaries have no reason to remove a vector as new ones get discovered. They only have the motivation to add more, right? Because somebody comes into their platform and says, "I want to launch an attack that's going to take out my opponent." It's probably going to look a lot better if there's a lot of attack options in there where I can just go through and start clicking buttons left and right. And so all of a sudden now I've got this complex multi-vector attack that I don't have to pay anything extra for. Adversary already did all the work for me and now I can launch an attack. And so we saw four different vectors that were weaponized in 2020. One of those are notably the Jenkins that you see listed on the screen in the key findings. That one isn't necessarily a DDoS vector. It started out as one, it does amplify, but what happens is Jenkins servers are very vulnerable and when you actually initiate this attack, it tips over the Jenkins server. So it kind of operates as like a DoS event versus DDoS but it still has the same effect of availability, it takes a server offline. And then now just in the first part of 2021 we're tracking multiple other vectors that are starting to be weaponized. And when we see this, we go from a few, you know, incidents or alerts to thousands month over month. And so we're seeing even more vectors added and that's only going to continue to go up into the right. You know that theme that we talked about at the beginning here. >> As more vectors get added, and what did you see last year in terms of industries that may have been more vulnerable? As we talked about the work from home, everyone was dependent, really here we are on Zoom, dependent on Zoom, dependent on Netflix. Streaming media was kind of a lifeline for a lot of us but it also was healthcare and education. Did you see any verticals in particular that really started to see an increase in the exploitation and in the risk? >> Yeah, so let's start, let's separate this into two parts. The last part of the key findings that we had was talking about a group we, or a campaign we call Lazarus Borough Model. So this is a global DDoS extortion campaign. We're going to cover that a little bit more when we talk about kind of extorted events and how that operates but these guys, they started where the money is. And so when they first started targeting industries and this kind of coincides with COVID, so it started several months after the pandemic was announced, they started targeting a financial organizations, commercial banking. They went after stock exchange. Many of you would hear about the New Zealand Stock Exchange that went offline. That's this LBA campaign and these guys taking it off. So they started where the money is. They moved to a financial agation targeting insurance companies. They targeted currency exchange places. And then slowly from there, they started to expand. And in so much as our Arbor Cloud folks actually saw them targeting organizations that are part of vaccine development. And so these guys, they don't care who they hurt. They don't care who they're going after. They're going out there for a payday. And so that's one aspect of the industry targeting that we've seen. The other aspect is you'll see, on the next slide here, we actually saw a bunch of different verticals that we really haven't seen in the top 10 before. In fact, if you actually look at this you'll see the number one, two and three are pretty common for us. We almost always are going to see these kinds of telecommunications, wireless, satellite, broadband, these are always going to be in the top. And the reason for that is because gamers and DDoS attacks associated with gaming is kind of the predominant thing that we see in this landscape. And let's face it, gamers are on broadband operating systems. If you're in Asian communities, often they'll use mobile hotspots. So now you start to have wireless come in there. And so that makes sense seeing them. But what doesn't make sense is this internet publishing and broadcasting and you might say, "Well, what is that?" Well, that's things like Zoom and WebEx and Netflix and these other streaming services. And so we're seeing adversaries going after that because those have become critical to people's way of life. Their entertainment, what they're using to communicate for work and school. So they realized if we can go after this it's going to disrupt something and hopefully we can get some recognition. Maybe we can show this as a demonstration to get more customers on our platform or maybe we can get a payday. In a lot of the DDoS attacks that we see, in fact most of them, are all monetary focused. And so they're looking for a payday. They're going to go after something that's going to likely, you know, send out that payment. And then just walk down the line. You can see COVID through this whole thing. Electronic shopping is number five, right? Everybody turned to e-commerce because we're not going to in-person stores anymore. Electronic computer manufacturing, how many more people have to get computers at home now because they're no longer in a corporate environment? And so you can see how the pandemic has really influenced this industry target. >> Significant influencer and I also wonder too, you know, Zoom became a household name for every generation. You know, we're talking to five generations and maybe the generations that aren't as familiar with computer technology might be even more exploitable because it's easy to click on a phishing email when they don't understand how to look for the link. Let's now unpack the different types of DDoS attacks and what is on the rise. You talked about in the report the triple threat and we often think of that in entertainment. That's a good thing, but again, not here. Explain that triple threat. >> Yeah, so what we're seeing here is we have adversaries out there that are looking to take advantage of every possible angle to be able to get that payment. And everybody knows ransomware is a household name at this point, right? And so ransomware and DDoS have a lot in common because they both attack the availability of network resources, where computers or devices or whatever they might be. And so there's a lot of parallels to draw between the two of these. Now ransomware is a denial of service event, right? You're not going to have tens of thousands of computers hitting a single computer to take it down. You're going to have one exploitation of events. Somebody clicked on a link, there was a brute force attempt that managed to compromise a little boxes, credentials, whatever it might be, ransomware gets put on a system, it encrypts all your files. Well, all of a sudden, you've got this ransom note that says "If you want your files decrypted you're going to send us this amount of human Bitcoin." Well, what adversaries are doing now is they're capitalizing on the access that they already gained. So they already have access to the computer. Well, why not steal all the data first then let's encrypt whatever's there. And so now I can ask for a ransom payment to decrypt the files and I can ask for an extortion to prevent me from posting your data publicly. Maybe there's sensitive corporate information there. Maybe you're a local school system and you have all of your students' data on there. You're a hospital that has sensitive PI on it, whatever it might be, right? So now they're going to extort you to prevent them from posting that publicly. Well, why not add DDoS to this entire picture? Now you're already encrypted, we've already got your files, and I'm going to DDoS your system so you can't even access them if you wanted to. And I'm going to tell you, you have to pay me in order to stop this DDoS attack. And so this is that triple threat and we're seeing multiple different ransomware families. In fact, if you look at one of the slides here, you'll see that there's SunCrypt, there's Ragnar Cryptor, and then Maze did this initially back in September and then more recently, even the DarkSide stuff. I mean, who hasn't heard about DarkSide now with the Colonial Pipeline event, right? So they came out and said, "Hey we didn't intend for this collateral damage but it happened." Well, April 24th, they actually started offering DDoS as part of their tool kits. And so you can see how this has evolved over time. And adversaries are learning from each other and are incorporating this kind of methodology. And here we have triple extortion event. >> It almost seems like triple extortion event as a service with the opportunities, the number of vectors there. And you're right, everyone has heard of the Colonial Pipeline and that's where things like ransomware become a household term, just as much as Zoom and video conferencing and streaming media. Let's talk now about the effects that the threat report saw and uncovered region by region. Were there any regions in particular that were, that really stood out as most impacted? >> So not particularly. So one of the phenomena that we actually saw in the threat report, which, you know, we probably could have talked about it before now but it makes sense to talk about it regionally because we didn't see any one particular region, one particular vertical, a specific organization, specific country, none was more heavily targeted than another. In fact what we saw is organizations that we've never seen targeted before. We've seen industries that have never been targeted before all of a sudden are now getting DDoS attacks because we went from a local on-prem, I don't need to be connected to the internet, I don't need to have my employees remote access. And now all of a sudden you're dependent on the internet which is really, let's face it, that's critical infrastructure these days. And so now you have all of these additional people with a footprint connected to the internet then adversary can figure out and they can poke at it. And so what we saw here is just overall, all industries, all regions saw these upticks. The exception would be in China. We actually, in the Asia Pacific region specifically, but predominantly in China. But that often has to do with visibility rather than a decrease in attacks because they have their own kind of infrastructure in China. Brazil's the same way. They have their own kind of ecosystems. And so often you don't see what happens a lot outside the borders. And so from our perspective, we might see a decrease in attacks but, for all we know, they actually saw an increase in the attacks that is internal to their country against their country. And so across the board, just increases everywhere you look. >> Wow. So let's talk about what organizations can do in light of this. As we are here, we are still doing this program by video conferencing and things are opening up a little bit more, at least in the states anyway, and we're talking about more businesses going back to some degree but there's going to still be some mix, some hybrid of working from home and maybe even distance learning. So what can enterprises do to prepare for this when it happens? Because it sounds to me like with the sophistication, the up and to the right, it's not, if we get attacked, it's when. >> It's when, exactly. And that's just it. I mean, it's no longer something that you can put off. You can't just assume that I've never been DDoS attacked, I'm never going to be DDoS attacked anymore. You really need to consider this as part of your core security platform. I like to talk about defense in depth or a layer defense approach where you want to have a layered approach. So, you know, maybe they target your first layer and they don't get through. Or they do get through and now your second layer has to stop it. Well, if you have no layers or if you have one layer, it's not that hard for an adversary to figure out a way around that. And so preparation is key. Making sure that you have something in place and I'm going to give you an operational example here. One of the things we saw with the LBA campaigns is they actually started doing network of conasense for their targets. And what they would do is they would take the IP addresses belonging to your organization. They would look up the domains associated with that and they would figure out like, "Hey, this is bpn.organization.com or VPN two." And all of a sudden they've found your VPN concentrator and so that's where they're going to focus their attack. So something as simple as changing the way that you name your VPN concentrators might be sufficient to prevent them from hitting that weak link or right sizing the DDoS protection services for your company. Did you need something as big as like OnPrem Solutions? We need hardware. Do you instead want to do a managed service? Or do you want to go and talk to a cloud provider because there's right solutions and right sizes for all types of organizations. And the key here is preparation. In fact, all of the customers that we've worked with for the LBA extortion campaigns, if they were properly prepared they experienced almost no downtime or impact to their business. It's the people like the New Zealand Stock Exchange or their service provider that wasn't prepared to handle the attacks that were sent out them that were crippled. And so preparation is key. The other part is awareness. And that's part of what we do with this threat report because we want to make sure you're aware what adversaries are doing, when new attack vectors are coming out, how they're leveraging these, what industries they're targeting because that's really going to help you to figure out what your posture is, what your risk acceptance is for your organization. And in fact, there's a couple of resources that that we have here on the next slide. And you can go to both both of these. One of them is the threat report. You can view all of the details. And we only scratched the surface here in this Cube interview. So definitely recommend going there but the other one is called Horizon And netscout.com/horizon is a free resource you can register but you can actually see near real-time attacks based on industry and based on region. So if your organization out there and you're figuring, "Well I'm never attacked." Well go look up your industry. Go look up the country where you belong and see is there actually attacks against us? And I think you'll be quite surprised that there's quite a few attacks against you. And so definitely recommend checking these out >> Great resources netscout.com/horizon, netscout.com/threatreport. I do want to ask you one final question. That's in terms of timing. We saw the massive acceleration in digital transformation last year. We've already talked about this a number of times on this program. The dependence that businesses and consumers, like globally in every industry, in every country, have on streaming on communications right now. In terms of timing, though, for an organization to go from being aware to understanding what adversaries are doing, to being prepared, how quickly can an organization get up to speed and help themselves start reducing their risks? >> So I think that with DDoS, as opposed to things like ransomware, the ramp up time for that is much, much faster. There is a finite period of time with DDoS attacks that is actually going to impact you. And so maybe you're a smaller organization and you get DDoS attacked. There's a, probably a pretty high chance that that DDoS attack isn't going to last for multiple days. So maybe it's like an hour, maybe it's two hours, and then you recover. Your network resources are available again. That's not the same for something like ransomware. You get hit with ransomware, unless you pay or you have backups, you have to do the rigorous process of getting all your stuff back online. DDoS is more about as soon as the attack stops, the saturation goes away and you can start to get back online again. So it might not be as like immediate critical that you have to have something but there's also solutions, like a cloud solution, where it's as simple as signing up for the service and having your traffic redirected to their scrubbing center, their detection center. And then you may not have to do anything on-prem yourself, right? It's a matter of going out to an organization, finding a good contract, and then signing up, signing on the dotted line. And so I think that the ramp up time for mitigation services and DDoS protection can be a lot faster than many other security platforms and solutions. >> That's good to know cause with the up and to the right trend that you already said, the first quarter is usually slow. It's obviously not that way as what you've seen in 2021. And we can only expect what way, when we talk to you next year, that the up and to the right trend may continue. So hopefully organizations take advantage of these resources, Richard, that you talked about to be prepared to mediate and protect their you know, their customers, their employees, et cetera. Richard, we thank you for stopping by theCube. Talking to us about the sixth NetScout Threat Intelligence Report. Really interesting information. >> Absolutely; definitely a pleasure to have me here. Lisa, anytime you guys want to do it again, you know where I live? >> Yes. It's one of my favorite topics that you got and I got to point out the last thing, your Guardians of the Galaxy background, one of my favorite movies and it should be noted that on the NetScout website they are considered the Guardians of the Connected World. I just thought that connection was, as Richard told me before we went live, not planned, but I thought that was a great coincidence. Again, Richard, it's been a pleasure talking to you. Thank you for your time. >> Thank you so much. >> Richard Hummel, I'm Lisa Martin. You're watching this Cube conversation. (relaxing music)
SUMMARY :
Excited to talk to you. it's a pleasure to be here. that you saw in particular that that comes to mind because One of the global trends and themes And then you have this normal where and to the right trend? And so any person that wants that really started to see an increase In a lot of the DDoS attacks that we see, and maybe the generations that aren't And so there's a lot of parallels to draw effects that the threat report And so now you have all but there's going to still be some mix, and I'm going to give you to understanding what that is actually going to impact you. that the up and to the a pleasure to have me here. and I got to point out the last thing, You're watching this Cube conversation.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Richard | PERSON | 0.99+ |
Richard Hummel | PERSON | 0.99+ |
Lisa Martin | PERSON | 0.99+ |
two hours | QUANTITY | 0.99+ |
2020 | DATE | 0.99+ |
China | LOCATION | 0.99+ |
$10 | QUANTITY | 0.99+ |
New Zealand Stock Exchange | ORGANIZATION | 0.99+ |
April 24th | DATE | 0.99+ |
New Zealand Stock Exchange | ORGANIZATION | 0.99+ |
20% | QUANTITY | 0.99+ |
September | DATE | 0.99+ |
two | QUANTITY | 0.99+ |
2021 | DATE | 0.99+ |
July 2021 | DATE | 0.99+ |
Lisa | PERSON | 0.99+ |
second layer | QUANTITY | 0.99+ |
last year | DATE | 0.99+ |
mid 2020 | DATE | 0.99+ |
Guardians of the Galaxy | TITLE | 0.99+ |
February | DATE | 0.99+ |
NetScout | ORGANIZATION | 0.99+ |
first layer | QUANTITY | 0.99+ |
January | DATE | 0.99+ |
bpn.organization.com | OTHER | 0.99+ |
next year | DATE | 0.99+ |
one layer | QUANTITY | 0.99+ |
800,000 | QUANTITY | 0.99+ |
last year | DATE | 0.99+ |
12 million attacks | QUANTITY | 0.99+ |
both | QUANTITY | 0.99+ |
Colonial Pipeline | EVENT | 0.99+ |
190,000 individuals | QUANTITY | 0.99+ |
four | QUANTITY | 0.99+ |
an hour | QUANTITY | 0.99+ |
One | QUANTITY | 0.99+ |
netscout.com/horizon | OTHER | 0.99+ |
first articles | QUANTITY | 0.99+ |
Netflix | ORGANIZATION | 0.99+ |
Guardians of the Connected World | TITLE | 0.99+ |
Zoom | ORGANIZATION | 0.99+ |
one | QUANTITY | 0.99+ |
one final question | QUANTITY | 0.99+ |
two parts | QUANTITY | 0.98+ |
2.9 million attacks | QUANTITY | 0.98+ |
over 10 million attacks | QUANTITY | 0.98+ |
Arbor Networks | ORGANIZATION | 0.98+ |
one aspect | QUANTITY | 0.98+ |
pandemic | EVENT | 0.98+ |
2019 | DATE | 0.98+ |
five generations | QUANTITY | 0.97+ |
three | QUANTITY | 0.97+ |
tens of thousands | QUANTITY | 0.97+ |
first | QUANTITY | 0.96+ |
Ragnar Cryptor | PERSON | 0.96+ |
first quarter of 2021 | DATE | 0.96+ |
four quarters | QUANTITY | 0.95+ |
ORGANIZATION | 0.95+ | |
nearly 200,000 folks | QUANTITY | 0.95+ |
Stephen Chin, JFrog | DockerCon 2021
>>Hello and welcome back to the cubes coverage of dr khan 2021. I'm john for your host of the cube. Great guests here cube alumni Stephen Chin, vice president of developer relations for jay frog Stephen, great to see you again this remote this time this last time was in person. Our last physical event. We had you in the queue but great to see you. Thanks for coming in remotely. >>No, no, I'm very glad to be here. And also it was, it was awesome to be in person at our s a conference when we last talked and the last year has been super exciting with a whole bunch of crazy things like the I. P. O. And doing virtual events. So we've, we're transitioning to the new normal. We're looking forward to things getting to be hybrid. >>Great success with jay frog. We've been documenting the history of this company, very developer focused the successful I. P. O. And just the continuation that you guys have transitioned beautifully to virtual because you know, developer company, it runs virtual, but also you guys have been all about simplicity for developers and and we've been talking for many, many years with you guys on this. This is the theme that dr khan again, this is a developer conference, not so much an operator conference, but more of a deva deV developer focused. You guys have been there from the beginning, um nationally reported on it. But talk about jay Frog and the Doctor partnership and why is this event so important for you? >>Yeah. So I think um like like you said, jay Frog has and always is a developer focused company. So we we build tools and things which which focus on developer use cases, how you get your code to production and streamlining the entire devoPS pipeline. And one of the things which which we believe very strongly in and I think we're very aligned with with doctor on this is having secure clean upstream dependencies for your Docker images for other package and language dependencies and um you know, with the announcement of dr khan and dr Hubbs model changing, we wanted to make sure that we have the best integration with doctor and also the best support for our customers on with Docker hub. So one of the things we did strategically is um, we um combined our platforms so um you can get the best in class developer tools for managing images from Docker. Um everyone uses their um desktop tools for for building and managing your containers and then you can push them right to the best container registry for managing Docker Images, which is the jay frog platform. And just like Docker has free tools available for developers to use. We have a free tier which integrates nicely what their offerings and one of the things which we collaborate with them on is for anybody using our free tier in the cloud. Um there's there's no limits on the Docker images. You can pull no rate limiting, no throttling. So it just makes a clean seamless developer experience to to manage your cloud native projects and applications. >>What's the role of the container registry in cloud NATO? You brought that up? But can you just expand on that point? >>Yeah. So I think when you when you're doing deployments to production, you want to make sure both that you have the best security so that you're making sure that you're scanning and checking for vulnerabilities in your application and also that you have a complete um traceability. Basically you need a database in a log of everything you're pushing out to production. So what container registries allow you to do is um they keep all of the um releases all of the Docker images which are pushing out. You can go back and roll back to a previous version. You can see exactly what's included in those Docker images. And we jay frog, we have a product called X ray which does deep scanning of container images. So it'll go into the Docker Image, it'll go into any packages installed, it'll go into application libraries and it does kind of this onion peel apart of your entire document image to figure out exactly what you're using. Are there any vulnerabilities? And the funny thing about about Docker Images is um because of the number of libraries and packages and installed things which you haven't given Docker Image. If you just take your released Docker Image and let it sit on the shelf for a month, you have thousands of vulnerabilities, just just buy it um, by accruing from different reported zero day vulnerabilities over time. So it's extremely important that you, you know what those are, you can evaluate the risk to your organization and then mitigated as quickly as possible. If there is anything which could impact your customers, >>you bring up a great point right there and that is ultimately a developer thing that's been, that's generational, you know what generation you come from and that's always the problem getting the patches in the old days, getting a new code updated now when you have cloud native, that's more important than ever. And I also want to get your thoughts on this because you guys have been early on shift left two years ago, shift left was not it was not a new thing for you guys ever. So you got shift left building security at the point of coding, but you're bringing up a whole another thing which is okay automation. How do you make it? So the developments nothing stop what they're doing and then get back and say, okay, what's out there and my containers. So so how do you simplify that role? Because that's where the partnership, I think really people are looking to you guys and Dakar on is how do you make my life easier? Bottom line, what's it, what's it, what's it about? >>Yeah. So I I think when you when you're looking at trying to manage um large applications which are deployed to big kubernetes clusters and and how you have kind of this, this um all this infrastructure behind it. One of the one of the challenges is how do you know what you have that in production? Um So what, how do you know exactly what's released and what dependencies are out there and how easily can you trace those back? Um And one of the things which we're gonna be talking about at um swamp up next week is managing the overall devops lifecycle from code all the way through to production. Um And we we have a great platform for doing package management for doing vulnerability scanning, for doing um ci cd but you you need a bunch of other tools too. So you need um integrations like docker so you can get trusted packages into your system. You need integrations with observe ability tools like data, dog, elastic and you need it some tools for doing incident management like Patriot duty. And what we've, what we've built out um is we built out an ecosystem of partner integrations which with the J frog platform at the center lets you manage your entire and and life cycle of um devops infrastructure. And this this addresses security. It addresses the need to do quick patches and fixes and production and it kind of stitches together all the tools which all of the successful companies are using to manage their fast moving continuous release cycle, um and puts all that information together with seamless integration with even developer tools which um which folks are using on a day to day basis, like slack jeer A and M. S. Teams. >>So the bottom line then for the developer is you take the best of breed stuff and put it, make it all work together easily. That right? >>Yeah. I mean it's like it's seamless from you. You've got an incidents, you click a button, it sticks Ajira ticket in for you to resolve. Um you can tie that with the code, commits what you're doing and then directly to the security vulnerability which is reported by X ray. So it stitches all these different tools and technologies together for a for a seamless developer experience. And I think the great relationship we have with Docker um offers developers again, this this best in class container management um and trusted images combined with the world's best container registry. >>Awesome. Well let's get into that container issue products. I think that's the fascinating and super important thing that you guys solve a big problem for. So I gotta ask you, what are the security risks of using unverified and outdated Docker containers? Could you share your thoughts on what people should pay attention to because if they got unverified and outdated Docker containers, you mentioned vulnerabilities. What are those specific risks to them? >>Yeah, so I there's there's a lot of um different instances where you can see in the news or even some of the new government mandates coming out that um if you're not taking the right measures to secure your production applications and to patch critical vulnerabilities and libraries you're using, um you end up with um supply chain vulnerability risks like what happened to solar winds and what's been fueling the recent government mandates. So I think there's a there's a whole class of of different vulnerabilities which um bad actors can exploit. It can actually go quite deep with um folks um exploiting application software. Neither your your company or in other people's systems with with the move to cloud native, we also have heavily interconnected systems with a lot of different attack points from the container to the application level to the operating system level. So there's multiple different attack vectors for people to get into your software. And the best defense is an organization against security. Vulnerabilities is to know about them quickly and to mitigate them and fix them in production as quickly as possible. And this requires having a fast continuous deployment strategy for how you can update your code quickly, very quick identification of vulnerabilities with tools like X ray and other security scanning tools, um and just just good um integration with tools developers are using because at the end of the day it's the developers who both are picking the libraries and dependencies which are gonna be pushed into production and also they're the ones who have to react and and fix it when there's a uh production incident, >>you know, machine learning and automation. And it's always, I love that tech because it's always kind of cool because it's it's devops in action, but you know, it's it's not like a silver bullet, your machine, your machine learning is only as good as your your data and the code is written on staying with automation. You're not automating the right things or or wrong things. It's all it's all subjective based on what you're doing and you know Beauty's in the eye of the beholder when you do things like that. So I wanna hear your thoughts on on automation because that's really been a big part of the story here, both on simplicity and making the load lighter for developers. So when you have to go out and look at modifying code updates and looking at say um unverified containers or one that gets a little bit of a hair on it with with with more updates that are needed as we say, what do you what's the role of automation? How do you guys view that and how do you talk to the developers out there when posturing for a strategy on and a playbook for automation? >>Yeah, I think you're you're touching on one of the most critical parts of of any good devops um platform is from end to end. Everything should be automated with the right quality gates inserted at different points so that if there's a um test failure, if you have a build failure, if you have a security vulnerability, the the automatic um points in there will be triggered so that your release process will be stopped um that you have automated rollbacks in production um so that you can make sure that their issues which affect your customers, you can quickly roll back and once you get into production um having the right tools for observe ability so that you can actually sift through what is a essentially a big data problem. So with large systems you get so much data coming back from your application, from the production systems, from all these different sources that even an easy way to sift through and identify what are the messages coming back telling you that there's a problem that there's a real issue that you need to address versus what's just background noise about different different processes or different application alerts, which really don't affect the security of the functionality of your applications. So I think this this end to end automation gives you the visibility and the single pane of glass to to know how to manage and diagnose your devops infrastructure. >>You know, steve you bring up a great point. I love this conversation because it always highlights to me why I love uh Coop Con and Cloud Native con part of the C N C F and dr khan, because to me it's like a microcosm of two worlds that are living together. Right? You got I think Coop khan has proven its more operated but not like operator operator, developer operators. And you got dr khan almost pure software development, but now becoming operators. So you've got that almost those two worlds are fusing together where they are running together. You have operating concerns like well the Parachute open, will it work? And how do I roll back these roll back? These are like operating questions that now developers got to think about. So I think we're seeing this kind of confluence of true devops next level where you can't you can be just a developer and have a little bit of opposite you and not be a problem. Right? Or or get down under the under the hood and be an operator whenever you want. So they're seeing a flex. What's your thoughts on this is just more about my observation kind of real time here? >>Yeah, so um I think it's an interesting, obviously observation on the industry and I think you know, I've been doing DEVOPS for for a long time now and um I started as a developer who needed to push to production, needed to have the ability to to manage releases and packages and be able to automate everything. Um and this naturally leads you on a path of doing more operations, being able to manage your production, being able to have fewer incidents and issues. Um I think DEVOPS has evolved to become a very complicated um set of tools and problems which it solves and even kubernetes as an example. Um It's not easy to set up like setting up a kubernetes cluster and managing, it is a full time job now that said, I think what you're seeing now is more and more companies are shifting back to developers as a focus because teams and developers are the kingmakers ends with the rise of cloud computing, you don't need a full operations team, you don't need a huge infrastructure stack, you can you can easily get set up in the cloud on on amazon google or as your and start deploying today to production from from a small team straight from code to production. And I think as we evolve and as we get better tools, simpler ways of managing your deployments of managing your packages, this makes it possible for um development teams to do that entire site lifecycle from code through to production with good quality checks with um good security and also with the ability to manage simple production incidents all by themselves. So I think that's that's coming where devoPS is shifting back to development teams. >>It's great to have your leadership and your experience. All right there. That's a great call out, great observation, nice gym there. I think that's right on. I think to get your thoughts if you don't mind going next level because you're, you're nailing what I see is the successful companies having these teams that could be and and workflows and have a mix of a team. I was talking about Dana Lawson who was the VP of engineering get up and she and I were riffing on this idea that you don't have to have a monolithic team because you've got you no longer have a monolithic environment. So you have this microservices and now you can have these, I'm gonna call micro teams, but you're starting to see an SRE on the team, that's the developer. Right? So this idea of having an SRE department maybe for big companies, that could be cool if you're hyper scalar, but these development teams are having certain formations. What's your observation to your customer base in terms of how your customers are organizing? Because I think you nailed the success form of how teams are executing because it's so much more agile, you get the reliability, you need to have security baked in, you want end to end visibility because you got services starting and stopping. How are teams? How are you seeing developers? What's the state of the art in your mind for formation? >>Yeah, so I think um we we work with a lot of the biggest companies who were really at the bleeding edge of innovation and devoPS and continuous delivery. And when you look at those teams, they have, they have very, very small teams, um supporting thousands of developers teams um building and deploying applications. So um when you think of of SRE and deVOPS focus there is actually a very small number of those folks who typically support humongous organizations and I think what we're hearing from them is their increasingly getting requirements from the teams who want to be self service, right? They want to be able to take their applications, have simple platforms to deploy it themselves to manage things. Um They don't they don't want to go through heavy way processes, they wanted to be automated and lightweight and I think this is this is putting pressure on deVOPS teams to to evolve and to adopt more platforms and services which allow developers to to do things themselves. And I think over time um this doesn't this doesn't get rid of the need for for devops and for SRE roles and organizations but it it changes because now they become the enablers of success and good development teams. It's it's kind of like um like how I. T. Organizations they support you with automated rollouts with all these tools rather than in person as much as they can do with automation. Um That helps the entire organization. I think devops is becoming the same thing where they're now simplifying and automating how developers can be self service and organizations. >>And I think it's a great evolution to because that makes total sense because it is kind of like what the I. T. Used to do in the old days but its the scale is different, the services are different, the deVOPS tools are different and so they really are enabling not just the cost center there really driving value. Um and this brings up the whole next threat. I'd love to get your thoughts because you guys are, have been doing this for developers for a while. Tools versus platform because you know, this whole platform where we're a platform were control plane, there's still a need for tooling for developers. How do we thread the needle between? What's, what's good for a tool? What's good for a platform? >>Yeah, So I I think that um, you know, there's always a lot of focus and it's, it's easier if you can take an end to end platform, which solves a bunch of different use cases together. But um, I I think a lot of folks, um, when you're looking at what you need and how you want to apply, um, devops practices to your organization, you ideally you want to be able to use best in breed tools to be able to solve exactly what your use cases. And this is one of the reasons why as a company with jay frog, we we try to be as open as possible to integrations with the entire vendor ecosystem. So um, it doesn't matter what ci cd tool you're using, you could be using Jenkins circle, ci spinnaker checked on, it doesn't matter what observe ability platform you're using in production, it doesn't matter what um tools you're using for collaboration. We, we support that whole ecosystem and we make it possible for you to select the the best of breed tools and technologies that you need to be successful as an organization. And I think the risk is if, if you, if you kind of accept vendor lock in on a single platform or or a single cloud platform even um then you're, you're not getting the best in breed tools and technologies which you need to stay ahead of the curve and devops is a very, very fast moving um, um, discipline along with all the cloud native technologies which you use for application development and for production. So if you're, if you're not staying at the bleeding edge and kind of pushing things forward, then you're then you're behind and if you're behind, you're not be able to keep up with the releases, the deployments, you need to be secure. So I think what you see is the leading organizations are pushing the envelope on on security, on deployment and they're they're using the best tools in the industry to make that happen. >>Stephen great to have you on the cube. I want to just get your thoughts on jay frog and the doctor partnership to wrap this up. Could you take them in to explain what's the most important thing that developers should pay attention to when it comes to security for Docker images? >>Yeah. So I think when you're when you're developer and you're looking at your your security strategy, um you want tools that help you that come to you and that help you. So you want things which are going to give you alerts in your I. D. With things which are going to trigger your in your Ci cd and your build process. And we should make it easy for you to identify mitigate and release um things which will help you do that. So we we provide a lot of those tools with jay frog and our doctor partnership. And I think if you if you look at our push towards helping developers to become more productive, build better applications and more secure applications, this is something the entire industry needs for us to address. What's increasingly a risk to software development, which is a higher profile vulnerabilities, which are affecting the entire industry. >>Great stuff. Big fan of jay frog watching you guys be so successful, you know, making things easy for developers is uh, and simpler and reducing the steps it takes to do things as a, I say, is the classic magic formula for any company, Make it easier, reduce the steps it takes to do something and make it simple. Um, good success formula. Great stuff. Great to have you on um for a minute or two, take a minute to plug what's going on in jay frog and share what's the latest increase with the company, what you guys are doing? Obviously public company. Great place to work, getting awards for that. Give the update on jay frog, put a plug in. >>Yeah. And also dr Frog, I've been having a lot of fun working at J frog, it's very, very fast growing. We have a lot of awesome announcements at swamp up. Um like the partnerships were doing um secure release bundles for deployments and just just a range of advances. I think the number of new features and innovation we put into the product in the past six months since I. P. O. Is astounding. So we're really trying to push the edge on devops um and we're also gonna be announcing and talking about stuff that dr khan as well and continue to invest in the cloud native and the devops ecosystem with our support of the continuous delivery foundation and the C. N C F, which I'm also heavily involved in. So it's it's exciting time to be in the devoPS industry and I think you can see that we're really helping software developers to improve their art to become better, better at release. Again, managing production applications >>and the ecosystem is just flourishing. It's only the beginning and again Making bring the craft back in Agile, which is a super big theme this year. Stephen. Great, great to see you. Thanks for dropping those gems and insights here on the Cube here at Dr. 2021 virtual. Thanks for coming on. >>Yeah. Thank you john. >>Okay. Dr. 2020 coverage virtual. I'm John for your host of the Cube. Thanks for watching. Mhm. Mhm. Yeah.
SUMMARY :
great to see you again this remote this time this last time was in person. We're looking forward to things getting to be hybrid. successful I. P. O. And just the continuation that you guys have transitioned beautifully to virtual because you know, and language dependencies and um you know, with the announcement of dr khan and because of the number of libraries and packages and installed things which you haven't given Docker Image. So you got shift left building So you need um integrations like docker so you can get trusted packages into your system. So the bottom line then for the developer is you take the best of breed stuff and put And I think the great relationship we have with Docker um offers developers again, Could you share your thoughts on what people should pay attention to because if they got unverified and outdated Yeah, so I there's there's a lot of um different instances where you can see So when you have to go out and look at modifying code updates and looking at say So I think this this end to end automation gives you the visibility and the single the hood and be an operator whenever you want. and I think you know, I've been doing DEVOPS for for a long time now and um So you have this microservices and now you can have these, I'm gonna call micro teams, So um when you think of of SRE and deVOPS focus there is actually a And I think it's a great evolution to because that makes total sense because it is kind of like what the I. So I think what you see is the leading organizations are Stephen great to have you on the cube. So you want things which are going to give you alerts in your I. D. With things which are going to trigger and share what's the latest increase with the company, what you guys are doing? and I think you can see that we're really helping software developers to improve their bring the craft back in Agile, which is a super big theme this year. I'm John for your host of the Cube.
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Dana Lawson | PERSON | 0.99+ |
Stephen Chin | PERSON | 0.99+ |
John | PERSON | 0.99+ |
one | QUANTITY | 0.99+ |
Stephen | PERSON | 0.99+ |
a minute | QUANTITY | 0.99+ |
last year | DATE | 0.99+ |
thousands | QUANTITY | 0.99+ |
two | QUANTITY | 0.99+ |
J frog | ORGANIZATION | 0.99+ |
next week | DATE | 0.99+ |
zero day | QUANTITY | 0.99+ |
both | QUANTITY | 0.99+ |
two worlds | QUANTITY | 0.98+ |
john | PERSON | 0.98+ |
amazon | ORGANIZATION | 0.98+ |
jay frog | ORGANIZATION | 0.98+ |
two years ago | DATE | 0.98+ |
One | QUANTITY | 0.97+ |
single platform | QUANTITY | 0.97+ |
dr Hubbs | PERSON | 0.97+ |
X ray | ORGANIZATION | 0.97+ |
dr khan | PERSON | 0.96+ |
Docker Image | TITLE | 0.95+ |
single | QUANTITY | 0.94+ |
jay | ORGANIZATION | 0.94+ |
a month | QUANTITY | 0.94+ |
today | DATE | 0.92+ |
Coop khan | ORGANIZATION | 0.92+ |
I. P. O. | EVENT | 0.92+ |
Docker | TITLE | 0.92+ |
JFrog | PERSON | 0.91+ |
Patriot | TITLE | 0.91+ |
this year | DATE | 0.91+ |
Agile | TITLE | 0.9+ |
Docker | ORGANIZATION | 0.9+ |
past six months | DATE | 0.89+ |
single cloud platform | QUANTITY | 0.86+ |
Parachute | TITLE | 0.85+ |
developers | QUANTITY | 0.8+ |
thousands of vulnerabilities | QUANTITY | 0.79+ |
C N C F | TITLE | 0.77+ |
X ray | TITLE | 0.75+ |
Jenkins | TITLE | 0.75+ |
DockerCon 2021 | EVENT | 0.74+ |
Dakar | ORGANIZATION | 0.72+ |
M. S. Teams | ORGANIZATION | 0.71+ |
Ajira | TITLE | 0.71+ |
NATO | ORGANIZATION | 0.71+ |
Cube | COMMERCIAL_ITEM | 0.71+ |
jay Frog | PERSON | 0.71+ |
slack | TITLE | 0.69+ |
Coop Con | ORGANIZATION | 0.66+ |
SRE | TITLE | 0.66+ |
frog | PERSON | 0.63+ |
jay Frog | ORGANIZATION | 0.63+ |
dr | PERSON | 0.62+ |
Dr. | TITLE | 0.6+ |
Frog | PERSON | 0.59+ |
N C F | ORGANIZATION | 0.57+ |
I. P. | EVENT | 0.56+ |
Cloud Native con | ORGANIZATION | 0.54+ |
2021 | DATE | 0.52+ |
ORGANIZATION | 0.51+ | |
2021 | EVENT | 0.49+ |
LIVE Panel: FutureOps: End-to-end GitOps
>>and hello, we're back. I've got my panel and we are doing things real time here. So sorry for the delay a few minutes late. So the way let's talk about things, the reason we're here and we're going around the room and introduce everybody. Got three special guests here. I got my evil or my john and the normal And we're going to talk about get ops I called it future office just because I want to think about what's the next thing for that at the end, we're gonna talk about what our ideas for what's next for getups, right? Um, because we're all starting to just get into get ups now. But of course a lot of us are always thinking about what's next? What's better? How can we make this thing better? So we're going to take your questions. That's the reason we're here, is to take your questions and answer them. Or at least the best we can for the next hour. And all right, so let's go around the room and introduce yourself. My name is Brett. I am streaming from Brett from that. From Brett. From Virginia Beach in Virginia beach, Virginia, United States. Um, and I talk about things on the internet, I sell courses on you, to me that talk about Docker and kubernetes Ive or introduce yourself. >>How's it going? Everyone, I'm a software engineer at axel Springer, currently based in Berlin and I happen to be Brett Brett's teaching assistant. >>All right, that's right. We're in, we're in our courses together almost every day. Mm john >>hey everyone, my name is john Harris, I used to work at Dhaka um, I now work at VM ware is a star field engineer. Um, so yeah, >>and normal >>awesome by the way, you are streaming from Brett Brett, >>I answered from breath to breath. >>Um I'm normal method. I'm a distinguished engineer with booz allen and I'm also a doctor captain and it's good to see either in person and it's good to see you again john it's been a little while. >>It has the pre covid times, right? You're up here in Seattle. >>Yeah. It feels, it feels like an eternity ago. >>Yeah, john shirt looks red and reminds me of the Austin T shirt. So I was like, yeah, so we all, we all have like this old limited edition doctor on E. >>T. That's a, that's a classic. >>Yeah, I scored that one last year. Sometimes with these old conference church, you have to like go into people's closets. I'm not saying I did that. Um, but you know, you have to go steal stuff, you to find ways to get the swag >>post post covid. If you ever come to my place, I'm going to have to lock the closets. That >>that's right, That's right. >>So the second I think it was the second floor of the doctor HQ in SAn Francisco was where they kept all the T shirts, just boxes and boxes and boxes floor to ceiling. So every time I went to HQ you just you just as many as you can fit in your luggage. I think I have about 10 of these. You >>bring an extra piece of luggage just for your your shirt shirt grab. Um All right, so I'm going to start scanning questions uh so that you don't have to you can you help you all are welcome to do that. And I'm going to start us off with the topic. Um So let's just define the parameters. Like we can talk about anything devops and here we can go down and plenty of rabbit holes. But the kind of, the goal here is to talk about get ups and get ups if you haven't heard about it is essentially uh using versioning systems like get like we've all been getting used to as developers to track your infrastructure changes, not just your code changes and then automate that with a bunch of tooling so that the robots take over. And essentially you have get as a central source of truth and then get log as a central source of history and then there's a bunch of magic little bits in the middle and then supposedly everything is wonderful. It's all automatic. The reality is is what it's often quite messy, quite tricky to get everything working. And uh the edges of this are not perfect. Um so it is a relatively new thing. It's probably three, maybe four years old as an official thing from. We've uh so we're gonna get into it and I'll let's go around the room and the same word we did before and um not to push on that, put you on the spot or anything. But what is, what is one of the things you either like or either hate about getups um that you've enjoyed either using it or you know, whatever for me. I really, I really love that I can point people to a repo that basically is hopefully if they look at the log a tracking, simplistic tracking of what might have changed in that part of the world or the environment. I remember many years past where, you know, I've had executive or some mid level manager wants to see what the changes were or someone outside my team went to see what we just changed. It was okay, they need access to this system into that dashboard and that spreadsheet and then this thing and it was always so complicated and now in a world where if we're using get up orbit bucket or whatever where you can just say, hey go look at that repo if there was three commits today, probably three changes happened. That's I love that particular part about it. Of course it's always more complicated than that. But um Ive or I know you've been getting into this stuff recently. So um any thoughts? Yeah, I think >>my favorite part about get ops is >>reproducibility. Um >>you know the ability to just test something and get it up and running >>and then just tear it down. >>Uh not >>being worried that how did I configure it the first time? I think that's my favorite part about >>it. I'm changing your background as we do this. >>I was going to say, did you just do it get ups pushed to like change his >>background, just a dialogue that different for that green screen equals false? Uh Change the background. Yeah, I mean, um and I mean I think last year was really my first year of actually using it on anything significant, like a real project. Um so I'm still, I still feel like I'm very new to john you anything. >>Yeah, it's weird getups is that thing which kind of crystallizes maybe better than anything else, the grizzled veteran life cycle of emotions with the technology because I think it's easy to get super excited about something new. And when I first looked into get up, so I think this is even before it was probably called getups, we were looking at like how to use guest source of truth, like everything sounds great, right? You're like, wait, get everyone knows, get gets the source of truth, There's a load of robust tooling. This just makes a sense. If everything dies, we can just apply the get again, that would be great. Um and then you go through like the trough of despair, right? We're like, oh no, none of this works. The application is super stateless if this doesn't work and what do we do with secrets and how do we do this? Like how do we get people access in the right place and then you realize everything is terrible again and then everything it equalizes and you're kind of, I think, you know, it sounds great on paper and they were absolutely fantastic things about it, but I think just having that measured approach to it, like it's, you know, I think when you put it best in the beginning where you do a and then there's a magic and then you get C. Right, like it's the magic, which is >>the magic is the mystery, >>right? >>Magic can be good and bad and in text so >>very much so yeah, so um concurrence with with john and ever uh in terms of what I like about it is the potential to apply it to moving security to left and getting closer to a more stable infrastructures code with respect to the whole entire environment. Um And uh and that reconciliation loop, it reminds me of what, what is old is new again? Right? Well, quote unquote old um in terms of like chef and puppet and that the reconciliation loop applied in a in a more uh in a cleaner interface and and into the infrastructure that we're kind of used to already, once you start really digging into kubernetes what I don't like and just this is in concurrence with the other Panelist is it's relatively new. It has um, so it has a learning curve and it's still being, you know, it's a very active um environment and community and that means that things are changing and constantly and there's like new ways and new patterns as people are exploring how to use it. And I think that trough of despair is typically figuring out incrementally what it actually is doing for you and what it's not going to solve for you, right, john, so like that's that trough of despair for a bit and then you realize, okay, this is where it fits potentially in my architecture and like anything, you have to make that trade off and you have to make that decision and accept the trade offs for that. But I think it has a lot of promise for, for compliance and security and all that good stuff. >>Yeah. It's like it's like the potentials, there's still a lot more potential than there is uh reality right now. I think it's like I feel like we're very early days and the idea of especially when you start getting into tooling that doesn't appreciate getups like you're using to get up to and use something else and that tool has no awareness of the concept so it doesn't flow well with all of the things you're trying to do and get um uh things that aren't state based and all that. So this is going to lead me to our first question from Camden asking dumb questions by the way. No dumb questions here. Um How is get apps? Not just another name for C. D. Anybody want to take that as an answer as a question. How is get up is not just another name for C. D. I have things but we can talk about it. I >>feel like we need victor foster kids. Yeah, sure you would have opinions. Yeah, >>I think it's a very yeah. One person replied said it's a very specific it's an opinionated version of cd. That's a great that's a great answer like that. Yeah. >>It's like an implement. Its it's an implementation of deployment if you want it if you want to use it for that. All right. I realize now it's kind of hard in terms of a physical panel and a virtual panel to figure out who on the panel is gonna, you know, ready to jump in to answer a question. But I'll take it. So um I'll um I'll do my best inner victor and say, you know, it's it's an implementation of C. D. And it's it's a choice right? It's one can just still do docker build and darker pushes and doctor pulls and that's fine. Or use other technologies to deploy containers and pods and change your, your kubernetes infrastructure. But get apps is a different implementation, a different method of doing that same thing at the end of the day. Yeah, >>I like it. I like >>it and I think that goes back to your point about, you know, it's kind of early days still, I think to me what I like about getups in that respect is it's nice to see kubernetes become a platform where people are experimenting with different ways of doing things, right? And so I think that encourages like lots of different patterns and overall that's going to be a good thing for the community because then more, you know, and not everything needs to settle in terms of only one way of doing things, but a lot of different ways of doing things helps people fit, you know, the tooling to their needs, or helps fit kubernetes to their needs, etcetera. Yeah, >>um I agree with that, the, so I'm gonna, since we're getting a load of good questions, so um one of the, one of the, one of the, I want to add to that real quick that one of the uh from the, we've people themselves, because I've had some on the show and one of things that I look at it is distinguishing is with continuous deployment tools, I sort of think that it's almost like previous generation and uh continuous deployment tools can be anything like we would consider Jenkins cd, right, if you if you had an association to a server and do a doctor pull and you know, dr up or dr composed up rather, or if it did a cube control apply uh from you know inside an ssh tunnel or something like that was considered considered C. D. Well get ops is much more rigid I think in terms of um you you need to apply, you have a specific repo that's all about your deployments and because of what tool you're using and that one your commit to a specific repo or in a specific branch that repo depends on how you're setting it up. That is what kicks off a workflow. And then secondly there's an understanding of state. So a lot of these tools now I have uh reconciliation where they they look at the cluster and if things are changing they will actually go back and to get and the robots will take over and will commit that. Hey this thing has changed um and you maybe you human didn't change it, something else might have changed it. So I think that's where getups is approaching it, is that ah we we need to we need to consider more than just a couple of commands that be runnin in a script. Like there needs to be more than that for a getups repo to happen anyway, that's just kind of the the take back to take away I took from a previous conversation with some people um >>we've I don't think that lost, its the last piece is really important, right? I think like for me, C d like Ci cd, they're more philosophical ideas, write a set of principles, right? Like getting an idea or a code change to environments promoting it. It's very kind of pipeline driven um and it's very imperative driven, right? Like our existing CD tools are a lot of the ways that people think about Cd, it would be triggered by an event, maybe a code push and then these other things are happening in sequence until they either fail or pass, right? And then we're done. Getups is very much sitting on the, you know, the reconciliation side, it's changing to a pull based model of reconciliation, right? Like it's very declarative, it's just looking at the state and it's automatically pulling changes when they happen, rather than this imperative trigger driven model. That's not to say that there aren't city tools which we're doing pull based or you can do pull based or get ups is doing anything creatively revolutionary here, but I think that's one of the main things that the ideas that are being introduced into those, like existing C kind of tools and pipelines, um certainly the pull based model and the reconciliation model, which, you know, has a lot in common with kubernetes and how those kind of controllers work, but I think that's the key idea. Yeah. >>Um This is a pretty specific one Tory asks, does anyone have opinions about get ops in a mono repo this is like this is getting into religion a little bit. How many repos are too many repose? How um any thoughts on that? Anyone before I rant, >>go >>for it, go for it? >>Yeah. How I'm using it right now in a monitor repo uh So I'm using GIT hub. Right, so you have what? The workflow and then inside a workflow? Yeah, mo file, I'll >>track the >>actual changes to the workflow itself, as well as a folder, which is basically some sort of service in Amman Arepa, so if any of those things changes, it'll trigger the actual pipeline to run. So that's like the simplest thing that I could figure out how to, you know, get it set up using um get hubs, uh workflow path future. Yeah. And it's worked for me for writing, you know? That's Yeah. >>Yeah, the a lot of these things too, like the mono repo discussion will, it's very tool specific. Each tool has various levels of support for branch branching and different repos and subdirectories are are looking at the defense and to see if there's changes in that specific directory. Yeah. Sorry, um john you're going to say something, >>I was just going to say, I've never really done it, but I imagine the same kind of downsides of mono repo to multiple report would exist there. I mean, you've got the blast radius issues, you've got, you know, how big is the mono repo? Do we have to pull does the tool have to pull that or cashier every time it needs to determine def so what is the support for being able to just look at directories versus you know, I think we can get way down into a deeper conversation. Maybe we'll save it for later on in the conversation about what we're doing. Get up, how do we structure our get reposed? We have super granular repo per environment, Perper out reaper, per cluster repo per whatever or do we have directories per environment or branches per environment? How how is everything organized? I think it's you know, it's going to be one of those, there's never one size fits all. I'll give the class of consultant like it depends answer. Right? >>Yeah, for sure. It's very similar to the code struggle because it depends. >>Right? >>Uh Yeah, it's similar to the to the code problem of teams trying to figure out how many repose for their code. Should they micro service, should they? Semi micro service, macro service. Like I mean, you know because too many repose means you're doing a bunch of repo management, a bunch of changes on your local system, you're constantly get pulling all these different things and uh but if you have one big repo then it's it's a it's a huge monolithic thing that you usually have to deal with. Path based issues of tools that only need to look at a specific directory and um yeah, it's a it's a culture, I feel like yeah, like I keep going back to this, it's a culture thing. Does your what is your team prefer? What do you like? What um what's painful for everyone and who's what's the loudest pain that you need to deal with? Is it is it repo management? That's the pain um or is it uh you know, is that that everyone's in one place and it's really hard to keep too many cooks out of the kitchen, which is a mono repo problem, you know? Um How do we handle security? So this is a great one from Tory again. Another great question back to back. And that's the first time we've done that um security as it pertains to get up to anyone who can commit can change the infrastructure. Yes. >>Yes. So the tooling that you have for your GIT repo and the authentication, authorization and permissions that you apply to the GIT repo using a get server like GIT hub or get lab or whatever your flavor of the day is is going to be how security is handled with respect to changes in your get ups configuration repository. So um that is completely specific to your implementation of that or ones implementation of of how they're handling that. Get repositories that the get ups tooling is looking at. To reconcile changes with respect to the permissions of the for lack of better term robot itself. Right? They get up tooling like flux or Argosy. D Um one kid would would create a user or a service account or uh other kind of authentication measures to limit the permissions for that service account that the Gaddafi's tooling needs to be able to read the repose and and send commits etcetera. So that is well within the realm of what you have already for your for your get your get um repo. Yeah. >>Yeah. A related question is from a g what they like about get apps if done nicely for a newbie it's you can get stuff done easily if you what they dislike about it is when you have too many get repose it becomes just too complicated and I agree. Um was making a joke with a team the other week that you know the developer used to just make one commit and they would pass pass it on to a QA team that would then eventually emerging in the master. But they made the commits to these feature branches or whatever. But now they make a commit, they make a pR there for their code then they go make a PR in the helm chart to update the thing to do that and then they go make a PR in the get ups repeal for Argo. And so we talked about that they're probably like four or five P. R. Is just to get their code in the production. But we were talking about the negative of that but the reality was It's just five or 4 or five prs like it wasn't five different systems that had five different methodologies and tooling and that. So I looked at it I was like well yeah that's kind of a pain in the get sense but you're also dealing with one type. It's a repetitive action but it's it's the one thing I don't have to go to five different systems with five different ways of doing it. And once in the web and one's on the client wants a command line that I don't remember. Um Yeah so it's got pros and cons I think when you >>I think when you get to the scale where those kind of issues are a problem then you're probably at the scale where you can afford to invest some time into automation into that. Right? Like what I've when I've seen this in larger customers or larger organizations if there ever at that stage where okay apps are coming up all the time. You know, there's a 10 X 100 X developer to operations folks who may be creating get repose setting up permissions then that stuff gets automated, right? Like, you know, maybe ticket based systems or whatever. Developers say I need a new app. It templates things or more often using the same model, right of reconciliation and operators and the horrific abuse of cogs that we're seeing in the communities community right now. Um You know, developers can create a crd which just says, hey, I'm creating a new app is called app A and then a controller will pick up that app a definition. It will go create a get a repo Programmatically it will add the right definitely will look up and held up the developers and the permissions that need to be able to get to that repo it will create and template automatically some name space and the clusters that it needs in the environments that it needs, depending on, you know, some metadata it might read. So I think, you know, those are definite problems and they're definitely like a teething, growing pain thing. But once you get to that scale, you kind of need to step back and say, well look, we just need to invest in time into the operational aspect of this and automating this pain away, I think. Yeah, >>yeah. And that ultimately ends in Yeah. Custom tooling, which it's hard to avoid it at scale. I mean, there's there's two, there's almost two conversations here, right. There is what I call the Solo admin Solo devops, I bought that domain Solo devops dot com because, you know, whenever I'm talking to dr khan in the real world, it's like I asked people to raise hands, I don't know how we can raise hands here, but I would ask people to raise hands and see how many of you here are. The sole person responsible for deploying the app that your team makes and like a quarter of the room would raise their hand. So I call that solo devops like those, that person can't make all the custom tooling in the world. So they really need dr like solutions where it's opinionated, the workflow is sort of built in and they don't have to wrangle things together with a bunch of glue, you know, in other words bash. Um and so this kind of comes to a conversation uh starting this question from lee he's asking how do you combine get ops with ci cd, especially the continuous bit. How do you avoid having a human uh sort of the complaint the team I was working with has, how do you avoid a human editing and get committing for every single deploy? They've settled on customized templates and a script for routine updates. So as a seed for this conference, this question I'm gonna ask you all uh instead of that specific question cause it's a little open ended. Um Tell me whether you agree with this. I I kind of look at the image, the image artifact because the doctor image or container image in general is an artifact that I I view it that way and that thing going into the registry with the right label or right part of the label. Um That tag rather not the label but the tag that to me is like one of the great demarche points of, we're kind of done with Ci and we're now into the deployment phase and it doesn't necessarily mean the tooling is a clear cut there, but that artifact being shipped in a specific way or promoted as we sometimes say. Um what do you think? Does anyone have opinions on that? I don't even know if that's the right opinion to have so mhm. >>So um I think what you're, what you're getting at is that get ups, models can trigger off of different events um to trigger the reconciliation loop. And one way to do that is if the image, if it notices a image change in the registry, the other is if there's a commit event on a specific rebo and branch and it's up to, you are up to the person that's implementing their get ups model, what event to trigger there, that reconciliation loop off of, You can do both, you can do one or the other. It also depends on the Templeton engine that you're using on top of um on top of kubernetes, such as helm or um you know, the other ones that are out there or if you're not even doing that, then, you know straight. Yeah, mo um so it kind of just depends, but those are the typically the two options one has and a combination of of those to trigger that event. You can also just trigger it manually, right? You can go into the command line and force a a, you know, a really like a scan or a new reconciliation loop to occur. So it kind of just, I don't want to say this, but it depends on what you're trying to do and what makes sense in your pipeline. Right? So if you're if you're set up where you are tag, if you're doing it based off of image tags, then you probably want to use get ups in a way that you're using the image tags. Right. And the pattern that you've established there, if you're not really doing that and you're more around, like, different branches are mapped to different environments, then triggered off of the correct branch. And that's where the permissions also come into play. Where if you don't want someone to touch production and you've got your getups for your production cluster based off of like uh you know, a main branch, then whoever can push a change to that main branch has the authority to push that change to production. Right? So that's your authentication and permissions um system same for the registry itself. Right. So >>Yeah. Yeah. Sorry, anyone else have any thoughts on that? I was about to go to the next topic, >>I was going to say. I think certain tools dictate the approach, like, if you're using Argosy d it's I think I'm correct me if I'm wrong, but I think the only way to use it right now is just through image modification. Like, the manifest changes, it looks at a specific directory and anything changes then it will do its thing. And uh Synchronize the cost there with whatever's and get >>Yeah, flux has both. Yeah, and flux has both. So it it kind of depends. I think you can make our go do that too, but uh this is back to what we were saying in the beginning, uh you know, these things are changing, right? So that might be what it is right now in terms of triggering the reconciliation loops and get ups, tooling, but there might be other events in the future that might trigger it, and it's not completely stand alone because you still need you're tooling to do any kind of testing or whatever you have in terms of like the specific pipeline. So oftentimes you're bolting in getups into some other part of broader Cfd solution. That makes sense. Yeah, >>we've got a lot of questions about secrets or people that are asking about secrets. >>So my my tongue and cheek answered the secrets question was, what's the best practices for kubernetes? Secrets? That's the same thing for secrets with good apps? Uh getups is not last time I checked and last time I was running this stuff get ups is not has nothing to do with secrets in that sense. It's just there to get your stuff running on communities. So, um there's probably a really good session on secrets at dr concept. I >>would agree with you, I agree with you. Yeah, I mean, get off stools, I mean every every project of mine handles secrets differently. Uh huh. And I think I'm not sure if it was even when I was talking to but talking to someone recently that I'm very bullish on get up actions, I love get up actions, it's not great for deployments yet, but we do have this new thing and get hub environments, I think it's called. So it allows me at least the store secrets per environment, which it didn't have the concept of that before, which you know, if you if any of you running kubernetes out there, you typically end up when you start running kubernetes, you end up with more than one kubernetes, like you're going to end up with a lot of clusters at some point, at least many multiple, more than two. Um and so if you're trying to store secret somewhere, you do have and there's a discussion happening in chat right now where people are talking about um sealed secrets which if you haven't heard of that, go look that up and just be versed on what sealed secrets is because it's a it's a fantastic concept for how to store secrets in the public. Um I love it because I'm a big P. K. I nerd but um it's not the only way and it doesn't fit all models. So I have clients that use A W. S. Secrets because they're in A W. S. And then they just have to use the kubernetes external secret. But again like like like normal sand, you know, it's that doesn't really affect get ops, get ops is just applying whatever helm charts or jahmal or images that you're, you're you're deploying, get off. It was more about the approach of when the changes happen and whether it's a push or pull model like we're talking about and you know, >>I would say there's a bunch of prerequisites to get ups secrets being one of them because the risk of you putting a secret into your git repo if you haven't figured out your community secrets architecture and start diving into getups is high and removing secrets from get repose is you know, could be its own industry, right. It's >>a thing, >>how do >>I hide this? How do I obscure this commit that's already now on a dozen machines. >>So there are some prerequisites in terms of when you're ready to adopt get up. So I think is the right way of saying the answer to that secrets being one of them. >>I think the secrets was the thing that made me, you know, like two or three years ago made me kind of see the ah ha moment when it came to get ups which, which was that the premier thing that everyone used to say about get up about why it was great. Was its the single source of truth. There's no state anywhere else. You just need to look at git. Um and then secrets may be realized along with a bunch of other things down the line that is not true and will never be true. So as soon as you can lose the dogmatism about everything is going to be and get it's fantastic. As long as you've understood everything is not going to get. There are things which will absolutely never be and get some tools just don't deal with that. They need to earn their own state, especially in communities, some controls on their own state. You know, cuz sealed secrets and and other projects like SOps and I think there are two or three others. That's a great way of dealing with secrets if you want to keep them in get. But you know, projects like vault more kind of like what I would say, production grade secret strategies. Right? And if you're in AWS or a cloud, you're more likely to be using their secrets. Your secret policy is maybe not dictated by you in large organizations might be dictated by CSO or security or Great. Like I think once if you, if you're trying to adopt getups or you're thinking about it, get the dogmatism of get as a single point of truth out of your mind and think about getups more as a philosophy and a set of best practice principles, then you will be in much better stead, >>right? Yeah. >>People are asking more questions in chat like infrastructure as code plus C d essentially get ups or C I rather, um, these are all great questions and a part of the debate, I'm actually just going to throw up on screen. I'm gonna put this in chat, but this is, this is to me the source, Right? So we worked with when they coined the term. We, a lot of us have been trying to get, if we talk about the history for a minute and then tell me if I'm getting this right. Um, a lot of us were trying to automate all these different parts of the puzzle, but a lot of them, they, some things might have been infrastructure as code. Some things weren't, some things were sort of like settings is coded, like you're going to Jenkins and type in secrets and settings or type in a certain thing in the settings of Jenkins and then that it wasn't really in get and so what we was trying to go for was a way to have almost like eventually a two way state understanding where get might change your infrastructure but then your infrastructure might also change and needs to be reflected in the get if the get is trying to be the single source of truth. Um and like you're saying the reality is that you're never gonna have one repo that has all of your infrastructure in it, like you would have to have, you have to have all your terra form, anything else you're spinning up. Right. Um but anyway, I'm gonna put this link in chat. So this guide actually, uh one of things they talk about is what it's not, so it's, it's kind of great to read through the different requirements and like what I was saying well ago um mhm. Having having ci having infrastructure as code and then trying a little bit of continuous deployment out, it's probably a prerequisite. Forget ops so it's hard to just jump into that when you don't already have infrastructure as code because a machine doing stuff on your behalf, it means that you have to have things documented and somewhere and get repo but let me put this in the in the >>chitty chat, I would like to know if the other panelists agree, but I think get apps is a okay. I would say it's a moderate level, it's not a beginner level communities thing, it's like a moderate level advanced, a little bit more advanced level. Um One can start off using it but you definitely have to have some pre recs in place or some understanding of like a pattern in place. Um So what do the other folks think about that opinion? >>I think if you're if you're trying to use get out before, you know what problem you have, you're probably gonna be in trouble. Right. It's like having a solution to it probably don't have yet. Mhm. Right. I mean if if you're just evil or and you're just typing, keep control apply, you're one person right, Get off. It doesn't seem like a big a big jump, like, I mean it doesn't like why would I do that? I'm just, I'm just gonna inside, it's the type of get commit right, I'm typing Q control apply. But I think one of the rules from we've is none of your developers and none of your admins can have cute control access to the cluster because if you can't, if you do have access and you can just apply something, then that's just infrastructure as code. That's just continuous deployment, that's, that's not really get ops um, getups implies that the only way things get into the cluster is through the get up, get automation that you're using with, you know, flux Argo, we haven't talked about, what's the other one that Victor Farsi talks about, by the way people are asking about victor, because victor would love to talk about this stuff, but he's in my next life, so come back in an hour and a half or whatever and victor is going to be talking about sys, admin list with me. Um >>you gotta ask him nothing but get up questions in the next, >>confuse them, confuse them. But anyway, that, that, that's um, it's hard, it's hard to understand and without having tried it, I think conceptually it's a little challenging >>one thing with getups, especially based off the we've works blog post that you just put up on there. It's an opinionated way of doing something. Uh you know, it's an opinionated way of of delivering changes to an environment to your kubernetes environment. So it's opinionated were often not used to seeing things that are very opinionated in this sense, in the in the ecosystem, but get apps is a opinionated thing. It's it's one way of doing it. Um there are ways to change it and like there are options um like what we were talking about in terms of the events that trigger, but the way that it's structured is an opinion opinionated way both from like a tooling perspective, like using get etcetera, but also from a devops cultural perspective, right? Like you were talking about not having anyone access cube control and changing the cluster directly. That's a philosophical opinion that get ups forces you to adopt otherwise. It kind of breaks the model and um I just I want everyone to just understand that. That is very opinion, anything in that sense. Yeah, >>polygamy is another thing. Infrastructure as code. Um someone's mentioning plummy and chat, I just had actually my life show self plug bread that live go there. I'm on Youtube every week. I did the same thing. These these are my friends um and had palami on two weeks ago uh last week, remember uh and it was in the last couple of weeks and we talked about their infrastructure as code solution. Were actually writing code instead of um oh that's an interesting take on uh developer team sort of owning coding the infrastructure through code rather than Yamil as a data language. I don't really have an opinion on it yet because I haven't used it in production or anything in the real real world, but um, I'm not sure how much they are applying trying to go towards the get up stuff. I will do a plug for Solomon hikes. Who has a, the beginning of the day, it's already happened so you can go back and watch it. It's a, it's a, what's it called? Q. Rethinking application delivery with Q. And build kit. So go look this up. This is the found co founder of Dr and former CTO Solomon hikes at the beginning of the day. He has a tool called dagger. I'm not sure why the title of the talk is delivering with Q. And built it, but the tool is showing off in there for an hour is called dagger. And it's, it's an interesting idea on how to apply a lot of this opinionated automated stuff to uh, to deployment and it's get off space and you use Q language. It's a graph language. I watched most of it and it was a really interesting take. I'm excited to see if that takes off and if they try that because it's another way that you can get a little bit more advanced with your you're get deployments and without having to just stick everything in Yemen, which is kind of what we're in today with helm charts and what not. All right. More questions about secrets, I think. I think we're not going to have a whole lot of more, a lot more about secrets basically. Uh put secrets in your cluster to start with and kubernetes in encrypted, you know, thing. And then, you know, as it gets harder, then you have to find another solution when you have five clusters, you don't wanna have to do it five times. That's when you have to go for Walton A W. S secrets and all >>that. Right? I'm gonna post it note. Yeah. Crm into the cluster. Just kidding. >>Yes, there are recordings of this. Yes, they will be later. Uh, because we're that these are all gonna be on youtube later. Um, yeah, detects secrets cushion saying detect secrets or get Guardian are absolute requirements. I think it's in reference to your secrets comment earlier. Um, Camels asking about Cuban is dropping support for Docker that this is not the place to ask for that, but it, it is uh, basically it's a Nonevent Marantz has actually just created that same plug in available in a different repos. So if you want to keep using Docker and kubernetes, you know, you can do it like it's no big deal. Most of us aren't using doctor in our communities anyway, so we're using like container D or whatever is provided to us by our provider. Um yeah, thank you so much for all these comments. These are great people helping each other and chat. I feel like we're just here to make sure the chats available so people can help each other. >>I feel like I want to pick up on something when you mentioned pollux me, I think there's a um we're talking about getups but I think in the original like the origination of that I guess was deploying applications to clusters right, picking up deployment manifest. But I think with the gloomy and I obviously terra form and things have been around a long time, folks are starting to apply this I think I found one earlier which was like um kub stack the Terror Forms get ups framework. Um but also with the advent of things like cluster A. P. I. Um in the Cuban at the space where you can declare actively build the infrastructure for your clusters and build the cluster right? We're not just talking about deploying applications, the cluster A. P. I will talk to a W. S. Spin up, VPc spin up machines, you know, we'll do the same kind of things that terra form does and and those other tools do I think applying getups principles to the infrastructure spin up right, the proper infrastructure as code stuff, constantly applying Terror form um you know, plans and whatever, constantly applying cluster Api resources spinning up stuff in those clouds. That's a super interesting. Um you know, extension of this area, I'd be curious to see if what the folks think about that. >>Yeah, that's why I picked this topic is one of my three. Uh I got I got to pick the topics. I was like the three things that there like the most bleeding edge exciting. Most people haven't, we haven't basically we haven't figured all this out yet. We as an industry, so um it's I think we're gonna see more ideas on it. Um what's the one with the popsicle as the as the icon victor talks about all the time? It's not it's another getups like tool, but it's um it's getups for you use this kubernetes limit and then we have to look it up, >>You're talking about cross plane. >>So >>my >>wife is over here with the sound effects and the first sound effect of the day that she chooses to use is one. >>All right, can we pick it? Let's let's find another question bret >>I'm searching >>so many of them. All right, so uh I think one really quick one is getups only for kubernetes, I think the main to tooling to tools that we're talking about, our Argosy D and flux and they're mostly geared toward kubernetes deployments but there's a, it seems like they're organized in a way that there's a clean abstraction in with respect to the agent that's doing the deployment and the tooling that that can interact with. So I would imagine that in the future and this might be true already right now that get ups could be applied to other types of deployments at some point in the future. But right now it's mostly focused and treats kubernetes as a first class citizen or the tooling on top of kubernetes, let's say something like how as a first class citizen? Yeah, to Brett, >>to me the field, back to you bret the thing I was looking for is cross plane. So that's another tool. Um Victor has been uh sharing a lot about it in Youtube cross plane and that is basically runs inside a kubernetes, but it handles your other infrastructure besides your app. It allows you to like get ops, you're a W. S stuff by using the kubernetes state engine as a, as a way to manage that. And I have not used it yet, but he does some really great demos on Youtube. So people are liking this idea of get off, so they're trying to figure out how do we, how do we manage state? How do we uh because the probably terra form is that, well, there's many problems, but it's always a lot of problems, but in the get outs world it's not quite the right fit yet, It might be, but you still, it's still largely as expected for people to, you know, like type the command, um, and it keeps state locally the ss, clouds and all that. And but the other thing is I'm I'm now realizing that when I saw the demo from Solomon, I'm going back to the Solomon hikes thing. He was using the demo and he was showing it apply deploying something on S three buckets, employing internet wifi and deploying it on google other things beyond kubernetes and saying that it's all getups approach. So I think we're just at the very beginning of seeing because it all started with kubernetes and now there's a swarm one, you can look up swarm, get office and there's a swarm, I can't take the name of it. Swarm sink I think is what's called swarm sink on git hub, which allows you to do swarm based getups like things. And now we're seeing these other tools coming out. They're saying we're going to try to do the get ups concepts, but not for kubernetes specifically and that's I think, you know, infrastructure as code started with certain areas of the world and then now then now we all just assume that you're going to have an infrastructure as code way of doing whatever that is and I think get off is going to have that same approach where pretty soon, you know, we'll have get apps for all the clouds stuff and it won't just be flexor Argo. And then that's the weird thing is will flex and Argo support all those things or will it just be focused on kubernetes apps? You know, community stuff? >>There's also, I think this is what you're alluding to. There is a trend of using um kubernetes and see rDS to provision and control things that are outside of communities like the cloud service providers services as if they were first class entities within kubernetes so that you can use the kubernetes um focus tooling for things that are not communities through the kubernetes interface communities. Yeah, >>yeah, even criticism. >>Yeah, yeah, I'm just going to say that sounds like cross plane. >>Yeah, yeah, I mean, I think that's that's uh there were, you know, for the last couple of years, it's been flux and are going back and forth. Um they're like frenemies, you know, and they've been going back and forth with iterating on these ideas of how do we manage this complicated thing? That is many kubernetes clusters? Um because like Argo, I don't know if the flux V two can do this, but Argo can manage multiple clusters now from one cluster, so your, you can manage other clusters, technically external things from a single entity. Um Originally flux couldn't do that, but I'm going to say that V two can, I don't actually >>know. Um I think all that is gonna, I think that's going to consolidate in the future. All right. In terms of like the common feature set, what Iver and john what do you think? >>I mean, I think it's already begun, right, I think haven't, didn't they collaborate on a common engine? I don't know whether it's finished yet, but I think they're working towards a common getups engine and then they're just going to layer on features on top. But I think, I mean, I think that's interesting, right, because where it runs and where it interacts with, if we're talking about a pull based model, it shouldn't, it's decentralized to a certain extent, right? We need get and we need the agent which is pulling if we're saying there's something else which is orchestrating something that we start to like fuzzy the model even right. Like is this state living somewhere else, then I think that's just interesting as well. I thought flux was completely decentralized, but I know you install our go somewhere like the cargo has a server as well, but it's been a while since I've looked in depth at them. But I think the, you know, does that muddy the agent only pull model? >>I'm reading a >>Yeah, I would say that there's like a process of natural selection going on as as the C. N. C. F. Landscape evolves and grows bigger and a lot of divide and conquer right now. But I think as certain things kind of get more prominent >>and popular, I think >>it starts to trend and it inspires other things and then it starts to aggregate and you know, kind of get back into like a unified kind of like core. Maybe like for instance, cross plane, I feel like it shouldn't even really exist. It should be, it like it's a communities add on, but it should be built in, it should be built into kubernetes, like why doesn't this exist already >>for like controlling a cloud? >>Yeah, like just, you know, having this interface with the cloud provider and be able to Yeah, >>exactly. Yeah, and it kinda, you're right. That kinda happens because you do, I mean when you start talking about storage providers and networking providers was very specific implementations of operators or just individual controllers that do operate and control other resources in the cloud, but certainly not universally right. Not every feature of AWS is available to kubernetes out of the box. Um and you know, it, one of the challenges across plane is you gotta have kubernetes before you can deploy kubernetes. Like there's a chicken and egg issue there where if you're going to use, if you're going to use our cross plane for your other infrastructure, but it's gotta, but it has to run on kubernetes who creates that first kubernetes in order for you to put that on there. And victor talks about one of his videos, the same problem with flux and Argo where like Argo, you can't deploy Argo itself with getups. There has to be that initial, I did a thing with, I'm a human and I typed in some commands on a server and things happened but they don't really have an easy deployment method for getting our go up and running using simply nothing but a get push to an existing system. There's something like that. So it's a it's an interesting problem of day one infrastructure which is again only day one, I think data is way more interesting and hard, but um how can we spend these things up if they're all depending on each other and who is the first one to get started? >>I mean it's true of everything though, I mean at the end of that you need some kind of big bang kind of function too, you know, I started running start everything I >>think without going over that, sorry, without going off on a tangent. I was, I was gonna say there's a, if folks have heard of kind which is kubernetes and Docker, which is a mini kubernetes cluster, you can run in a Docker container or each container will run as a as a node. Um you know, that's been a really good way to spin up things like clusters. KPI because they boot strap a local kind, install the manifests, it will go and spin up a fully sized cluster, it will transfer its resources over there and then it will die itself. Right? So that, that's kind of bootstrapping itself. And I think a couple of folks in the community, Jason to Tiberius, I think he works for Quinyx metal um has, has experimented with like an even more minimal just Api server, so we're really just leveraging the kubernetes ideas of like a reconciliation loop and a controller. We just need something to bootstrap with those C R D s and get something going and then go away again. So I think that's gonna be a pattern that comes up kind of more and more >>Yeah, for sure. Um, and uh, the next, next quick answer to the question, Angel asked what your thoughts on getups being a niche to get or versus others vcs tools? Well, if I knew anyone who is using anything other than get, I would say no, you know, get ops is a horrible name. It should just be CVS office, but that doesn't or vcs ops or whatever like that, but that doesn't roll off the tongue. So someone had to come up with the get ups phrase. Um but absolutely, it's all about version control solutions used for infrastructure, not code. Um might get doctor asks a great question, we're not gonna have time for it, but maybe people can reply and chat with what they think but about infrastructure and code, the lines being blurred and that do develop, how much of infrastructure does developer do developers need to know? Essentially, they're having to know all the things. Um so unfortunately we've had way more questions like every panel here today with all the great community, we've got way more questions we can handle in this time. So we're gonna have to wrap it up and say goodbye. Go to the next live panel. I believe the next one is um on developer, developer specific setups that's gonna be peter running that panel. Something about development in containers and I'm sure it's gonna be great. Just like this one. So let's go around the room where can people find you on the internet? I'm at Brett fisher on twitter. That's where you can usually find me most days you are? >>Yeah, I'm on twitter to um, I'll put it in the chat. It's kind of confusing because the TSR seven. >>Okay. Yeah, that's right. You can't just say it. You can also look at the blow of the video and like our faces are there and if you click on them, it tells you our twitter in Arlington and stuff, john >>John Harris 85, pretty much everywhere. Get hub Twitter slack, etc. >>Yeah >>and normal, normal faults or just, you know, living on Youtube live with Brett. >>Yeah, we're all on the twitter so go check us out there and thank you so much for joining. Uh thank you so much to you all for being here. I really appreciate you taking time in your busy schedule to join me for a little chit chat. Um Yes, all the, all the cheers, yes. >>And I think this kid apps loop has been declarative lee reconciled. >>Yeah, there we go. And with that ladies and gentlemen, uh bid you would do, we will see you in the next, next round coming up next with Peter >>bye.
SUMMARY :
I got my evil or my john and the normal And we're going to talk about get ops I currently based in Berlin and I happen to be Brett Brett's teaching assistant. All right, that's right. Um, so yeah, it's good to see either in person and it's good to see you again john it's been a little It has the pre covid times, right? Yeah, john shirt looks red and reminds me of the Austin T shirt. Um, but you know, you have to go steal stuff, you to find ways to get the swag If you ever come to my place, I'm going to have to lock the closets. So the second I think it was the second floor of the doctor HQ in SAn Francisco was where they kept all the Um All right, so I'm going to start scanning questions uh so that you don't have to you can Um I still feel like I'm very new to john you anything. like it's, you know, I think when you put it best in the beginning where you do a and then there's a magic and then you get C. so it has a learning curve and it's still being, you know, I think it's like I feel like we're very early days and the idea of especially when you start getting into tooling sure you would have opinions. I think it's a very yeah. um I'll do my best inner victor and say, you know, it's it's I like it. then more, you know, and not everything needs to settle in terms of only one way of doing things, to a server and do a doctor pull and you know, dr up or dr composed up rather, That's not to say that there aren't city tools which we're doing pull based or you can do pull based or get ups I rant, Right, so you have what? thing that I could figure out how to, you know, get it set up using um get hubs, and different repos and subdirectories are are looking at the defense and to see if there's changes I think it's you know, Yeah, for sure. That's the pain um or is it uh you know, is that that everyone's in one place So that is well within the realm of what you have Um was making a joke with a team the other week that you know the developer used to just I think when you get to the scale where those kind of issues are a problem then you're probably at the scale this kind of comes to a conversation uh starting this question from lee he's asking how do you combine top of kubernetes, such as helm or um you know, the other ones that are out there I was about to go to the next topic, I think certain tools dictate the approach, like, if you're using Argosy d I think you can make our go do that too, but uh this is back to what That's the same thing for secrets with good apps? But again like like like normal sand, you know, it's that doesn't really affect get ops, the risk of you putting a secret into your git repo if you haven't figured I hide this? So I think is the right way of saying the answer to that I think the secrets was the thing that made me, you know, like two or three years ago made me kind of see Yeah. in it, like you would have to have, you have to have all your terra form, anything else you're spinning up. can start off using it but you definitely have to have some pre recs in if you do have access and you can just apply something, then that's just infrastructure as code. But anyway, one thing with getups, especially based off the we've works blog post that you just put up on And then, you know, as it gets harder, then you have to find another solution when Crm into the cluster. I think it's in reference to your secrets comment earlier. like cluster A. P. I. Um in the Cuban at the space where you can declare actively build the infrastructure but it's um it's getups for you use this kubernetes I think the main to tooling to tools that we're talking about, our Argosy D and flux I think get off is going to have that same approach where pretty soon, you know, we'll have get apps for you can use the kubernetes um focus tooling for things I mean, I think that's that's uh there were, you know, Um I think all that is gonna, I think that's going to consolidate But I think the, you know, does that muddy the agent only But I think as certain things kind of get more it starts to trend and it inspires other things and then it starts to aggregate and you know, the same problem with flux and Argo where like Argo, you can't deploy Argo itself with getups. Um you know, that's been a really good way to spin up things like clusters. So let's go around the room where can people find you on the internet? the TSR seven. are there and if you click on them, it tells you our twitter in Arlington and stuff, john Get hub Twitter slack, etc. and normal, normal faults or just, you know, I really appreciate you taking time in your And with that ladies and gentlemen, uh bid you would do,
SENTIMENT ANALYSIS :
ENTITIES
Entity | Category | Confidence |
---|---|---|
Brett | PERSON | 0.99+ |
Berlin | LOCATION | 0.99+ |
Victor Farsi | PERSON | 0.99+ |
john Harris | PERSON | 0.99+ |
Virginia Beach | LOCATION | 0.99+ |
Seattle | LOCATION | 0.99+ |
Jason | PERSON | 0.99+ |
Brett Brett | PERSON | 0.99+ |
Gaddafi | PERSON | 0.99+ |
two | QUANTITY | 0.99+ |
first question | QUANTITY | 0.99+ |
Yemen | LOCATION | 0.99+ |
last week | DATE | 0.99+ |
three | QUANTITY | 0.99+ |
last year | DATE | 0.99+ |
one | QUANTITY | 0.99+ |
Arlington | LOCATION | 0.99+ |
Brett fisher | PERSON | 0.99+ |
five times | QUANTITY | 0.99+ |
Tiberius | PERSON | 0.99+ |
Peter | PERSON | 0.99+ |
two options | QUANTITY | 0.99+ |
john | PERSON | 0.99+ |
Virginia beach | LOCATION | 0.99+ |
two weeks ago | DATE | 0.99+ |
AWS | ORGANIZATION | 0.99+ |
both | QUANTITY | 0.99+ |
Amman Arepa | LOCATION | 0.99+ |
three changes | QUANTITY | 0.99+ |
one cluster | QUANTITY | 0.99+ |
second floor | QUANTITY | 0.99+ |
Quinyx | ORGANIZATION | 0.99+ |
five | QUANTITY | 0.99+ |
Tory | PERSON | 0.99+ |
an hour and a half | QUANTITY | 0.99+ |
today | DATE | 0.99+ |
axel Springer | ORGANIZATION | 0.99+ |
Victor | PERSON | 0.99+ |
Jenkins | TITLE | 0.98+ |
youtube | ORGANIZATION | 0.98+ |
SAn Francisco | LOCATION | 0.98+ |
three special guests | QUANTITY | 0.98+ |
4 | QUANTITY | 0.98+ |
Each tool | QUANTITY | 0.98+ |
booz allen | PERSON | 0.98+ |
one person | QUANTITY | 0.98+ |
five clusters | QUANTITY | 0.98+ |
three things | QUANTITY | 0.98+ |
first time | QUANTITY | 0.98+ |
five different systems | QUANTITY | 0.98+ |
each container | QUANTITY | 0.98+ |
day one | QUANTITY | 0.98+ |
Youtube | ORGANIZATION | 0.98+ |
Angel | PERSON | 0.98+ |
Iver | PERSON | 0.98+ |
five different ways | QUANTITY | 0.98+ |
first year | QUANTITY | 0.97+ |
V two | OTHER | 0.97+ |
three commits | QUANTITY | 0.97+ |
more than two | QUANTITY | 0.97+ |
One person | QUANTITY | 0.97+ |
two way | QUANTITY | 0.96+ |
ORGANIZATION | 0.96+ | |
one way | QUANTITY | 0.96+ |
single source | QUANTITY | 0.96+ |
single point | QUANTITY | 0.96+ |
five prs | QUANTITY | 0.95+ |
first one | QUANTITY | 0.95+ |
John Harris 85 | PERSON | 0.95+ |
first | QUANTITY | 0.95+ |
more than one kubernetes | QUANTITY | 0.95+ |