>>Okay, we're back with the hybrid Cloud power panel. I'm Dave Ante and with me our Eric Lockhart, who's the corporate vice president of Microsoft Azure, Specialized Thomas Corny, the senior vice president of products at Nutanix, and Indu Care, who's the Senior Vice President of engineering, NCI and nnc two at Nutanix. Gentlemen, welcome to the cube. Thanks for coming on. >>It's to >>Be here. Have us, >>Eric, let's, let's start with you. We hear so much about cloud first. What's driving the need for hybrid cloud for organizations today? I mean, I wanna just ev put everything in the public cloud. >>Yeah, well, I mean, the public cloud has a bunch of inherent advantages, right? I mean, it's, it has effectively infinite capacity, the ability to, you know, innovate without a lot of upfront costs, you know, regions all over the world. So there is a, a trend towards public cloud, but you know, not everything can go to the cloud, especially right away. There's lots of reasons. Customers want to have assets on premise, you know, data gravity, sovereignty and so on. And so really hybrid is the way to achieve the best of both worlds, really to kind of leverage the assets and investments that customers have on premise, but also take advantage of, of the cloud for bursting or regionality or expansion, especially coming outta the pandemic. We saw a lot of this from work from home and, and video conferencing and so on, driving a lot of cloud adoption. So hybrid is really the way that we see customers achieving the best of both worlds. >>Yeah, makes sense. I wanna, Thomas, if you could talk a little bit, I don't wanna inundate people with the acronyms, but, but the Nutanix Cloud clusters on Azure, what is that? What problems does it solve? Give us some color there, please. >>That is, so, you know, cloud clusters on Azure, which we actually call NC two to make it simple. And so NC two on Azure is really our solutions for hybrid cloud, right? And you think about the hybrid cloud, highly desirable customers want it. They, they know this is the right way to do for them, given that they wanna have workloads on premises at the edge, any public clouds. But it's complicated. It's hard to do, right? And the first thing that you deal with is just silos, right? You have different infrastructure that you have to go and deal with. You have different teams, different technologies, different areas of expertise and dealing with different portals. Networkings get complicated, security gets complicated. And so you heard me say this already, you know, hybrid can be complex. And so what we've done, we then c to Azure is we make that simple, right? We allow teams to go and basically have a solution that allows you to go and take any application running on premises and move it as is to any Azure region where ncq is available. Once it's running there, you keep the same operating model, right? And that's something actually super valuable to actually go and do this in a simple fashion, do it faster, and basically do, do hybrid in a more cost effective fashion, know for all your applications. And that's really what's really special about NC Azure today. >>So Thomas, just a quick follow up on that. So you're, you're, if I understand you correctly, it's an identical experience. Did I get that right? >>This is, this is the key for us, right? Is when you think you're sending on premises, you are used to way of doing things of how you run your applications, how you operate, how you protect them. And what we do here is we extend the Nutanix operating model two workloads running in Azure using the same core stack that you're running on premises, right? So once you have a cluster deploying C to an Azure, it's gonna look like the same cluster that you might be running at the edge or in your own data center, using the same tools, using, using the same admin constructs to go protect the workloads, make them highly available with disaster recovery or secure them. All of that becomes the same, but now you are in Azure, and this is what we've spent a lot of time working with Americanist teams on, is you actually have access now to all of those suites of Azure services in from those workloads. So now you get the best of both world, you know, and we bridge them together and you get seamless access of those services between what you get from Nutanix, what you get from Azure. >>Yeah. And as you alluded to, this is traditionally been non-trivial and people have been looking forward to this for, for quite some time. So Indu, I want to understand from an engineering perspective, your team had to work with the Microsoft team, and I'm sure there was this, this is not just a press releases or a PowerPoint, you had to do some some engineering work. So what specific engineering work did you guys do and what's unique about this relative to other solutions in the marketplace? >>So let me start with what's unique about this, and I think Thomas and Eric both did a really good job of describing that the best way to think about what we are delivering jointly with Microsoft is that it speeds up the journey to the public cloud. You know, one way to think about this is moving to the public cloud is sort of like remodeling your house. And when you start remodeling your house, you know, you find that you start with something and before you know it, you're trying to remodel the entire house. And that's a little bit like what journey to the public cloud sort of starts to look like when you start to refactor applications. Because it wasn't, most of the applications out there today weren't designed for the public cloud to begin with. NC two allows you to flip that on its head and say that take your application as is and then lift and shift it to the public cloud, at which point you start the refactor journey. >>And one of the things that you have done really well with the NC two on Azure is that NC two is not something that sits by Azure side. It's fully integrated into the Azure fabric, especially the software defined network and SDN piece. What that means is that, you know, you don't have to worry about connecting your NC two cluster to Azure to some sort of a net worth pipe. You have direct access to the Azure services from the same application that's now running on an C2 cluster. And that makes your refactoring journey so much easier. Your management claim looks the same, your high performance notes let the NVMe notes, they look the same. And really, I mean, other than the facts that you're doing something in the public cloud, all the Nutanix goodness that you're used to continue to receive that, there is a lot of secret sauce that we have had to develop as part of this journey. >>But if we had to pick one that really stands out, it is how do we take the complexity, the network complexity, offer public cloud, in this case Azure, and make it as familiar to Nutanix's customers as the VPC construc, the virtual private cloud construct that allows them to really think of their on-prem networking and the public cloud networking in very similar terms. There's a lot more that's gone on behind the scenes. And by the way, I'll tell you a funny sort of anecdote. My dad used to say when I drew up that, you know, if you really want to grow up, you have to do two things. You have to like build a house and you have to marry your kid off to someone. And I would say our dad a third do a code development with the public cloud provider of the partner. This has been just an absolute amazing journey with Eric and the Microsoft team, and you're very grateful for their support. >>I need NC two for my house. I live in a house that was built and it's 1687 and we connect old to new and it's, it is a bolt on, but, but, but, and so, but the secret sauce, I mean there's, there's a lot there, but is it a PAs layer? You didn't just wrap it in a container and shove it into the public cloud, You've done more than that. I'm inferring, >>You know, the, it's actually an infrastructure layer offering on top of fid. You can obviously run various types of platform services. So for example, down the road, if you have a containerized application, you'll actually be able to tat it from OnPrem and run it on C two. But the NC two offer itself, the NCAA often itself is an infrastructure level offering. And the trick is that the storage that you're used to the high performance storage that you know, define Nutanix to begin with, the hypervisor that you're used to, the network constructs that you're used to light MI segmentation for security purposes, all of them are available to you on NC two in Azure, the same way that we're used to do on-prem. And furthermore, managing all of that through Prism, which is our management interface and management console also remains the same. That makes your security model easier, that makes your management challenge easier, that makes it much easier for an accusation person or the IT office to be able to report back to the board that they have started to execute on the cloud mandate and they have done that much faster than they'll be able to otherwise. >>Great. Thank you for helping us understand the plumbing. So now Thomas, maybe we can get to like the customers. What, what are you seeing, what are the use cases that are, that are gonna emerge for this solution? >>Yeah, I mean we've, you know, we've had a solution for a while and you know, this is now new on Azure is gonna extend the reach of the solution and get us closer to the type of use cases that are unique to Azure in terms of those solutions for analytics and so forth. But the kind of key use cases for us, the first one you know, talks about it is a migration. You know, we see customers on the cloud journey, they're looking to go and move applications wholesale from on premises to public cloud. You know, we make this very easy because in the end they take the same culture that are around the application and make them, we make them available Now in the Azure region, you can do this for any applications. There's no change to the application, no networking change. The same IP will work the same whether you're running on premises or in Azure. >>The app stays exactly the same, manage the same way, protected the same way. So that's a big one. And you know, the type of drivers point to politically or maybe I wanna go do something different or I wanna go and shut down education on premises, I need to do that with a given timeline. I can now move first and then take care of optimizing the application to take advantage of all that Azure has to offer. So migration and doing that in a simple fashion, in a very fast manner is, is a key use case. Another one, and this is classic for leveraging public cloud force, which are doing on premises IT disaster recovery and something that we refer to as elastic disaster recovery, being able to go and actually configure a secondary site to protect your on premises workloads, but I that site sitting in Azure as a small site, just enough to hold the data that you're replicating and then use the fact that you cannot get access to resources on demand in Azure to scale out the environment, feed over workloads, run them with performance, potentially feed them back to on premises and then shrink back the environment in Azure to again, optimize cost and take advantage of elasticity that you get from public cloud models. >>Then the last one, building on top of that is just the fact that you cannot get boosting use cases and maybe running a large environment, typically desktop, you know, VDI environments that we see running on premises and I have, you know, a seasonal requirement to go and actually enable more workers to go get access the same solution. You could do this by sizing for the large burst capacity on premises wasting resources during the rest of the year. What we see customers do is optimize what they're running on premises and get access to resources on demand in Azure and basically move the workload and now basically get combined desktops running on premises desktops running on NC two on Azure, same desktop images, same management, same services, and do that as a burst use case during, say you're a retailer that has to go and take care of your holiday season. You know, great use case that we see over and over again for our customers, right? And pretty much complimenting the notion of, look, I wanna go to desktop as a service, but right now I don't want to refactor the entire application stack. I just wanna be able to get access to resources on demand in the right place at the right time. >>Makes sense. I mean this is really all about supporting customers', digital transformations. We all talk about how that was accelerated during the pandemic and, but the cloud is a fundamental component of the digital transformation generic. You, you guys have obviously made a commitment between Microsoft and and Nutanix to simplify hybrid cloud and that journey to the cloud. How should customers, you know, measure that? What does success look like? What's the ultimate vision here? >>Well, the ultimate vision is really twofold. I think the one is to, you know, first is really to ease a customer's journey to the cloud to allow them to take advantage of all the benefits to the cloud, but to do so without having to rewrite their applications or retrain their, their administrators and or or to obviate their investment that they already have and platforms like, like Nutanix. And so the, the work that companies have done together here, you know, first and foremost is really to allow folks to come to the cloud in the way that they want to come to the cloud and take really the best of both worlds, right? Leverage, leverage their investment in the capabilities of the Nutanix platform, but do so in conjunction with the advantages and and capabilities of, of Azure. You know, Second is really to extend some of the cloud capabilities down onto the on-premise infrastructure. And so with investments that we've done together with Azure arc for example, we're really extending the Azure control plane down onto on premise Nutanix clusters and bringing the capabilities that that provides to the, the Nutanix customer as well as various Azure services like our data services and Azure SQL server. So it's really kind of coming at the problem from, from two directions. One is from kind of traditional on-premise up into the cloud and then the second is kind of from the cloud leveraging the investment customers have in in on-premise hci. >>Got it. Thank you. Okay, last question. Maybe each of you can just give us one key takeaway for our audience today. Maybe we start with with with with Thomas and then Indu and then Eric you can bring us home. >>Sure. So the key takeaway is, you know, Nutanix Cloud clusters on Azure is now ga you know, this is something that we've had tremendous demand from our customers, both from the Microsoft side and the Nutanix side going, going back years literally, right? People have been wanting to go and see this, this is now live GA open for business and you know, we're ready to go and engage and ready to scale, right? This is our first step in a long journey in a very key partnership for us at Nutanix. >>Great Indu >>In our Dave. In a prior life about seven or eight, eight years ago, I was a part of a team that took a popular cat's preparation software and moved it to the public cloud. And that was a journey that took us four years and probably several hundred million. And if we had had NC two then it would've saved us half the money, but more importantly would've gotten there in one third the time. And that's really the value of this. >>Okay. Eric, bring us home please. >>Yeah, I'll just point out like this is not something that's just both on or something. We, we, we started yesterday. This is something the teams, both companies have been working on together for, for years, really. And it's, it's a way of, of deeply integrating Nutanix into the Azure Cloud and with the ultimate goal of, of again, providing cloud capabilities to the Nutanix customer in a way that they can, you know, take advantage of the cloud and then compliment those applications over time with additional Azure services like storage, for example. So it really is a great on-ramp to the cloud for, for customers who have significant investments in, in Nutanix clusters on premise, >>Love the co-engineering and the ability to take advantage of those cloud native tools and capabilities, real customer value. Thanks gentlemen. Really appreciate your time. >>Thank >>You. Thank you. >>Okay. Keep it right there. You're watching Accelerate Hybrid Cloud, that journey with Nutanix and Microsoft technology on the cube. You're a leader in enterprise and emerging tech coverage.

(upbeat music) >> Hello, and welcome to this startup showcase. It's great to be here and talk about some of the innovations we are doing at AWS, how we work with our partner community, especially our open source partners. My name is Deepak Singh. I run our compute services organization, which is a very vague way of saying that I run a number of things that are connected together through compute. Very specifically, I run a container services organization. So for those of you who are into containers, ECS, EKS, fargate, ECR, App Runner Those are all teams that are within my org. I also run the Amazon Linux and BottleRocketing. So anything AWS does with Linux, both externally and internally, as well as our high-performance computing team. And perhaps very relevant to this discussion, I run the Amazon open source program office. Serving at AWS for over 13 years, almost 14, involved with compute in various ways, including EC2. What that has done has given me a vantage point of seeing how our customers use the services that we build for them, how they leverage various partner solutions, and along the way, how AWS itself has gotten involved with opensource. And I'll try and talk to you about some of those factors and how they impact, how you consume our services. So why don't we get started? So for many of you, you know, one of the things, there's two ways to look at AWS and open-source and Amazon in general. One is the number of contributors you may have. And the number of repositories that contribute to. Those are just a couple of measures. There are people that I work with on a regular basis, who will remind you that, those are not perfect measures. Sometimes you could just contribute to one thing and have outsized impact because of the nature of that thing. But it address being what it is, increasingly we'll look at different ways in which we can help contribute and enhance open source 'cause we consume a lot of it as well. I'll talk about it very specifically from the space that I work in the container space in particular, where we've worked a lot with people in the Kubernetes community. We've worked a lot with people in the broader CNCF community, as well as, you know, small projects that our customers might have got started off with. For example, I want to like talking about is Argo CD from Intuit. We were very actively involved with helping them figure out what to do with it. And it was great to see how into it. And we worked, etc, came together to think about get-ups at the Kubernetes level. And while those are their projects, we've always been involved with them. So we try and figure out what's important to our customers, how we can help and then take because of that. Well, let's talk about a little bit more, here's some examples of the kinds of open source projects that Amazon and AWS contribute to. They arranged from the open JDK. I think we even now have our own implementation of Java, the Corretto open source project. We contribute to projects like rust, where we are very active in the rest foundation from a leadership role as well, the robot operating system, just to pick some, we collaborate with Facebook and actively involved with the pirates project. And there's many others. You can see all the logos in here where we participate either because they're important to us as AWS in the services that we run or they're important to our customers and the services that they consume or the open source projects they care about and how we get to those. How we get and make those decisions is often depends on the importance of that particular project. At that point in time, how much impact they're having to AWS customers, or sometimes very feel that us contributing to that project is super critical because it helps us build more robust services. I'll talk about it in a completely, you know, somewhat different basis. You may have heard of us talk about our new next generation of Amazon Linux 2022, which is based on fedora as its sub stream. One of the reasons we made this decision was it allows us to go and participate in the preneurial project and make sure that the upstream project is robust, stays robust. And that, that what that ends up being is that Amazon Linux 2022 will be a robust operating system with the kinds of capabilities that our customers are asking for. That's just one example of how we think about it. So for example, you know, the Python software foundation is something that we work with very closely because so many of our customers use Python. So we help run something like PyPy which is many, you know, if you're a Python developer, I happened to be a Ruby one, but lots of our customers use Python and helping the Python project be robust by making sure PyPy is available to everybody is something that we help provide credits for help support in other ways. So it's not just code. It can mean many different ways of contributing as well, but in the end code and operations is where we hang our happens. Good examples of this is projects that we will create an open source because it makes sense to make sure that we open source some of the core primitives or foundations that are part of our own services. A great example of that, whether this be things that we open source or things that we contribute to. And I'll talk about both and I'll talk about things near and dear to my heart. There's many examples I've picked the two that I like talking about. The first of these is firecracker. Many of you have heard about it, a firecracker for those of you who don't know is a very lightweight virtual machine manager, which allows you to run these micro VMs. And why was this important many years ago when we started Lambda and quite honestly, Fugate and foggy, it still runs quite a bit in that mode, we used to have to run on VMs like everything else and finding the right VM for the size of tasks that somebody asks for the size of function that somebody asks for is requires us to provision capacity ahead of time. And it also wastes a lot of capacity because Lambda function is small. You won't even if you find the smallest VM possible, those can be a little that can be challenging. And you know, there's a lot of resources that are being wasted. VM start at a particular speed because they have to do a whole bunch of things before the operating system spins up and the virtual machine spins up and we asked ourselves, can we do better? come up with something that allows us to create right size, very lightweight, very fast booting. What's your machines, micro virtual machine that we ended up calling them. That's what led to firecracker. And we open source the project. And today firecrackers use, not just by AWS Lambda or foggy, but by a number of other folks, there's companies like fly IO that are using it. We know people using firecracker to run Kubernetes on prem on bare metal as an example. So we've seen a lot of other folks embrace it and use it as the foundation for building their own serverless services, their own container services. And we think there's a lot of value and learnings that we can bring to the table because we get the experience of operating at scale, but other people can bring to the table cause they may have specific requirements that we may not find it as important from an AWS perspective. So that's firecracker an example of a project where we contribute because we feel it's fundamentally important to us as continually. We were found, you know, we've been involved with continuity from the beginning. Today, we are a whole team that does nothing else, but contribute to container D because container D underlies foggy. It underlies our Kubernetes offerings. And it's increasingly being used by customers directly by their placement. You know, where they're running container D instead of running a full on Docker or similar container engine, what it has allowed us to do is focus on what's important so that we can operate continuously at scale, keep it robust and secure, add capabilities to it that AWS customers need manifested often through foggy Kubernetes, but in the end, it's a win-win for everybody. It makes continuously better. If you want to use containers for yourself on AWS, that's a great way to you. You know, you still, you still benefit from all the work that we're doing. The decision we took was since it's so important to us and our customers, we wanted a team that lived in breathed container D and made sure a super robust and there's many, many examples like that. No, that we ended up participating in, either by taking a project that exists or open sourcing our own. Here's an example of some of the open source projects that we have done from an AWS on Amazon perspective. And there's quite a few when I was looking at this list, I was quite surprised, not quite surprised I've seen the reports before, but every time I do, I have to recount and say, that's a lot more than one would have thought, even though I'd been looking at it for such a long time, examples of this in my world alone are things like, you know, what work had to do with Amazon Linux BottleRocket, which is a container host operating system. That's been open-sourced from day one. Firecracker is something we talked about. We have a project called AWS peril cluster, which allows you to spin up high performance computing clusters on AWS using the kind of schedulers you may use to use like slum. And that's an open source project. We have plenty of source projects in the web development space, in the security space. And more recently things like the open 3d engine, which is something that we are very excited about and that'd be open sourced a few months ago. And so there's a number of these projects that cover everything from tooling to developer, application frameworks, all the way to database and analytics and machine learning. And you'll notice that in a few areas, containers, as an example, machine learning as an example, our default is to go with open source option is where we can open source. And it makes sense for us to do so where we feel the product community might benefit from it. That's our default stance. The CNCF, the cloud native computing foundation is something that we've been involved with quite a bit. You know, we contribute to Kubernetes, be contribute to Envoy. I talked about continuity a bit. We've also contributed projects like CDK 8, which marries the AWS cloud development kit with Kubernetes. It's now a sandbox project in Kubernetes, and those are some of the areas. CNCF is such a wide surface area. We don't contribute to everything, but we definitely participate actively in CNCF with projects like HCB that are critical to eat for us. We are very, very active in just how the project evolves, but also try and see which of the projects that are important to our customers who are running Kubernetes maybe by themselves or some other project on AWS. Envoy is a good example. Kubernetes itself is a good example because in the end, we want to make sure that people running Kubernetes on AWS, even if they are not using our services are successful and we can help them, or we can work on the projects that are important to them. That's kind of how we think about the world. And it's worked pretty well for us. We've done a bunch of work on the Kubernetes side to make sure that we can integrate and solve a customer problem. We've, you know, from everything from models to work that we have done with gravity on our arm processor to a virtual GPU plugin that allows you to share and media GPU resources to the elastic fabric adapter, which are the network device for high performance computing that it can use at Kubernetes on AWS, along with things that directly impact Kubernetes customers like the CDKs project. I talked about work that we do with the container networking interface to the Amazon control of a Kubernetes, which is an open source project that allows you to use other AWS services directly from Kubernetes clusters. Again, you notice success, Kubernetes, not EKS, which is a managed Kubernetes service, because if we want you to be successful with Kubernetes and AWS, whether using our managed service or running your own, or some third party service. Similarly, we worked with premetheus. We now have a managed premetheus service. And at reinvent last year, we announced the general availability of this thing called carpenter, which is a provisioning and auto-scaling engine for Kubernetes, which is also an open source project. But here's the beauty of carpenter. You don't have to be using EKS to use it. Anyone running Kubernetes on AWS can leverage it. We focus on the AWS provider, but we've built it in such a way that if you wanted to take carpenter and implemented on prem or another cloud provider, that'd be completely okay. That's how it's designed and what we anticipated people may want to do. I talked a little bit about BottleRocket it's our Linux-based open-source operating system. And the thing that we have done with BottleRocket is make sure that we focus on security and the needs of customers who want to run orchestrated container, very focused on that problem. So for example, BottleRocket only has essential software needed to run containers, se Linux. I just notice it says that's the lineups, but I'm sure that, you know, Lena Torvalds will be pretty happy. And seeing that SE linux is enabled by default, we use things like DM Verity, and it has a read only root file system, no shell, you can assess it. You can install it if you wanted to. We allowed it to create different bill types, variants as we call them, you can create a variant for a non AWS resource as well. If you have your own homegrown container orchestrator, you can create a variant for that. It's designed to be used in many different contexts and all of that is open sourced. And then we use the update framework to publish and secure repository and kind of how this transactional system way of updating the software. And it's something that we didn't invent, but we have embraced wholeheartedly. It's a bottle rockets, completely open source, you know, have partners like Aqua, where who develop security tools for containers. And for them, you know, something I bought in rocket is a natural partnership because people are running a container host operating system. You can use Aqua tooling to make sure that they have a secure Indiana environment. And we see many more examples like that. You may think so over us, it's all about AWS proprietary technology because Lambda is a proprietary service. But you know, if you look peek under the covers, that's not necessarily true. Lambda runs on top of firecracker, as we've talked about fact crackers and open-source projects. So the foundation of Lambda in many ways is open source. What it also allows people to do is because Lambda runs at such extreme scale. One of the things that firecracker is really good for is running at scale. So if you want to build your own firecracker base at scale service, you can have most of the confidence that as long as your workload fits the design parameters, a firecracker, the battle hardening the robustness is being proved out day-to-day by services at scale like Lambda and foggy. For those of you who don't know service support services, you know, in the end, our goal with serverless is to make sure that you don't think about all the infrastructure that your applications run on. We focus on business logic as much as you can. That's how we think about it. And serverless has become its own quote-unquote "Sort of environment." The number of partners and open-source frameworks and tools that are spun up around serverless. In which case mostly, I mean, Lambda, API gateway. So it says like that is pretty high. So, you know, number of open source projects like Zappa server serverless framework, there's so many that have come up that make it easier for our customers to consume AWS services like Lambda and API gateway. We've also done some of our own tooling and frameworks, a serverless application model, AWS jealous. If you're a Python developer, we have these open service runtimes for Lambda, rust dot other options. We have amount of number of tools that we opened source. So in general, you'll find that tooling that we do runtime will tend to be always be open-sourced. We will often take some of the guts of the things that we use to build our systems like firecracker and open-source them while the control plane, etc, AWS services may end up staying proprietary, which is the case in Lambda. Increasingly our customers build their applications and leverage the broader AWS partner network. The AWS partner network is a network of partnerships that we've built of trusted partners. when you go to the APN website and find a partner, they know that that partner meets a certain set of criteria that AWS has developed, and you can rely on those partners for your own business. So whether you're a little tiny business that wants some function fulfill that you don't have the resources for or large enterprise that wants all these applications that you've been using on prem for a long time, and want to keep leveraging them in the cloud, you can go to APN and find that partner and then bring their solution on as part of your cloud infrastructure and could even be a systems integrator, for example, to help you solve this specific development problem that you may have a need for. Increasingly, you know, one of the things we like to do is work with an apartment community that is full of open-source providers. So a great one, there's so many, and you have, we have a panel discussion with many other partners as well, who make it easier for you to build applications on AWS, all open source and built on open source. But I like to call it a couple of them. The first one of them is TIDELIFT. TIDELIFT, For those of you who don't know is a company that provides SAS based tools to curate track, manage open source catalogs. You know, they have a whole network of maintainers and providers. They help, if you're an independent open developer, or a smart team should probably get to know TIDELIFT. They provide you benefits and, you know, capabilities as a developer and maintainer that are pretty unique and really help. And I've seen a number of our open source community embraced TIDELIFT quite honestly, even before they were part of the APN. But as part of the partner network, they get to participate in things like ISP accelerate and they get to they're officially an advanced tier partner because they are, they migrated the SAS offering onto AWS. But in the end, if you're part of the open source supply chain, you're a maintainer, you are a developer. I would recommend working with TIDELIFT because their goal is making all of you who are developing open source solutions, especially on AWS, more successful. And that's why I enjoy this partnership with them. And I'm looking to do a lot more because I think as a company, we want to make sure that open source developers don't feel like they are not supported because all you have to do is read various forums. It's challenging often to be a maintainer, especially of a small project. So I think with helping with licensing license management, security identification remediation, helping these maintainers is a big part of what TIDELIFT to us and it was great to see them as part of a partner network. Another partner that I like to call sysdig. I actually got introduced to them many years ago when they first launched. And one of the things that happened where they were super interested in some of our serverless stuff. And we've been trying to figure out how we can work together because all of our customers are interested in the capabilities that cystic provides. And over the last few years, he found a number of areas where we can collaborate. So sysdig, I know them primarily in a security company. So people use cystic to secure the bills, detect, you know, do threat response, threat detection, completely continuously validate their posture, get this continuous analytics signal on how they're doing and monitor performance. At the end of it, it's a SAS platform. They have a very nice open source security stack. The one I'm most familiar with. And I think most of you are probably familiar with is Falco. You know, sysdig, a CNCF project has been super popular. It's just to go SSS what 3, 37, 40 million downloads by now. So that's pretty, pretty cool. And they have been a great partner because we've had to do make sure that their solution works at target, which is not a natural place for their software to run, but there was enough demand and interest from our customers that, you know, or both companies leaned in to make sure they can be successful. So last year sister got a security competency. We have a number of specific competencies that we for our partners, they have integration and security hub is great. partners are lean in the way cystic has onto making our customer successful. And working with us are the best partners that we have. And there's a number of open source companies out there built on open source where their entire portfolio is built on open source software or the active participants like we are that we love working with on a day to day basis. So, you know, I think the thing I would like to, as we wind this out in this presentation is, you know, AWS is constantly looking for partnerships because our partners enable our customers. They could be with companies like Redis with Mongo, confluent with Databricks customers. Your default reaction might be, "Hey, these are companies that maybe compete with AWS." but no, I mean, I think we are partners as well, like from somebody at the lower end of the spectrum where people run on top of the services that I own on Linux and containers are SE 2, For us, these partners are just as important customers as any AWS service or any third party, 20 external customer. And so it's not a zero sum game. We look forward to working with all these companies and open source projects from an AWS perspective, a big part of how, where my open source program spends its time is making it easy for our developers to contribute, to open source, making it easy for AWS teams to decide when to open source software or participate in open source projects. Over the last few years, we've made significant changes in how we reduce the friction. And I think you can see it in the results that I showed you earlier in this stock. And the last one is one of the most important things that I say and I'll keep saying that, that we do as AWS is carry the pager. There's a lot of open source projects out there, operationalizing them, running them at scale is not easy. It's not all for whatever reason. It may not have anything to do with the software itself. But our core competency is taking that and being really good at operating it and becoming experts at operating it. And then ideally taking that expertise and experience and operating that project, that software and contributing back upstream. Cause that makes it better for everybody. And I think you'll see us do a lot more of that going forward. We've been doing that for the last few years, you know, in the container space, we do it every day. And I'm excited about the possibilities. With that. Thank you very much. And I hope you enjoy the rest of the showcase. >> Okay. Welcome back. We have Deepak sing here. We just had the keynote closing keynote vice-president of compute services. Deepak. Great to a great keynote, great wisdom and insight from that session. A very notable highlights and cutting edge trends and product information. Thanks for sharing. >> No, anytime it's always good to be here. It's too bad that we still doing this virtually, but always good to talk to you, John. >> We'll get hopefully through this way pretty quickly, I want to jump right in. Cause we don't have a lot of time. I want to get some quick question. You've brought up a good things. Open source innovation. Okay. Going next level. You've seen the rise of super clouds and super apps developing at open source. You're seeing big companies contributing, you know, you mentioned Argo into it. You're seeing that dynamic where companies are forming around this. This is a rising tide. This is, this is actually real. It's not the old school of, okay, here's a project. And then someone manages support and commercialization of it. It's actually platform in cloud scale. This is next gen. >> Yeah. And actually I think it started a few years ago. We can talk about a company that, you know, you're very familiar with as part of this event, which is armory many years ago, Netflix spun off this project called Spinnaker. A Spinnaker is CISED you know, CSED system that was developed at Netflix for their own purposes, but they chose to open solicit. And since then, it's become very popular with customers who want to use it even on prem. And you have a company that spun up on it. I think what's making this world very unique is you have very large companies like Facebook that will build things for themselves like VITAS or Netflix with Spinnaker and open source them. And you can have a lot of discussion about why they chose to do so, etc. But increasingly that's becoming the default when Amazon or Netflix or Facebook or Mehta, I guess you call them these days, build something for themselves for their own needs. The first question we ask ourselves is, should it be opensource? And increasingly we are all saying yes. And here's what happens because of that. It gives an opportunity depending on how you open source it for innovation through commercial deployments, so that you get SaaS companies, you know, that are going to take that product and make it relevant and useful to a very broad number of customers. You build partnerships with cloud providers like AWS, because our customers love this open source project and they need help. And they may choose an AWS managed service, or they may end up working with this partner on a day-to-day basis. And we want to work with that partner because they're making our customers successful, which is one reason all of us are here. So you're having this set of innovation from large companies from, you know, whether they are just consumer companies like Metta infrastructure companies like us, or just random innovation that's happening in an open source project that which ends up in companies being spun up and that foster that innovative innovation and that flywheel that's happening right now. And I think you said that like, this is unique. I mean, you never saw this happen before from so many different directions. >> It really is a nice progression on the business model side as well. You mentioned Argo, which is a great organic thing that was Intuit developed. We just interviewed code fresh. They just presented here in the showcase as well. You seeing the formation around these projects develop now in the community at a different scale. I mean, look at code fresh. I mean, Intuit did it Argo and they're not just supporting it. They're building a platform. So you seeing the dynamics of tools and now emerging the platforms, you mentioned Lambda, okay. Which is proprietary for AWS and your talk powered by open source. So again, open source combined with cloud scale allows for new potential super applications or super clouds that are developing. This is a new phenomenon. This isn't just lift and shift and host on the cloud. This is actually a construction production developer workflow. >> Yeah. And you are seeing consumers, large companies, enterprises, startups, you know, it used to be that startups would be comfortable adopting some of these solutions, but now you see companies of all sizes doing so. And I said, it's not just software it's software, the services increasingly becoming the way these are given, delivered to customers. I actually think the innovation is just getting going, which is why we have this. We have so many partners here who are all in inventing and innovating on top of open source, whether it's developed by them or a broader community. >> Yeah. I liked, I liked the represent container. Do you guys have, did that drove that you've seen a lot of changes and again, with cloud scale and open source, you seeing the dynamics change, whether you're enabling that, and then you see kind of like real big change. So let's take snowflake, a big customer of AWS. They started out as a startup too, but they weren't a data warehouse. They were bringing data warehouse like functionality and then changing everything differently and making it consumable for the cloud. And hence they're huge. So that's a disruption into an incumbent leader or sector. Then you've got new capabilities emerging. What's your thoughts, Deepak? Can you share your vision on how you have the disruption to existing leaders, old guard, if you will, as you guys call them and then new capabilities as these new platforms emerge at a net new functionality, how do you see that emerging? >> Yeah. So I speak from my side of the world. I've lived in over the last few years, which has containers and serverless, right? There's a lot of, if you go to any enterprise and ask them, do you want to modernize the infrastructure? Do you want to take advantage of automated software delivery, continuous delivery infrastructure as code modern observability, all of them will say yes, but they also are still a large enterprise, which has these enterprise level requirements. I'm using the word enterprise a lot. And I usually it's a trigger word for me because so many customers have similar requirements, but I'm using it here as large company with a lot of existing software and existing practices. I think the innovation that's coming and I see a lot of companies doing that is saying, "Hey, we understand the problems you want to solve. We understand the world where you live in, which could be regulated." You want to use all these new modalities. How do we allow you to use all of them? Keep the advantages of switching to a Lambda or switching to, and a service running on far gate, but give you the same capabilities. And I think I'll bring up cystic here because we work so closely with them on Falco. As an example, I just talked about them in my keynote. They could have just said, "Oh no, we'll just support the SE2 and be done with it." They said, "No, we're going to make sure that serverless containers in particular are something that you're going to be really good at because our customers want to use them, but requires us to think differently. And then they ended up developing new things like Falco that are born in this new world, but understand the requirements of the old world. If you get what I'm saying. And I think that a real example. >> Yeah. Oh, well, I mean, first of all, they're smart. So that was pretty obvious for most people that know, sees that you can connect the dots on serverless, which is a great point, but not everyone can see that again, this is what's new and and systig was just found in his backyard. As I found out on my interview, a great, great founder, they would do a new thing. So it was a very easy to connect the dots there again, that's the trend. Well, I got to ask if they're doing that for serverless, you mentioned graviton in your speech and what came out of you mentioned graviton in your speech and what came out of re-invent this past year was all the innovation going on at the compute level with gravitron at many levels in the Silicon. How should companies and open source developers think about how to innovate with graviton? >> Yeah, I mean, you've seen examples from people blogging and tweeting about how fast their applications run and grab it on the price performance benefits that they get, whether it's on, you know, whether it's an observability or other places. something that AWS is going to embrace across a compute something that AWS is going to embrace across a compute portfolio. Obviously you can go find EC2 instances, the gravitron two instances and run on them and that'll be great. But we know that most of our customers, many of our customers are building new applications on serverless containers and serveless than even as containers increasingly with things like foggy, where they don't want to operate the underlying infrastructure. A big part of what we're doing is to make sure that graviton is available to you on every compute modality. You can run it on a C2 forever. You've been running, being able to use ECS and EKS and run and grab it on almost since launch. What do you want me to take it a step further? You elastic Beanstalk customers, elastic Beanstalk has been around for a decade, but you can now use it with graviton. people running ECS on for gate can now use graviton. Lambda customers can pick graviton as well. So we're taking this price performance benefits that you get So we're taking this price performance benefits that you get from graviton and basically putting it across the entire compute portfolio. What it means is every high level service that gets built on compute infrastructure. And you get the price performance benefits, you get the price performance benefits of the lower power consumption of arm processes. So I'm personally excited like crazy. And you know, this has graviton 2 graviton 3 is coming. >> That's incredible. It's an opportunity like serverless was it's pretty obvious. And I think hopefully everyone will jump on that final question as the time's ticking here. I want to get your thoughts quickly. If you look at what's happened with containers over the past say eight years since the original founding of the first Docker instance, if you will, to how that's evolved and then the introduction of Kubernetes and the cloud native wave we're seeing now, what is, how would you describe the relationship between the success Docker, seeing now with Kubernetes in the cloud native construct what's different and why is this combination so successful? >> Yeah. I often say that containers would have, let me rephrase that. what I say is that people would have adopted sort of the modern way of running applications, whether containers came around or not. But the fact that containers came around made that migration and that journey is so much more efficient for people. So right from, I still remember the first doc that Solomon gave Billy announced DACA and starting to use it on customers, starting to get interested all the way to the more sort of advanced orchestration that we have now for containers across the board. And there's so many examples of the way you can do that. Kubernetes being the most, most well-known one. Here's the thing that I think has changed. I think what Kubernetes or Docker, or the whole sort of modern way of building applications has done is it's taken people who would have taken years adopting these practices and by bringing it right to the fingertips and rebuilding it into the APIs. And in the case of Kubernetes building an entire sort of software world around it, the number of, I would say number of decisions people have to take has gone smaller in many ways. There's so many options, the number of decisions that become higher, but the com the speed at which they can get to a result and a production version of an application that works for them is way low. I have not seen anything like what I've seen in the last 6, 7, 8 years of how quickly the most you know, the most I would say is, you know, a company that you would think would never adopt modern technology has been able to go from, this is interesting to getting a production really quickly. And I think it's because the tooling makes it So, and the fact that you see the adoption that you see right and the fact that you see the adoption that you see right from the fact that you could do Docker run Docker, build Docker, you know, so easily back in the day, all the way to all the advanced orchestration you can do with container orchestrator is today. sort of taking all of that away as well. there's never been a better time to be a developer independent of whatever you're trying to build. And I think containers are a big central part of why that's happened. >> Like the recipe, the combination of cloud-scale, the timing of Kubernetes and the containerization concepts just explode as a beautiful thing. And it creates more opportunities and will challenges, which are opportunities that are net new, but it solves the automation piece that we're seeing this again, it's only makes things go faster. >> Yes. >> And that's the key trend. Deepak, thank you so much for coming on. We're seeing tons of open cloud innovations, thanks to the success of your team at AWS and being great participants in the community. We're seeing innovations from startups. You guys are helping enabling that. Of course, they want to live on their own and be successful and build their super clouds and super app. So thank you for spending the time with us. Appreciate. >> Yeah. Anytime. And thank you. And you know, this is a great event. So I look forward to people running software and building applications, using AWS services and all these wonderful partners that we have. >> Awesome, great stuff. Great startups, great next generation leaders emerging. When you see startups, when they get successful, they become the modern software applications platforms out there powering business and changing the world. This is the cube you're watching the AWS startup showcase. Season two episode one open cloud innovations on John Furrier your host, see you next time.

>>Good morning. Welcome back to the cubes. Continuing coverage of AWS reinvent 2021. I'm Lisa Martin. We have two live sets here. We've got over a hundred guests on the program this week with our live sets of remote sets, talking about the next decade in cloud innovation. And I'm pleased to be welcoming back. One of our cube alumni timbers. She ran the founder and CPO of Jenny-O to the program. Tom is going to be talking about why 2022 is the year open data architectures surpass the data warehouse Timur. Welcome back to the >>Cube. Thanks for having me. It's great to be here. It's >>Great to be here at a live event in person, my goodness, sitting side by side with guests. Talk to me a little bit about before we kind of dig into the data lake house versus the data warehouse. I want to, I want to unpack that with you. Talk to me about what what's going on at Jemena you guys were on the program earlier this summer, but what are some of the things going on right now in the fall of 2021? >>Yeah, for us, it's a big year of, uh, a lot of product news, a lot of new products, new innovation, a company's grown a lot. We're, uh, you know, probably three times bigger than we were a year ago. So a lot of, a lot of new, new folks on the team and, uh, many, many new customers. >>It's good, always new customers, especially during the last 22 months, which have been obviously incredibly challenging, but I want to unpack this, the difference between a data lake and data lake house, but I love the idea of a lake house by the way, but talk to me about what the differences are similarities and how customers are benefiting. Sure. Yeah. >>I think you could think of the lake house as kind of the evolution of the lake, right? So we have, we've had data lakes for a while. Now, the transition to the cloud made them a lot more powerful and now a lot of new capabilities coming into the world of data lakes really make the, that whole kind of concept that whole architecture, much more powerful to the point that you really are not going to need a data warehouse anymore. Right. And so it kind of gives you the best of both worlds, all the advantages that we had with data lakes, the flexibility to use different processing engines, to have data in your own account and open formats, um, all those benefits, but also the benefits that you had with warehouses, where you could do transactions and get high performance for your, uh, BI workloads and things like that. So the lake house makes kind of both of those come together and gives you the, the benefits of both >>Elizabeth talk to me about from a customer lens perspective, what are some of the key benefits and how does the customer go about from say they've got data warehouses, data lakes to actually evolving to the lake house. >>You know, data warehouses have been around forever, right? And you know, there's, there's been some new innovation there as we've kind of moved to the cloud, but fundamentally there are very close and very proprietary architecture that gets very expensive quickly. And so, you know, with a data warehouse, you have to take your data and load it into the warehouse, right. You know, whether that's a, you know, Terra data or snowflake or any, any other, uh, you know, database out there, that's, that's what you do. You bring the data into the engine. Um, the data lake house is a really different architecture. It's one where you actually, you're having, you have data as its own tier, right? Stored in open formats, things like parquet files and iceberg tables. And you're basically bringing the engines to the data instead of the data to the engine. And so now all of a sudden you can start to take advantage of all this innovation that's happening on the same set of data without having to copy and move it around. So whether that's, you know, Dremio for high performance, uh, BI workloads and SQL type of analysis, a spark for kind of batch processing and machine learning, Flink for streaming. So lots of different technologies that you can use on the, on the same data and the data stays in the customer's own account, right? So S3 effectively becomes their new data warehouse. >>Okay. So it can imagine during the last 22 months of this scattered work from Eddie, and we're still in this work from anywhere environment with so much data being generated at the edge of the edge, expanding that bringing the engines to the data is probably now more timely than ever. >>Yeah. I think the, the growth in data, uh, you see it everywhere, right? That that's the reason so many companies like ourselves are doing so well. Right? It's, it's, there's so much new data, so many new use cases and every company wants to be data-driven right. They all want to be, you know, to, to democratize data within the organization. Um, you know, but you need the platforms to be able to do that. Right. And so, uh, that's very hard if you have to constantly move data around, if you have to take your data, you know, which maybe is landing in S3, but move it into, you know, subsets of it into a data warehouse. And then from there move, you know, substance of that into, you know, BI extracts, right? Tableau extracts power BI imports, and you have to create cubes and lots of copies within the data warehouse. There's no way you're going to be able to provide self-service and data democratization. And so really requires a new architecture. Um, and that's one of the main things that we've been focused on at Dremio, um, is really taking the, the, the lake house and the lake and making it, not just something that data scientists use for, you know, really kind of advanced use cases, but even your production BI workloads can actually now run on the lake house when you're using a SQL technology. Like, and then >>It's really critical because as you talked about this, you know, companies, every company, these days is a data company. If they're not, they have to be, or there's a competitor in the rear view mirror that is going to be able to take over what they're doing. So this really is really critical, especially considering another thing that we learned in the last 22 months is that there's no real-time data access is no longer, a nice to have. It's really an essential for businesses in any organization. >>I think, you know, we, we see it even in our own company, right? The folks that are joining the workforce now, they, they learn sequel in school, right. They, they, they don't want to report on their desk, printed out every Monday morning. They want access to the database. How do I connect my whatever tool I want, or even type sequel by hand. And I want access to the data and I want to just use it. Right. And I want the performance of course, to be fast because otherwise I'll get frustrated and I won't use it, which has been the status quo for a long time. Um, and that's basically what we're solving >>The lake house versus a data warehouse, better able to really facilitate data democratization across an organization. >>Yeah. Because there's a big, you know, people don't talk a lot about the story before the story, right. With, with a data warehouse, the data never starts there. Right. You typically first have your data in something like an S3 or perhaps in other databases, right. And then you have to kind of ETL at all into, um, into that warehouse. And that's a lot of work. And typically only a small subset of the data gets ETL into that data warehouse. And then the user wants to query something that's not in the warehouse. And somebody has to go from engineering, spend, you know, a month or two months, you know, respond to that ticket and wiring up some new ETL, uh, to get the data in. And so it's a big problem, right? And so if you can have a system that can query the data directly in S3 and even join it with sources, uh, outside of that things like your Oracle database, your, your SQL server database here, you know, Mongo, DB, et cetera. Well, now you can really have the ability to expose data to your, to your users within the company and make it very self-service. They can, they can query any data at any time and get a fast response time that that's, that's what they need >>At self-service is key there. Speaking of self-service and things that are new. I know you guys dromio cloud launched that recently, new SAS offering. Talk to me about that. What's going on there. Yeah. >>We want to stream your cloud. We, we spent about two years, um, working on that internally and, uh, really the goal was to simplify how we deliver all of the, kind of the benefits that we've had in our product. Right. Sub-second response times on the lake, a semantic layer, the ability to connect to multiple sources, but take away the pain of having to, you know, install and manage software. Right. And so we did it in a way that the user doesn't have to think about versions. They don't have to think about upgrades. They don't have to monitor anything. It's basically like running and using Gmail. Right? You log in, you, you get to use it, right. You don't have to be very sophisticated. There's no, not a lot of administration you have to do. Um, it basically makes it a lot, a lot simpler. >>And what's the adoption been like so far? >>It's been great. It's been limited availability, but we've been onboarding customers, uh, every week now. Um, many startups, many of the world's largest companies. So that's been, that's been really exciting actually. >>So quite a range of customers. And one of the things, it sounds like you want me to has grown itself during the pandemic. We've seen acceleration of, of that, of, of, uh, startups, of a lot of companies, of cloud adoption of migration. What are some, how have your customer conversations changed in the last 22 months as businesses and every industry kind of scrambled in the beginning to, to survive and now are realizing that they need to modernize, to thrive and to be competitive and to have competitive advantage. >>I think I've seen a few different trends here. One is certainly, there's been a lot of, uh, acceleration of movement to the cloud, right? With, uh, uh, you know, how different businesses have been impacted. It's required them to be more agile, more elastic, right. They don't necessarily know how much workload they're gonna have at any point in time. So having that flexibility, both in terms of the technology that can, you know, with Dremio cloud, we scale, for example, infinitely, like you can have, you know, one query a day, or you can have a thousand queries a second and the system just takes care of it. Right. And so that's really important to these companies that are going through, you know, being impacted in various different ways, right? You had the companies, you know, the Peloton and zooms of the world that were business was exploding. >>And then of course, you know, the travel and hospitality industries, and that went to zero, all of a sudden it's been recovering nicely, uh, you know, since then, but so that flexibility, um, has been really important to customers. I think the other thing is just they've realized that they have to leverage data, right? Because in parallel to this pandemic has been also really a boom in technology, right? And so every industry is being disrupted by new startups, whether it's the insurance industry, the financial services, a lot of InsureTech, FinTech, you know, different, uh, companies that are trying to take advantage of data. So if you, as a, as an enterprise are not doing that, you know, that's a problem. >>It is a problem. It's definitely something that I think every business and every industry needs to be very acutely aware of because from a competitive advantage perspective, you know, there's someone in that rear view mirror who is going to be focused on data. I have a real solid, modern data strategy. That's going to be able to take over if a company is resting on its laurels at all. So here we are at reinvent, they talked a lot about, um, I just came off of Adam psyllid speeds. So Lipsey's keynote. But talk to me about the jumbo AWS partnership. I know AWS its partner ecosystem is huge. You're one of the partners, but talk to me about what's going on with the partnership. How long have you guys been partners? What are the advantages for your customers? >>You know, we've been very close partners with AWS for, for a number of years now, and it kind of spans many different parts of AWS from kind of the, uh, the engineering organization. So very close relationship with the S3 team, the C2 team, uh, you know, just having dinner last night with, uh, Kevin Miller, the GM of S3. Um, and so that's kind of one side of things is really the engineering integration. You know, we're the first technology to integrate with AWS lake formation, which is Amazon's data lake security technology. So we do a lot of work together on kind of upcoming features that Amazon is releasing. Um, and then also they've been really helpful on the go-to-market side of things on the sales and marketing, um, whether it's, you know, blogs on the Amazon blog, where their sales teams actually promoting Dremio to their customers, um, uh, to help them be successful. So it's really been a good, good partnership. >>And there they are, every time I talked to somebody from Amazon, we always talk about their kind of customer first focus, their customer obsession sounds like you're, there's deep alignment on from the technical engineering perspective, sales and marketing. Talk to me a little bit about cultural alignment, because when you're going into customer conversations, I imagine they want to see one unified team. >>Yeah. You know, I think Amazon does have that customer first and obviously we do as well. And we, you know, we have to right as a, as a startup for us, you know, if a customer has a problem, the whole company will jump on that problem. Right. So that's where we call it customer obsession internally. Um, and I think that's very much what we've seen, you know, with, with AWS as well as the desire to make the customer successful comes before. Okay. How does this affect a specific Amazon product? Right? Because anytime a customer is, uh, you know, using Dremio on AWS, they're also consuming many different AWS services and they're bringing data into AWS. And so, um, I, I think for both of us, it's all about how do we solve customer problems and make them successful with their data in this case. Yup. >>Solving those customer problems is the whole reason that we're all here. Right. Talk to me a little bit about, um, as we have just a few more minutes here, we, when we hear terms like, future-proof, I always want to dig in with, with folks like yourself, chief product officers, what does it actually mean? How do you enable businesses to create these future-proof data architectures that are gonna allow them to scale and be really competitive? Sure. >>So yeah, I think many companies have been, have experienced. What's known as lock-in right. They, they invest in some technology, you know, we've seen this with, you know, databases and data warehouses, right? You, you start using that and you can really never get off and prices go up and you find out that you're spending 10 times more, especially now with the cloud data warehouses 10 times more than you thought you were going to be spending. And at that point it becomes very difficult. Right? What do you do? And so, um, one of the great things about the data lake and the lake house architecture is that the data stays stored in the customer's own account. Right? It's in their S3 buckets in source formats, like parquet files and iceberg tables. Um, and they can use many different technologies on that. So, you know, today the best technology for, for, you know, sequel and, you know, powering your, your mission critical BI is, is Dremio, but tomorrow they might be something else, right. >>And that customer can then take that, uh, uh, that company can take that new technology point at the same data and start using it right. That they don't have to go through some really crazy migration process. And, you know, we see that with Teradata data and Oracle, right? The, the, the old school vendors, um, that's always been a pain. And now it is with the, with the newer, uh, cloud data warehouses, you see a lot of complaints around that, so that the lake house is fundamentally designed. Especially if you choose open source formats, like iceberg tables, as opposed to say a Delta, like you're, you're really, you know, future-proofing yourself. Right. Um, >>Got it. Talk to me about some of the things as we wrap up here that, that attendees can learn and see and touch and feel and smell at the jumbo booth at this reinvent. >>Yeah. I think there's a, there's a few different things they can, uh, they can watch, uh, watch a demo or play around with the dremmel cloud and they can talk to our team about what we're doing with Apache iceberg. It's a iceberg to me is one of the more exciting projects, uh, in this space because, you know, it's just created by Netflix and apple Salesforce, AWS just announced support for iceberg with that, with their products, Athena and EMR. So it's really kind of emerging as the standard table format, the way to represent data in open formats in S3. We've been behind iceberg now for, for a while. And so that to us is very exciting. We're happy to chat with folks at the booth about that. Um, Nessie is another project that we created an source project for, uh, really providing a good experience for your data, where you have version control and branching, and kind of trying to reinvent, uh, data engineering, data management. So that's another cool project that there, uh, we can talk about at the booth. >>So lots of opportunity there for attendees to learn even thank you, Tomer for joining me on the program today, talking about the difference between a data warehouse data lake, the lake house, did a great job explaining that Jamil cloud what's going on and how you guys are deepening that partnership with AWS. We appreciate your time. Thank you. Thanks for having me. My pleasure for Tomer. She ran I'm Lisa Martin. You're watching the cube. Our coverage of AWS reinvent continues after this.

>> Announcer: Live from San Francisco, celebrating ten years of high-tech coverage, it's theCUBE! Covering VMworld, 2019. Brought to you by VMware and its ecosystem partners. >> Kay welcome back everyone, live CUBE coverage here at VMworld 2019 in San Francisco, we're in Moscone North lobby, I'm John Furrier. My cohost Stu Miniman. We're here with two great guests, David Appel, Vice President C2 Space and Intelligence and Defense, Civil Solutions at Raytheon, and Gil Shneorson, who's the senior vice president general manager of VxRail, of Dell EMC, great to have Raytheon, anything with space Stu and I get jacked up for that. Thanks for coming on. >> Yeah I appreciate it, thank you, I'm glad to be here. >> Gil, VxRail, got a customer here, impressive role out. Talk about the story. >> Well I think it starts with the fact that we have recently announced our support for Pivotal community services over VMware Cloud Foundation over VxRail which has actually the only Q-rated automated stacking industry that allows people to leverage containers and infrastructure as a service on one stack and we've been doing this for about three years now in a different way called Pivotal Ready Architecture and Raytheon has actually adopted that architecture to help their customer, the air force. And that's why we're here today together to talk about you know. >> Seriously modernization couldn't be a more important conversation in government solutions, you guys are a big provider, Raytheon, known for the tech chops, known for having good engineering. Talk about the solution, what you guys did, what's the use case, talk about the deployment. >> Yes with what's going on with the federal government for a while is the acquisition processes and what's taking sometimes years or decades to get software in the field is causing a lot of unmet requirements and needs of the ultimate user, the war fighters out in the field, to be met. So we've been on a journey for the last two years with Pivotal and Dell of how to help the air force, modernize the air force has gone under a transformation and a program called Kessel Run which is where we've deployed the Pivotal Ready Architecture to allow us to quickly deploy an infrastructure and allow us to focus on the end users and develop the capabilities that they need worldwide. And what took years and to now months and days so it's been a fantastic journey. >> Tell us what that means for the folks that might not know the pace of the procurement process. I mean some of this stuff is like 1995 procurement rules. I mean modernization these days is such an important part of it because the impact is significantly relevant. Share some color into the process. >> If you think about in the commercial world today where hundreds of applications be deployed overnight and updates on the what, hourly basis. In the government space it can literally take years to define a requirement, then you have to go through a budgeting cycle all the way up through congress and then you have to go through an acquisition cycle that could take a year to complete and so by the time you're actually fielding capability it is literally five years or more by the time the need was actually identified. And in that five years the technology probably changed which means your solution has probably changed from what's currently available. So shortening the cycles is what it's all about. >> And that's really about having the right product at the right time, not the old product five years ago. How fast things change, it's pretty important to have that nailed down. >> It's pretty amazing and you know I think you look at transformation and there's usually a trade off. What we have been working on and what we're announcing but really what we've been leaving over the last four years is a way to transform but stay close to your core. In other words transformation without trade offs. And so if you can get your VMware stack now running containers in a fully managed automated stack you don't have to change your skill set and you can do all of that and start innovating while staying very close to your core competency. You know you transform but you don't have to go too far and I think the story what Raytheon did is fairly amazing because they turned, you know, what did you tell me, a 50-year-old process, you know in like in less than half a year you turned automated systems that you know saves the US air force a lot of money. >> And lives too, are saved. I mean you're talking about people in the field, this is about people's lives too, I mean this is the money making. >> And it's been about transforming the culture of the way the DoD does software and the first example that Gil is mentioning was tanker planning which was the ability for the air force to refuel flight missions in the air, would typically take over eight hours to plan. And it was done by a white board. It was done manually. And in order to automate that and shrink the time, again that would have gone to that five year procurement cycle. We were able to deploy new applications using the Pivotal-ready architecture within 150 days and get those out worldwide to the field. That's done two things. It's from a financial perspective it's saving over $200,000 a day in just fuel costs from optimizing the tanker planning. But more importantly it's actually more efficient and protecting the safety of those flight crews. They're not in the air as long, they might not be in a hostile environment as long, so the security of the air force is even more important. >> As Pivotal always says they're outcome driven and that's pretty good outcome. I mean talk about the impact that you've had on everyone else around you because I'm sure there's some blockers in your way, people's feathers got ruffled, but then people see success they want to come copy it, right? So that's a pattern you see in a lot of government work. Hey there's a new way to do it, modern way. >> Yeah so our hindsight we're seeing it in two ways. One from a broader DoD perspective. The air force was out front here. They established this and from a DoD perspective what they're calling their Kessel Run initiative is really taking off. You're seeing other Kessel Run like programs being stood up like a program called Kobayashi Maru and Rogue Blue and a few others across DoD. So it's proliferating out across the DoD from a customer perspective, DoD customer perspective. From an industry perspective you know our competitors are quickly trying to catch up to us and they're trying to, you know, copy our playbook but we're continuing to innovate and continue on this journey so we're moving ahead with Pivotal and Dell. >> First of all David I think Pat Gelsinger must have been talking to your team because you're mashing up Star Wars and Star Trek with Kessel Run and Kobayashi there. But talk about mashing up, the stack that you're putting together, VxRail was really built around simplicity. It delivers that, that's what hyperconverged infrastructure does. You start talking about VCF and containers and PKS on that, Kubernetes nobody says is simple, but you know help us walk through, you know, how simple is it for you to leverage and deploy this. You've got organizational challenges and other things, so, you know, where is the solution, it sounds like you use the ready node, and where directionally is it headed? >> Yeah let me answer from this perspective. So we started this journey with Pivotal and the air force about two years ago. And at that time we started with a group of probably a dozen or less folks that actually even understood the technology or the products and the solutions that Dell and Pivotal bring forward. In those two years we're now up to over 100 people. Fully embracing the technology. It's creating an environment where it's easier for us to recruit and retain people because it's modern, it's not the old ways we used to do business. And we're finding that it's been very easy to deploy, very easy to train people up and very easy to operate. So from that perspective it's just been fantastic from not just the technology perspective but also the cultural transformation perspective. >> Yeah Gil I'd love you to comment on that because you know remember gosh when CI and HCI first rolled out you know the people that had those jobs were worried we were going to take their jobs away. Now when I hear your customer talking about, you know, it's easy to train them and even easier for me to recruit and retain, a powerful story. Are you hearing that across your customer base? >> Yeah I'll tell you what's a little different. In the past we have simplified things and we've made work somewhat go away but there was no alternative work. Today every developer, every IT person, they can't wait to go and be a dev ops person, right? So for IT when we come in and we say we're going to take this off your plate so you can free up your time, it really means something now, 'cause they know exactly what they want to do. They want to go and they want to be dev ops, they want to develop new apps, they want to move forward. And so it's very syngergistic in a way that we offload some of the burden from them and they actually do free up to do cooler stuff and then they like it. >> And they get to keep their traditional apps, with containers, gives them great capabilities. Not the throwaway. >> And that's a great point I think as I said before and it's really important to convey this, the transformation without trade offs is a big deal because they can keep the application. They can run the same environment. Right in our case they can do it you know at ease and in remote locations all over the world with less management. And at the same time they can innovate and manage those environments. And I think as long as we can keep that up we'll make a lot of people productive. >> Well I got to ask David the security question because one of the things that comes up all the time obviously Department of Defense, security's top of mind. Industrial IOT are now not just malware getting in for credit card information, you're talking about actual equipment, you're talking about flights in the air, hacking with physical things is a concern and it's a big IOT kind of conversation. You're in the middle of that, this is your world. What's your thoughts on the security? >> You know so we've obviously had to go through that in order to get authority to operate to push things into theater and one of the strongest benefits we've seen is the dev ops process and the platforms has all that security built in and all the testing as we're going through it. So the thousands of tests that are running as new threats are identified, the platform is updating with the latest patches or whatever it may be, so. >> John: On the automation stuff? >> On the automation side of it. So we're actually seeing a lot of the security, I don't want to call it risks go away, but our ability to mitigate them is being built into the software itself. So we haven't seen an issue yet where we haven't been able to get things authority to operate and push it out to the field, so. >> There's a high bar there too, obviously. >> It's a very high bar, very high bar, and that was part of the also the challenge of getting systems fielded in months and days versus years because of the ability to get that operations. >> Now this is a really big story I think. First of all Raytheon's a well-known brand, but, the modernization of getting stuff into theater and or into your production theater, military operations, that's a big deal, I mean, I think people don't really understand that aren't in government how fast this happens. I think that's a real testament to the solution, so I mean. >> Well the powerful thing to it is the national defense strategy is all about capability at the speed of relevance, and that's all about technology. Future wars aren't going to be decided by the size of your army or the size of your arsenal. It's going to be about how do you get data to decision makers faster and how do they can act faster. And that's where software and this infrastructure we're putting in place and putting capabilities in the hands of people that need it faster. That's what it's all about. >> And you know Secretary Matthis who was former Secretary of Defense said 48% of all the casualties are usually frontline war fighters. And that's where the technology edges so to speak. So again this is such a cutting edge topic, talk about it for days. How do you feel about this? This is pretty exciting. >> I'm just happy that every time I come into theCUBE, this is the second time I do it with a customer, you give me the opportunity to learn, you know, have a deeper relationship with one of my of probably now 7,000 customers. Which you know is really hard to keep up with these days and so you know we make technologies for people to use and when you see it in the field doing good it's a great thing. >> Well it's a transformation story. It's really a great transformation story. They have to, making a difference. >> Great, David, would love to hear, you know, what's on your ask for your partners that are deploying. Kind of give us a look forward roadmap that you can share. >> Yeah again I go back to everything we're about right now is speed and and getting capability faster. Currently in our marketplace right now we're fully embracing agile dev ops and everything it takes to deploy software from that perspective. Moving into things like artificial intelligence and machine learning and autonomy are the big things that are on our horizon from a technology perspective. And as our partners are in those areas and can help us bring more capability in that, that's going to help our end customer, the DoD, faster as well, so. >> What's the big takeaway from VMworld this year for you guys? What's the big observation? >> I'll be honest this is my first time at VMware. I'm amazed, I was at Dell Technology World a few months ago, I've really enjoyed it, I think it's a great event. And I'm just enjoying learning all the technologies so, it's, I've enjoyed the day. >> Gil what's your big takeaway? >> Well I'm part of the family. So I'm a little more familiar and even for me-- >> Whoever: You were briefed. >> No, no, even for me the rate of innovation that Vmworld puts out there is amazing. Right and you see how everything plugs together and you see how the vision keeps being, you know, completed, right, and we're in a good spot in the sense that we actually have what people need right now. And we do it better than everybody else. And you'd think that being number one in almost every category you'd be sitting there complacent and no, you know, we keep pushing the envelope, doing more innovating, more integrating more, so it's very exciting to see what's happening. >> Well great story here, Raytheon congratulations for your success I think it's super important to have a prepared military, certaintly, and saving lives and doing it in a modern way is kind of of a miracle these days in government, so congratulations. >> And I thank our partners for continuing to innovate 'cause that's helping us so. >> All right, great story, CUBE coverage here, Vmworld 2019, I'm John Furrier with Stu Miniman. We'll be back with more after this short break. (upbeat electronic music)

>> Announcer: Live from Las Vegas, it's theCUBE, covering AWS reInvent 2017. Presented by AWS, Intel, and our ecosystem of partners. >> Can you hear that? That's the sound of a happy conference right now. 40,000 plus here gathered, we are live here in Las Vegas. Here at re:Invent, AWS putting on its three day event with great success we might add. Along Justin Warren, I'm John Walls. We're now joined with a couple of folks who are from the Red Hat side of the fence. Let's start with Tim Apnell who is the Senior Principal Product Manager at OpenShift. Tim, nice to have you here. >> Oh with Ansible. >> Oh Ansible, OpenShift, alright. He's on the OpenShift side of the family. Alright so, I knew I was gonna get that confused. First of all, let's talk about OpenShift a little bit though Eric. >> Sure. >> You had an announcement just about a week ago. >> Yep. >> Getting a little more aligned with AWS. Obviously, you're here with that announcement a week ago, but tell us a little bit more about that. >> Yeah certainly. So what we've actually done is we've had a long partnership with Amazon, or AWS. And we're enabling the AWS services natively on OpenShift. So what that really means is you can go right from what we call is the service catalog is the User interface. And developers really don't need to know where their services are running. What they're able to do now is go into that service catalog, order AWS services along side of their applications and they really can deploy hybrid workloads. And really, it couldn't be any easier you don't have to switch between consoles, you don't have to go to outside of OpenShift. It can all be done on the platform. >> And what was that response to? Because I'm sure you talk to customers right? You hear what the workloads that they're trying to handle. They liked the cloud environment, they like AWS, like what's going on there, but what were you trying to do for them that solved the problem solvent? >> Yeah we're definitely listening to our customers and we have a lot of customers who run hybrid workloads. And really the goal of this was to make it easier, right. We heard loud and clear hybrid workloads are important. They're a part of most companies' business. And they wanted a way that was really seamless and easy to reduce the overhead and complication on the developers. And by being able to pull those services into the user interface, it really makes it a lot easier to deploy all the popular services on AWS again right from the platform without having to ever leave that environment. So it makes it a lot more easier and comfortable for the developers, and it makes them a lot more efficient. >> Yeah, what are some of the services that you're hearing developers demand? Like what are the ones that they really want to use on OpenShift? >> Yeah, there's quite a few. So we've enabled 10 initially, I'm not gonna go through all 10, but things like RDS, right, so their relational database service, uh, SQS, simple queuing service, SNS, Athena, RHEL53, I mean the list goes on an on. So... You know there's definitely a lot of services we have today, but what we're really doing is we're taking a lot of that feedback now that we've actually enabled this. We made it available, it's public. You can get the code today. And then we're starting, getting feedback, and as we get that feedback, we're enabling more services. And the nice part about this is the, it's automatic. When you put a new service out there, their environment can immediately consume it, right. It doesn't have to do any special changes or enablements or reconfigurations. It's really just up to the administrator to decide which services they want to expose to their users. >> Yeah, so what is it about putting those services in OpenShift that really amplifies the way that you develop with OpenShift? Because developing software on OpenShift is quite different from other forms of software development which, without that kind of platform. So, what is it about putting these services that amplifies the ability of what you can do as a developer in OpenShift? >> Yeah, so it's kind of a multi-part question. Let me see if I can do it some justice. I think one of the nice things is we're based on Kubernetes, and Kubernetes is one of the defacto standards today for orchestrating workloads. So not only do a lot of these workloads again, are hybrid based, right. So they're both on premise and in the cloud, but it pretty much adds that layer of flexibility there that you really don't have to kind of pick, right. You don't have to have it all in, you know, Amazon's AWS environment or on prem, right. You can run it full. And the nice part about this enablement that we did, which makes it really flexible, is in an on prem environment, we can actually enable the services there to be able to take advantage of deploying AWS services natively from on premise. I mean, obviously all those services still run in the cloud, but you can actually run them, run the software to enable it locally. Likewise if you have an instance of OpenShift where you're doing development in the cloud, in C2, you can actually run it there, and you still have access to it. So it's really flexible in how you want to do that. It's not just confined to, you know, in the cloud, it's also available on prem. >> Yeah, that's, it provides you with that flexibility without it being too complicated and having to go into the weeds and figure out exactly how you do it in 900 different ways. You can say well actually we just standardized on this one OpenShift approach but you get this, the access and the choice that developers really, really like. >> Yeah, it's, one of the things that we're, again, we're based on the Kubernetes standard, so we have, something called the OpenShift service catalog, and that's the Kubernetes upstream project. And what that is is that standardized interface. And it's really meant to automate, to make things more efficient. Normally you would have a ticket queuing system, you order a service, you know, a number of days it takes an IT operations person some time to get that implemented. And then you get the credentials, you get an in point, and then you can finally tie that in to your service, right. And that stays wasted. With the service catalog, it really sort of enables self service, right for developers. So they can go in, not only that, all those services that they create and they put in that catalog that they can deploy, yeah, and that's sort of married with all the services that they may need for their hardware workload. So we all need less services. So it really makes it a simple, easy way to deploy your workloads, deploy your applications without a lot of work. >> And I know one of the ways that you're exposing those services is using the Ansible. What's it, the Ansible service broker, is that what it's called? >> Yeah, we're using Ansible, the OpenShift team has used Ansible automation to make creating these services more easy to develop and deploy into their platform. >> Yeah, so... >> Just one of the ways that, you know, the flexibility of the Ansible tool. Adapting. >> Tell us a bit more about how developers are using that Ansible, particularly around that service brokerage idea, but more around like, Ansible is available as Open source, Red Hat is famous for being very open. >> Yes it is. >> But it also has Enterprise capabilities. So could you walk us through a bit more about that. How are developers using this to access services? And then what are some of the enterprise capabilities that they can get with Ansible? >> Well, specific to what the OpenShift team launched, they're able to develop these services and use the entire suite of Ansible bundle modules that are bundled together. And then brought in as services, so they're able to mount and provision different types of services only knowing Ansible automation. They don't need to know like Golang or some type of other sophisticated thing, so there's a lot... It's bringing something more powerful in a more simple way to the OpenShift platform. More specifically, or more broadly I should say, Ansible's always been a highly flexible tool that can adapt to different workflows, different environments, whether that's on prem, legacy environments, or pure cloud or hybrid cloud environments. So you know, this is just one way that it's been used differently, but we're seeing it used throughout the RedHat portfolio. And it's always been a strength with Amazon that we've always had a strong Amazon Web Services community within Ansible whether it's just traditional compute, or even doing things in the server-less space, Lambda, and moving beyond that, we're able to do that complete automation from end to end. >> Yeah. As a Python guy I've got a special place in my heart for Ansible. >> Yeah. >> I actually quite like that type of thing. And I like being able to do things in a Python-y kind of way >> Yeah. >> So yeah, it's like Golang... I hear people really like, but I like my Python. >> Yeah. But we try to keep that where users don't have to really know Python, but that is what Ansible is underneath, and it is, when you want to extend Ansible, what you would use, but the vast majority of users don't really need programming skills, they're working with very human readable, declarative forms of defining the state they want their servers and their computing resources to be in. >> Yeah, Ansible is sort of historically used for things like, it's more of an infrastructure configuration tool, but we've got service configuration now as well. And something like OpenShift is much more application developer-centric. So I'm seeing a real blending of those two kinds of people who are doing development. They're kind of two different forms of developers. But now they're basically blending themselves together and becoming one team... Do you see that as where development is going? That pretty much everyone becomes a software developer? >> Well I know from the Ansible stand point, we're continuing to explore bringing that simplicity and power to all these different ways that we can... We can adapt that and... Since we've joined the RedHat family we're finding all these different, exploring all these different ways that we can work together and bring that type of value to its end-users, to its customers. >> And what do you think at the end of the day, when you say, you know we talked about customers and trying to meet demands and what have you. If you have to look down the road, and say for the next 6, 9 months, this is what we're going to try to address, this is what we're hearing from our customers that they need attended to, that you can provide help for, what would that be? What headache are people bringing to you right now? And say Tim give me a hand. >> The headaches? Well, generally the headaches, it's a lot of people just trying to automate and make sense of all this legacy things that they've had and the issues where they've done things manually or before you had cloud native applications and how do they move it to a cloud native architecture like an OpenShift. So that's a lot of our focus. It's how do I, how do I wrestle some of these private clouds? How do I wrestle Windows, how do I bring things into AWS? How do I do multi-cloud? You know, things of that nature. So it's how do I manage things when they're moving so fast and there's so many moving parts. And we give them that single language that they can use through their automation. So you've got all this legacy work that's been done, you're trying to get them into the 21st century, well not even, 2018. >> Right. >> And there's a lot of retroactivity that needs to be done there right. I mean you've got to fix a lot of plumbing. >> The legacy hasn't gone away they still need to automate and manage it. >> Right. >> So we're very much a swiss army knife and can cover a lot of ground in a lot of different environments. >> Well it's good to be handy. >> Yes, yes it is. >> Nothing wrong with that. Alright gentlemen, from OpenShift, and from Ansible again thanks for joining us, we appreciate the time. >> Right, thank you. >> Thank you. >> Good guys, good having you here. We'll be back more here from reInvent AWS live in Las Vegas in just a moment here on theCUBE. (upbeat music)

>> Narrator: Live from Las Vegas, Nevada, it's theCUBE covering AWS re:Invent 2016. Brought to you by AWS and its ecosystem partners. Now here is your host, John Furrier. >> Hey, welcome back everyone. We are here live in Las Vegas for AWS Amazon Web Services re:Invent 2016, their annual industry conference. The center of the universe in the tech world, 32,000 attendees, broke all records. It grew from 16,000 last year, almost double. I'm John Furrier with theCUBE. We are here getting all of the signal from the noise. Three days of wall-to-wall coverage. Our next guest Ramin Sayar, who's the President and CEO of Sumo Logic. Welcome to theCube, welcome back. >> Very well, thank you much. Nice to be here. >> So, when did you move over to Sumo Logic? >> So interestingly enough, it's two years this Friday. >> Okay so give us a quick update and then I want to dive into the relationship with Amazon. You guys clearly doing big data early. In the wave of the Hadoop is big data, but those other methodologies. Quick history of what you guys are doing now and status of the company. >> Sure. So the company is about seven years old. We were founded, born, actually bred on AWS. We don't have a single server in our place and interesting enough, the premise of founding Sumo, seven and a half years ago, actually was to build a multi-tenant SAAS-based machine data analytics platform to start to address a lot of the security, but also the operational issues that customers were facing. Our founders actually came from a security background and realized that rear-view mirror technologies and looking at historical aspects wasn't good enough. So low and behold, they made a big bet at that time, six years, almost seven years ago, to build exclusively on AWS and today, on an average day, we're ingesting about 70 terabytes of data, we're analyzing over 100 petabytes of data on AWS. >> So talk about the specific implementations. Obviously using all of the services, is there any particular ones, obviously storage, Glacier, you must be using some Glacier, but is it mostly S3, is it ElasticBox Storage? >> S3, C2, we use, obviously, some of the other services, but more importantly, we enable all of the services that AWS provides for their customers to be seamlessly supported by Sumo. So when you log into Sumo or you create a brand new account you give us your credentials, everything from Kinesis to Lambda, to EC2, to ElasticBox Storage, all of those are out-of-the-box that are supported. >> And you guys had a great booth last year. This huge booth, right in the front, with sumo wrestlers. I mean that stole the show in the age of Twitter and Instagram. The share of voice on that was pretty significant. >> Yeah I think there's an underpinning tone there, which is we want to wrangle your data, right. And no one knows big data more than a sumo. And we have earned the right now, after seven years in with 100 petabytes of data that we're analyzing every single day, to be a lot more prescriptive for customers in terms of how to approach the way they build, run, and secure these modern apps. >> We've been following you guys in context of the big data space. I don't think we've had a lot of briefings on the analysis side. I think we should get you guys certainly plugged-in with George Gilbert, our analyst, but what's interesting is the predictive marketing and then a lot of certain verticals were really in early on big data and you guys were there. What's evolved since then? Because now you're seeing, with AWS certainly, you've got streaming, you got redshift doing very well, the services that they've added on over the past few years has been pretty significantly and kind of right in your wheelhouse. >> Yeah. >> John: So what new use-cases are popping up now? What are you guys doing for business? What's some of the profile customers? How are they using Sumo and what's the value for them? >> Great question. So a few things we're seeing. One is with the availability of all these services that Amazon is providing, the cycle time for releasing new code and overall applications is becoming much less. And as a result there's not just a need to move to continuous integration or continuous deployment, it's about continuous updates. So the challenge that brings for a lot of our customers they need real-time visibility. We refer to that as continuous intelligence. So our platform is predicated on the fact that we have near real-time analytics streaming engine that as data is coming in, you can get visibility for your developers, you can get visibility for your operations teams, and you can get visibility for your security compliance teams. So let me give you a couple of examples. You asked for customers, Huddle is one of the customers they spoke about today. >> John: Jeff Frick and I love Huddle. >> Football videos, but you know they support Premier League, they support Aussie rule football, I mean there's a lot of sports right? And so they're uploading video and there's a great service not for just college or high school athletes, but professional athletes to understand their game and analyze their games. So underpinning that, actually Huddle's using Sumo to run their service, to manage their service. Not too distinct from Domo or Qualtrics or other customers like SalesForce, Adobe. We have customers like Land-O-Lakes. We do a lot in media and entertainment, gaming, online retailers. So what do they all have in common? They're either migrating to the cloud, one. Two, they're doing digital transformation or some sort of digital application initiative. Three, they need some way to get visibility real-time into their applications and services from a security perspective, but also an operational perspective. >> What's the driver for customers right now? Because one of the things we hear all the time is people are trying to account for their data. So analytics is kind of like this, well data warehouse was this old mentality, but now smart people started putting into mainstream, but now there's more of a data accountability aspect. The metadata, really valuable. How are customers doing that with you guys? 'Cause I can see them getting their toes wet with Sumo and then getting up and saying "Wow I can use some prescriptive analytics, predictive marketing", whatever the use-case could be, but now you gotta start thinking where's the data coming from and where's it accounted for. Is there a data economy? >> So what's interesting about that, you mentioned metadata, and that's what it's about. Our system, we ingest any type of structured or unstructured data. And we actually analyze a lot of the metadata. In fact, like I mentioned earlier, we're analyzing over 100 petabytes every single day on AWS. And so what we're able to actually help our customers do now is be much more prescriptive and provide insights as to the 1300 customers that are on Sumo, the 74% of them that run on AWS, about a quarter of them are using things like Lambda. Another two-thirds are using EC2, but how? And what types of queries are they doing? And what types of services are they building with Docker containers, or Mesosphere, or others of that type of services? So now we've actually entered a position where we're actually the trusted advisor for a lot of these companies in moving to the cloud, building new, modern apps because we've been doing it for seven and a half years. >> Yeah. >> Ramin: And so the metadata starts to become important because we actually put out a recent survey we called "The state of the modern app". And that whole report was premised on the 100 plus petabytes every single day over a six month period, how are customers using AWS, what services are they using and not using, and what should you consider? The number one thing we found in that report was only half of the customers, of which 74% of the 1300 run on AWS, were actually doing anything with CloudTrail with respect to security. That means the other half are potentially vulnerable to breach. >> John: Yeah. >> John: What percentage? >> 50%. >> So half were exposed. >> Half are exposed >> John: No audit at all. >> Ramin: No audit at all. So now we're actually proactively notifying them saying, "Hey listen for your type of deployment you're using these types of common services. Others similar to you should use the following." >> That brings up a good point. So let's unpack that because what that brings up is a lot of people get into data and they hear all this stuff in the news. Oh big data driven and you know they can drink the Kool-Aid and go "Okay I buy that vision." But there's some pretty urgent issues on the table that people got to deal with in the enterprise and or if they're cloud native and that is security. You mentioned it. I mean that has become such the low-hanging fruit for data analytics. So Splunk being very successful with that. Cyber, we talked to Teresa Carlson earlier. Their public-sector business is exploding, certainly with the CIA and others. I'm sure you guys got some of those clients. But that highlights that yeah that's all fine and dandy to do some nice stuff over here to figure out recommendation engine for this or that, when you got security holes out there. Are you seeing that on your end too? >> Well interestingly enough, that's how we started. We started with the goal of providing analytics and more importantly we wanted to democratize analytics initially for security in the cloud. And so, we actually before Amazon Web Services really built things like PKI or public key encryption or things around encrypting data transfer, we had built that into our system and service. So what we actually are able to do now is not only show how we can encrypt the data and do all this services, but show them how they should actually start to use CloudTrail and how they should architect these modern apps, and what things they should be concerned about from a vulnerability and risk point of view. One of the newest products that we just announced is in early-access around threat vulnerability and threat intelligence because now we're getting a 360 degree view for a lot of our customers because you saw today the hybrid announcement right? That's going to be there for a while. What Sumo allows a lot of our customers to do is from their on-premise data center to their CDNs to all their SAAS applications like SalesForce, or WorkDay, or DropBox, or Box to all those things running on ASH or Amazon and the like, we provide a whole 360 view. And we can actually now >> John: So you get real-time >> John: as well on that? >> Real-time. >> Ramin: So our system and service is predicated on a real-time data streaming engine. >> Yeah so you guys can coexist in multi-cloud world. >> Absolutely. >> John: That's your premise. >> Ramin: No pun intended right? (laughing) >> All right, let's talk about contextual data and what companies should do and why they should get you guys involved in the use-cases of going forward, planning. A lot of conversation here at re:Invent is AWS 2.0. They go on to the next level, Enterprise, a little bit more complicated than say Cloud Native greefield apps. How should they be thinking about their data? You've been doing this for seven years in AWS and you probably have clients that aren't on AWS some are, some aren't, that's the makeup. But generally what's the architecture? What should be holistic concept for CIO, CXO, or down to the practitioner level, what's the guiding principles? >> It starts with a fundamental principle of form follows function. And you know this is a sports analogy, but if you're not formed right, you're not going to function right. So a lot has to do with a conscious decision customers need to make in terms of how they're going to structure their teams and whether they're going to move to a true dev-ops model where they're pushing hourly, daily, weekly, and whether they need to or not for certain applications versus others. And then it goes into function in terms of how they start to architect their applications. What services they need to use. And we've actually learned that over seven and a half, eight years ourselves, seven which years were running on AWS. And so the advice often times we give to a lot of our customers is understand where the mission critical workloads that you need to migrate, categorize those. Second is, which of the greenfield apps you're building and why. And what type of retention and security policies do you need and these are the common services you should probably consider with AWS. And then third is, the other set of applications you don't really care about, leave them for now. Focus on your expertise here. >> It's really triaging the sequence or order of app rollout, basically. Well thanks for coming on theCube. Really appreciate Ramin. I want you to take a minute to close us out and talk about for the folks watching, what's new with Sumo Logic? Why should they be working with you? What's the pitch? What's new? What's relevant for you guys? >> Great, so obviously we're a big data company, but more specifically our service and our strategy was predicated on democratizing analytics. And so we refer to that as continuous intelligence. And so as this digital transformation is taking place, and we're seeing it here, we're seeing it across every part of the businesses, we are well suited for every company that's got either a migration effort or an active, new project going on AWS. And so we can provide a simple, secure, highly scalable machine data analytics platform as a service and that's what Sumo is all about. >> And your business plan for the next year is what? Knock down more customers? Do more product development? All of the above? Channel? What's the strategy? >> So good question. So on one hand we're introducing a new product. We've kind of hinted to some of that today with some threat intelligence. Second is, we just introduced a new product about a month ago that we're starting to monetize. It's about semi-structured data. And third is, we're gonna start to really expand our routes to market and channels. One of the things that we participated in recently with Amazon is the new Amazon SAAS marketplace program. We're in with a handful of companies that participate in design and development there. And so that allows very seamlessly for customers to come try, buy, and decide whether they go month-to-month, semi-annually, or year. >> Well that will accelerate the operational nature of your product. >> Absolutely, but that's the way we sell today. In fact, our whole business model is predicated on land and expand. You're probably familiar with this whole notion of cohorts. >> Yup. >> And that dollar retention. Well the median, if you look at PACCrest and Morgan Stanely and the other firms, tend to be 103 to 105. Best in class tends to be 110 to 115. We've been well north of 160 for 19 straight quarters. >> Well Jassie said that on his keynote today. The bombastic days of handwaving are over. If you don't see it right there, the value, in front of you, don't buy it. >> Don't buy it. >> It's really the marketplace's vision. >> That's marketplace vision and that's what we're all about at Sumo Logic. >> Ramir Sayar, President and CEO of Sumo Logic. Congratulations on your success. Continued success. This is theCube bringing you all the action live in Las Vegas for re:Invent 2016, I'm John Furrier. Be right back with more after this short break. You're watching theCube.