 Live from San Francisco, California, the Cube. Covering MarkLogic World 2015. Brought to you by MarkLogic. Here are your hosts, John Furrier and Jeff Kelly. Okay, welcome back everyone. You are watching Silicon Angles the Cube, our flagship program. We go out to the events, this is from the noise. We are live in Silicon Valley at MarkLogic World 2015. I'm John Furrier, co-founder of Silicon Angles. So my co-host, Jeff Kelly, Big Data Analysts at Wikibon.com. Our next guest is Paolo Pellezzoli, who's the Global Head of Architecture and Global Technology Operations for Broadbridge Financial Solutions. Welcome to the Cube. Thank you. So architecture, which means you have to lay everything out. You mentioned you've got about 6,000 people worldwide, global operation. Man, you're in the thick of things. You've got to lay it all out there. What, I mean, it's a double-edged sword. You've got technology and you've got to move fast. So give us the update. What's your world like right now? It's actually interesting because we've got technologies that range back around 50 years through technologies that are being developed as we speak. So because things are rapidly evolving, it's trying to go through and make sure that we've got an applied strategy going forward and doing it at the enterprise level rather than at the departmental level. And the requirements change on a daily basis, which means any kind of traditional technologies that you would use, databases and so on, become defunct the second you actually put them in place. So we've really started taking a look at the entire stack, how we present, how we acquire data, how we aggregate data. And because we do this for the financial services industry, we have data that ranges back a significant amount of time. I mean, we have one system that has railway bonds from 1908. So it's an interesting challenge. So what is the big concern right now? What's the top conversation in your world right now? Internally to your staff, in terms of creating your operational support, DevOps, operations, developers and customers, what are the top conversations in each kind of area that you're having? What are the folks out there right now share that data? I think that regulation is a part of our industry, especially it's been increasing ever since 2008 and it's showing no signs of slowing down. In fact, I think regulation from the US is starting to percolate into other geographies. And it's all driven off some very, very similar pieces of information, who knew what, where, what kind of transaction were they doing, were they allowed to do it. On top of that, you do have data sovereignty and you do have security. So to be able to do this across an enterprise with quite an interesting diversity of technologies is no small feat. And you really do need to change the game in order to go through and look at it because doing it piecemeal, it'll take 15, 20 years and we don't have that time. So contrast that with the approach that you're taking and how that's going to obviously take a lot less than 15 or 20 years, you want to move much quicker. So the contrast was that we believe that the schema side of it worked well through the 80s, 90s and early 2000s. You start taking a look at things like Hadoop that came out that didn't require schema, but it was more from an analytical perspective that the latency wasn't really a requirement. The recoverability wasn't a huge requirement. That would solve only one piece of the puzzle for us. It would not really solve the fundamental problem. Can you replatform? Can you share data from multiple platforms in real time and be able to go through and get event-based analytics? Something happens here. How do I go through and percolate it to the appropriate people? With security, with asset compliance and all the other pieces that Mark Logic is well known for. Now regulation is an interesting thing. It really does have a time series function to it because as things change, if you can track what changed and who actually touched it and what it looked like before the change, that's something which we really do go through and struggle with. I think that the byte temporal aspects are huge for us. So it allows you to do things with your data. You simply couldn't do in the past or you couldn't do it at least faster than that. You could do it, but it was something which was unnatural. So you would have to create what they call an insert-only model. An insert-only model will go through and expand the size of the data that you have considerably. So it's not as economical with the byte temporal mode where it just saves the change. That's really where you go through and start saving on the overall storage and you do have the auditability at any point in time. Talk about the financial services industry generally and about how you see some of these new approaches whether it's NoSQL or Hadoop or other big data quote unquote approaches. Impacting that industry. We see that as financial services is leading the way in a lot of cases in terms of adopting new technologies, always trying to find an edge. How is both the technology and then the speed of business changing the way the financial services industry works? Financial services, it's an interesting dilemma, right? When you start talking about wealth management, they're looking for how are people performing. How is an advisor, a financial advisor giving you the appropriate advice? When you start taking a look at some of the other ones, they're a little more structured and they've got a latency aspect to them. So buy side and sell side have different drivers. But I do think that people have realized that the old way of doing it has become more expensive than it should be. You can do it and financial services typically gone through and push the envelope and whatever they try. But I think traditional relational models, because they're so stringent, you end up getting many variants of it. So you'll end up having 100 or 500 warehouses and it starts very quickly, the data lineage, you start losing it. That's one of the main things that no sequel, you do have the Hadoop side of it or the HDFS and some of the other technologies. But I think that when we start still marrying some of the database capabilities, I think that that's where we're really pushing. What are the biggest things in big data enablement are you seeing at technical levels that's enabling organizations to move faster? Is there a technology innovator or enabler that's driving all this change? What could you point to if you say, hey, that's this one, this area of innovation. Flash is a hardware, cloud, is it software, is it virtualization? Where can you highlight as an architectural view? I mean, I think about it, I think about like a building, oh, we're going to have this new concrete, this columns or, you know, I mean, is there a technology disruptor enabler for your business happening now? There were actually quite a few, I think that it's, you know, I don't think there was one standout, you know, to be perfectly honest, you've got virtualization, which has become something which people have tried to reduce the cost. Cloud, I think, is definitely something which, you know, allows infrastructure to elastically, you know, expand and contract as you need. Storage has obviously come down. I think that the application, there was so much noise out there about which one was the silver bullet. You know, I think that if you really take a look at it, the data side of it, if you don't know what to do with the data, all of these technologies are going to just go through and obfuscate it further, you know. So, when you really take a look at why would somebody move to a new technology like MarkLogic, it's really a, you know, is there something familiar that I can take with me? And the asset compliance, which is, it petrifies a lot of people and you lose it. Petrifies? Yeah, they get deer in the headlights, they don't know what to do, indecision. Yep, and they'll say for analytics purposes, it's fine, 95% is fine. It's enough for me to know which way to travel. But you can't do that with somebody else's money. You know, 10 years ago, if you said my best move is not to move at all, then you go slower, but today I think it's different. Today it is very different. You've got to move fast, get the top line. So I got to ask you on the other end is that, what are some of the KPIs that you're looking at in your business? You look at your dashboard. Is there a dashboard in your metaphor? Or maybe there is one. What are your key performance indicators of are we on the right track? Are we vectoring in the right direction for our technology innovation strategy? What are some of those metrics you look at? I think the biggest one is, it's a combination of time to market and cost. If you take a look at the cost of what we're using in the technology stack today, it's fractions of the cost of what it used to be. Making a developer be able to go through and turn around a request with the same data that they've always had in such a short period of time is, it is a game changer. What we do, it's the auditability and the regulation behind it, and the ability to go through and scale it up cost effectively is something you just can't underestimate. You need agile. I mean, I hate to use the cliche. I mean, you've got to be agile, flexible, getting stuff very fast out of data that could be literally parked somewhere in the organization. Well, the thing is that people always believe that the data has to come into a central point in order to be able to ask the question. We don't necessarily believe that. We believe that. Policy-based access is critical. You have compliance overlaid on top of it. And the thing is that it's, the model that we take is really trying to go through and take the data as raw as we can take it. Don't run it through a lot of ETL functions because the second you start doing that, you'll either change the meaning of the data or you'll lose certain valuable pieces of that data. Okay, final question for you. We're on the break here. Got the crowd behind us folks. This is happening in Mark Lodgic World 2015. Hello. Hello, Sully. He's getting late today. Final question. Share with the folks out there that might not be familiar with Mark Lodgic's benefits. What should they know about the company, the product? What is something that they should pay attention to? It's actually, it's quite a long list, but if you really take a look at it, it does remove the requirement of forcing structure. So being able to go through and link data together, that doesn't fit within a table construct or the limitations of a table construct and doesn't fit within the limitations of SQL, right? Which is a structured query language that has very defined rules. Is, you know, it is totally different way of looking at how you can access data. Being able to provide that data through API layers is again something that traditional developers are comfortable with, customers are comfortable with. You know, and I think that if you can remove some of the, you know, let me massage everything to look the same, you know, I think that that's something which you have to get some of the traditional relational folks out of that mindset. Semantic modeling on top of that is, I think going to be the next major area that people look at. So good solid product, you're happy with it? Very, very happy with it, yep. Awesome. Palo, Pellezzoli, global head of architecture, broad range financial solutions, obviously architecture support and great endorsement for MarkLogic to have your blessing on that, fill the holy water on that, it's been good. And we are here live at MarkLogic World 2015's theCUBE. I'm John Furrier with Jeff Kelly. We'll be back with more wall-to-wall coverage all day. Stay with us here. We'll be right back after this short break.