 from Las Vegas, it's theCUBE. Covering EMC World 2016. Brought to you by EMC. Now, here are your hosts, John Furrier and Dave Vellante. Okay, welcome back everyone. We are here live at EMC World 2016. This is Silicon Angles theCUBE. This is our flagship program. We go out to the events and extract the significant noise. I'm John Furrier with my co-host Dave Vellante. My next guest was Hal Guy, who's the Vice President and General Manager of Scale I.O. at EMC. CUBE alumni, welcome back to theCUBE. Good to see you. Thank you, good to see you. In town from Israel, what's going on? Scale I.O., give us the update, because they're kind of in the map now. Yes. On the map, in the map. Absolutely. Emerging and core where they sit. ETD, emerging. I think, so first of all, we released 2.0. A couple of months ago. A lot of additional capabilities there. Security, LDAP, Active Director Integration, IPv6, Inflate checksum, which is very important actually because we are running on the application servers. Our checksum is straight from the I.O., leaving the application all the way down to the storage and back. We have a lot of additional capabilities related to that, for example, background scrubbing for silent corruption. Basically, a lot of enterprise, great capabilities I've been adding to the product. It's becoming a... What are some of the top use cases? Real time, is it much more app integration? Where are you seeing Scale I.O.? So our two main use cases that we see are infrastructure as a service. So public clouds, private clouds, and databases. So we see customers wanting the agility, high performance. Scaler is the highest performance product in the market today. Scale, elasticity, so the ability to add components, nodes, move them, take them away. Elimination of forklift upgrades. So with Scale I.O. you never need to do a data migration project ever again. Actually, this morning, one of our customers, a city group, presented how they are running Scale I.O. in their environment, and Chris, their head of storage engineering, told that they are doing an upgrade Tuesday afternoon. So no more night work, no more weekends. With Scale I.O. that's... So Boas, for the people who might not be familiar with Scale I.O., describe how it's different from like a traditional SAN system. So Scale I.O. is a software only enterprise class block storage device. What we do is we provide software components that you run either in a hyper-converged manner, so running the storage on the same server as the applications or the hyper-visors, or you can also run Scale I.O. in a two-layer architecture on commodity hardware, so compute on commodity servers and storage on commodity servers in a separate layer, or any mix and match of hyper-converged and two-layer. But in any case, so what we provide is a software only. We are agnostic to the underlying hardware. We run on any hardware of the customer's choice. We run in virtual environments like ESX, Hyper-V, Zen, KVM, et cetera, and on bare metal environments, Windows, all kinds of Linuxes, Red Hat, Ubuntu, CoreOS, et cetera. So it's consistent with what you would expect with sort of, you know, everybody's talking about cloud-native, modern architectures. I mean, this essentially is a modern architecture. You're not buying a big storage box. Of course, the EMC sells a lot of big storage boxes. You're the disruptor inside of EMC, which is kind of interesting, right? Yes. So it's a beautiful EMC, isn't it? So EMC understands where the market is going and is not afraid to disrupt themselves. And that's what we are doing. So, yeah, Scale I.O. is indeed a modern architecture. So you get all the characteristics of modern architectures, commodity hardware, software-only, scale-out, hardware independence, flash, magnetic media, et cetera. But we are a block device that enables customers to run traditional platform-to-applications and databases on a modern architecture, scale-out, commodity-based architecture. And that's the beauty of Scale I.O. So in that respect, it's very similar to what Symmetrix did with EMC in the 90s. So in the 90s, the Symmetrix was at that time a client-server enabling architecture that worked with the Platform One mainframe, right? And bridged to the Platform Two. So similarly, Scale I.O. bridges Platform Two applications running to the Platform Three infrastructure. Well, the interesting thing about Symmetrix at the time was you had a big box. It was consolidated, connected to mainframe or Unix or every different type. Remember, the Unix is 10 different flavors of Unix, right? The windows, whatever it was. And they supported everything and allowed that kind of consolidation to support these open client-server apps. What's the analog today for Scale I.O. Is it these so-called cloud-native apps, the DevOps environment? Is that the analogous? I would say the analogy is that Scale I.O. enables you to take the platforms that you are used to work with today and the applications that you're used to work with today. So Linux, all kinds of Linuxes, Windows, hypervisors like ESX and others, databases, Oracle, SAP HANA, and so forth. But to run them not in traditional silos with dedicated storage arrays, fabric switches, HBA cards, et cetera, but to run them in a scale-out approach where you can benefit from the elasticity of commodity hardware, where you can regard your server nodes as commodity. You can add nodes on the fly. You can replace them on the fly. You can grow as you go. Scale I.O. rebalance is automatically as you add more nodes. So you get the flexibility and the elasticity of cloud-native infrastructures and cloud-native applications, but for both P2 and P3 type of applications. And you're talking about high degrees of automation. I mean, this is the way, what you're describing as an observer would say, well, I guess this is how Facebook would do it, or this is how Amazon would do it, or Google would do it. Right. But generally for those organizations, they're thinking about a lot of file-oriented data, but Scale I.O. is block-oriented data. So what's the, what are the typical use cases that you mentioned in Citi as an example? So there's obviously a lot of transactions going on in Citi. So it's not, so yeah, so Citi Group actually also presented this morning and so it's not a secret, or any use case of Citi Group that can run on Scale I.O. is going on to Scale I.O. So Citi obviously bought a lot of arrays, traditional storage boxes over the past two decades from EMC. Today, environments that cannot run on Scale I.O., like AIX, mainframe are going onto Vmaxes and the like. Whatever can go onto Scale I.O. And Citi Group is going onto Scale I.O. So modern apps are going to Scale I.O. Modern apps and traditional platform, two apps. Oracle, MongoDB, ESX, ESX environments, big ESX environments. And why is that? Is this just performance or is it? Performance, so they run better performance. It's cost, on the first deployment they already got 60% lower cost. So 6% savings, better performance, more elasticity, operational ease. Not locked in, they're getting moving around, very versatile. Elimination of vendor hardware lock in, yes. All right, so when a customer says, bottom line me, what's the bottom line for Scale I.O., how would you describe it? Bottom line is get you all the enterprise class storage functionality that you are used to, plus the flexibility and elasticity of commodity-based hardware at a significantly lower cost and at a higher scale and higher performance than what you're used to. So we call it service-and, right? You've seen our service-and stuff and we've been on this trend for a long, we predicted this long, long time ago. We said this just makes so much sense. However, having said that, the criticisms that we got at the time were, well, how are you going to protect it? How are you going to bring enterprise class resiliency and recovery? And our answer was always, well, that's your problem. You're the technologist. So you've cracked that code, right? Or are cracking that. Absolutely. So talk about the stack that enables that resiliency. So the approach that we took in Scale I.O. is an approach where we are creating a mesh mirroring high availability layout where data is being spread across the nodes in a platform and where we are able to realize a very short rebuild time. So every storage system, every high availability is about mitigating the risk of outages. And so when you look at traditional systems, when you have a disk failure in the road, in the shelf, you have a rebuild time that might take several hours. And if during those hours you have another disk failure, you might lose access to your data or you might lose your data. When you look at Scale I.O., our rebuild times are literally seconds. So if you have just a simple environment, 100 servers each with one single device of one terabyte and a 10 gigabit network, if a server goes down, the rebuild time is 10 seconds instead of three, four hours. So this means that if you don't have another outage within 10 seconds, you are again fully protected. So your enterprise class high availability with Scale I.O. is more than guaranteed. Raider rays weren't conceived in the day where there were 20 terabyte drives on the horizon. So big difference. Yeah, okay, cool. So what's the landscape for the marketplace look like today? As emerging with cloud native becomes more and more relevant, what are the top conversations that you are having with customers? What we're seeing that customers want is they want resilience, they want operational ease, elasticity, they want high performance, they want scale because their data centers are consolidating and growing. They want hardware independence. Really, software only solution. Scale I.O. is right where the customer wants to go. Noaz, thanks for spending your time on theCUBE here. How many times you've come to the U.S. from Israel a year? Once a month? About once a month, once every six weeks, yes. Well, congratulations regularly. Congratulations on all your success. This is theCUBE here live at EMC World 2016. We are on the ground live for EMC World 2016. I'm John Furrier, Dave Vellante, you're watching theCUBE. It's always fun to come back to theCUBE because the discussion is always interesting.