>> Live from Las Vegas it's theCUBE covering AWS re:Invent 2018. Brought to you by Amazon Web Services, Intel, and their ecosystem partners. >> And welcome back Paul D here at AWS re:Invent, John Wall's on the (mumbles), we are live here on theCUBE continuing our second day of three days of coverage here in Las Vegas. Joined now by Patrick McFadden, who's the Vice President of developer relations at DataStax. Patrick good afternoon to you. >> Hey guys thanks for having me. >> You bet, glad you could be with us here. First off, tell us about DataStax a little bit and then I want to ask you a question about hybrid cloud. I've got a chuckle about a comment that Justin just made. First off tell us about DataStax. >> Hybrid cloud, we could talk about that all day. We only have so much time here. So DataStax, we're a database company. We were formed around Apache Casandra, the database. We are really an enterprise database company for those who want to use Apache Casandra but we add a lot of things to make it enterprise ready. So things like search, analytics, we have graph database. More importantly some of the harder bits, the less sexy parts, like security, compliance for different regulatory things. Taking an open-source database and really buffing it up and making it for an enterprise, that's what we do. And we have a variety of products we well sell around that, but essentially in a nutshell that's what we do. >> What I was chuckling about, 'cause Justin was saying, we were talking about hybrid. Yeah we've been talking about it a lot over the last two days, said I've been talking about it for years. So this is no secret to you, you've been banging that drum for a while now. >> So I've been working with the Apache Casandra project for about eight years now. And that database was built to do hybrid anything. It was purpose built to work to work in multiple clouds. It's a mask-less architecture that works in one data center, two data centers, three or four. So years ago we were talking about this, and this was back when people were still trying to get, they had an on premise data center in east coast and west coast, how do we make that work. Now we're talking about, okay now we have on-premise and now cloud, or how about two clouds, or how many clouds do you have. We do not care, you can run it as all those that you want to we will work across all of them anywhere, anytime. We're there to cheer you on, help you do it, and be successful. >> That is something that we've noticed in the last couple of days here at Amazing re:Invent. Amazon has kind of relaxed its stance a bit about where data can live, previously hybrid cloud was not a thing. It was one cloud all the time, where as for most enterprises I think that wasn't actually a practical reality they had a lot of data that living somewhere else. So now it's good that Amazon has opened that up. Actually there is a way that you can do this in multiple different locations and it's perfectly valid to do that. It's now a choice of what should live where and why. When you have customers who are trying to make this kind of decision which is quite complicated about where do I put my data. If I could put it anywhere, it's like, "I'm going to put it "in all the places." That's probably not ideal either. So how do you help customers decide when they're architecting their database, where the data should live, how do you help them decide should I have one on each coast, should I have one on all the coasts. Should I put everything into my finder, my car, my robots. >> Well there's two parts to it. The first question we're always going to ask is what is your cloud strategy. 'Cause everyone has one or at least they should. We can form ourselves into it, so if they're going to have their new applications running in the cloud, legacy applications running on prem, great we can help you do that. Second thing is thinking about where we are with applications now, this is 2018, people do not go with latency, and everything is fairly global at this point. Global economy is real, your data needs to be where your customers are, to get around the world, so if you have a website or a mobile application that runs in North America and you have someone in India trying to use it, automatically you get a half a second of delay, you cannot survive that way. No one's going to use it there. If you're truly a global company you need to put your data where your customers are and they're probably everywhere. So we also want to have your data everywhere and we can support that and help you be successful doing it. >> As someone who lives on the other side of the planet I can definitely attest to that it is very far away. Even if you are traveling at the speed of light. >> Exactly, we're ready for SpaceX, if they put stuff out there, we're ready for it. >> The space database, I like that idea. >> We're not terrestrial, we're galactic baby. (laughing) >> So this is something you've been doing for a long time. As you've said you've been working on this for a long time. When you are looking at customers who are doing things today it's 2018 as you said. What are customers looking for DataStax to help them to do today, rather than things they were doing five years ago, what are the customers right on the edge doing where you help them out. >> First of all, for customers it's going to be something that's really, we're closer to your customer of course. But there's also this angle of open-source databases. Open-source databases are a very hot topic, or any open-source infrastructure is a hot topic. We're a proprietary enterprise company that also supports and open-source product, we have to respond in kind, in a lot of ways to how we can provide something for someone who's very like, "We only believe in open-source." Great, we can help with that. We have our DataStax distribution of Apache Casandra which is a feature compatible with open-source Casandra just support, there you go. All the way up to our full enterprise product, and then in the open-source side we help with a lot of other things like developer enablement, that's of course my job, so I'm going to be on that. We developed the drivers, we give education. Because right now developers, they're the money makers at every enterprise, every enterprise is going to be a technical, every company is a technical company. An enterprise has a goal to make money, developers are the engine making that happen. So we're going to help enable their developers, you're probably looking for use cases, I'm a little more nuts and bolts, they're looking for how do we even do this. >> That was going to be my question, how do you get developers excited about databases? >> I think it's what you do with the database. It's opening up those new use cases. For instance, I want to do fraud detection, and that's an important part of my application. What gets them excited is something that's easy to use. A database that actually does work, it's performing, it stays online, that I don't have to make excuses to my boss whenever it goes down. That I'm not woke up at three o'clock in the morning, that whenever I want to extend into another country, another domain, and I got to manage all the regulatory stuff like GDPR, that's a fun time. We could do that, and so developers are going to be very excited about not having to deal with that. >> Sorry John. >> I was going to say, when you talk about the developing community, you're VP of developer relations, so how do you maintain those relations, how do you get them engaged, how do you get them involved? Do you have any special or unique initiatives that you do from and outreach perspective that allows you to build that bridge and develop a better sense of community? >> Well our primary community is the Apache Casandra community, and it's events like this. We had a lot of Apache Casandra community members come to our booth, but we also do events where we do developer days, we have our accelerate conference, which is next year in May. We have a special relationship with our community, we try to walk that fine line, we're going to have speakers there that are not customers of our but use Apache Casandra and we're good with that. We want people to use Apache Casandra first, and we hope that they would want to be our customer eventually, but that may not happen and we're okay with that. That's part of that outreach, now whenever someone builds an application, bottom line we want you to be successful, and we have a keen interest in the whole chain, all the way up to the sea level where they feel confident in using a solution that's going to do it. Like hybrid cloud, oh we have a solution, great let's do that. >> Now databases are just one part of the whole solution, so you have this data and you put it into a database, but there's generally some other components that live in there, not everyone just wants to talk directly to the database. I do, but not everyone does. So what do you see developers using DataStax to build? What are the applications that they're building on top of DataStax, what are some of the use cases that customers are interacting with these applications? >> Right now mobile is of course really hot. That's user management, taking care of the state of your data itself, just the simple stuff. If you look at applications on your phone, I bet if I looked at your phone about half of those applications have Casandra running behind them. I'm very confident in saying that because that's a real-time problem. We have other use cases as well that are really interesting like fraud detection I mentioned, messaging, very important part of that. Time series data is making the world go round right now, you can see this morning there was an announcement. Amazon was like yeah, we have a whole solution for time series. Something that we've always embraced, time series data is very important, IOT, massive part of that. If you have a database that can scale like ours and can run anywhere, think of the use cases. That's IOT right there. >> You've mentioned a bunch of technologies which are, been an outsider over the last couple of years, IOT's been around for a little while, they're pretty hot. Have you seen anything in the show so far in the last couple of days that's really caught your eye about, "Oh looks like that's where the future is." Or there's a lot of momentum in that particular area. >> I feel like the worlds kind of turned around and I've been stuck in my own bubble for a long time with Casandra because I believe in replicated data and hybrid cloud. It seems like everyone is oh wait, data should be everywhere where four years ago when I said your data should be everywhere. It's like, I'm fine with my relational database in one server, I don't need anymore, thanks. Okay, well I'll see you in a few years. So I don't want to say I told you so, but I'm going to sit back and relax. (laughing) I'm just going to let it happen, I'm very happy to see everyone's at the party now, welcome. >> Well thanks for having us. We've had a great couple of days Patrick. And next time bring that crystal ball with you and we can look down the road for another three or five years too. >> I think I'm out of magic. Don't ask me about Super Bowl winners or anything like that. >> You're on the hook, go with the Saints by the way. Back with more from AWS re:Invent, you're watching theCUBE, we're live here in Las Vegas.

(upbeat music) >> From Tavern on the Green, in Central Park New York, it's theCUBE; covering Veritas Vision Solution Day. Brought to you by Veritas. >> Welcome to the heart of New York City. We're here in Central Park the Tavern on the Green. You're watching theCUBE, the leader in live tech coverage. And we're covering the Veritas Solution Day; hashtag Vtasday. So, Scott Genereux is here as executivee president of world wide field ops for Veritas. Scott, good to see you again. Thanks for coming on. >> Thank you good to see you. Thank you. >> So, I love the location. A lot of our crew, they've never been here before; I said wait until you see Tavern on the Green, it's sweet. Customers love it. So, why this location? What are you guys doing with the Solutions Days different than the big tent event? You guys have gone to a more intimate format, explain that. >> Yeah, so last year we did the big event. We also did regional events, and it was interesting. And when we looked at the regional events; the input from our customers was; they loved the idea of doing something local, a little bigger, so they didn't have to travel. You know it's just difficult to get somebody to come out fly across the country to spend a week. And so, we decided to do 20 of these around the world. We also found out last year that the number of people who were coming to the regional events; was very very large. I mean some of our events we had four, 500 people coming. So it just made a lot more sense to us is; how do we get close to our customers, make sure they didn't have to travel; and be able to touch 'em so. >> So, collectively you're probably hitting as many if not more people. >> A lot more. >> Probably a different type of audience too when you go. So, you're doing a bunch in the US and a bunch in overseas right? >> Correct, yeah, so we've got New York, Chicago, San Francisco, we got one in Washington D.C. focus on the Fed, and we have one up in Toronto in North America. And then we've got 'em in Latin America. >> So you've been a kind of customer success executive all your life; you spend a lot of time in New York City. A lot of customers down here. A lot of the more advanced and sophisticated customers here. So, what are you hearing as you see digital transformation, big data, cloud, multi cloud; people are changing the way in which they think about data, and protecting data and getting more value out of data. What are they telling you here; the challenges that they're facing and where do they want to go with Veritas? >> You know the exciting is that look, we're still the market leader, right? Well, people say what's going on with Veritas? We're the market leader, we have been for the last 15 plus years. And, the people we're doing data protection for today, are the largest of the largest. You know, 95% of the Fortune 100 use our technology. 85% of the Fortune 500 use our technology. So, we get a lot of information knowledge experience from what you would argue and I would too. The customers here; which are the toughest of the tough too, right? I mean, they're not always nice, they tell you what they think. And they're thinking you know, two three years out of what we have to go do to support those environments. So it's interesting; you know the big thing going into this year, there was a lot of conversation around compliance. You know, GDPR in Europe was huge. And really, I kind of narrow it down to P.I.I. Regardless if you're banking, healthcare, whoever. The whole question around how do you protect data? Where is my data located? Who's touching my data? Has just become a bigger and bigger issue. And then you throw in the word cloud and as you said multi clouds, no one's using one cloud. All of a sudden your data is spread out all over the place. So, how you focus on that, how do you have visibility on that, becomes more and more important. And obviously that makes data protection, center of what's going on with customers now. >> So there are a couple of vectors now there that I'd like to explore. One is the idea that we're now looking at data protection to get more value out of it. You talked about GDPR, privacy, things of that nature. So, I want to talk about that. But also, the last thing customers want that I talked to; they don't want yet another stove pipe of data protection. And as you go, every cloud has it's own back up approach. So, I'm curious what you guys are doing. Let's start there. Are you putting in some sort of a extraction layer to be able to service all of those different multi clouds. Which cloud companies are you working with? >> Yeah, so first of all we serve all major cloud providers. For us, we're very agnostic in the sense of we don't care where your data is located; it can be behind your Firewall, it can be in Amazon, it can be Microsoft, it can be in Google, it can be in a pseudo what we would call more of a regional, you know, a sass type cloud that you support based on something uniquely in your environment. So we don't really care on where it's located. And that's actually one of our big positives. But you're right, one of the big issues customers have today is okay they start out and they might use Amazon for test development. Amazon has their own way of moving data into the cloud. And what do you do and how do you protect it? And then you go all of a sudden Office 365 because that's the you know, the Microsoft way of getting into the cloud. And so now you've got two clouds. Oracle's pushing you to do clouds. So you've got an Oracle cloud probably right? And we can go down that whole list. So everyone is driving a cloud strategy. But the problem customers have today is; they don't want to have six or seven different ways of on boarding data applications into the cloud, and they also do not want to have different ways of moving data or protecting data. And I think, so for us what we do that's very different is that, we have software that allows you to move data and applications into any one of those clouds the exact same way. I mean, if you think about it today. When you think about data replication, or protecting data; a lot of customers use hardware replication to move data. Well, the problem you run into today, when you think about it, is that the traditional cloud vendors, we just listed who they were, they don't use traditional hardware. No one's using EMCSRDF in the Amazon cloud. No one's using Hitachi's products. So, you need a software based replication tool and a data mover I'll call it, to be able to do that. And that's an area we've invested a lot of time and money on to be able to do it. And more importantly, even though I don't hear this a lot from customers any more, there was a fear for a while of cloud lock in; I don't want to be too into one cloud. We could move data between clouds also. So, you know, you don't have to bring it back and bring it back forward. So, that also makes customers at ease of how do you manage it. But it just creates a whole different environment of what to do and how to do it. >> So you're not in a technical role at the company but when you're in this business and you talk to a lot of technology people, you have to be conversant in technology. So I'm curious, so you've mentioned the high speed data mover that's something that's always been fundamental to the Veritas architecture. But you've done some other things. I've got briefed and seen some of the videos of what you guys done on 8.1.2. There's components of that are really different. I mean, modern software, micro services based architecture. >> Yep. >> That have allowed you to actually create this multi cloud sort of affinity. Maybe talk about what's the conversation like with customers with regard to modernizing your platform. >> Right. I think two things; you know it's interesting, the two things that customers always have asked us for is a new U.I. interface. You know now it's interesting like anything, customers have used us for 10 years. There's customers who love the old interface right? >> Right. >> But today, when you think about cloud or think about particular work loads, which is probably more important. You know, it's no longer the back up administrator who might have to do everything. When it used to be just the back up person, you know, having the way we used to do it, made a lot of sense. But now, you're basically grabbing someone who could be the virtual machine administrator. It could be the cloud person administrator. It could be security. And those people don't have a background in data protection. So the question is, how do you give them an interface that makes it easy for them to understand and use to be able to administrate that. So now the back up administrator can actually create groups inside of net back up. And allow those organizations to be able to look at their environments and be able to manage it very differently. So, and it's the same thing with work loads. When you think about it today, most of the data growth that we're seeing, it's traditionally not, it's not the Oracle work load, SAP work loads. 60 70 plus percent of our largest customers are creating new data based applications on non sequel stuff. It's Mongo, it's Casandra. So the new 8.1.2, supports all those environments. We didn't do that before. So that's a great interface for us. Because those data bases don't natively do back up well. The Hadoop, data analytics; huge amount of data being created there. It used to be that it used to be a sandbox; a playground. But those applications have gotten to become you know important in these customers. And so it used to be you just used to take a snap shot of this stuff and you would have about 20 copies of peta bites of data. Now you can do point in time back ups using those types of products. So 8.1.2 has that type of support in it too. And we've done a lot of stuff around VM ware specifically, focused around new innovative things that we needed to do to modernize the products. >> So those emerging work loads like not only sequel but you know, Mongo, Hadoop, etc cetera. That's now native to your stack, correct? >> Completely, yup. >> Okay, that's different. Because you've hardened that. A lot of companies in your business; maybe the some of the newer guys have to go to a partner to find those capabilities. >> Right. >> So, that's I think, big. The other thing I heard was, cloud like I think I heard self-service essentially for some of the liza business folks. Or whomever that you don't want to send them necessarily back to the back up admin. Do it on your own. Here's some policies they'll make it kindergarten proof. >> Right. >> Okay, so that's a trend you're seeing as well. >> Yes, yes, completely. >> Okay. I want to come back to something you said before, this other vector, which is other uses for back up or the back up data then just insurance. Because people don't want to pay for insurance. >> Right. >> So, you've mentioned a compliance, GDPR. I would imagine as well; when you get things like ransom ware, there's also analytics. I know you guys are applying a lot of A.I. >> Correct. >> You've got the corpus of data, just so happens that the back up data contains the data of the company. >> Correct. >> So presuming we do other things with it. So what are some of the things the customers are doing? How are they getting additional value out of the investment that they are making at Veritas? >> I think, you know, it's a couple of areas. Before we leave compliance, let me focus on one thing that's been really important is the whole question about where my data is located. This whole visual-ness of data; who's touched it last, all of that has become a really really important thing for customers because even in the natural cloud, sometimes you don't know that maybe one of the cloud providers moved your second copy of data in to a data center that is a problem for you, right? >> Physically it's in a place it shouldn't be. >> Right, yeah. It shouldn't be in a data center. It moved out of a country boundary for compliance reasons right? So, you know, we've spent a lot of time and energy creating a software technology that gives you that visibility. And not just with net back up. We also plug in all the cloud providers; we also plug in Oracle, we also plug in box.net. You know I mean, so a lot of these other companies are also plugged in. So, back to your point, we've created this huge data repository of information that now allows us when you look at our future, and we talked about a little on this session earlier; data analytics, some capabilities that we should be able to go do because we have meta data to be able to give customers that visual capability. The other thing that's interesting is that visualization software, is it also tells, it finally gives customers a proof point of what we've always known. That probably roughly about 50% of their data. And I'm being kind when I say 50. Probably hasn't been touched in three, five, four, 10 plus years, right? And we've always known that. But now we actually show a customer. Hey, using this visualization software, that you're using for compliance has also now told you where the data is located and who's touched it last, and by the way it hasn't been touched forever. It allows the customer to have two conversations; one, do they need to save it? And if they do, do they move it into a glacier type environment? Or three, do they move it to a software defying storage on the customer's floor? We can help the customer migrate it after we showed them who hasn't touched it. But we also have a software defying storage solution. That Gardener just came out and said that we're number one in this space, right? So, it's one of our fastest growing pieces of our business. Because customers all the time say to me, Scott our data protection cost is going up. And the reality is, it isn't. The reality is data is growing dramatically. Storage is going up, and oh by the way I got to back up my data that sits on the storage, right? So it all kind of combines together. >> So data protection is the percentage on the spend is not necessarily increasing but everything is growing. >> Everything is growing, yes. >> So the other thing, just a couple of points that you made me think of, the other cloud that you support is on prime. >> Yes, yeah, it's still big by the way. >> So that's another piece of it. Because you got the three laws of the cloud right? It's the law of physics. You can't necessarily put everything into the public eye. Then you got the law of economics, and you got the law of the land, in which you were talking about before, >> Right. >> If you're not supposed to leave Germany, >> Correct. >> You can't leave Germany, okay. And then, so you're using analytics to help customers to determine this. And the other thing, some of the general counselors out there don't want to keep data forever. >> Correct. >> I hear a lot from vendors, oh you could now keep it forever and GC says no, we don't want to keep it forever. >> Exactly, right. >> Okay, so you're using analytics to sort of sift through that data and surface these clues. >> Yes. >> And actions to customers. >> Yes and the new thing also at 8.1.2 is we've come out with a smart meter type technology which will let customers know how much data they're using, where they're using the data? Any hot spots in the data. And it's very file based, you know, data focused. It obviously helps customers really understand who's using what where, you know. And to be fair, they can use that to help go drive costs, figure out you know maybe someone's using something they shouldn't, maybe people are storing stuff that they don't want to store. It's not just a benefit to figure what they're doing but it's also could help and drive cost out. >> Big customer base obviously, probably the largest in the business. >> Yup, over 50,000. >> 50,000 customers? >> Yup. >> You've modernized the software. Just rap it up, the competitive customer differentiation, a lot of noise in the market place. >> Yup. >> Where do you stand? What's your position relative to the competition? Why Veritas? >> Yeah, well, so for us, when we walk in to a large customer, as you can appreciate, they don't want three or four different products; back to the cloud conversation, they don't want three or four ways of moving data in to cloud, right? They really want one. And the other issue they all ran into is this compliance conversation. You, know not everybody does everything the same. And they don't all talk together. Having a single platform, to be able to give customers the capability of backing up everything from traditional work loads of Oracle, and SAP to Mongo DB, to Casandra, to Hadoop, to containers, to open source; we're the only company out there that can do all those work loads. There are start ups. And they may do one or two things really really well, or so they say they do, we don't think they do, but they say they do, and that's what they focus in on. That's not what a large enterprise customer wants. They want capabilities to be able to scale high performance, ease of use, and 8.1.2 gives that to them. And we do more work loads than any body else in the industry. >> Excellent, well Scott thanks for coming on. We are here in the heart of New York City, at Tavern on the Green. A lot of customers, I've been talking to some of those customers today, those customers, they're as tough as Yankee fans I could tell ya. (laughing) So Scott thanks agan, good to see you. >> Alright, thank you. >> Alright, keep it right there everybody. We'll be back with our next guest right after this short break. Thank you for watching theCUBE from Veritas Solutions Days in New York, right back. (upbeat music)

>> Announcer: Live from Las Vegas! It's theCUBE. Covering Edge 2016. Brought to you by IBM. Here's your host, Dave Vellante. >> Welcome back to IBM Edge everybody. This is theCUBE's fifth year covering IBM Edge. We were at the inaugural Edge five years ago in Orlando. Marc Linster is here and he's joined by Lenley Hensarling. Marc is the Senior Vice President of Product Development. And Lenley is the Senior Vice President of Product Management and Strategy at EDB, Enterprise Database. Gentlemen, welcome to theCUBE. Thanks for coming on. >> Male Voice: Thank you. >> Okay, who wants to start. Enterprise Database, tell us about the company and what you guys are all about. >> Well the company has been around for little over 10 years now. And our job is really to give companies the ability to use Postgres as the platform for their digital business. So think about this, Postgres is a great open source database. Great capabilities for transactional management of data. But also multi-model data management. So think about standard SQL data but think also about document oriented, think about key-value pair. Think about GIS. So a great capability that is very, very robust. Has been around for quite a few years. And is really ready to allow companies to build on them for the new digital business but also to migrate off their existing commercial databases that are too expensive. >> What's the history of Postgres? Can you sort of educate me on that? >> Sort of the same roots back with System R, where DB2 came from, Oracle came from. So Berkeley, that's where the whole thing started out. Postgres is really the successor to Ingres. >> Dave: Umhmm. >> And then it turned into PostgreSQL. And it has been licensed under open source license, the Postgres license since 1996. And it's a very, very vibrant open source community that has been driving forward for many years now. And our view is the best available relational and multi-model database today. >> It's the mainspring of relational database management systems essentially >> Marc: Yeah. >> is what you're saying. And Lindley, from a product standpoint, how do you productize that, open source. >> Open source really, companies that have a distribution of open source for database and operating system, whatever the open source company most people are acquainted with, is Red Hat and Linux right. And so, we do the same thing that they do but for Postgres database. We take the distribution, we add testing, we add some other functionality around it so you can run Postgres responsively as Marc likes to say. So high availability, capability, fail-over management, replication, a backup solution. And instead of leaving it as an exercise for a customer, who wants to use open source, we test all this together. And then we validate it and we give them a complete package with documentation and services that they can access to help them be successful it. >> So if Michael Stonebraker were sitting right here, I say Michael, what do you think about Postgres? I'd say I had to start Vertica because we needed a new way. Yet, sort of PostgreSQL, is the killer remains the killer platform in the industry, doesn't it? >> Male Voice: Umhmm. Why is that? It's interesting when you talk to guys like Stonebraker, it's sort of dogma almost. But yet, customers, talk with their wallet. >> And it is, >> He did a very, very nice job of architecting it. It is a database that is extensible. The reason we add the first JSONB or document oriented implementation in the relational database space is because it was designed to make it easy to add new capabilities, new datatypes, new indexes, et cetera, into the same transactional model. That's why we have JSONB. That's why we have PostGIS. That's why we have key-value pair. So it was really well architected. And when you think about who else, not just Vertica has taken this engine >> Dave: Yeah. >> It is in Netezza, it is in a bunch of other. >> Dave: Master Data. >> Lenley: Greenplum. >> Greenplum yes. So it's a really robust architecture. Very, very nicely designed. It just does the job and it does it really well. Which is, what you want a database to do, right. It's not that exciting but it's really stable. It really works. The data is still there tomorrow. That's what really the requirements are. >> And to translate a little bit, Marc mentioned PostGIS, which is geo spacial capability for the Postgres database. And so we distribute that along with Postgres and test it so that you know it works. And he mentioned H-Store, so that's how you can actually store internet of things data really well into Postgres. And we talk about SQL, noSQL databases, so they're document databases. And the ability to have personalization at the same level you can in a document oriented database but in a structured SQL database are the kinds of things that have been added to Postgres over the years. Again, it's because of the basic architecture that Stonebraker put in place as an object relational database. >> It's so interesting to look at the history of database. Talk about Stonebraker, he's been on a number of times. It's just fascinating to listen to one of the fathers of this industry. But 10 years ago, database was like such a boring topic. And now it's exploded. Now you got Amazon going after Oracle. Oracle fighting the good fight. So many noSQL databases coming in. SQL becoming the killer big data app if you will. >> Male Voice: Umhmm. >> Why all of a sudden did database get so interesting? >> What happened was, application models changed. Led by Facebook, led by Amazon and Google. They said, let's refactor the applications and let's refactor the way we handle storage. >> Dave: Umhmm. >> And that led to the rise of the polyglot of databases is what a lot of people are saying. You have fit for purpose solutions and you may have three or four or five of them in your overall architecture. One thing about Postgres is, we're able to, because of the datatypes support that Marc mentioned, fit into that well. We don't try and do everything so if somebody says, I'm going to use Mongo for data capture, or I'm going to use Cassandra for capturing my internet of things data. We have what we call foreign data wrappers in the Postgres world. We call them just Enterprise DB Adapters but to Mongo, to Casandra, to Hadoop and can do bidirectional data there and just keep that data at rest over there in the other world. But be able to project relational schema onto it. We can push our data into those. We've got a great use case we've been talking about with a customer who had over a petabyte of data. And in the past what you do is, you'd go buy an expensive archiving solution and add that to it. Now, you just use Hadoop distributed file system. Push the data off there as it ages and have a foreign data wrapper that allows you to still query that data when it's out of your basic operational dataset. And move forward. >> Can I call that a connector or? >> Lenley: Yeah, a connector, that's not a bad idea. >> And it's interesting because If you guys remember Hadapt, probably. [Male Voices] Yeah. Yes. >> They came out, they were the connector killer. >> Male Voice: Umhmm. >> And it failed. >> Male Voice: Yeah. >> Seems like connectors are just fine. >> Male Voice: Yeah. >> And one of the really interesting things is, we call it data federation right. With philosophy here is, leave the data where it is. There are some data that should live in Hadoop or Cassandra. If I'm doing an e-commerce site with transactions and click streams, well, the click streams really should live in Hadoop. That the night natural place for them. The transactions should be in a transactional database. With the foreign data wrapper, I can run queries without moving the data, that will allow me to say, well, before you bought the brown teddy bear, which pages did you look at? >> Dave: Yeah. >> And I can do that integrated system and I can do a fit for purpose architecture. And that's what we think is really exciting. >> And that's fundamental to this new sort of programming or application models. >> Male Voice: That's right. >> The one that you were talking about is moving five megabytes of code to a petabyte of data. As opposed to moving data which we know has gravity and speed of light issues and so forth. >> Thank you for that little brief education. Appreciate it. So let's get into your business now, your relationship with IBM. What customers are doing. You mentioned IoT data so talk more about your business and your relationship with IBM and what you guys are doing for customers. >> There are a couple of things. We mentioned Oracle. And there are all the new databases. And then there's your, dare we say, legacy, proprietary databases as well. And people are looking to become more efficient in how they spend. We've done another thing with Postgres. We've added Oracle compatibility in terms of datatypes. So we support all the datatypes that Oracle does. And we support PL/SQL, they're sort of variant of stored procedure language. And implemented a lot of the packages that they have as well. So we can migrate workloads from Oracle over into an open source based solution. And give a lot cost effectiveness options to customers. >> Dave: Steal. This is a way that I can sort of have Oracle licensed database licensed and maintenance avoidance. >> Lenley: Yes. Yeah. >> Where possible, right. >> Where it makes sense. Where it makes sense. >> Obvious my quorum, I keep, but let's face it, the number one cost component of a TCO analysis of an Oracle customer is the database license and maintenance cost. >> Male Voice: That's right. >> It's not the people. One of the few examples I can think of where that's the case. There's always the people cost. [Male Voice] That's right, that's right. IT is very labor intensive. But for an Oracle customer, it's the database license. Cuz they license by Core. >> Male Voice: Yup. Cores are going through the roof. >> Male Voice: That's right. It's been great for Oracle's business. Although, wouldn't you agree, Oracle sees the writing on the wall that the SAS is really sort of the new control point for the industry. You see the acquisition of NetSuite and competition with Workday >> Male Voice: Yup. >> and the like. >> But the database remains the heart of the business. >> And really it's movement to the cloud, both private cloud and public cloud. And so we've been doing work there. We've had public cloud database as a service solution on Amazon for, what, [Marc] Four years. >> Four years, Marc. And have gained a lot experience with that. And were running that sort of running a retail, you can license the database and we'll provision it there. And so what we've done recently is change our perspective and said, let's put this into hands of customers. And let them standup their own database as a service. But also do it in a way that they can choose what workload should go to Amazon and what workload might go to their private cloud, built on open stack. And be able to arbitrage that if you will. Because they now have a way to provision the databases and make a choice about where to put it. >> So that's a bring your own license model that you just talked about? >> Bring your own license model or >> Are you in the Marketplace and, >> We're in the Marketplace in Amazon, where we can supply it that way. But customers have shown a preference for bring your own license. They want to make the best enterprise deal they can with a vendor like us or whomever else. And then have control over it. >> Amazon obviously wants you to be in the Marketplace. I won't even mention but I talked to some CEOs of database companies and they say, you know, we're in the Marketplace but we get in the Marketplace, next thing you know, Amazon is pushing them towards DynamoDB or you know. >> Male Voice: That's right, that's right. >> Now Amazon's come out with Aurora and Oracle migration and you know the intent to go after that business. Amazon's moving up the stack and you got to be careful. >> They are. But the thing about Amazon is that, they're a pure play in the cloud company. >> Dave: Yup. >> And all of the data shows that it's like a mix, it's going to be a hybrid cloud. Half the company in this world [Dave] Not Angie Jassie's data >> Eighty percent of the people in the cloud are going to be on-prem, still continuing their journey through virtualization. >> Dave: Yeah, that's right. >> Let along going to the cloud. But we want to be something that let's them put what they want in the public cloud and let's them manage on the private cloud in the same manner. So they can provision databases with a few clicks. Just like they do on Amazon. But do it in their data center. >> You doing that with Softlayer as well or not yet? >> Lenley: Not yet. >> Marc: Not yet. >> We've built this provisioning capability ourselves. And it came out of the work we did putting up databases on Amazon. >> So what are you guys doing here at Edge. Edge is kind of infrastructure show. Database is infrastructure. >> We're talking about our work with Power. >> Power is a big partner for us. Power is I think very, very interesting for our database customers. Because of the much higher clock speeds and the capabilities that the Power processor has. When I'm looking at Power, I get more oomph out of a single core which really for a database customer is very, very interesting. Because all databases are licensed by Core. >> Dave: Right. >> So it's a much better deal for the customer. And specifically for Postgres, Postgres scales very well with higher clock speeds. So by having, let's say, by growing performance, not by adding more cores but by making the individual cores faster, that plays very, very well to the Postgres capabilities. >> Okay, so you are a Power partner, part of that ecosystem that IBM is appealing to to grow the OpenPOWER base. And what kind of workloads are you seeing your customers demand and where you're having success? >> Across the board. Database is mostly infrastructure capabilities so there's a lot of interest that we're seeing that, for all kinds of applications really. >> What's the typical Power customer look like these days? You got some Oracle, you got some DB2, you guys are running on there, what's the mix? Paint the picture for us. >> I think the typical Power customer is the typical enterprise company. And, [Dave] Little bit of everything. >> It's a little bit of everything. But one of the key things is that, people are also looking at what they've got and the skills they have in place. You were talking about people cost right. [Dave] Yeah. >> And their understanding of management. Their understanding of how to manage the relationship with the vendor even. And then saying, look, how can I move into the new world of digital transformation and start my own private cloud options and things like that in an efficient way. That makes efficient use of hardware I have in place and has a growth curve and new hardware that's coming out that fits my workloads. >> Dave: Umhmm. >> And the profiles that Marc was talking about. >> And also the resources. Which is very interesting when we look at these new digital applications with Postgres. Because you can do so much in Postgres from geographic information systems to document oriented to key-value. But you can do that with your existing developers through existing DBAs. They don't need to go to school to learn a new database. And that's also a very, very, interesting capability. So you can use your existing team to do new stuff. [Male Voice] Yup. >> What's happening in IoT, what problems are you solving there and where's the limit? >> Sensor data collection. >> Lenley: Yeah. Real interesting because sensor data tends to come in all different forms. We have customer who collects temperature sensor, temperature data. But the sensors are all sending different data packets. So because we can do document oriented or key-value, we can easily accommodate that. In the old days with the relational model, I had to do all kinds of tricks to sort of stuff all that into a relational table. My table would be almost empty at the end because I'd have to add columns for every vendor et cetera. Here, now I can use put all that into the same format and provide it for analysis. So that's a real interesting capability. >> And it's interesting too because we've got really strong geo spacial data support. And the intersection of that, with IoT is a big deal. They track your iPhone, they know where we are. They know what's going on. That's sensor data. They know which lights in which building, which you know, louvers that are controlling HVAC are malfunctioning or not. They want to know specifically where it is, not just what the sensor is. And some of that stuff moves around. And it gets replaced in a new place in the building and such. So we're well setup to handle those types of workloads. >> What's interesting, when IBM bought the weather company, [Lenley] Yeah. >> And they thought okay great, they're getting all these data scientists and weather data, that's cool. They can monetize that but it's an IoT play, isn't it? [Male Voice] Right. Right. >> Talk about sensor. >> It's reference data. It's reference data for other company specific IoT plays. To have a broader set of sensors out there in their region and understand what's happening with weather and things. And then play that against what their experience is, managing new building or manufacturing processes, everything. >> So what's the engagement model. I'm a customer, I want to do business with you. How do I do it, how do I engage? >> Well, a lot of our businesses direct with us. Others through partners. And then a lot of customers come to us because they want to get off legacy systems. But really, what they do is, once they understand the database and the capabilities, they say, okay yeah, you can do the Oracle stuff. But what I'm really going to do with you is my new things. Because that's really exciting and it helps me kind of put a lid on the commercial license growth. So maybe I'm not going to get off it, but I will stop growing it. So I will start doing my new stuff on Postgres. Whenever I modernize something, Postgres is going to be my database of choice. If I already open up an application with its whole stack, this is one of the changes I'm going to make. And then the database as service, is very, very interesting. So these four entry vectors and what happens is, quite a few customers after a short time when they started with project or applications, they end up making Postgres as one of their database standards. Not the only one. But they make it one of the database standards so it gets into the catalog and every new project then has to consider Postgres. >> It's interesting, there's a space created as Microsoft sort of put all their wood behind the era of becoming a competitor to high end Oracle. And with this last release, they probably are on there, arguable. But they've also raised their prices too. And they've made the solution more complex. So there's this space that was vacated for like a ton of workloads and Postgres fits in there just about perfectly. We see enterprise after enterprise come to us with a sheet that says, now we're going to get some of this noSQL stuff. We're going to keep Oracle or DB2 over here for these really high end things. Run my financials, run my sales order processing, my manufacturing. And then we got this space in here. We got a slot for relational database and we want to go open source. Because of the cost savings. Because of other factors. It's ability to grow and not be bound to, hey, what if the vendor decides they're going to go for a new cooler thing and make me upgrade. >> Dave: Right. >> And I want to stay there and know that there's still being an investment made. And so there's a vibrant community around it. And it just fits that slot perfectly. >> You got to pay for that digital transformation and all these IoT initiates. You can't just keep pouring [Male Voice] Somehow. >> down to database licenses. [Male Voice] That's right. >> Tell me, we have to leave it there. >> Thanks very much >> Male Voice: Alright. >> for coming to theCUBE. >> Thanks so much. >> We appreciate the time. You welcome. [Male Voice] Enjoy it. Keep it right there buddy. We'll be right back with our next guest. This is theCUBE. We're live from IBM Edge 2016, be right back. (upbeat music)