Live from Las Vegas. It's the Cube covering AWS Reinvent 2017 presented by AWS, Intel, and our ecosystem of partners. >> Hello, welcome back. This is live coverage of the Cube's AWS re:Invent 2017. Two sets, a lot of action, day one of three days of wall to wall coverage. I'm John Furrier with my co-host Keith Townsend. Our next guest cube alumni is Yaron Haviv who's the founder and CTO of Iguazio, a hot new start up. And big news coming next. We got a big announcement. In following their work, Yaron, good to see you again. Thanks for coming back on. >> Hi, thanks! >> Hey you got a new shirt. Share that logo there. >> That's nuclio. That's our new serverless brainwork which is open source. Really kicks ass, it's about 100 times faster than Amazon. >> Word says it's 200 times faster. >> Yeah we don't want to shame. >> You set the bar. >> We doing 400,000 events per second on a single process. They do about 2000. Most of the open source project around the same ball park. >> Yaron, I got to get this off the bat. And then we can have a nice discussion afterwards. A pleasant discussion. Serverless. Let's first define what that means. Because there's a bunch of- I can take nuclio, install it in my data center, run it, am I serverless? >> You know so I mean I'm in the serverless working group. >> For CNCF >> for CNCF. And a we had a hot debate between the open source start ups. Doing what is called functional service and Amazon and others trying to push the notion of serverless. Which is serverless stands for server less. Meaning you don't manage server. And the way we position nucleo, it's actually both. Because on one end you can consume it as an open source project. Very easy to download. Single docker instruction and it's up and running unlike some other solutions. And on the other hand you can consume it as something within the Iguazio data platform. There is a slide from Amazon which I really like. Which is about serverless. They show serverless is attached to kinesis, DynaomoDB, S3 and Athena. Four services of data that attach to Lamda. Iguazio has API compatibility with kineses, DynamoDB with S3 and Presto, which is Athena as well. So exactly the same four data services that they position as far as the service ecosystem are supported on our platform. So we provide one platform, all the data services at Amazon has or at least interesting ones, serverless functions which are a hundred times faster, a few more tricks that they don't have-- >> So what is the definition then. In a pithy way, for someone out there who's learning about serverless. What is it? What's the definition? >> So the notion as a developer, you're sort of avoiding IT. You go, open a nice portal, you write the function, or you write your function in a get up repository somewhere. You click on a button and it gets deployed somewhere. Right now you know where it's going to get deployed. In the future, you may not know. >> Instead of an EC2 instance, get that prepared >> It's not really an EC2. >> The old way. The old way was. Right? >> The old way there were infrastructure guys building your EC2 instance, security layers, milware, etc. You go develop on your laptop and then you need to go and conform and all the continuous integration play was very complicated. Serverless comes inherently with scale out without the scale in, with continuous integration. You have versioning for the code. You can downgrade the version, you can upgrade the version. So essentially its a package version of a cloud native solution. That's the general idea. >> So I can do that if I'm doing it and managing it myself. It functions as a server. And if I'm doing it and it's a provided it as a cloud provider as a server, as a service, it's serverless. None of my operations team is dealing with servers. It's just writing code and just go. >> Yeah, you're writing a function. Push commit. You should play with nucleo, not just other things. But you'll see you're writing a function. Even see it has a built in editor. You write, you push deploy and it's already deployed somewhere. >> So give us some perspective before you move on. On the game what the impact is to a developer. Apples to oranges. Our old way you described it, new ways, it sounds easier! What's the impact? Is it time? Money? Can you quantify? >> The biggest challenge for businesses is to transform. I saw an interesting sentence. It's not about digital transformation, it's about businesses that need to work in a digital world. Okay? Because again, most of the communication of customers to businesses is becoming digital. Okay? Whether it's today from mobile apps tomorrow through Alexa. >> As Luke Cerney says, it's all software. Your business is the software. >> It's all about interactive really. Okay. As a business I always position there are two things you need to take care of as a business. One is increasing the revenue. And that's by engaging more customers. And increasing the revenue per customer. How do you engage more customer? Through digital services. Whether it's Twitters or proving a new service through your web portal. And the next thing is how do you generate more revenue from a customer is by showing recommendations. >> Finding more value. >> And the other aspect is operational efficiency. How do you automate your reparations to reduce the cost. You know Amazon uses robots to do the shipping and packing. So their margins can now be lower. So the generator is both those things. Reducing cost is becoming more and more dependent on automation which is digital. And increasing revenue become more about customer engagement which is digital. Okay so now you're a traditional enterprise. And you have your exchange to worry about. And all the legal stuff and the mainframes. But if you're not going to work on the transformation piece. You're going to die. Because some other start up is going to build insurance company which is sort of agile and all that. >> So you made an interesting comment earlier when you were talking about nucleo. And integrating the functions that really matter. The services that matter. Amazon releases 800 new services a year. >> Actually 1300. >> I'm sorry 1300. >> This time less, no? >> Right now they're at 1130 and they expect 1500, 1700 by the end of the year. Two years ago it was like 750 and then the year before that was 600. >> So is that an indicator as to Amazon's leading this race between the big, I don't know, three, four cloud providers. Rack and stack them for us. How do we assess the capability? >> It's a matter of mentality. Okay. Persos thinks like a supermarket. Just like an Amazon market. I could say I need a cover for my iPad. I'm gonna get 100 covers for my iPad. No one really, I need to now choose. So their strategy is we'll put dozens of services that do similar things. One is better at this, one is better at that. We control the market we'll sell more. We have a different approach. We do fewer services but each one sort of kicks ass. Each one is much better, much faster, much better engineered. Okay? This is also why we are on data plus provides 10 different data APIs and not 10 different individual data platforms. >> Alright so let's talk about the scoreboard. Even though they might be thinking about the supermarket. You've got Amazon, Azure Microsoft and Google. I've looked at some of the data. I mean, Microsoft's been international for a while from their MSN business. They now have Skype. They have data centers, they know a little bit about cloud. Amazon's got a lot more services. They support multiple versions of things. Google is kind of non-existent on the scale of comprehensiveness. >> Have you looked at their serverless functions? By the way? >> There's new stuff. Tensorflow, serverless. >> But serverless they only support an OJS. They have very few triggers and it's still defined as beta. >> That's the point, so people are touting my Forbes article. They're touting like a feature. There's a lot more that needs to get done. So the question I have for you is. There's a level of comprehensiveness that you need now. And I know you guys spend a lot of time building your solution. We've talked abut this at our last Cube interview. So the question is the whole MVP cousin, minimal viable product. Is great when you're building a consumer app for an iPhone. But when you start talking about a platform and now cloud. Question to you is there a level of completeness bar to be hurdled over for a legit cloud or cloud player? >> I don't think you need 1000 services to build a good cloud. But you do need a bunch of services. Okay? Now the way we see the world like Satya. Okay? Which is there is a core cloud. But there is sort of a belt around it which is what we call intelligence cloud. We would define ourselves as the intelligence cloud. So if someone is building a machine learning model and it needs a 5 year worth of data. And it just needs to do crawling on top of it. It's not really an interesting problem. It's commoditized, lots of CPO power, object storage. But the bigger challenge is doing game referencing close to the edge. This is what needs to happen in real time. You need fewer services but you need to be real time. >> Smarter integration to do that. Right? I mean. >> You have density problems. You don't have a lot of room to put a 100 servers. It needs to be a lot more integrated. You know look at Azure stack. Their slogan is consistency. Look at a slide that shows which Azure services are part of Azure stack. Less than 20%. Because it's a lot more complicated to take technology design whereas hyper scale and put them on few servers. >> How do customers figure it out? What does a customer do? It's all mind boggling. >> I love that concept of core services and then value around those core services. What are those core services that a cloud must have before I start to invest in that cloud providers strategy? >> So the point again, there's a lot of legacy that you need to grab with you. Especially someone like Amazon. So they have to have VMs and migration services from Oracle, etc. But let's assume I'm a start up and building a new client native applications. Do I need any of that? No. I can probably can do with containers. I don't really need to be VMs. I can use something like cybernetics, I can use sequel databases maybe some like sequel. So I can redesign my application differently with a lot fewer services. The problem for someone like Amazon in order to grow and be a supermarket, you have to have ten of everything. If I'm someone that focus on new applications I don't need so many services and so much legacy. >> Well I'll say one thing. You can call them a supermarket, use that retail analogy, I buy that analogy only to the extent that you used it. But if that's the case, then everyone's hungry for food. And they're the only supermarket in town. >> But Wholefoods maybe less stuff on the shelf. >> Everyone else is like a little hot dog stand compared to the supermarket. Amazon is crushing it. Your thoughts? I say that. Are they kicking ass? >> Obviously Amazon is kicking ass. But I think Azure is ramping up faster. Amazon is generating more alienation among people that they are starting to compete with. You know. >> Azure is copying Amazon. Right? >> Yeah. But they have a different angle. They know how to sell to enterprises. They already have the foot in the door for Office 365. I've talked to a customer. We're going Azure. I say why? >> Together: They've got 365. >> We already certify the security with 365 for us to use Azure it's a- >> Right up until that next breech. >> So the guys owning ITs, it's easier for them to go to Azure. The developers want Amazon. Because Amazon is sexier. >> We got to break. We debated this on the intro segment with he analyst. Question. IT buyers have been driven by a top down CIO driven, CXO driven waterfall, whatever you want to call it, old way. With developers now at the driver's seat, with all of this serverless function, serverless coming around the corner very fast. Are developers driving the buying decisions or not? Or is it IT? The budget's still there. They want to eliminate labor. They want more efficiencies. Are you seeing it again? Will it happen? >> Yeah because we are just in the middle. On one end we're an infrastructure. We're an infrastructure consumed by developers. So we keep on having those challenges within the accounts themselves. IT doesn't get what we're doing. Serverless, and database is serverless. Because they like to build stuff. They want to take the nutanix and take a hundred services on top of it. And it will take them two years to integrate it. By that time the business already moved somewhere else. >> So IT could be a dinosaur like the mainframe? >> Right. I think the smart ITs understand they need to adopt cloud instead of fight it. And more the line further up the step. And that sort of the thing we are trying to provide to them. When you are building stuff you are buying EMC storage. You are not just taking discs. So why do you focus on this low level block storage when you're buying infrastructure. Why no buy database as a service. And then you don't need all the hassle. Streaming is a service. Serverless is a service. And then you don't need all that stack. >> Yaron, you should be our guest analyst. But you're too busy building a company. We're going see you next week in Austin for Cubicon. Congratulations. I know you guys have worked hard. The founder and CTO of Iguazio. You're going to hear a lot about these guys. Smart team. They're either going to go big or go home. I think they're going to go big. Congratulations. More coverage here at AWS Re:Invent after this short break. I'm John Furrier with Keith Townsend.

>> Hey welcome back everybody, Jeff Frick here with theCUBE. We are in downtown San Francisco at the Mission Bay Convention Center at Node Summit 2017. We've been coming to Node Summit off and on for a number of years. And it's pretty amazing, the growth of this application for development. It really seems to take off. There's about 800 or 900 people here. It's kind of the limits of the facility here at Mission Bay. But we're really excited to be here. And it's not surprising to have me see Intel is here in full force. Our first guest is Monica Ene-Pietrosanu. And she is the Director of Software Engineering for Intel, welcome. >> Thank you, hello, and thank you very much for inviting me. It's definitely exciting to be here. Node is this dynamic community that grows in one year, like others can. So it's always exciting to be part one of these events. And present about the work we are doing for Node. >> So you're on a panel later on Taking Benchmarking to the Next Level. So what is that all about? >> That is part of the work we are doing for Node. And I want to mention here the word stewardship. Intel is a long time contributor in the open source communities. And has assumed a performance leadership in many of these communities. We are doing the same for Node. We are driving, we are trying to be a steward for the performance in OJS. And what this means, is we are watching to make sure that every check in that happens, doesn't impact performance. We are also optimizing Nodes, so it give the best of the hardware, Node runs best on the newest hardware that we have. And also, we are developing, right now new measures, new benchmarks which better reflect the reality of the data center use cases. The way your Node is getting used in the Cloud. The way Node is getting used in the data center. There are very few ways to measure that today. And with this fast development of the ecosystem, my team has also taken this role of working with the industry partners and coming up with realistic measures for the performance. >> Right, so these new benchmarks that you're defining around the capabilities of Node. Or are you using old benchmarks? Or how are you kind of addressing that challenge? >> We started by running what was available. And most of the benchmarks were quite, let's say, isolated. They were focused on single Node, one operation, not realistic in terms of what the measurements were being done for the data center. Especially, in the data center everything is evolving. So nothing is just running with one single computer. Everything is impacted by network latencies. We have a significant number of servers out there. We have multiple software components interacting. So it's way more complex. And then you have containers coming into the picture. And everything makes it harder and harder to evaluate from the performance perspective. And I think Node is doing a pretty good job from the performance perspective. But who's watching that it stays the same? I think performance is one of those things that you value when you don't have it, right? Otherwise you just take it as granted, like it's there. So, my team at Intel is focused on top tier scripting languages. We are part of this larger software organization called Software and Services Group. And we are, right now, optimizing and writing the performance for Python, No-gs, PHP HHVM, and for some of the top tier languages used in the data centers. So Node is actually our interesting story in terms of evolution. Because we've seen, also, an extraordinary growth. We've seen, it's probably the one who's doubled for the past three years. The community has doubled. Everything has doubled for Node, right? Even, the number of commits, it depends on which statuses you look-- >> They're all up and to the right, very steep. >> Yeah, so then it's a very fast progress which we need to keep pace with. And one thing that is important for us is to make sure that we expose the best of our hardware to the software. With Node that is taking an interesting approach. Because Node is one of, what we called CPU front end bounce. It's having a large footprint. It's one of the largest footprint applications that we've seen. And for this we want to make sure that the newest CPUs we bring to market are able to handle it. >> I was just going to say, they have Trevor Livingston on it from HomeAway. Kicked off things today. We're talking about the growth. He said a year ago, they had one Node JS project. And this is a big site that competes with, like, Air B&B. That's now owned by Expedia. Now they say, he said, they had, "15 projects in production. "22 almost in production, and 75 other internal projects." In one year, from one. So that shows pretty amazing growth and the power of the application. And from Intel's point of view, you guys are all in on cloud. You're all in on data centers. You've all seen all the adds. So you guys are really, aggressively taking on the optimization, for the unique challenges and special environment that is Cloud. Which is computing everywhere, computing nowhere. But at the end of the day, it's got to sit on somebody's servers. And there's got to be a CPU in the background. So you look at all these different languages. Why do you think Node has gone so crazy? >> I think there are several reasons. And my background is a C++ developer, coming and security. So coming into the Node space, one thing amazed me. Like, only 2% of the code is yours, when you write an application. So that is like-- >> Jeff: 2%? >> So where is the other 98% coming from? Or it's already pre developed. It's an ecosystem, you just pull in those libraries. So that's what brings, in addition to the security risks you have. It brings a fantastic time to market. So it enables you as the developer to launch an application in a matter of days, instead of months or a year. So time to market is an unbeatable proposition. And I think that's what drives this space. When you need to launch new applications faster and faster, and upgrade. For us, that's also an interesting challenge. Because we have, our super road maps are not days, right? Are years? So what we want to make sure is that we feed back into the CPU road map the developments we are seeing into this space. I have on my team, I have several principal engineers who are working with the CPU architects to make sure that we are continuously providing this information back. One thing I wanted to mention is, as you probably know, since you've been talking to other Intel people, we've been launching recently, the latest generation server, Skylake. And on this latest generation Nodes. So all the Node workloads we've been optimizing and measuring. So one point five x performance improvement, from the prior generation. So this is a fantastic boost. And this doesn't happen only from hardware. It happens from a combination of hardware and software. And we are continuing to work now with the CPU architects to make sure that the future generation also keeps space with the developments. >> It's interesting, kind of the three horsemen of computing, if you will, right? There's compute, there's store, and there's IO. And now we're working, and it's interesting that Ryan Dahl, it's funny, they brought up Ryan Dahl. We interviewed him back at the Node JS, I think back in 2011? Still one of our most popular segments on theCUBE. We do thousands of interviews a year. He's still one of the most popular. But to really rethink the IO problem, in this asynchronous form, seems to be just another real breakthrough that opens up all types of capacity in compute and store. When you don't have to sit and wait. So that must be another thing that you guys have addressed from coming from the hardware and the software perspective? >> You are right on spot, because I think Node, comparing to other scripting languages brings more into the picture, the whole platform. So it's not only a CPU. It's also a networking. It's also related to storage. Also, it makes the entire platform to shine if it's optimized to the right capability. And we've been investing a lot into this. We have all our work is made available is open source. All our contributions are up-streamed back into the mainstream. We also started an effort to work with the industry in developing these new workloads. So last year at Node Interactive, we launched one new workload, benchmark, for Node. Which we called Node DC. With his first use case, which is an employee information system, simulating what a large data center distributed application will be doing. This year, now at Node Summit, we will be presenting the updated version of that, one point zero, this time. It was version zero point nine, last time. Where we added support for containers. We included several capabilities to be able to run, in a configural manner, in as many configurations as needed. And we are also contributing this back. We submitted it to the Node Foundation. So it becomes an official benchmark for the Node Foundation. Which means, every night, after the build system runs, this will be run as part of the regressions. To make sure that the performance doesn't degrade. So that's part of our work. And that's also continuing an effort we started with what we call the languages performance portal. If you go to languagesperformance.intel.com we have an entire lab behind that portal, in which every night we build this top tier scripting languages. Including Python, including Node, including PHP, and we run performance regressions on the latest Intel architecture. So we are contributing the results back into the open source community, to make sure that the community is aware if any regression happens. And we have a team of engineers who jumps on those regression center root causes and analyzes it. So to figure it out. >> So Monica, but we're almost out of time. But before I let you go, we talked before we got started, I love Kim Stevenson, I've interviewed her a bunch of times. And one of the conversations that we had was about Moore's Law. And that Moore's Law's really an attitude. And it's kind of a way to do things more than hitting the physical limitations on chips, which I think is a silly conversation. You're in a constantly, the role of constantly optimizing. And making things better, faster, cheaper. As you sit back and look at, kind of, what you've done to date, and looking forward, do you see any slowdown in this ability to continue to tweak, optimize, tweak, optimize? And just get more and more performance out of some of these new technologies? >> I wouldn't see slow down. At least from where I sit on the software side. I'm seeing only acceleration. So, the hardware brings a 30%, 40% improvement. We add, on top of that, the software optimizations. Which bring 10%, 20% improvements as well. So that continuously is going on. And I am not seeing it improving. I'm seeing it becoming more, there is a need for customization. So that's where when we design the workloads, we need to make them customizable. Because there are different use cases across the data center customers. So they are used differently. And we want to make sure that we reflect the reality. That's how they're in the world. And that's how our customers, our partners can also leverage them, to measure something that's meaningful for them. So in terms of speed, now, we want to make sure that we fully utilize our CPU. And we grow to more and more cores and increase frequency. We also grow to more capabilities. And our focus is also to make the entire platform to shine. And when we talk about platform we talk about networking. We talk about non volatile memory. We talk about storage as well as CPU. >> So Gordon's safe. You're safe, Gordon Moore. Your law's still solid. Monica, thanks for taking a few minutes out of your day and good luck on your panel later this afternoon. >> Thank you very much for having me here. It was pleasure. >> Absolutely, all right, Jeff Frick checking in from Node Summit 2017 in San Francisco. We'll be right back after this short break. Thanks for watching. (upbeat music)