>>Welcome back to NYC the Cube's coverage of Mongo DB 2022, a few thousand people here at least bigger than many people, perhaps expected, and a lot of buzz going on and we're gonna talk devs. I'm really excited to welcome back. Robbie Bellson who's the developer relations lead at Verizon and Ian Massingham. Who's the vice president of developer relations at Mongo DB Jens. Good to see you. Great >>To be here. >>Thanks having you. So Robbie, we just met a few weeks ago at the, the red hat summit in Boston and was blown away by what Verizon is doing in, in developer land. And of course, Ian, you know, Mongo it's rayon Detra is, is developers start there? Why is Mongo so developer friendly from your perspective? >>Well, it's been the ethos of MongoDB since day one. You know, back when we launched the first version of MongoDB back in 2009, we've always been about making developers lives easier. And then in 2016, we announced and released MongoDB Atlas, which is our cloud managed service for MongoDB, you know, starting with a small number of regions built on top of AWS and about 2,500 adoption events per week for MongoDB Atlas. After the first year today, MongoDB Atlas provides a managed service for MongoDB developers around the world. We're present in almost a hundred cloud regions across S DCP and Azure. And that adoption number is now running at about 25,000 developers a week. So, you know, the proof are in proof is really in the metrics. MongoDB is an incredibly popular platform for developers that wanna build data-centric applications. You just can't argue with the metrics really, >>You know, Ravi, sometimes there's an analyst who come up with these theories and one of the theories I've been spouting for a long time is that developers are gonna win the edge. And now to, to see you at Verizon building out this developer community was really exciting to me. So explain how you got this started with this journey. >>Absolutely. As you think about Verizon 5g edge or mobile edge computing portfolio, we knew from the start that developers would play a central role and not only consuming the service, but shaping the roadmap for what it means to build a 5g future. And so we started this journey back in late 20, 19 and fast forward to about a year ago with Mongo, we realized, well, wait a minute, you look at the core service offerings available at the edge. We didn't know really what to do with data. We wanted to figure it out. We wanted the vote of confidence from developers. So there I was in an apartment in Colorado racing, your open source Mongo against that in the region edge versus region, what would you see? And we saw tremendous performance improvements. It was so much faster. It's more than 40% faster for thousands and thousands of rights. And we said, well, wait a minute. There's something here. So what often starts is an organic developer, led intuition or hypothesis can really expand to a much broader go to market motion that really brings in the enterprise. And that's been our strategy from day one. Well, >>It's interesting. You talk about the performance. I, I just got off of a session talking about benchmarks in the financial services industry, you know, amazing numbers. And that's one of the hallmarks of, of Mongo is it can play in a lot of different places. So you guys both have developer relations in your title. Is that how you met some formal developer relations? >>We were a >>Program. >>Yeah, I would say that Verizon is one of the few customers that we also collaborate with on a developer relations effort. You know, it's in our mutual best interest to try to drive MongoDB consumption amongst developers using Verizon's 5g edge network and their platform. So of course we work together to help, to increase awareness of MongoDB amongst mobile developers that want to use that kind of technology. >>But so what's your story on this? >>I mean, as I, as I mentioned, everything starts with an organic developer discovery. It all started. I just cold messaged a developer advocate on Twitter and here we are at MongoDB world. It's amazing how things turn out. But one of the things that's really resonated with me as I was speaking with one of, one of your leads within your organization, they were mentioning that as Mongo DVIA developed over the years, the mantra really became, we wanna make software development easy. Yep. And that really stuck with me because from a network perspective, we wanna make networking easy. Developers are not gonna care about the internals of 5g network. In fact, they want us to abstract away those complexities so that they can focus on building their apps. So what better co-innovation opportunity than taking MongoDB, making software easy, and we make the network easy. >>So how do you think about the edge? How does you know variety? I mean, to me, you know, there's a lot of edge use cases, you know, think about the home Depot or lows. Okay, great. I can put like a little mini data center in there. That's cool. That's that's edge. Like, but when I think of Verizon, I mean, you got cell towers, you've got the far edge. How do you think about edge Robbie? >>Well, the edge is a, I believe a very ambiguous term by design. The edge is the device, the mobile device, an IOT device, right? It could be the radio towers that you mentioned. It could be in the Metro edge. The CDN, no one edge is better than the other. They're all just serving different use cases. So when we talk about the edge, we're focused on the mobile edge, which we believe is most conducive to B2B applications, a fleet of IOT devices that you can control a manufacturing plant, a fleet of ground and aerial robotics. And in doing so you can create a powerful compute mesh where you could have a private network and private mobile edge computing by way of say an AWS outpost and then public mobile edge computing by way of AWS wavelength. And why keep them separate. You could have a single compute mesh even with MongoDB. And this is something that we've been exploring. You can extend Atlas, take a cluster, leave it in the region and then use realm the mobile portfolio and spread it all across the edge. So you're creating that unified compute and data mesh together. >>So you're describing what we've been expecting is a new architecture emerging, and that's gonna probably bring new economics of new use cases, right? Where are we today in that first of all, is that a reasonable premise that this is a sort of a new architecture that's being built out and where are we in that build out? How, how do you think about the, the future of >>That? Absolutely. It's definitely early days. I think we're still trying to figure it out, but the architecture is definitely changing the idea to rip out a mobile device that was initially built and envisioned for the device and only for the device and say, well, wait a minute. Why can't it live at the edge? And ultimately become multi-tenant if that's the data volume that may be produced to each of those edge zones with hypothesis that was validated by developers that we continue to build out, but we recognize that we can't, we can't get that static. We gotta keep evolving. So one of our newest ideas as we think about, well, wait a minute, how can Mongo play in the 5g future? We started to get really clever with our 5g network APIs. And I, I think we talked about this briefly last time, 5g, programmability and network APIs have been talked about for a while, but developers haven't had a chance to really use them and our edge discovery service answering the question in this case of which database is the closest database, doesn't have to be invoked by the device anymore. You can take a thin client model and invoke it from the cloud using Atlas functions. So we're constantly permuting across the entire portfolio edge or otherwise for what it means to build at the edge. We've seen such tremendous results. >>So how does Mongo think about the edge and, and, and playing, you know, we've been wondering, okay, which database is actually gonna be positioned best for the edge? >>Well, I think if you've got an ultra low latency access network using data technology, that adds latency is probably not a great idea. So MongoDB since the very formative years of the company and product has been built with performance and scalability in mind, including things like in memory storage for the storage engine that we run as well. So really trying to match the performance characteristics of the data infrastructure with the evolution in the mobile network, I think is really fundamentally important. And that first principles build of MongoDB with performance and scalability in mind is actually really important here. >>So was that a lighter weight instance of, of Mongo or not >>Necessarily? No, not necessarily. No, no, not necessarily. We do have edge cashing with realm, the mobile databases Robbie's already mentioned, but the core database is designed from day one with those performance and scalability characteristics in mind, >>I've been playing around with this. This is kind of a, I get a lot of heat for this term, but super cloud. So super cloud, you might have data on Preem. You might have data in various clouds. You're gonna have data out at the edge. And, and you've got an abstraction that allows a developer to, to, to tap services without necessarily if, if he or she wants to go deep into the S great, but then there's a higher level of services that they can actually build for their customers. So is that a technical reality from a developer standpoint, in your view, >>We support that with the Mongo DB multi-cloud deployment model. So you can place Mongo DB, Atlas nodes in any one of the three hyperscalers that we mentioned, AWS, GCP or Azure, and you can distribute your data across nodes within a cluster that is spread across different cloud providers. So that kinds of an kind of answers the question about how you do data placement inside the MongoDB clustered environment that you run across the different providers. And then for the abstraction layer. When you say that I hear, you know, drivers ODMs the other intermediary software components that we provide to make developers more productive in manipulating data in MongoDB. This is one of the most interesting things about the technology. We're not forcing developers to learn a different dialect or language in order to interact with MongoDB. We meet them where they are by providing idiomatic interfaces to MongoDB in JavaScript in C sharp, in Python, in rust, in that in fact in 12 different pro programming languages that we support as a first party plus additional community contributed programming languages that the community have created drivers for ODMs for. So there's really that model that you've described in hypothesis exist in reality, using >>Those different Compli. It's not just a series of siloed instances in, >>In different it's the, it's the fabric essentially. Yeah. >>What, what does the Verizon developer look like? Where does that individual come from? We talked about this a little bit a few weeks ago, but I wonder if you could describe it. >>Absolutely. My view is that the Verizon or just mobile edge ecosystem in general for developers are present at this very conference. They're everywhere. They're building apps. And as Ian mentioned, those idiomatic interfaces, we need to take our network APIs, take the infrastructure that's being exposed and make sure that it's leveraging languages, frameworks, automation, tools, the likes of Terraform and beyond. We wanna meet developers where they are and build tools that are easy for them to use. And so you had talked about the super cloud. I often call it the cloud continuum. So we, we took it P abstraction by abstraction. We started with, will it work in one edge? Will it work in multiple edges, public and private? Will it work in all of the edges for a given region, public or private, will it work in multiple regions? Could it work in multi clouds? We've taken it piece by piece by piece and in doing so abstracting way, the complexity of the network, meaning developers, where they are providing those idiomatic interfaces to interact with our API. So think the edge discovery, but not in a silo within Atlas functions. So the way that we're able to converge portfolios, using tools that dev developers already use know and love just makes it that much easier. Do, >>Do you feel like I like the cloud continuum cause that's really what it is. The super cloud does the security model, how does the security model evolve with that? >>At least in the context of the mobile edge, the attack surface is a lot smaller because it's only for mobile traffic not to say that there couldn't be various configuration and human error that could be entertained by a given application experience, but it is a much more secure and also reliable environment from a failure domain perspective, there's more edge zones. So it's less conducive to a regionwide failure because there's so many more availability zones. And that goes hand in hand with security. Mm. >>Thoughts on security from your perspective, I mean, you added, you've made some announcements this week, the, the, the encryption component that you guys announced. >>Yeah. We, we issued a press release this morning about a capability called queryable encryption, which actually as we record this Mark Porter, our CTO is talking about in his keynote, and this is really the next generation of security for data stored within databases. So the trade off within field level encryption within databases has always been very hard, very, very rigid. Either you have keys stored within your database, which means that your memory, so your data is decrypted while it's resident in memory on your database engine. This allow, of course, allows you to perform query operations on that data. Or you have keys that are managed and stored in the client, which means the data is permanently OBS from the engine. And therefore you can't offload query capabilities to your data platform. You've gotta do everything in the client. So if you want 10 records, but you've got a million encrypted records, you have to pull a million encrypted records to the client, decrypt them all and see performance hit in there. Big performance hit what we've got with queryable encryption, which we announced today is the ability to keep data encrypted in memory in the engine, in the database, in the data platform, issue queries from the client, but use a technology called structural encryption to allow the database engine, to make decisions, operate queries, and find data without ever being able to see it without it ever being decrypted in the memory of the engine. So it's groundbreaking technology based on research in the field of structured encryption with a first commercial database provided to bring this to market. >>So how does the mobile edge developer think about that? I mean, you hear a lot about shifting left and not bolting on security. I mean, is this, is this an example of that? >>It certainly could be, but I think the mobile edge developer still stuck with how does this stuff even work? And I think we need to, we need to be mindful of that as we build out learning journeys. So one of my favorite moments with Mongo was an immersion day. We had hosted earlier last year where we, our, from an enterprise perspective, we're focused on BW BS, but there's nothing stopping us. You're building a B2C app based on the theme of the winner Olympics. At the time, you could take a picture of Sean White or of Nathan Chen and see that it was in fact that athlete and then overlaid on that web app was the number of medals they accrued with the little trumpeteer congratulating you for selecting that athlete. So I think it's important to build trust and drive education with developers with a more simple experience and then rapidly evolve overlaying the features that Ian just mentioned over time. >>I think one of the keys with cryptography is back to the familiar messaging for the cloud offloading heavy lifting. You actually need to make it difficult to impossible for developers to get this wrong, and you wanna make it as easy as possible for developers to deal with cryptography. And that of course is what we're trying to do with our driver technology combined with structure encryption, with query encryption. >>But Robbie, your point is lots of opportunity for education. I mean, I have to say the developers that I work with, it's, I'm, I'm in awe of how they solve problems and I, and the way they solve problems, if they don't know the answer, they figure out how to go get it. So how, how are your two communities and other communities, you know, how are they coming together to, to solve such problems and share whether it's best practices or how do I do this? >>Well, I'm not gonna lie in person. Events are a bunch of fun. And one of the easiest domain knowledge exchange opportunities, when you're all in person, you can ideate, you can whiteboard, you can brainstorm. And often those conversations are what leads to that infrastructure module that an immersion day features. And it's just amazing what in person events can do, but community groups of interest, whether it's a Twitch stream, whether it's a particular code sample, we rely heavily on digital means today to upscale the developer community, but also build on by, by means of a simple port request, introduce new features that maybe you weren't even thinking of before. >>Yeah. You know, that's a really important point because when you meet people face to face, you build a connection. And so if you ask a question, you're more likely perhaps to get an answer, or if one doesn't exist in a, in a search, you know, you, oh, Hey, we met at the, at the conference and let's collaborate on this guys. Congratulations on, on this brave new world. You're in a really interesting spot. You know, developers, developers, developers, as Steve bomber says screamed. And I was glad to see Dave was not screaming and jumping up and down on the stage like that, but, but the message still resonates. So thank you, definitely appreciate. All right, keep it right there. This is Dave ante for the cubes coverage of Mago DB world 2022 from New York city. We'll be right back.

>> Narrator: From around the globe, it's theCUBE with digital coverage of Dockercon Live 2020, brought to you by Docker and it's ecosystem partners. >> Everyone welcome back to Dockercon 2020, #Docker20. This is theCUBE and Docker's coverage of Dockercon 20. I'm John Furrier in the Palo Alto studios with our quarantine crew, we got a great interview segment here and big news around developer workflow code to cloud. We've got Amanda Silver, Corporate Vice President, product for developer tools at Microsoft and Scott Johnson, the CEO of Docker. Scott had a great Keynote talking about this relationship news has hit about the extension of the Microsoft partnership. So congratulations, Amanda, welcome to theCUBE. >> Thanks for having me. >> Amanda, tell us about what your role is at Microsoft. You guys are well known in the developer community. You had to develop a ecosystem even when I was in college going way back. Very modern now, the cloud is the key, code to cloud, that's the theme. Tell us about your role at Microsoft. >> Yeah, so I basically run the product, Product Design and User Research team that works on our developer tools at Microsoft. And so that includes the Visual Studio product as well as Visual Studio code that's become pretty popular in the last few years but it also includes things like the dotNET runtime and the TypeScript programming language, as well as all of our Azure tooling. >> What's your thoughts on the relationship with Docker? Obviously the news extension of an existing relationship, Microsoft's got a lot of tools, you got a lot of things you guys are doing, bringing the cloud to every business. Tell us about your thoughts on this relationship with Docker? >> Yeah well, we're very excited about the partnership for sure. Our goal is really to make sure that Azure is a fantastic place where all developers can kind of bring their code and they feel welcome. They feel natural. We really see a unique opportunity to make the experience really great for the Docker community by creating more integrated and seamless experience across Docker desktop, Windows and Visual Studio and we really appreciate how Docker has kind of, supported our Windows ecosystem to run in Docker as well. >> Scott, this relationship and an extension with Microsoft is really, I think, impressive and also notable because Microsoft's got so many tools out there and they have so successful with Azure. You guys have been so successful with your developer community but this also is a reflective of the new Docker. Can you share your thoughts on how this partnership with Microsoft, extending the way it is, with the growth of the cloud is a reflection of the new Docker? >> Yeah, absolutely John, it's a great question. One of the things that we've really been focused on since November is fully embracing the ecosystem and all the partnerships and all the possibilities of that ecosystem and part of that is just reality that we're a smaller company now and we can't do it all, nor should we do it all. Part of it's the reality that developers love choice and no one's going to change their minds on choice, and third is just acknowledging that there's so much creativity and so much energy outside the four walls of Docker that we'd be silly not to take advantage of that and welcome it and embrace it and provide that as a phenomenal experience for our developers. So this is a great example of that. The Snyk partnership we announced last week is a great example of that and you're going to see many more partnerships like this going forward that are reflective of exactly this point. >> You've been a visionary on the product side, interviewed before. Also deploying is more important than ever, that whole workflow simplifying, it's not getting complex, people want choice, building code, managing code, deploying code. This has been a big focus of yours. Can you just share your thoughts on where Microsoft comes in? Because they got stuff too, you've got stuff, it all works together. What's your thoughts? >> Right, so it needs to work together because developers want to focus on their app. They don't want to focus on duct taping and stringing together different siloed pools. So you can see in the demo and you'll see in demonstrations later throughout the conference, just the seamless experience that a developer gets in the Docker command line inner operating with Visual Studio Code, with the Docker command line and then deploying to Azure and what's wonderful about the partnership is that both parties put real engineering effort and design effort into making it a great experience. So a lot of the complexities around configuration, around default settings, around security, user management, all of that is abstracted out and taken away from the developers so they can focus on applications and getting those applications deployed to the cloud as quickly as possible. Getting their apps from code to cloud is the watchword or the call to action for this partnership and we think we've really hit it out of the park with the integration that you saw. >> Great validation in the critical part of the workflow you guys been part of. Amanda, we're living in a time we're doing these remote interviews. The COVID crisis has shown the productivity gains of working at home and working, sheltering in place but it also has highlighted the focus of developers, mainly who have also worked at home. They're been kind of used to this, you see the rigs. I saw at Microsoft build some amazing rigs from the studio, so these guys streaming their code demos. This is a Cambrian explosion of new kinds of productivity. You got the world's getting more complex at scale. This is what cloud does. What's your thoughts on this? 'Cause the tooling, there's more tools than ever, right? >> Yeah. >> I still got to deploy code. It's got to be more agile, it's got to be faster, it's got to be at scale. This is what you guys believe in. What's your thinking on all these tooling and abstraction layers? And the end of the day, developers still got to do their job. >> Yeah, well, absolutely. And now even more than ever, I think we've certainly seen over the past few months, a more rapid acceleration of digital transformation that has really happened in the past few years. Paper processes are now becoming digital processes all of a sudden. Everybody needs to work and learn from home and so there's just this rapid acceleration to kind of move everything to support our new remote first lifestyle. But even more so, we now have remote development teams actually working from home as well in a variety of different kinds of environments, whether they're using their own personal machine to connect to their infrastructure or they're using a work issued machine. It's more important than ever that developers are productive but they are productive as a team. Software is a team sport, we all need to be able to work together and to be able to collaborate. And one of the most important aspects of agility for developers is consistency. And what Docker really enables with containerization, is to make the infrastructure consistent and repeatable so that as developers are moving through the lifecycle from their local desktop and developing on their local desktop, to a test environment and to staging and to production, it's really, it's infrastructure for developers as well as operations. And so, that infrastructure, that's completely customizable for what the developers operating system of choice is, what their app stack is, all of those dependencies kind of running together. And so that's what really enables developers to be really agile and have a really fast iteration cycle but also to have that consistency across all of their development team. And we now need to think about things like, how are we actually going to bring on interns for the summer and make sure that they can actually set up their developer boxes in a consistent way that we can actually support them and things like Docker really help with that. >> As your container instances and Visual Studio cloud that you guys have has had great success. There's a mix and match formula here and the other day, developers want to ship the code. What's the message that you guys are sending here with this because I think productivity is one, simplification is the other but as developers, we're on the front lines and they're shipping in real time. This is a big part of the value proposition that you guys bringing to the table. >> Yeah, the core message is that any developer and their code is welcome (laughs) and that we really want to support them, empower them and increase their velocity and the impact that they can have. And so, having things like the fact that the Docker CLI is natively integrated into the Azure experience is a really important aspect of making sure that developers are feeling welcome and feeling comfortable. And now that the Docker CLI tools that are part of Docker desktop have access to native commands that work well with Azure container instances, Azure container instances, if anybody is unfamiliar with that, is the simplest and fastest way to kind of set up containers in Azure and so we believe that developers have really been looking for a really simple way to kind of get containers on Azure and now we have that really consistent experience across our servers, services and our tools. Visual Studio code and Visual Studio extensions make full use of Docker desktop and the Docker CLI so that they can get that combination of the productivity and the power that they're looking for. And in fact, we've integrated these as a design point since very early on in our partnership when we've been partnering with Docker for quite a while. >> Amanda, I want to ask you about the tool chain. We've heard about workflows, making it simpler. Bottom line from a developer standpoint, what's the bottom line for me? What does this mean to me, everyday developer out there? >> I really think it means, your productivity on your terms. And so, Microsoft has been a developer company since the very beginning with Bill Gates and GW Basic. And it's actually similar for Docker. They really have a developer first point of view, which certainly speaks to my heart and so one of the things that we're really trying to do with Docker is to make sure that we can create a workflow that's super productive at every stage of the developer experience, no matter which stack they're actually targeting, whether there's targeting Node or Python, or dotNET and C Sharp or Java, we really want to make sure that we have a super simple experience that you can actually initiate all of these commands, create Docker container images and use the Docker compose files. And then, just kind of do that consistently, as you're deploying it all the way up into your infrastructure in Azure. And the other thing that we really want to make sure is that that even post deployment, you can actually inspect and diagnose these containers and images without having to leave the tool. So we also think about the process of writing the code but also the process of kind of managing the code and remediating issues that might come up in production. And so we really want you to be able to look at containers up in the Azure, that are deployed into Azure and make sure that they're running and healthy and that if something's wrong, that you can actually open up a shell and be in an interactive mode and be able to look at the logs from those containers and even inspect one to see environment variables or other details. >> Yeah, that's awesome. Writing code, managing code and then you got to deploy, right? So what I've been loving about the past generation of Agile is deployment's been faster to play off all the time. Scott, this brings up that the ease of use but you'll want to actually leverage automation. This is the trend that you want to get into. You want to make it easy to write code, manage code but during the deployment phase, that's a big innovation. That's the last point, making that better and stronger. What's your thoughts on simplifying that? >> Well, as a big part of this partnership, John, that Docker and Microsoft embarked on, as you saw from the demo in the keynote, all within the Docker command line, the developer's able to do it in two simple commands, deploy an app, define and compose from their desktop to Azure. And there's a whole slew of automation and pre-configured smart defaults or sane defaults that have gone on behind the scenes and it a lot of hardcore engineering work on part of Docker-Microsoft together to simplify that and make that easy. And that goes exactly to your point, which is, the simpler you can make it, make an abstract way to kind of underline plumbing and infrastructure, the faster Devs can get their application from code to cloud. >> Scott, you've been a product CEO, you've been a product person now you're the CEO but you have a product back when you've been involved with a relationship with Microsoft for a long time. What's the state of the market right now? I see Microsoft has evolved because just the performance, corporate performance, the shift to the cloud has been phenomenal. Now developers getting more empowered, there's more demand for the pressure to put developers to do more and more creativity. So you've seen this evolve, this relationship, what does it mean? >> Yeah, it's honestly a wonderful question, John and I want to thank Amanda and the entire Microsoft team for being long standing partners with us on this journey. So it might not be known to everyone on today's day's event but Microsoft came to the very first Dockercon event way back in June 2014 and I had the privilege of greeting them and welcoming them and then they were full on, ready to see what all the excitement about Docker was about and really embraced it. And you mentioned kind of openness in Microsoft's growth over time in that dimension and we think Docker, together with Microsoft have really shown what an open developer community can do. That started back in 2014 and then we embarked on an open source collaboration around the Docker command line of the Docker engine, bringing that Docker engine from Linux and now moving it to Windows applications. And so all the sudden the promise of write once and use the same primitives, the same formats, the same command lines, as you can with Linux onto Windows applications, we brought that promise to the market. And it's been an ongoing journey together with Microsoft on open standards base, developer facing friendliness, ease of use, fast time to deploy and this partnership that we announced yesterday and we highlighted at the keynote is just another example of that ongoing relationship, laser-like focused on developer productivity and helping teams build great apps. >> Why do you like Azure in the cloud for Docker? Can you share why? >> Well, as Amanda has been sharing, it's super focused on, what are the needs of developers to help them continue to stay focused on their apps and not have their cognitive load burdened by other aspects of getting their apps to the cloud and Azure does a phenomenal job of simplifying and providing sane defaults out of the box. And as we've been talking about, it's also very open to partner integrations like the one we've announced yesterday and highlighted that make it just easy for development teams to choose their tools and build their apps and deploy them onto Azure as quickly as possible. So it's a phenomenal platform for developers and we're very excited and proud to partner with Microsoft on it. >> Amanda on your side, I see Docker's got millions of developers. you guys got millions of developers even more. How do you see the developers in Microsoft's side engaging with Docker desktop and Docker hub? Where does it all fit? I mentioned earlier how I see Docker context really improving the way that individuals and teams work with their environments in making sure that they're consistent but I think this really comes together as we work with Docker desktop and Docker Hub. When developers sign in to Docker Hub from Docker desktop, everything kind of lights up and so they can see all of the images in their repositories and they can also see the cloud environments that they're running them in. And so, once you sign into the Hub, you can see all the contexts that map to the logical environments they have access to, like Dev, NQA and maybe staging. And another use case that's really important is that we can access the same integration environment. So, I can have microservices that I've been working on but I can also see microservices that my teammates and their logs from the services that they've been working on, which I think is really great and certainly helps with team productivity. The other thing too, is that this also really helps with hybrid cloud deployments, where, you might have some on-premises hosted containers and you might have some that's hosted in a public cloud. And so you can see all of those things through your Docker Hub. >> Well, I got to say, I love the code to cloud tagline, I think that's very relevant and catchy. And I think, I guess to me what I'm seeing and I'd love to get your thoughts, Amanda on this is you oversee a key part of Microsoft's business that's important for developers, just the vibe and people are amped up right now. I know people are tensed, anxiety with the COVID-19 crisis but I think people are generally agreeing that this is going to be a massive inflection point for just more headroom needed for developers to accelerate their value on the front lines. What's your personal take on this? You've seen these waves before but now in this time, what are you most excited about? What are you optimistic about? What's your view on the opportunities? Can you share your thoughts, because people are going to get back to work. They're working now remotely but if we go back to hybrid world, they're going to be jamming on projects. >> Yeah, for sure but people are jamming on projects right now and I think that in a lot of ways, developers are first responders in that they are... Developers are always trying to support somebody else. We're trying to support somebody else's workflow and so we have examples of people who are creating new remote systems to be able to schedule meetings in hospitals for the doctors who are actually the first responders taking care of patients but at the end of the day, it's the developer who's actually creating that solution. And so we're being called to duty right now and so we need to make sure that we're actually there to support the needs of our users and that we're basically cranking on code as fast as we can. And to be able to do that, we have to make sure that every developer is empowered and they can move quickly but also that they can collaborate really quickly. And so I think that Docker Hub, Docker kind of helps you ensure that you have that consistency but you also have that connection to the infrastructure that's hosted by your your organization. >> I think you nailed, that's amazing insight. I think that's... The current situation in the community matters because there's a lot of frontline work being done to your point but then we got to rebuild, the modernization is happening as well coming out of this so there's going to be that. And there's a lot of camaraderie going on and massive community involvement I'm seeing more of. The empathy but also now there's going to be the building, the creation, the new creation. So, Scott, this is going to call for more simplicity and to abstract away the complexities. This is the core issue. >> Well, that's exactly right. And it is time to build and we're going to build our way out of this and it is the community that's responding. And so in some sense, Microsoft and Docker are there to support that moory energy and give them the tools to go and identify and have an impact as quickly as possible. I referenced in the keynote, completely bottoms up organic adoption of Docker desktop and Docker Hub in racing to provide solutions against the COVID-19 virus. It's a war against this pandemic that is heavily dependent on applications and data. And there's over 200 projects, community projects on Docker Hub today, where you've got tools and containers and data analysis all in service to the COVID-19 battle that's being fought. And then as you said, John, as we get through the other side, there's entire industries that are completely rethinking their approach that were largely offline before but now see the imperative and the importance of going online. And that tectonic shift, nearly overnight of offline to online behavior and commerce and social and going down the list, that requires new application development. And I'm very pleased about this partnership is that together, we're giving developers the tools to really take advantage of that opportunity and go and build our way out of it. >> Well, Scott, congratulations on a great extended partnership with Microsoft and the Docker brand. I'm a big fan from day one. I know you guys have pivoted on a new trajectory, which is phenomenal, very community oriented, very open source, very open. So congratulations on that. Amanda, thanks for spending the time to come on. I'll give you the final word. Take a minute to talk about what's new at Microsoft for the folks that know Microsoft, know they have a developer mindset from day one. Cloud is exploding, code to cloud. What's the update? What's the new narrative? What should people know about Microsoft with developer community? Can you share some data for the folks that aren't in the community or might want to join or the folks in the community who want to get an update? >> Yeah, it's a great kind of question. Right now, I think we are all really focused on making sure that we can empower developers throughout the world and that includes both those who are building solutions for their organizations today but also, I think we're going to end up with a ton of new developers over this next period, who are really entering the workforce and learning to create digital solutions. Overall, there's a massive developer shortage across the world. There's so much opportunity for developers to kind of address a lot of the needs that we're seeing out of organizations, again, across the world. And so I think it's just a really exciting time to be a developer and my only hope is that basically we're building tools that actually enable them to solve the problem. >> Awesome insight, and thank you so much for your time. Code to cloud developers are cranking away, they're the first responders, going to take care of business and then continue to build out the modern applications. And when you have a crisis like this, people cut right through the noise and get right to the tools that matter. So thanks for sharing the Microsoft-Docker partnership and the things that you guys are working on together. Thanks for your time. >> Thank you. >> Thank you. >> Okay, this is theCUBE's coverage. We are at Dockercon 2020 Digital. This is theCUBE Virtual. I'm John Furrier, bringing all the action, more coverage. Stay with us for more Dockercon Virtual after this short break. (gentle music)

>>From around the globe. It's the view with digital coverage of Docker con live 2020 brought to you by Docker and its ecosystem partners. >>LeBron. Welcome back to DockerCon 2020 hashtag Docker 20 this is the cube and Dockers coverage of Docker con 20 I'm Sean for you and the Palo Alto studios with our quarantine crew. We've got a great interview segment here in big news around developer workflow code to cloud. We've got Amanda silver corporate vice president, product for developer tools at Microsoft and Scott Johnson, the CEO of Docker. Scott had a great keynote talking about this relationship news has hit about the extension of the Microsoft partnership. So congratulations Amanda. Welcome to the cube. >>Thanks for having me. >>Amanda, tell us a bit about what your role is at Microsoft. You guys are well known in the developer community to develop an ecosystem when even when I was in college going way back, very modern. Now cloud is, is the key code to cloud. That's the theme. Tell us about your role at Microsoft. >>Yeah. So I basically run the product, uh, product design and user research team that works on our developer tools that Microsoft and so that includes the visual studio product as well as visual studio code. Um, that's become pretty popular in the last few years, but it also includes things like the.net runtime and the TypeScript programming language as well as all of our Azure tooling. >>What's your thoughts on the relationship with Docker? I'll show you the news extension of an existing relationship. Microsoft's got a lot of tools. You've got a lot of things you guys are doing, bringing the cloud to every business. Tell us about your thoughts on this relationship with Donker. >>Yeah, well we're very excited about the partnership for sure. Um, you know, our goal is really to make sure that Azure is a fantastic place where all developers can kind of bring their code and they feel welcome. They feel natural. Uh, we really see a unique opportunity to make the experience really great for Docker, for the Docker community by creating more integrated and seamless experience across Docker, desktop windows and visual studio. And we really appreciate how, how Docker is kind of, you know, supported our windows ecosystem to run in Docker as well. >>Scott, this relationship and an extension with Microsoft is really, uh, I think impressive and also notable because Microsoft's got so many, so many tools out there and they have so successful with Azure. You guys have been so successful with your developer community, but this also is reflective of the new Docker. Uh, could you share your thoughts on how this partnership with Microsoft extending the way it is with the growth of the cloud is a reflection of the new Docker? >>Yeah, absolutely. John's great question. One of the things that we've really been focused on since November is fully embracing the ecosystem and all the partnerships and all the possibilities of that ecosystem. And part of that is just reality. That we're a smaller company now and we can't do it all, nor should we do it all. Part of us. The reality that developers love voice and no one's gonna change their minds on choice. And third is just acknowledging that there's so much creativity and so much energy. The four walls of Docker that we'd be building, not the big advantage of that and welcome it and embrace it and provide that as a phenomenal experience part of Alfred's. So this is a great example of that. The sneak partnership we announced last week is a grant to have that and you're going to see many more of uh, partnerships like this going forward that are reflective of exactly this point. >>You've been a visionary on the product side of the interviewed before. Also deploying is more important than ever. That whole workflow, simplifying, it's not getting complex. People want choice, building code, managing code, deploying code. This has been a big focus of yours. Can you just share your thoughts on where Microsoft comes in because they got stuff too. You've got stuff, it all works together. What's your thoughts? >>Right? So it needs to work together, right? Because developers want to focus on their app. They don't want to focus on duct taping and springing together different siloed pools, right? So you can see in the demo and you'll see in, uh, demonstrations later throughout the conference. Just the seamless experience that a developer gets in the document man line inter-operating with visual studio code with the Docker command line and then deploying to Azure and what's what's wonderful about the partnership is that both parties put real engineering effort and design effort into making it a great experience. So a lot of the complexities around the figuration around default settings around uh, security, user management, all of that is abstracted out and taken away from the developer so they can focus on applications and getting those applications deployed to the proudest quickly as possible. Getting their app from code to cloud is the wok word or the or the call to action for this partnership. And we think we really hit it out of the park with the integration that you saw, >>Great validation and a critical part of the workflow. You guys have been part of Amanda, we're living in a time we're doing these remote interviews. The coven crisis has shown the productivity gains of working at home and working in sheltering in place, but also as highlighted, the focus of developers mainly who have also worked at home. They've kind of used to this. Do you see the rigs? I saw her at Microsoft build some amazing rigs from the studio. So these guys streaming their code demos. This is, um, a Cambrin explosion of new kinds of productivity. And yet the world's getting more complex at scale. This is what cloud does. What's your thoughts on this? Cause the tooling is more tools than ever, right? So I still gotta deploy code. It's gotta be more agile. It's gotta be faster. It's gotta be at scale. This is what you guys believe in. What's your thinking on all these tooling and abstraction layers and the end of the day, don't you still got to do their job? >>Yeah, well, absolutely. And now, even more than ever. I mean, I think we've, we've certainly seen over the past few months, uh, uh, a more rapid acceleration of digital transformation. And it's really happened in the past few years. Uh, you know, paper processes are now becoming digit digital processes. All of a sudden, you know, everybody needs to work and learn from home. And so there's just this rapid acceleration to kind of move everything to support our new remote lifestyle. Um, but even more so, you know, we now have remote development teams actually working from home as well in a variety of different kinds of, uh, environments. Whether they're using their own personal machine to connect to their infrastructure or they're using a work issued machine. You know, it's more important than ever that developers are productive, but they are productive as a team. Right? Software is a team sport. >>We all need to be able to work together and to be able to collaborate. And one of the most important aspects of agility for developers is consistency. And, uh, what Docker really enables is, uh, with, with containerization is to make the infrastructure consistent and repeatable so that as developers are moving through the life cycle from their local, local dev desktop and developing on their local desktop to a test environment and to staging and to production, it's really, it's infrastructure of or, or developers as well as operations. And so it's that, that infrastructure that's completely customizable for what the developer's operating system of choices, what their app stack is, all of those dependencies kind of running together. And so that's what really enables developers to be really agile and have a really, really fast iteration cycle but also to have that consistency across all of their development team. And you know, we, we now need to think about things like how are we actually going to bring on interns for the summer, uh, and make sure that they can actually set up their developer boxes in a consistent way that we can actually support them. And things like Docker really helped with that >>As your container instances and a visual studio cloud that you guys have has had great success. Um, there's a mix and match formula here. At the end of the day, developers want to ship the code. What's the message that you guys are sending here with this? Because I think productivity is one, simplification is the other, but as developers on the front lines and they're shipping in real time, this is a big part of the value proposition that you guys are bringing to the table. >>Yeah, I mean the, the core message is that any developer and their code is welcome, uh, and that we really want to support them and power them and increase their velocity and the impact that they can have. Um, and so, you know, having things like the fact that the Docker CLI is natively integrated into the Azure experience, uh, is a really important aspect of making sure that developers are feeling welcome and feeling comfortable. Um, and now that the Docker CLI tools are, that are part of Docker desktop, have access to native commands that work well with Azure container instances. Uh, Azure container instances, if anybody's on familiar with that, uh, is the simplest and fastest way to kind of set up containers and Azure. And, and so we believe that developers have really been looking for a really simple way to kind of get containers on Azure. And now we that really consistent experience across our service services and our tools and visual studio code and visual studio extensions make full use of Docker desktop and the Docker CLI so that they can get that combination of the productivity and the power that they're looking for. And in fact, we've, we've integrated these as a design point since very early on in our partnership when we've been partnering with, with Docker for quite a while. >>Amanda, I want to ask you about the, the, the, the tool chain. We've heard about workflows, making it simpler, bottom line, from a developer standpoint, what's the bottom line for me? What does this mean to me? Uh, every day developer out there? >>Um, I, I mean, I really think it means you know, your productivity on your terms. Um, and so, you know, Microsoft has been a developer company since the very, very beginning with, you know, bill Gates and, and, uh, GW basic. Um, and it's actually similar for Docker, right? They really have a developer first point of view, uh, which certainly speaks to my heart. And so one of the things that we're really trying to do with, with Docker is to make sure that we can create a workflow that's super productive at every stage of the developer experience, no matter which stack they're actually targeting, whether there's targeting node or Python or.net and C-sharp or Java. Uh, we really want to make sure that we have a super simple experience that you can actually initiate all of these commands, create, you know, Docker container images and use the compose Docker compose files. >>Um, and then, you know, just kind of do that consistently as you're deploying it all the way up into your infrastructure in Azure. And the other thing that we really want to make sure is that that even post deployment, you can actually inspect and diagnose these containers and images without having to leave the tool. Um, so we, we also think about the process of writing the code, but also the process of kind of managing the code and remediating issues that might come up in production. And so, you know, we really want you to be able to look at containers up in the Azure. Uh, up that are deployed into Azure and make sure that they're running and healthy and that if there, if something's wrong, that you can actually open up a shell and be in an interactive mode and be able to look at the logs from those containers and even inspect when to see environment variables or other details. >>Yeah, that's awesome. You know, writing code, managing code, and then you've got to deploy, right? So what I've been loving about the, the past generation of agile is deployment's been fast to deploy all the time. Scott, this brings up that the ease of use, but you want to actually leverage automation. This is the trend that you want to get in. You want, you don't want, you want to make it easy to write code, manage code. But during the deployment phase, that's a big innovation. That's the last point. Making that better and stronger. What's your thoughts on simplifying that? >>So that was a big part of this partnership, John, that the Docker in Microsoft embarked on and as you saw from the demo and the keynote, um, all within the man line, the developers able to do in two simple commands, deploy an app, uh, defining compose from the desktop to Azure and there's a whole slew of automation and pre-configured smart defaults or sane defaults that have gone on behind the scenes and that took a lot of hardcore engineering work on part of Docker and Microsoft together to simplify that and make that easy and that, that goes exactly to your point. We just like the simpler you can make it more, you can abstract a way to kind of underlying plumbing and infrastructure. The faster devs can get there. Their application from code to cloud. >>Scott, you've been a product CEO, you've been a product person, a CEO, but you have a product background. You've been involved with the relationship with Microsoft for a long time. What's the state of the market right now? I mean, obviously Microsoft has evolved. Look at just the performance corporate performance. The shift to the cloud has been phenomenal. Now developers getting more empowered, there's more demand for the pressure to put on developers to do more and more, more creativity. So you've seen this evolve, this relationship, what does it mean? >>Yeah, it's honestly a wonderful question, John. And I want to thank Amanda and the entire Microsoft team for being long standing partners with us on this journey. So it's might not be known to everyone on today's, uh, day's event. But Microsoft came to the very first Docker con event, uh, way back in June, 2014 and I had the privilege of, of reading them and welcoming them and they're, they were full on ready to see what all the excitement about Docker was about and really embrace it. And you mentioned kind of openness and Microsoft's growth over that, uh, over time in that dimension. And we think kind of Docker together with Microsoft have really shown what an open developer community can do. And that started back in 2014 and then we embarked on an open source collaboration around the Docker command line of the Docker engine, bringing that Docker engine from Linux and now moving it to windows applications. And so all of a sudden the promise of right ones and use the same primitives, the same formats, the same fan lines, uh, as you can with Linux onto windows applications. We brought that promise to the market and it's been an ongoing journey together with Microsoft of open standards based, developer facing friendliness, ease of use, fast time to deploy. And this, this partnership that we announced yesterday and we highlighted at the keynote is just another example of that ongoing relationship laser like focused on developer productivity and helping teams build great apps. >>Why do you like Azure in the cloud for Docker? Can you share why? >>Well, it's as Amanda has been sharing, it's super focused on what are the needs of developers to help them continue to stay focused on their apps and not have their cognitive load burdened by other aspects of getting their apps to the cloud. And Azure, phenomenal job of simplifying and providing sane defaults out of the box. And as we've been talking about, it's also very open to partner like the one we've announced >>Yesterday and highlighted, you know, but >>Uh, make it just easy for development teams to choose their tools and build their apps and deploy them onto Azure. It's possible. So, uh, it's, it's a phenomenal plan, one for developers and we're very excited and proud of partner with Microsoft on it. >>Amanda, on your side, I see DACA has got millions of developers. You guys got millions of developers even more. How do you see the developers in Microsoft side engaging with Docker desktop and Docker hub? Where does it all fit? >>I think it's a great question. I mean, I mentioned earlier how the Docker context can help individuals and teams kind of work in their environments work. Let me try that over. I mentioned earlier how I, how I see Docker context really improving the way that individuals and teams work with their environments and making sure that they're consistent. But I think this really comes together as we work with Docker desktop and Docker hub. Uh, when developers sign into Docker hub from Docker desktop, everything kind of lights up. And so they can see all of the images in their repositories and they can also see the cloud environments they're running them in. And so, you know, once you sign into the hub, you can see all the contexts that map to the logical environments that they have access to like dev and QA and maybe staging. And another use case that's really important is that, you know, we can access the same integration environment. >>So, so I could have, you know, microservices that I've been working on, but I can also see microservices that my, my teammates and their logs, uh, from the services that they've been working on, which I think is really, really great and certainly helps with, with team productivity. The other thing too is that this also really helps with hybrid cloud deployments, right? Where, you know, you might have some on premises, uh, hosted containers and you might have some that's hosted in a public cloud. And so you can see all of those things, uh, through your Docker hub. >>Well, I got to say I love the code to cloud tagline. I think that's very relevant and, and catchy. Um, and I think, I guess to me what I'm seeing, and I'd love to get your thoughts, Amanda, on this, as you oversee a key part of Microsoft's business that's important for developers, just the vibe and people are amped up right now. I know people are tense and anxiety with the covert 19 crisis, but I think people are generally agreeing that this is going to be a massive inflection point for just more headroom needed for developers to accelerate their value on the front lines. What's your personal take on this and you've seen these ways before, but now in this time, what are you most excited about? What are you optimist about? What's your view on the opportunities? Can you share your thoughts? Because people are going to get back to work or they're working now remotely, but when we go back to hybrid world, they're going to be jamming on projects. >>Yeah, for sure. But I mean, people are jamming on projects right now. And I think that, you know, in a lot of ways, uh, developers are our first responders in, you know, in that they are, developers are always trying to support somebody else, right? We're trying to somebody else's workflow and you know, so we have examples of people who are, uh, creating new remote systems to be able to, uh, schedule meetings in hospitals or the doctors who are actually the first, first responders taking care of patients. But at the end of the day, it's the developer who's actually creating that solution, right? And so we're being called the duty right now. Um, and so we need to make sure that we're actually there to support the needs of our users and that we're, we're basically cranking on code as fast as we can. Uh, and to be able to do that, we have to make sure that every developer is empowered and they can move quickly, but also that they can collaborate freely. And so, uh, I think that, you know, Docker hub Docker kind of helps you ensure that you have that consistency, but you also have that connection to the infrastructure that's hosted by your, your organization. >>I think you nailed that amazing insight. And I think that's, you know, the current situation in the community matters because there's a lot of um, frontline work being done to your point. But then we've got to rebuild. The modernization is happening as well coming out of this. So there's going to be that and there's a lot of comradery going on and massive community involvement. I'm seeing more of, you know, the empathy, but also now there's going to be the building, the creation, the new creation. So Scott, this is going to call for more simplicity and to abstract away the complexities. This is the core issue. >>Well that's exactly right and it is time to build, right? Um, and we're going to build our way out of this. Um, and it is the community that's responding. And so in some sense, Microsoft and Docker are there to support that, that community energy and give them the tools to go. And identify and have an impact as quickly as possible. We have referenced in the keynote, um, completely bottoms up organic adoption of Docker desktop and Docker hub in racing to provide solutions against the COBIT 19 virus. Right? It's a, it's a war against this pandemic that is heavily dependent on applications and data and there's over 200 projects, community projects on Docker hub today where you've got uh, cools and containers and data analysis all in service to the photo at 19 battle that's being fought. And then as you said, John, as we, as we get through this, the other side, there's entire industries that are completely rethinking their approach that were largely offline before that. Now see the imperative and the importance of going online and that tectonic shift nearly overnight of offline to online behavior and commerce and social and go on down the list that requires new application development. And I'm very pleased about this partnership is that together we're giving developers the tools to really take advantage of that opportunity and go and build our way out of it. >>Well, Scott, congratulations on a great extended partnership with Microsoft and the Docker brand. You know, I'm a big fan of from day one. I know you guys have pivoted on a new trajectory which is very community oriented, very open source, very open. So congratulations on that Amanda. Thanks for spending the time to come on. I'll give you the final word. Take a minute to talk about what's new at Microsoft. For the folks that know Microsoft, know they have a developer mindset from day one cloud is exploding code to cloud. What's the update? What's the new narrative? What should people know about Microsoft with developer community? Can you share from some, some, some uh, data for the folks that aren't in the community or might want to join with folks in the community who want to get an update? >>Yeah, it's a, it's a great, great kind of question. I mean, you know, right now I think we are all really focused on making sure that we can empower developers throughout the world and that includes both those who are building solutions for their organizations today. But also I think we're going to end up with a ton of new developers over this next period who are really entering the workforce and uh, and learning to create, you know, digital solutions overall. There's a massive developer shortage across the world. Um, there's so much opportunity for developers to kind of, you know, address a lot of the needs that we're seeing out of organizations again across the world. Um, and so I think it's just a really exciting time to be a developer. Uh, and you know, my, my uh, my only hope is that basically we're, we're building tools that actually enable them to solve problems. >>Awesome insight and thank you so much for your time code to cloud developers are cranking away that the first responders are going to take care of business and then continue to build out the modern applications. And when you have a crisis like this, people cut right through the noise and get right to the tools that matter. So thanks for sharing the Microsoft Docker partnership and the things that you guys are working on together. Thanks for your time. Okay. This is the cubes coverage. We are Docker con 2020 digital is the cube virtual. I'm Sean for bringing all the action. More coverage. Stay with us for more Docker con virtual. After this short break.

(upbeat music) >> Announcer: It's theCUBE covering the virtual Vertica Big Data Conference 2020 brought to you by Vertica. >> Welcome back to the Vertica Virtual Big Data Conference, BDC 2020. You know, it was supposed to be a physical event in Boston at the Encore. Vertica pivoted to a digital event, and we're pleased that The Cube could participate because we've participated in every BDC since the inception. Rich Gaston this year is the global solutions architect for security risk and governance at Micro Focus. Rich, thanks for coming on, good to see you. >> Hey, thank you very much for having me. >> So you got a chewy title, man. You got a lot of stuff, a lot of hairy things in there. But maybe you can talk about your role as an architect in those spaces. >> Sure, absolutely. We handle a lot of different requests from the global 2000 type of organization that will try to move various business processes, various application systems, databases, into new realms. Whether they're looking at opening up new business opportunities, whether they're looking at sharing data with partners securely, they might be migrating it to cloud applications, and doing migration into a Hybrid IT architecture. So we will take those large organizations and their existing installed base of technical platforms and data, users, and try to chart a course to the future, using Micro Focus technologies, but also partnering with other third parties out there in the ecosystem. So we have large, solid relationships with the big cloud vendors, with also a lot of the big database spenders. Vertica's our in-house solution for big data and analytics, and we are one of the first integrated data security solutions with Vertica. We've had great success out in the customer base with Vertica as organizations have tried to add another layer of security around their data. So what we will try to emphasize is an enterprise wide data security approach, where you're taking a look at data as it flows throughout the enterprise from its inception, where it's created, where it's ingested, all the way through the utilization of that data. And then to the other uses where we might be doing shared analytics with third parties. How do we do that in a secure way that maintains regulatory compliance, and that also keeps our company safe against data breach. >> A lot has changed since the early days of big data, certainly since the inception of Vertica. You know, it used to be big data, everyone was rushing to figure it out. You had a lot of skunkworks going on, and it was just like, figure out data. And then as organizations began to figure it out, they realized, wow, who's governing this stuff? A lot of shadow IT was going on, and then the CIO was called to sort of reign that back in. As well, you know, with all kinds of whatever, fake news, the hacking of elections, and so forth, the sense of heightened security has gone up dramatically. So I wonder if you can talk about the changes that have occurred in the last several years, and how you guys are responding. >> You know, it's a great question, and it's been an amazing journey because I was walking down the street here in my hometown of San Francisco at Christmastime years ago and I got a call from my bank, and they said, we want to inform you your card has been breached by Target, a hack at Target Corporation and they got your card, and they also got your pin. And so you're going to need to get a new card, we're going to cancel this. Do you need some cash? I said, yeah, it's Christmastime so I need to do some shopping. And so they worked with me to make sure that I could get that cash, and then get the new card and the new pin. And being a professional in the inside of the industry, I really questioned, how did they get the pin? Tell me more about this. And they said, well, we don't know the details, but you know, I'm sure you'll find out. And in fact, we did find out a lot about that breach and what it did to Target. The impact that $250 million immediate impact, CIO gone, CEO gone. This was a big one in the industry, and it really woke a lot of people up to the different types of threats on the data that we're facing with our largest organizations. Not just financial data; medical data, personal data of all kinds. Flash forward to the Cambridge Analytica scandal that occurred where Facebook is handing off data, they're making a partnership agreement --think they can trust, and then that is misused. And who's going to end up paying the cost of that? Well, it's going to be Facebook at a tune of about five billion on that, plus some other finds that'll come along, and other costs that they're facing. So what we've seen over the course of the past several years has been an evolution from data breach making the headlines, and how do my customers come to us and say, help us neutralize the threat of this breach. Help us mitigate this risk, and manage this risk. What do we need to be doing, what are the best practices in the industry? Clearly what we're doing on the perimeter security, the application security and the platform security is not enough. We continue to have breaches, and we are the experts at that answer. The follow on fascinating piece has been the regulators jumping in now. First in Europe, but now we see California enacting a law just this year. They came into a place that is very stringent, and has a lot of deep protections that are really far-reaching around personal data of consumers. Look at jurisdictions like Australia, where fiduciary responsibility now goes to the Board of Directors. That's getting attention. For a regulated entity in Australia, if you're on the Board of Directors, you better have a plan for data security. And if there is a breach, you need to follow protocols, or you personally will be liable. And that is a sea change that we're seeing out in the industry. So we're getting a lot of attention on both, how do we neutralize the risk of breach, but also how can we use software tools to maintain and support our regulatory compliance efforts as we work with, say, the largest money center bank out of New York. I've watched their audit year after year, and it's gotten more and more stringent, more and more specific, tell me more about this aspect of data security, tell me more about encryption, tell me more about money management. The auditors are getting better. And we're supporting our customers in that journey to provide better security for the data, to provide a better operational environment for them to be able to roll new services out with confidence that they're not going to get breached. With that confidence, they're not going to have a regulatory compliance fine or a nightmare in the press. And these are the major drivers that help us with Vertica sell together into large organizations to say, let's add some defense in depth to your data. And that's really a key concept in the security field, this concept of defense in depth. We apply that to the data itself by changing the actual data element of Rich Gaston, I will change that name into Ciphertext, and that then yields a whole bunch of benefits throughout the organization as we deal with the lifecycle of that data. >> Okay, so a couple things I want to mention there. So first of all, totally board level topic, every board of directors should really have cyber and security as part of its agenda, and it does for the reasons that you mentioned. The other is, GDPR got it all started. I guess it was May 2018 that the penalties went into effect, and that just created a whole Domino effect. You mentioned California enacting its own laws, which, you know, in some cases are even more stringent. And you're seeing this all over the world. So I think one of the questions I have is, how do you approach all this variability? It seems to me, you can't just take a narrow approach. You have to have an end to end perspective on governance and risk and security, and the like. So are you able to do that? And if so, how so? >> Absolutely, I think one of the key areas in big data in particular, has been the concern that we have a schema, we have database tables, we have CALMS, and we have data, but we're not exactly sure what's in there. We have application developers that have been given sandbox space in our clusters, and what are they putting in there? So can we discover that data? We have those tools within Micro Focus to discover sensitive data within in your data stores, but we can also protect that data, and then we'll track it. And what we really find is that when you protect, let's say, five billion rows of a customer database, we can now know what is being done with that data on a very fine grain and granular basis, to say that this business process has a justified need to see the data in the clear, we're going to give them that authorization, they can decrypt the data. Secure data, my product, knows about that and tracks that, and can report on that and say at this date and time, Rich Gaston did the following thing to be able to pull data in the clear. And that could be then used to support the regulatory compliance responses and then audit to say, who really has access to this, and what really is that data? Then in GDPR, we're getting down into much more fine grained decisions around who can get access to the data, and who cannot. And organizations are scrambling. One of the funny conversations that I had a couple years ago as GDPR came into place was, it seemed a couple of customers were taking these sort of brute force approach of, we're going to move our analytics and all of our data to Europe, to European data centers because we believe that if we do this in the U.S., we're going to violate their law. But if we do it all in Europe, we'll be okay. And that simply was a short-term way of thinking about it. You really can't be moving your data around the globe to try to satisfy a particular jurisdiction. You have to apply the controls and the policies and put the software layers in place to make sure that anywhere that someone wants to get that data, that we have the ability to look at that transaction and say it is or is not authorized, and that we have a rock solid way of approaching that for audit and for compliance and risk management. And once you do that, then you really open up the organization to go back and use those tools the way they were meant to be used. We can use Vertica for AI, we can use Vertica for machine learning, and for all kinds of really cool use cases that are being done with IOT, with other kinds of cases that we're seeing that require data being managed at scale, but with security. And that's the challenge, I think, in the current era, is how do we do this in an elegant way? How do we do it in a way that's future proof when CCPA comes in? How can I lay this on as another layer of audit responsibility and control around my data so that I can satisfy those regulators as well as the folks over in Europe and Singapore and China and Turkey and Australia. It goes on and on. Each jurisdiction out there is now requiring audit. And like I mentioned, the audits are getting tougher. And if you read the news, the GDPR example I think is classic. They told us in 2016, it's coming. They told us in 2018, it's here. They're telling us in 2020, we're serious about this, and here's the finds, and you better be aware that we're coming to audit you. And when we audit you, we're going to be asking some tough questions. If you can't answer those in a timely manner, then you're going to be facing some serious consequences, and I think that's what's getting attention. >> Yeah, so the whole big data thing started with Hadoop, and Hadoop is open, it's distributed, and it just created a real governance challenge. I want to talk about your solutions in this space. Can you tell us more about Micro Focus voltage? I want to understand what it is, and then get into sort of how it works, and then I really want to understand how it's applied to Vertica. >> Yeah, absolutely, that's a great question. First of all, we were the originators of format preserving encryption, we developed some of the core basic research out of Stanford University that then became the company of Voltage; that build-a-brand name that we apply even though we're part of Micro Focus. So the lineage still goes back to Dr. Benet down at Stanford, one of my buddies there, and he's still at it doing amazing work in cryptography and keeping moving the industry forward, and the science forward of cryptography. It's a very deep science, and we all want to have it peer-reviewed, we all want to be attacked, we all want it to be proved secure, that we're not selling something to a major money center bank that is potentially risky because it's obscure and we're private. So we have an open standard. For six years, we worked with the Department of Commerce to get our standard approved by NIST; The National Institute of Science and Technology. They initially said, well, AES256 is going to be fine. And we said, well, it's fine for certain use cases, but for your database, you don't want to change your schema, you don't want to have this increase in storage costs. What we want is format preserving encryption. And what that does is turns my name, Rich, into a four-letter ciphertext. It can be reversed. The mathematics of that are fascinating, and really deep and amazing. But we really make that very simple for the end customer because we produce APIs. So these application programming interfaces can be accessed by applications in C or Java, C sharp, other languages. But they can also be accessed in Microservice Manor via rest and web service APIs. And that's the core of our technical platform. We have an appliance-based approach, so we take a secure data appliance, we'll put it on Prim, we'll make 50 of them if you're a big company like Verizon and you need to have these co-located around the globe, no problem; we can scale to the largest enterprise needs. But our typical customer will install several appliances and get going with a couple of environments like QA and Prod to be able to start getting encryption going inside their organization. Once the appliances are set up and installed, it takes just a couple of days of work for a typical technical staff to get done. Then you're up and running to be able to plug in the clients. Now what are the clients? Vertica's a huge one. Vertica's one of our most powerful client endpoints because you're able to now take that API, put it inside Vertica, it's all open on the internet. We can go and look at Vertica.com/secure data. You get all of our documentation on it. You understand how to use it very quickly. The APIs are super simple; they require three parameter inputs. It's a really basic approach to being able to protect and access data. And then it gets very deep from there because you have data like credit card numbers. Very different from a street address and we want to take a different approach to that. We have data like birthdate, and we want to be able to do analytics on dates. We have deep approaches on managing analytics on protected data like Date without having to put it in the clear. So we've maintained a lead in the industry in terms of being an innovator of the FF1 standard, what we call FF1 is format preserving encryption. We license that to others in the industry, per our NIST agreement. So we're the owner, we're the operator of it, and others use our technology. And we're the original founders of that, and so we continue to sort of lead the industry by adding additional capabilities on top of FF1 that really differentiate us from our competitors. Then you look at our API presence. We can definitely run as a dup, but we also run in open systems. We run on main frame, we run on mobile. So anywhere in the enterprise or one in the cloud, anywhere you want to be able to put secure data, and be able to access the protect data, we're going to be there and be able to support you there. >> Okay so, let's say I've talked to a lot of customers this week, and let's say I'm running in Eon mode. And I got some workload running in AWS, I've got some on Prim. I'm going to take an appliance or multiple appliances, I'm going to put it on Prim, but that will also secure my cloud workloads as part of a sort of shared responsibility model, for example? Or how does that work? >> No, that's absolutely correct. We're really flexible that we can run on Prim or in the cloud as far as our crypto engine, the key management is really hard stuff. Cryptography is really hard stuff, and we take care of all that, so we've all baked that in, and we can run that for you as a service either in the cloud or on Prim on your small Vms. So really the lightweight footprint for me running my infrastructure. When I look at the organization like you just described, it's a classic example of where we fit because we will be able to protect that data. Let's say you're ingesting it from a third party, or from an operational system, you have a website that collects customer data. Someone has now registered as a new customer, and they're going to do E-commerce with you. We'll take that data, and we'll protect it right at the point of capture. And we can now flow that through the organization and decrypt it at will on any platform that you have that you need us to be able to operate on. So let's say you wanted to pick that customer data from the operational transaction system, let's throw it into Eon, let's throw it into the cloud, let's do analytics there on that data, and we may need some decryption. We can place secure data wherever you want to be able to service that use case. In most cases, what you're doing is a simple, tiny little atomic efetch across a protected tunnel, your typical TLS pipe tunnel. And once that key is then cashed within our client, we maintain all that technology for you. You don't have to know about key management or dashing. We're good at that; that's our job. And then you'll be able to make those API calls to access or protect the data, and apply the authorization authentication controls that you need to be able to service your security requirements. So you might have third parties having access to your Vertica clusters. That is a special need, and we can have that ability to say employees can get X, and the third party can get Y, and that's a really interesting use case we're seeing for shared analytics in the internet now. >> Yeah for sure, so you can set the policy how we want. You know, I have to ask you, in a perfect world, I would encrypt everything. But part of the reason why people don't is because of performance concerns. Can you talk about, and you touched upon it I think recently with your sort of atomic access, but can you talk about, and I know it's Vertica, it's Ferrari, etc, but anything that slows it down, I'm going to be a concern. Are customers concerned about that? What are the performance implications of running encryption on Vertica? >> Great question there as well, and what we see is that we want to be able to apply scale where it's needed. And so if you look at ingest platforms that we find, Vertica is commonly connected up to something like Kafka. Maybe streamsets, maybe NiFi, there are a variety of different technologies that can route that data, pipe that data into Vertica at scale. Secured data is architected to go along with that architecture at the node or at the executor or at the lowest level operator level. And what I mean by that is that we don't have a bottleneck that everything has to go through one process or one box or one channel to be able to operate. We don't put an interceptor in between your data and coming and going. That's not our approach because those approaches are fragile and they're slow. So we typically want to focus on integrating our APIs natively within those pipeline processes that come into Vertica within the Vertica ingestion process itself, you can simply apply our protection when you do the copy command in Vertica. So really basic simple use case that everybody is typically familiar with in Vertica land; be able to copy the data and put it into Vertica, and you simply say protect as part of the data. So my first name is coming in as part of this ingestion. I'll simply put the protect keyword in the Syntax right in SQL; it's nothing other than just an extension SQL. Very very simple, the developer, easy to read, easy to write. And then you're going to provide the parameters that you need to say, oh the name is protected with this kind of a format. To differentiate it between a credit card number and an alphanumeric stream, for example. So once you do that, you then have the ability to decrypt. Now, on decrypt, let's look at a couple different use cases. First within Vertica, we might be doing select statements within Vertica, we might be doing all kinds of jobs within Vertica that just operate at the SQL layer. Again, just insert the word "access" into the Vertica select string and provide us with the data that you want to access, that's our word for decryption, that's our lingo. And we will then, at the Vertica level, harness the power of its CPU, its RAM, its horsepower at the node to be able to operate on that operator, the decryption request, if you will. So that gives us the speed and the ability to scale out. So if you start with two nodes of Vertica, we're going to operate at X number of hundreds of thousands of transactions a second, depending on what you're doing. Long strings are a little bit more intensive in terms of performance, but short strings like social security number are our sweet spot. So we operate very very high speed on that, and you won't notice the overhead with Vertica, perse, at the node level. When you scale Vertica up and you have 50 nodes, and you have large clusters of Vertica resources, then we scale with you. And we're not a bottleneck and at any particular point. Everybody's operating independently, but they're all copies of each other, all doing the same operation. Fetch a key, do the work, go to sleep. >> Yeah, you know, I think this is, a lot of the customers have said to us this week that one of the reasons why they like Vertica is it's very mature, it's been around, it's got a lot of functionality, and of course, you know, look, security, I understand is it's kind of table sticks, but it's also can be a differentiator. You know, big enterprises that you sell to, they're asking for security assessments, SOC 2 reports, penetration testing, and I think I'm hearing, with the partnership here, you're sort of passing those with flying colors. Are you able to make security a differentiator, or is it just sort of everybody's kind of got to have good security? What are your thoughts on that? >> Well, there's good security, and then there's great security. And what I found with one of my money center bank customers here in San Francisco was based here, was the concern around the insider access, when they had a large data store. And the concern that a DBA, a database administrator who has privilege to everything, could potentially exfil data out of the organization, and in one fell swoop, create havoc for them because of the amount of data that was present in that data store, and the sensitivity of that data in the data store. So when you put voltage encryption on top of Vertica, what you're doing now is that you're putting a layer in place that would prevent that kind of a breach. So you're looking at insider threats, you're looking at external threats, you're looking at also being able to pass your audit with flying colors. The audits are getting tougher. And when they say, tell me about your encryption, tell me about your authentication scheme, show me the access control list that says that this person can or cannot get access to something. They're asking tougher questions. That's where secure data can come in and give you that quick answer of it's encrypted at rest. It's encrypted and protected while it's in use, and we can show you exactly who's had access to that data because it's tracked via a different layer, a different appliance. And I would even draw the analogy, many of our customers use a device called a hardware security module, an HSM. Now, these are fairly expensive devices that are invented for military applications and adopted by banks. And now they're really spreading out, and people say, do I need an HSM? Well, with secure data, we certainly protect your crypto very very well. We have very very solid engineering. I'll stand on that any day of the week, but your auditor is going to want to ask a checkbox question. Do you have HSM? Yes or no. Because the auditor understands, it's another layer of protection. And it provides me another tamper evident layer of protection around your key management and your crypto. And we, as professionals in the industry, nod and say, that is worth it. That's an expensive option that you're going to add on, but your auditor's going to want it. If you're in financial services, you're dealing with PCI data, you're going to enjoy the checkbox that says, yes, I have HSMs and not get into some arcane conversation around, well no, but it's good enough. That's kind of the argument then conversation we get into when folks want to say, Vertica has great security, Vertica's fantastic on security. Why would I want secure data as well? It's another layer of protection, and it's defense in depth for you data. When you believe in that, when you take security really seriously, and you're really paranoid, like a person like myself, then you're going to invest in those kinds of solutions that get you best in-class results. >> So I'm hearing a data-centric approach to security. Security experts will tell you, you got to layer it. I often say, we live in a new world. The green used to just build a moat around the queen, but the queen, she's leaving her castle in this world of distributed data. Rich, incredibly knowlegable guest, and really appreciate you being on the front lines and sharing with us your knowledge about this important topic. So thanks for coming on theCUBE. >> Hey, thank you very much. >> You're welcome, and thanks for watching everybody. This is Dave Vellante for theCUBE, we're covering wall-to-wall coverage of the Virtual Vertica BDC, Big Data Conference. Remotely, digitally, thanks for watching. Keep it right there. We'll be right back right after this short break. (intense music)

>>Live from Las Vegas. That's the Q covering splunk.com 19 brought to you by Splunk. >>Hey, welcome back. Every once the Q's live coverage here in Las Vegas for Splunk's dot com 2019 it's Splunk's 10th year having the events, the cubes coverage seven years, the cube independent media company breaking down, extracting the signal from the noise dot on the top people, top experts, tell them the stories that matter. We're here with Mike EG, director of applied research for coming red Canary. Mike, thanks for coming on. I appreciate it. Thank you. So red Canary is a company doing here. What's the focus? What does it company do? Take a minute to explain red County area and why you're here at.com. Sure, thank you. So we are a managed endpoint detection and response organization. We partner with organizations of all sizes to help them eradicate evil, for instance. So we help them with monitoring their environment. We investigate, respond and act on threats or so on the notes here, you guys have a topic session finding titled finding evil is never an accident, how to hunt in bots. >>So using bots, hunting down evil, you guys are out there doing this as a business. What does it mean? What does he, what if, first of all, what is evil and how do you hunt it down? Take us through that Sarah. So the talk is based around the boss of the SOC data set that was released by Splunk. They have version two, version one and version three will be coming out soon and they just released version four here. And so the talks all focused on how to find evil within bots. The three are actually V forum, sorry, the one that just came out. And so what we do as an organization is we help businesses get through their data, kind of like your guys' mission as well. Like get through them all the haystack, find the bad things and present that to our customers in a really fast way. >>So that's kind of where we are today. Archives to find the good content. Great experts like yourself tell about your role. You're like a researcher, but it's not like you're sitting back there applied research we applied means it's not like just making it up, you know the next moonshot, you guys are applied specifically to hunting down evil. That's your role. What does that entail? You guys have to sit back, zoom back, look at the data that the Splunk's providing some benefits with their, they're exposing their data. What does it mean to hunt down? What's, what's the requirements? How do you set that up? What are you looking at you going through day? Those are the dashboards. What are the what? What, what do you deal with and your job? >> Yeah, so like a day to day or like kind of what our team does is we focus on like what's going on previously, what are we seeing in the wild? >>Like what campaigns are happening and then my role within my team is focused on what's coming. So what are, what are red team's working on? What are pen testers looking into? Take that information, begin testing and begin building proof of concepts. Put that back into our products so that whether it's two weeks, six months, two years, we have coverage for it, no matter what. So a of us, a lot of our time is generating proof of concepts on what may be coming. So there's a lot of very unique things that may be in the wild today. And then there's some things that we may never see that are just very novel and kind of once, once, once a time kind of thing. Right? >> So you know, we love talking about data that we've been covering data since 2010 the thing that's interesting and I want to get your thoughts on this because you know, eval has arbitrage built into it. >>They know where to hide. And so the question is, is that what are you looking at matters, right? So the so, so, so there's a lot of exposure. But the question I have for you is, what is the problem that you're solving? Why do you guys exist? Was it because evil was better to adversaries? Were better at hiding? Is it automation can solve patterns they haven't seen yet? Because if you automate something you haven't seen yet, so is it new things? So why, what's the problem statement that you guys are attacking? Yeah. So hit it. It's a lot. There's a lot, there's a lot to inbox. Um, so like in particular in this instance, seeing something that happened yesterday and then what's happening today is actors are working to break process lineage within what's happening on the employee. Because actors know that everything's happening on an employment. >>Yes, there's traffic coming in, but there's execution going on in a single place on that box. So their whole tactic now is to try to break that lineage. So it's not Microsoft word spawning something. It's now Microsoft word opens and as spawns over there off another process, right? So we're here to monitor those types of behaviors. And that's pretty much like the core of red Canary. We've always focused on the end points. We only do emblem implant based products. We don't like monitor networks. We don't monitor firewalls or anything like that. We're very focused, uh, hyper focus on employee behaviors. And so, and that, that's the cool part about our job is we get to see all the really new things that are happening. And if you look at it, these breaches in the past, it's happening on the endpoint and that's probably where we are. >>And actually day the Canary in the coal mines all expression, everyone knows that or if older might know that. But you know, identifying and being that early warning detection system really kind of was the whole purpose of the Canary in the coal mine, red Canary red teams. I'm kind of putting it together. What are some of the things that you've seen that, that as an example of why you exist? Because it, is it new things, is it that, you know, Hey, our known thing or balls, what are some of the examples that you can point to that, that point of why you guys exist? Yeah, sure. Um, a good example is kind of like the looking forward stuff where red team's going, where actor's going. So a lot of them are moving to C sharp and.net Tradecraft, which is very native to the operating system. >>And windows. Um, so if they're doing that, they're moving away from what they're always, what they've been used to the last few years, which is PowerShell. So our sales kind of dead then now we're going to C sharp and.net. So a lot of our focus today is how can we better detect those? And vendors are moving that way too. They're, they're starting to see that they have to evolve their products to the next level order to detect these behaviors. Cause I mean that's, that's the whole reason why a lot of these EDR vendors are here. Right? And, and it's all data like you said. And so feeding it into a Sam or with a Splunk in particular, you're able to correlate those behaviors and look at very specific things and find it real well know. One of the things that a lot of security practitioners and experts and advisors have been looking at over years is data. >>So it's not, it's no secret data and critical. But one of the things that's interesting is that data availability has always been an issue. Sharing data. And then the message here@splunk.com for the 19 is interesting. You've got data diversity now exposure to the fabric search concept there they got accelerated and realtime times too. We've always had that. But as it kind of comes together, they're looking to get more diverse aperture to data. Yup. Is that still an ongoing challenge and what are, cause if you have a blind spot, you only, this is where the potential danger. How do you guys talk about that? What's the narrative around diverse data sets? How to deal with them effectively and then if blind spots exist, what do they look like or how do you figure that out? Yeah, we, so I, I've been with red Canary for over three years, about three years now. >>And one of the things I started at was a technical account manager incident handler. And so I helped a lot of our customers go from, we bought you red Canary to monitor points, but what should we do next? And so we, our incident handling team will come in and assist a customer with, you guys should start going down this road. Like, how are you bringing everything together? How are you analyzing your data down to just operationalizing like some use cases and playbooks within their data. Like you got EDR. Now let's look at your firewalls. How, how rich of that data can be helped enrich what the EDR information like here's the IP address and carbon black response. Where's it going this way on your firewall or your appliance is going out and you know, and things like that. So we have a whole team dedicated to it and that's like the focus of the. >>We took a poll in our, we have a, you know, this acumen operate for 10 years. It's our seventh year squad, Dave and I took a poll of our cube community, um, but 5,000 alumni and we asked them about cloud security, which vendors are the best and Splunk is clearly number one in third party data management. I got him out, he's got a category but cloud security. How should the cloud vendors provide security, Google, AWS and Azure. But outside of the core cloud providers, Splunk's number one, clearly across the board. How is Splunk doing in your mind? How do you guys work with Splunk? What's the dynamic? What's your relationship with Splunk and where Splunk position in your mind? Because as cloud becomes more prevalent with cloud native, born in the cloud and with hybrid there's a unification, not just with data. They have infrastructure operations. >>Yup. So Splunk role and then their future prospects share. Um, so red Canary uses Splunk too. So we, we process I think like 30 terabytes plus of data a day coming to our engine that we built. And that's the kind of like proprietary piece of red Canary. 30 terabytes of data flows through. We use a like a DSL, like a language that sits on top of it, that queries they're looking for those behaviors. We send those tip offs as we call to Splunk and we actually track a lot of the efficiencies of our detectors that way. So we look for how low detectors doing, is it triggering, is that false positives? How many false positives over time. And then also how much time our analysts are spending on those detectors. You know, they get a detector or a in event and they review that event and they're spending 2030 minutes on it and well what's wrong with it? >>Is there something going on here? Do we need to cut something back and fix it? So we use Splunk a lot of, for like the analytics piece of just how our operation works. It's awesome. It's really neat to see >> him for, one of the things that I've been proud of with covering Splunk is we showed them early when they were just started, then they went public. Yeah. Just watching how they've grown. That did a lot of great things. But now the theme is applications on top of Splunk. They're an enabling platform. They had a couple of key pillars. I want you to talk about where you guys fit and where you see the upside. So swamp has the developer area, which is, they have all these deck, new developers, security and compliance and fraud, um, foundations and platform stuff. And then the it ops does this analytics, AI ops, they've got signal FX, cloud native. >>So those are the kind of the four key areas around their apps, their app strategy. Do you guys cut across all those? You are you guys developing? Are you doing all, what's the, what's the red Canary fit into that? Yeah, it seems like you've probably our cross section. Yeah, probably most likely fitting into a few areas within Ed's. My team has developed a couple apps for Splunk, so we've published those. We have like a app that we pushed out. We have a carbon black response app, which we co-developed many years ago. Those things are all out there. We've helped other people with their apps and, but yeah, it's, it's a little mix of everything. And I think the big core thing that we're all looking to today is like how can we use more of the machine learning toolkit with Splunk, um, for our customers and for us internally. >>Like how can we predict things better with it? So there's, there's a lot of little bit of focus of that same thing. In your opinion, B2B out in the field, you mean the front lines, now you're in research, you got that holistic view, you're looking down at the, on the field, the battlefield, if you will, the adversaries will evil out there. What do you look for? I mean, what's the, what's the triggering event for you? How do you know when you need to jump in and get full ready, alert and really kind of sound off that, you know, that Canary alarm saying, Hey, you know, let's take action here or let's kind of like look at that and take us through some of those priorities. What's the, some of the workflow you go through? Yeah, so um, we'll end up either sending a detection to a customer and either they'll trigger like, Hey, can you give us more context around this event that happened? >>Or it will be, we had a pen test, red team, bad thing happen. Can someone else investigate further? And so I'll come in might from my perspective, I'll come in kind of like a, almost like a tier three in a way. We'll come in, we'll do the additional research beyond what our detectors already caught looking for. Many things, you know, did, was there something we missed that we can do better at detecting next time? Is there any new behaviors involved with something drop that you know, that the actor had left within the environment that may have gone by antivirus prevention controls, anything like that. Um, and then also just understanding their trade craft. Right? So we track a lot of teams and disturbed behaviors and we're able to kind of explore and you know, build those you gotta you gotta be on everything. Basically you gotta survey the entire landscape. >>Yep. You come in post event. Yeah. Do the collateral damage analysis and the dead map. That's a really cool thing about like the Splunk boss's a sock data set. Right. And that's where my talks a lot about is it's a very like, basic talk, but it focuses on how to go from beginning to end investigating this big incident that happened. You know, cause when you get an a detection from like in organization you might just find that it was delivered to a word doc, a couple of things executed. But was there something else that happened? Right? And there's like your Canadian Nicole mind piece, right. You know, finding other things that occurred within the organization and helping ideally your data essentially is the foundation for essentially preventative side. So it's, yes, it's kind of a closed loop kind of life cycle of yep. Leverage operating leverage data standpoint. >>Yeah, it's a solid point. We, I coined the term like three years ago called driving, driving prevention with detection. So take all your detection logic and understanding and things you see with products, even EDR Avi, and use that to drive your prevention. So it's just a way that if you're just alerting on everything, take that data and put it into your preventative preventative controls. So Michael got asked you, how is cloud, how is cloud changing the security formulas? Because obviously scale and data are big themes we hear all the time. I mean has been around is not a new thing. But the constant theme that I see in all my cube interviews we've done over the years and this year is the Nord scale comes up, is unprecedented scale, both in data volume, surface area needs for things like red Canary teams to be in there. What do you see with the impact the cloud is it really should change the game in any way? >>He has it's speed as new cloud. It's the speed of new cloud technology that seems to constantly be coming out. Like one day it's Docker, next day it's Coobernetti's and then there's going to be something tomorrow. Right? Like it just constantly changes. So how can vendors keep up with logging, making sure it's the right type of logging and being able to write detection on it or even detect anything out of it. Right. One, the diversity too is a great point. I want to know. Firstly, blogs are great. Yeah, you got tracing. So you have, so there's now different signaling. Yeah. So this app now a new thing that you got to stay on top. Oh, totally. Like look at any, any MSSP, they have thousands of data sources coming in. And now I want you to monitor my Coubernetties cluster that scales horizontally from 100 to 5,000 all day, every day like Netflix or something. >>Right? And I want you to find the bad things in that. It's a lot going on. And this is where machine learning and automation come into play because the observability you need the machine learning. They've got to categorize this. Okay. Again, humans do all this. No, yeah, it takes a machine. I'm using machines with human intelligence in a way, right? So have a human driving the machine to pull out those indicators, those notables. Michael, thanks for coming on. Great insight. Great signal from the noise. You're still distracting there. Great stuff. Final question for that to end the segment. In your opinion, what's the top story in the security industry that needs to be continually told and covered and reported on? >> Ooh, that's, that's a good one. Um, you hear any threats, platform development, new stacks developing. Is there like a one area that you think deep that's the high order bit in terms of like impact? Yeah. I think focus on, I'm going to say point cause that's where everything's executing and everything's happening. Um, and that's the biggest thing that it's only gonna get more challenging with IOT edge and industrial IOT. Yes. The edge is the end point. End points are changing. The definition is changing at exact right stuff coming on from red Canary here in the queue, the Canary in the coal mine. That's the cube. Brand-new. The signal here from.com 19. I'm John furrier back with more after this short break.

>>from Miami Beach, Florida It's the key. You covering a Cronus Global Cyber Summit 2019. Brought to you by a Cronus. >>Hello, everyone. Welcome to the Cube coverage here in Miami Beach Front and Blue Hotel with Cronus Global Cyber Summit 2019 2 days of coverage. Where here, Getting all the action. What's going on in cyber tools and platforms are developing a new model of cybersecurity. Cronus Leader, Fast growing, rapidly growing back in here in the United States and globally. We're here. William Toll, head of product marketing Cronus. Thanks for coming. I appreciate it. >>Thanks, John. I'm excited. You're >>here so way were briefed on kind of the news. But you guys had more news here. First great key notes on then special guest Shark tank on as well. That's a great, great event. But you had some news slip by me. You guys were holding it back. >>So we've opened our A p I, and that's enabling a whole ecosystem to build on top of our cyber protection solutions. >>You guys have a platform infrastructure platform and sweet asserts from backup all the way through protection. All that good stuff as well. Partners. That's not a channel action platforms are the MoD has been rapidly growing. That's 19 plus years. >>And now, with the opening of our AP, eyes were opening the possibility for even Maur innovation from third parties from Eyes V's from managed service providers from developers that want to build on our platform and deliver their solutions to our ecosystem. >>You guys were very technical company and very impressed with people. Actually, cyber, you gotta have the chops, you can't fake it. Cyber. You guys do a great job, have a track record, get the P I. C B Also sdk variety, different layers. So the FBI is gonna bring out more goodness for developers. You guys, I heard a rumor. Is it true that you guys were launching a developer network? >>That's right. So the Cronus developer network actually launches today here in the show, and we're inviting developed officials. That's official. Okay. And they can go to developers that Cronus dot com and when they go in there, they will find a whole platform where they can gain access to forums, documentation and logs, and all of our software development kids as well as a sandbox, so developers can get access to the platform. Start developing within minutes. >>So what's the attraction for Iess fees and developers? I mean, you guys are here again. Technical. What is your pitch developers? Why would they be attracted to your AP eyes? And developer Resource is >>sure it's simple. Our ecosystem way have over 50,000 I t channel partners and they're active in small businesses. Over 500,000 business customers and five million and customers all benefit from solutions that they bring to our cyber cloud solutions >>portal. What type of solutions are available in the platform today? >>So their solutions that integrate P s a tools professional service is automation are mm tools tools for managing cloud tools for managing SAS applications. For example, one of our partners manages office 3 65 accounts. And if you put yourselves in the shoes of a system administrator who's managing multiple SAS applications now, they can all be managed in the Cronus platform. Leverage our user experience. You I s t k and have a seamless experience for that administrator to manage everything to have the same group policies across all of this >>depression. That success with these channel a channel on Channel General, but I s freeze and managed service ROMs. Peace. What's the dynamic between Iess, freeze and peace? You unpack that? >>Sure. So a lot of m s peace depend on certain solutions. One of our partners is Connectwise Connectwise here they're exhibiting one sponsors at at this show and their leader in providing managed to lose management solutions for M s. He's to manage all of their customers, right? And then all the end points. >>So if I participate in the developer network, is that where I get my the FBI's someone get the access to these AP eyes? >>So you visits developer data cronies dot com. You come in, you gain access to all the AP eyes. Documentation way Have libraries that'll be supporting six languages, including C sharp Python, java. Come in, gain access to those documentation and start building. There's a sandbox where they could test their code. There's SD K's. There's examples that are pre built and documentation and guides on how to use those s >>So customer the end. You're in customers or your channel customers customer. Do they get the benefits of the highest stuff in there? So in other words, that was the developer network have a marketplace where speed push their their solutions in there. >>Also launching. Today we have the Cronus Cyber Cloud Solutions portal and inside there there's already 30 integrations that we worked over the years to build using that same set of AP eyes and SD case. >>Okay, so just get this hard news straight. Opening up the AP eyes. That's right. Cronus Developer Network launched today and Cloud Solutions Portal. >>That's right, Cyber Cloud Solutions Portal Inside there there's documentation on all the different solutions that are available today. >>What's been the feedback so far? Those >>It's been great. You know, if we think about all the solutions that we've already integrated, we have hundreds of manage service providers using just one solution that we've already integrated. >>William, we're talking before we came on camera about the old days in this business for a long time just a cube. We've been documenting the i t transformation with clouds in 10 years. I've been in this in 30 years. Ways have come and gone and we talked to see cells all the time now and number one constant pattern that emerges is they don't want another tour. They want a solid date looking for Jules. Don't get me wrong, the exact work fit. But they're looking for a cohesive platform, one that's horizontally scaled that enables them to either take advantage of a suite of service. Is boy a few? That's right. This is a trend. Do you agree with that? What you're saying? I totally agree >>with that, right? It makes it much easier to deal with provisioning, user management and billing, right? Think about a man of service provider and all of their customers. They need that one tool makes their lives so much easier. >>And, of course, on event would not be the same. We didn't have some sort of machine learning involved. How much his machine learning been focused for you guys and what's been some of the the innovations that come from from the machine. I mean, you guys have done >>artificial intelligence is critical today, right? It's, uh, how we're able to offer some really top rated ransomware protection anti malware protection. We could not do that without artificial intelligence. >>Final question for you. What's the top story shows week If you have to kind of boil it down high order bit for the folks that couldn't make it. Watching the show. What's the top story they should pay attention to? >>Top story is that Cronus is leading the effort in cyber protection. And it's a revolution, right? We're taking data protection with cyber security to create cyber protection. Bring that all together. Really? Democratize is a lot of enterprise. I t. And makes it accessible to a wider market. >>You know, we've always said on the Q. Go back and look at the tapes. It's a date. A problem that's right. Needed protection. Cyber protection. Working him, >>Cronus. Everything we do is about data. We protect data from loss. We protect data from theft and we protect data from manipulation. It's so critical >>how many customers you guys have you? I saw some stats out there. Founded in 2003 in Singapore. Second headquarters Whistle in 2000 a global company, 1400 employees of 32 offices. Nice nice origination story. They're not a Johnny come lately has been around for a while. What's the number? >>So five million? Any customers? 500,000 business customers. 50,000 channel partners. >>Congratulations. Thanks. Thanks for having us here in Miami Beach. Thanks. Not a bad venue. As I said on Twitter just a minute ago place. Thanks for Thanks. All right, John. Just a cube coverage here. Miami Beach at the front in Blue Hotel for the Cyber Global Cyber Security Summit here with Cronus on John Kerry back with more coverage after this short break.

>>live from Washington, D. C. It's the Cube covering Bumi World 19. >>Do you buy movie? >>Welcome to the Cube. I'm Lisa Martin at Bumi World 2019 in Washington, D. C. Been here all day. Had some great conversations. One of my favorite things about movie is how impactful they are making their customers. And I'm very pleased to welcome the CEO off American Cancer Society. Kenny Ocular Kenny, Welcome to the Cube. >>Thank you. Happy to be here. >>Really? Enjoyed your keynote this morning on stage with Chris McNab. You know, the American Cancer Society is one of those organizations. I think that that impacts every single person on this planet in some way or another. We've all been touched by cancer, and it's so it's so interesting to look at it as how is technology fueling the American Cancer Society? Your CEO talk to us a little bit about what you guys are doing with booming. How Bhumi is really helping you guys two integrate all these different systems so that an agency is old and historic as a C s is is really transforming to be a modern kind of cloud driven organization. >>Yeah, I think all organizations now are becoming I t organizations. It's their heart, and it's important for us to the American Cancer Society to interact with. Our constituents are volunteers. Our patients are staff right in a digital way. So it is critically important that we are right there with everybody else, uh, interacting with them. And so, whether they're on the go and doing it on their mobile phone or, you know, at the doctor's office talking with their doctor about treatment options that were there to help them get them what they need, an information for their best chance to beat the beat the disease. >>So talk to me first about the business transformation that the American Cancer Society winter before your time there. But first it was. We have all these different organizations different leadership, different I t infrastructure, different financial operations model. Talk to us about first powdered it transform from a business like process perspective and then start looking at digital transformation. >>So some of it happened at the same time the organization made the decision back in about 2012 to consolidate other organizations. We were we kind of run ran regionally at the time and each independent, different region. There were 13 different regions kind of ran independently with their own I T systems. There were some shared technologies that we had of the organization, starting in about 2012 decided that no, we wanted to centralize our model and come together. We thought it was a more efficient manner and allowed us, in essence, to doom or for our mission, which is the ultimate goal. So there was a lot of consolidation around people on organization. Some of the processes I will say, God, God consolidated. Some are still going through some of that transformation. So after we kind of keep brought the organization's together and some of the people together, we kind of looked at Where are we with our technology and how do we move forward into the 21st century and do that effectively? And so at the time, we did kind of an analysis of our current state. As I mentioned in the keynote, we had a lot of technologies >>that were just older, had kind of run their course for >>end of life or just become that, you know, over change over a decade of changes and just being a monstrous the e meth or systems. That way, we're really struggling to keep up right both in terms of change and enhancement and delivering those capabilities back to our constituents. So we decided that no, it's time for us to move to a new and technology modernization effort, and we really wanted to be on the cloud first strategy. So we were looking at our cloud vendors and everything else. And one of the big selections was, as we chose Salesforce's R C R M platform we chose. Net Suite is our financially rp platform that we we could consolidate all those. And then as a part of that, we were looking at all of the leftover processes that weren't standardized, that we were still doing differently, that we could simplify. So taking stuff from 21 steps down to six steps if we could, you know, et cetera, and bringing that along with the transformation just to create more efficiencies for us and then, at the end of the day, driving a better end user experience with your volunteer, your staff, your patient, et cetera, >>it's a tremendous amount of data just in a serum like cells fours and Oracle Net Sweet. What was the thought and the opportunity to actually put an integration platform to enable that data to be shared between the applications and enabled whether it's providers or as you said volunteers, and we'll talk about that? And second, to be ableto have an experience that allows them to get whatever is that they're looking for. Talk to us about integration and sort of that driving kind of hub centralized hub aspect. >>Yeah. I mean, with any business data is key. And historically, we had our data was was >>spread out across multiple systems but then didn't always sync up. So you'd have you know you'd pull a report out of one system and say something different than when you looked at another system. So one of the key foundational tenets with the transformation was is we wanted our data to be in sync. We >>wanted to be able to see the same things no matter where you were looking. At that way, we we were all looking at the same information and basically a single source of truth. Yes, and boom. He was a critical component of that, right? With their integration platform, they were going to be our integration hub that is going >>to keep everything in sync. So we knew we had over, Um well, we had 100 and 20 applications that ultimately were a part of it. There were probably 20 major ones that had most of our data in there. And then boom. He is integrating all of those. So when information's coming across, whether it's coming in from, ah, donation made or an event participants or a patient referral form, all of that data comes in, comes in through Bumi, and it's propagated, orchestrated across the systems as it needs to be to make sure that it has all of the right information in it, that the data is as clean as we can make it, and it's all in sync. At the end of the day, >>that's critical. Having the data is great, but if you actually can't utilize an extract values from that, it's I don't want a worthless, but it's clearly the value, and they're you know, >>it's a lot harder to make good business decisions without good data, >>right? And when we're talking about something like patients dealing with with very, very scary situations, being able to Matt, whether it's matching a volunteer with ah mentor with a patient is going through something similar that could be game changing in lives and really kind of propagate. Talk to me about this service match that you guys have built with Bhumi. I think it's such a great service that you guys are delivering. Tell us about that. What it's enabling. >>So service matches an application that is part of our road to recovery program, where we provide rides for cancer patients to and from cancer treatment So often when you're getting chemo therapy, driving after chemotherapy is not an option. And ah, lot of a patient's have trouble with caregivers and family, always helping them. So the American Cancer Society provides this program to provide those rides free of charge for cancer patients. And the service match application is about connecting those patients to volunteers for the rides. So if if a patient calls in, they say, I need a ride, this is what time I'm going etcetera. They can do that now online as well, and we can connect them with a volunteer. So then that goes out to our volunteer community and somebody can say I can do that. I can help this person out, connects them up so that they can get to their treatments on time. >>That's so fantastic. And such a impact that you guys could make isn't something where you guys were integrating on the background with, like, a rideshare service or these just folks like Hey, I've got a car that seats five I want to help is it is available. It is. It is available to anybody. Anybody can >>volunteer, and most of the rides are handled volunteers If we cannot find a volunteer, we have a lot of great partners that worked with the American Cancer Society. They can provide those rideshare opportunities, so we'll make it happen and and get the patient to their treatment >>to talk to me about the ability to do that. That's a one great application of what you guys are doing with Bhumi. What was the actual building? That application? How long did it take to be able to say, Hey, we had this idea? We can connect these systems. We can facilitate something that's critical in the care of the patients. What was that kind of build an implementation like because when we talked a lot about time to value. And we've talked about that a lot today. So talk to me about it through that lens >>eso for us. We started on we're all on spreadsheets, right and paper. And yeah, it was it was about a 12 months process actually build some of the the service match application itself. The bony implementation came in as part of our transformation to make sure that all of the systems were integrated with that. So as people are requesting rides or whether that's through the call center or going through the website, that that information is there, that they can help patients with it. So if they need to change the schedule or do something different, that those all take place and that everybody has the latest information, it also enables us has were as changes are happening or even the rides are taking place. Notifications air going back out and back and forth so that everybody is up to date on all of the activity that's taking place. >>And to date, you guys have helped with service match alone Nearly 30,000 patients. >>Yeah, we we service. I think It's 30,000 patients a year. >>Wow. >>On the on the platform, we, uh, over 500,000 rides have been delivered since its inception. >>And And when was that inception? >>I'd have to look at the date. I don't >>know. A couple years ago were in the last. >>It's been It's probably been in over a decade now. >>Okay, that's awesome. So another thing. I'm curious. Four volunteers who want to do to raise funds to support the American Cancer Society is integration kind of essential component. You're smiling. So I think the answer is I think I know the answer. Talk to us about how, um, Bhumi is helping a CS to deliver, you know, a more seamless, a better fundraising experience for anybody that wants to actually go out and do that. >>Yeah. So we have a lot of donation processing systems that that that we leverage As for the American Cancer Society, because part of what we want to do is make it easy for people to raise money and raise it in their way. Right? So we have multiple systems, both from all the events that we do, whether it's the relay for life, for the making strides against breast cancer, which are two of our major event platforms. But we also have raised your way platforms. So if you want to do it yourself and you want to host a wine front razer with your friends and raise some money, we can absolutely help you do that as well. And what we do is we take all that information from all of that that from those events, and then bring that into the system so that we know what happened when who you were, so we can properly thank you. You can also get your tax credits and and all of the other things that go along with it. So >>that's awesome. So I want to ask you from a CEO's perspective, Bumi being a A single instance multi tenant cloud application delivered as a service to you and your previous role before you came to the American Cancer Society was insurance. Talk to me about that as a differentiator. What is that as a. C s continues to scale on, offer more programs and have more data to integrate roomies architecture and your perspective is that something that gives the A. C. S really a leg up to be able to do more, more. >>Absolutely. I think boonies, low code development strategy is is a differentiated for anybody that's using the platform it. We have been able to deliver Maur integrations in a shorter amount of time with our transformation than I've done in the past with other integration platforms or just developing it. I'll say the old fashioned way with Java or C sharp. So I think I think it's an integration platform. It's it's It's a real game changer in terms of what enterprises can do in terms of delivering, uh, faster and with Maur stability and performance than in the past, >>which is critical for many businesses that obviously yours included. They also take a look back at your previous role in a different industry. How is the role of the CEO changing in your perspective as things are moving to the cloud? But there's the explosion of edge and this consume arised implementation, right or influence because as consumers, we have access to everything and we want to be able to transact anything, whether it's signing up to be a volunteer or an actual patient needing to have access to records or a ride? How How is that consumers ation effect changing the role of the CEO, opening up more opportunities? >>Yeah, that's a big question. >>Sorry. It's >>okay. Um, yeah, I think the role of C I. O. Is changing significantly in terms of they are required to be more of a business leader are as much as a business leader as as any of the other C suite executives. And it is justice critical for them to understand the business where it's going be a part of the strategy with it and helped drive. From that perspective, The consumer ization component is actually in some ways, I think, making the c i o in the i t. Job a little bit harder. There's, um there's a lot that goes into making sure that what we're doing is secure on, performs well and sometimes just the overall consumer ization of technology. It looks so easy sometimes, and sometimes it's easy to underestimate some of the the complex nature of what we're doing and the level of security that needs to be applied to make sure that were protecting our constituents and making sure that their data is safe and secure. >>How does Boonmee help facilitate doctors? You right? We talk about security all the time. In any industry. How is what you're doing with Louis giving you maybe that peace of mind or or the confidence that what's being moved around as data and applications migrate, that you've got a secure, safe environment? That data? >>Yeah, I think Bumi does several things. First off, they've got a lot of security certifications is a part of their program. They make it relatively easy to to leverage that they allow us to deploy the the atoms where we need to. So whether that's on Prem or in our own tenants, behind our firewalls, all of those things will allow us to deploy it in whatever method we feel is most secure based on the data that we're trying to move >>except Well, Kenny, it's been a pleasure having you on the Cube just really quickly. Where can we go if we want to become a volunteered to help patients >>san sir dot org's >>cancer dot org's Awesome Kenny has been a pleasure. Thank you so much. Thank congratulations on the massive impact that A C S is making not just with Bhumi, but in the lives of many, many people. We appreciate your time. >>We're very excited and happy. We can help. >>All right. I'm Lisa Martin. You're watching the Cube from Bhumi World 2019. Thanks for watching.

>> live from the Mandalay Bay Convention Center in Las Vegas. It's the king covering via World 2016 brought to you by IBM Wear and its ecosystem sponsors. Now here's your host stool minimum, >> including I Welcome back to the Q bomb stew. Minuteman here with my co host for this segment, Mark Farley, and we'll get the emerald 2016 here in Las Vegas. It's been five years since we've been in Vegas, and a lot of changes in five years back Elsa do this morning was talking about five years from now. They expect that to be kind of a crossover between public Cloud becomes majority from our research. We think that flash, you know, capacities. You know, you really are outstripping, You know, traditional hard disk drives within five years from now. So the two guests I have for this program, Brian Vials, is the CEO of Day Tree. Um, it's been a year since we had you on when you came out of stealth on really excited cause your customer along. We love having customers on down from Alaska, you know, within sight view of of of Russia. Maybe on Did you know Ben Craig, who's the c i O of Northern Bank. Thank you so much for coming. All right, so we want to talk a lot to you, but real quick. Ryan, why do you give us kind of the update on the company? What's happened in the last year where you are with the product in customer deployments? >> Sure. Last year, when we talked, daydream was just coming out of stealth mode. So we were introducing the notion of what we're doing. Starting in kind of mid Q. One of this year, we started shipping and deploying. Thankfully, one of our first customers was Ben. And, uh, you know, our our model of, ah, sort of convergence is different from anything else that you'll see a v m world. I think hearing Ben tell about his experience in deployment philosophy. What changed for him is probably the best way to understand what we do. >> All right, so and great leading. Start with first. Can you tell us a little bit about north from bank? How many locations you have your role there. How long you've been there? Kind of a quick synopsis. >> Sure. Where we're growing. Bank one of three publicly traded publicly held companies in the state of Alaska. We recently acquired residential mortgage after acquiring the last Pacific Bank. And so we have locations all the way from Fairbanks, Alaska, where it gets down to negative 50 negative, 60 below Fahrenheit down to Bellevue, Washington. And to be perfectly candid, what's helped propel some of that growth has been our virtual infrastructure and our virtual desktop infrastructure, which is predicated on us being able to grow our storage, which kind of ties directly into what we've got going on with a tree and >> that that that's great. Can you talk to you know what we're using before what led you to day tree? Um, you know, going with the startup is you know, it's a little risky, right? I thought, Cee Io's you buy on risk >> Well, and as a very conservative bank that serves a commercial market, risk is not something that way by into a lot. But it's also what propels some of our best customers to grow with us. And in this case, way had a lot of faith in the people that joined the company. From an early start, I personally knew a lot of the team from sales from engineering from leadership on That got us interested. Once we kind of got the hook way learned about the technology and found out that it was really the I dare say we're unicorn of storage that we've been looking for. And the reason is because way came from a ray based systems and we have the same revolution that a lot of customers did. We started out with a nice, cosy, equal logic system. We evolved into a nimble solution the hybrid era, if you will, of a raise. And we found that as we grew, we ran into scalability problems. A soon as we started tackling beady eye, we found that we immediately needed to segregate our workloads. Obviously, because servers and production beauty, I have a completely different read right profile. As we started looking at some of the limitations as we grew our video structure, we had to consider upgrading all our processors, all of our solid state drives, all of the things that helped make that hybrid array support our VD infrastructure, and it's costly. And so we did that once and then we grew again because maybe I was so darn popular. within our organization. At that time, we kind of caught wind of what was going on with the atrium, and it totally turned the paradigm on top of its head for what we were looking for. >> How did it? Well, I just heard that up, sir. How did the date Reum solution impact the or what did you talk about? The reed, Right balance? What was it about the day trim solution that solved what was the reed right? Balance you there for the >> young when we ran out of capacity with our equal logic, we had to go out and buy a whole new member when he ran out of capacity with are nimble, had to go out and buy a whole new controller. When we run out of capacity with day tree, um, solution, we literally could go out and get commoditized solid state drives one more into our local storage and end up literally impacting our performance by a magnifier. That's huge. So the big difference between day trim and these >> are >> my words I'm probably gonna screw this up, Bryant, So feel free to jump in, and in my opinion day trip starts out with a really good storage area network appliance, and then they basically take away all of you. I interface to it and stick it out on the network for durable rights. Then they move all of the logic, all of the compression, all of the D duplication. Even the raid calculations on to software that I call a hyper driver that runs the hyper visor level on each host. So instead of being bound by the controller doing all the heavy lifting, you now have it being done by a few extra processors, a few extra big of memory out on their servers. That puts the data as close as humanly possible, which is what hyper converging. But it also has this very durable back end that ensures that your rights are protected. So instead of having to span my storage across all of my hosts, I still have all the best parts of a durable sand on all the best parts of high performance. By bringing that that data closer to where the host. So that's why Atrium enabled us to be able to grow our VD I infrastructure literally overnight. Whenever we ran out of performance, we just pop in another drive and go and the performances is insane. We just finished writing a 72 page white paper for VM, where we did our own benchmarking. Um, using my OMETER sprayers could be using our secondary data center Resource is because they were, frankly, somewhat stagnant, and we knew that we'd be able to get with most level test impossible. And we found that we were getting insane amounts of performance, insane amounts of compression. And by that I can quantify we're getting 132,000 I ops at a little bit over a gig a sec running with two 0.94 milliseconds of late and see that's huge. And one of the things that we always used to compare when it came to performance was I ops and throughput. Whenever we talk to any storage vendor, they're always comparing. But we never talked about lately because Leighton See was really network bound and their storage bender could do anything about that. But by bringing the the brain's closer to the hosts, it solves that problem. And so now our latent C that was like a 25 minutes seconds using a completely unused, nimble storage sand was 2.94 milliseconds. What that translated into was about re X performance increase. So when we went from equal logic to nimble, we saw a multiplier. There we went from nimble toed D atrium. We saw three Export Supplier, and that translated directly into me being able to send our night processors home earlier. Which means less FT. Larger maintenance window times, faster performance for all of our branches. So it went on for a little bit there. But that's what daydreams done for us, >> right? And just to just to amplify that part of the the approached atrium Staking is to assume that host memory of some kind or another flash for now is going to become so big and so cheap that reads will just never leave the host at some point. And we're trying to make that point today. So we've increased our host density, for example, since last year, flash to 16 terabytes per host. Raw within line di Dupin compression. That could be 50 a 100 terabytes. So we have customers doing fairly big data warehouse operations where the reeds never leave the host. It's all host Flash Leighton see and they can go from an eight hour job to, ah, one hour job. It's, you know, and in our model, we sell a system that includes a protected repositories where the rights go. That's on a 10 big network. You buy hosts that have flash that you provisions from your server vendor? Um, we don't charge extra for the software that we load on the host. That does all the heavy lifting. It does the raid compression d do cloning. What have you It does all the local cashing. So we encourage people to put as much flash and as many hosts as possible against that repositories, and we make it financially attractive to do that. >> So how is the storage provisioned? Is it a They're not ones. How? >> So It all shows up, and this is one of the other big parts that is awesome for us. It shows up his one gigantic NFS datastore. Now it doesn't actually use NFS. Itjust presents that way to be anywhere. But previously we had about 34 different volumes. And like everybody else on the planet who thin provisions, we had to leave a buffer zone because we'd have developers that would put a bm where snapshot on something patches. Then forget about it, Philip. The volume bring the volume off lying panic ensues. So you imagine that 30 to 40% of buffer space times each one of those different volumes. Now we have one gigantic volume and each VM has its performance and all of its protection managed individually at the bm level. And that's huge because no longer do you have to set protection performance of the volume level. You can set it right in the B m. Um, >> so you don't even see storage. >> You don't ever have to log into the appliance that all you >> do serve earless storage lists. Rather, this is what we're having. It's >> all through the place. >> And because because all the rights go off, host the rights, don't interrupt each other the host on interrupt together. So we actually going to a lot of links to make sure that happens. So there's an isolation host, a host. That means if you want a provisional particular host for a particular set of demands, you can you could have VD I next door to data warehouse and you know the level of intensity doesn't matter to each other. So it's very specifically enforceable by host configuration or by managing the VM itself. Justus, you would do with the M where >> it gets a lot more flexibility than we would typically get with a hyper converge solution that has a very static growth and performance requirements. >> So when you talk about hyper convergence, the you know, number one, number two and number three things that we usually talk about is, you know, simplicity. So you're a pretty technical guy. You obviously understand this. Well, can you speak to beyond the, you know, kind of ecological nimble and how you scale that house kind of the day's your experience. How's the ongoing, how much you after, you know, test and tweak and adjust things? And how much is it? Just work? >> Well, this is one of the reasons that we went with the atrium is well, you know, when it comes down to it with a hyper converge solution, you're spanning all of your storage across your host, right? We're trying to make use of those. Resource is, but we just recently had one of our server's down because it had a problem with his bios for a little over 10 days. Troubleshooting it. It just doesn't want to stay up. If we're in a full hyper converged infrastructure and that was part of the cluster, that means that our data would've had to been migrated off of that hostess. Well, which is kind of a big deal. I love the idea of having a rock solid, purpose built, highly available device that make sure that my rights are there for me, but allows me to have the elastic configuration that I need on my host to be able to grow them as I see fit. And also to be able to work directly with my vendors to get the pricing points that I need for each. My resource is so our Oracle Servers Exchange Server sequel servers. We could put in some envy Emmy drives. It'll screen like a scalded dog, and for all of our file print servers, I t monitoring servers. We can go with Cem Samsung 8 50 e b o. Drives pop him in a couple of empty days, and we're still able to crank out the number of I ops that we need to be able. Thio appreciate between those at a very low cost point, but with a maximum amount of protection on that data. So that was a big song. Points >> are using both envy. Emmy and Block. >> We actually going through a server? Refresh. Right now, it's all part of the white paper that way. Just felt we decided to go with Internal in Vienna drives to start with two two terabyte internal PC cards. And then we have 2.5 inch in Vienna ready on the front load. But we also plumbed it to be able to use solid state drive so that we have that flexibility in the future to be able to use those servers as we see fit. So again, very elastic architecture and allows us to be kind of a control of what performance is assigned to each individual host. >> So what APS beyond VD? I Do you expect to use this for? Are you already deploying it further? >> VD I is our biggest consumer of resource is our users have come to expect that instant access to all of their applications eventually way have the ability to move the entire data center onto the day trim and so One of the things that we're currently completing this year is the rollout of beady eye to the remaining 40% of our branches. 60% of them are already running through the eye. And then after that, we're probably gonna end up taking our core servers and migrating them off and kind of through attrition, using some of our older array based technology for testing death. All >> right, so I can't let you go without asking you a bit. Just you're in a relationship with GM Ware House Veum. We're meeting your needs. Is there anything from GM wear or the storage ecosystem around them that would kind of make your job easier? >> Yes. If they got rid of the the Sphere Web client, that would be great. I am not a fan of the V Sphere Web client at all, and I wish they'd bring back the C Sharp client like to get that on the record because I tried to every single chance I could get. No, the truth is the integration between the day tree, um and being where is it's super tight. It's something I don't have to think about. It makes it easy for me to be able to do my job at the end of the day. That's what we're looking for. So I think the biggest focus that a lot of the constituents that air the Anchorage being where user group leader of said group are looking for stability and product releases and trying to make sure that there's more attention given to que es on some of the recent updates that they have. Hyper visor Weber >> Brian, I'll give you the final word takeaways that you want people to know about your company, your customers coming out. >> Of'em World. We're thrilled to be here for the second year, thrilled to be here with Ben. It's a It's a great, you know, exciting period for us. As a vendor, we're just moving into sort of nationwide deployment. So check us out of here at the show. If you're not, check us out on the Web. There's a lot of exciting things happening in convergence in general and atriums leading the way in a couple of interesting ways. All >> right, Brian and Ben, thank you so much for joining us. You know, I don't think we've done a cube segment in Alaska yet. so maybe we'll have to talk to you off camera about that. Recommended. All right. We'll be back with lots more coverage here from the emerald 2016. Thanks for watching the Cube. >> You're good at this. >> Oh, you're good.