Big Data Interview: Robert Barr of Barclays

DZone 's Guide to

Big Data Interview: Robert Barr of Barclays

Big Data has become an important tool in the financial industry as a way to gain a competitive advantage. Check out this interview with the VP of Data Grid Engineering at one of the leading UK banks,

· Big Data Zone ·
Free Resource

Robert Barr, VP Data Grid Engineering Lead at Barclays, will present a keynote presentation titled “In Memory Computing for Financial Services: Past, Present and Future” at the In-Memory Computing Summit on May 23-24 in San Francisco. (A limited number of seats are still available to the event. Register today to attend at http://imcsummit.org).

Robert’s presentation addresses the major data processing challenges faced by the financial services industry in regards to performance, scalability and security. Robert was kind enough to answer a few questions to give us a high-level look at what he will cover in his talk.

IMC Summit:
What new or evolving challenges do you foresee ahead for the financial sector, and how does in-memory computing address those challenges?

Robert Barr:
Regulatory requirements are on the increase, with emerging regulations such as the Markets in Financial Instruments Directive (MiFID), Protection of Clients Assets and Money (CASS) and the Fundamental Review of the Trading Book (FRTB) to name but a few impacting not only the reporting requirements but mandating how financial services organizations are structured and operate. The constantly evolving challenge is to streamline operations, to reduce running costs and to comply with regulations while maintaining and improving market position. Traditional models of technology use are no longer sufficient to operate in today’s economy and financial services are turning to emerging tools such as in memory computing, Big Data and Cloud computing to drive down costs while increasing the scale of operations.

IMC Summit:
To what extent are Regulatory requirements driving the adoption of In-Memory Computing technologies in the financial industry?

Robert Barr: 
Regulatory requirements are probably the major driver for the way Financial Services operate, and consequently the technology that is being adopted. Regulators are constantly seeking to improve consumer protections, to simplify complex products and to reduce the risk inherent in Financial Services operations. The direct consequence of this is an increase in the amount and complexity of regulatory reporting being performed, and the rate at which those are being passed to the regulators. Large scale in memory computing is increasingly being utilized to meet those challenges of volume and speed.

IMC Summit: 

Assuming a world where the spinning disk is obsolete and all business applications run in-memory, what stage do you think we are in in that adoption process?

Robert Barr:
In my experience, we’re in the infancy of this process. Applications are adopting in memory products to help meet their performance requirements but still rely heavily on spinning disk to meet their scalability and persistence needs. As technologies like NVDIMM and DSSD become more prevalent, and as the convergence of Relational, Big Data and NoSQL continues, we’ll start to see a shift away from disk-first and towards memory-first applications. As technology improves and the price disparity between memory and disk narrows, disk will become less and less relevant.

Attend Robert’s talk along with keynote talks from other thought leaders in the field of In-Memory Computing and over 30 deep-dive presentations from developers and decision makers who are pushing the limits of performance and scalability of big data systems at the In-Memory Computing Summit in San Francisco May 23-24. Register today.

big data, computing, data, financial services, in-memory, in-memory computing, technologies

Published at DZone with permission of Nikita Ivanov , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}