Data as a Service

Your company’s data should be its greatest asset. It ought to be easy to develop new applications based on your data and to generate essential business insights – but for too many, legacy systems and databases make this difficult or impossible.
Organizations are turning to a new approach: Data as a Service. This strategic initiative is an investment in consolidating and organizing your enterprise data in one place, then making it available to serve new and existing digital initiatives. Data as a Service becomes a system of innovation, exposing data as a cross-enterprise asset. It unlocks data from legacy systems to drive new applications and digital systems, without the need to disrupt existing backends.

Challenges

The keys to success in the digital age are how quickly you can build innovative applications, scale them, and gain insights from the data they generate – but legacy systems hold you back.

Lack of Agility

Demands for faster time to market and higher productivity are held back by traditional rigid relational data models, waterfall development, and wariness of altering existing systems

Data Locked in Silos

No complete view of your data? That means poor customer experience, missing insights, and slower app development.

Poor Data Accessibility

Existing systems aren’t built for the modern access patterns of 24/7 customer experiences on web, mobile, and social – and they’re single points of failure.

Limited Data Support

New classes of web, mobile, social, IoT, and AI applications produce data in a volume and variety that legacy systems just can’t handle.

Cloud Blockers

Brittle legacy systems prevent the shift to cloud computing, holding developers back from on-demand access to elastically scalable compute and storage infrastructure.

High Cost

Expensive hardware, huge jumps in costs as workloads scale, and punitive licensing impose barriers to innovation.

Solution

Deliver Data as a Service within your organization to speed development, integrate data, and improve accessibility and performance.

The path to Data as a Service is to implement an Operational Data Layer (ODL). This data layer sits in front of legacy systems, enabling you to meet challenges that the existing architecture can’t handle – without the difficulty and risk of a full rip and replace. Depending on your requirements, an ODL can draw data from one or many source systems and power one or many consuming applications. An ODL can be used to serve only reads, accept writes that are then written back to source systems, or evolve into a system of record and eventually replace legacy systems entirely and simplify the enterprise architecture.
An ODL makes your enterprise data available as a service on demand, simplifying the process of building transformational new applications. It can reduce load on source systems, improve availability, unify data from multiple systems into a single real-time platform, serve as a foundation for re-architecting a monolith into microservices, and more. An Operational Data Layer becomes a system of innovation, allowing an evolutionary approach to legacy modernization.

Benefits

Reduce Risk

  • Achieve always-on availability to eliminate downtime (and any associated penalties)

  • Avoid exposing source systems directly to new consuming applications

  • Implement a system of innovation without the danger of a full “rip and replace” of legacy systems

Improve Innovation

  • Build new applications and digital experiences that weren’t possible before

  • Improve customer experience

  • Provide digital experiences that are a unique differentiator vs. the competition

Move Faster

  • Develop new applications 3-5x faster

  • Iterate quickly on existing services, adding new features that would have been impossible with legacy systems

  • Deliver insights that improve your competitiveness and efficiency

Lower Costs

  • Reduce capacity on source systems, cutting costs for licensing, MIPS, and expensive hardware

  • Leverage cloud and/or commodity infrastructure for workloads

  • In the long term, decommission legacy systems

Why MongoDB?

When you choose MongoDB as the foundation for DaaS, you’re investing in the best technology for your system of innovation.

MongoDB is the best way to work with data

Ease

MongoDB’s document model makes it simple to model – or remodel – data in a way that fits the needs of your applications

Speed

Unifying data in MongoDB means you can write less code and get better performance when accessing data

Flexibility

A flexible data model is essential to integrate multiple source systems to offer a unified DaaS: adapt your schema at any time, without disruption

Versatility

Query data in any way your applications require, meeting the demands of different workloads while providing ACID guarantees to ensure data integrity

MongoDB lets you intelligently put data where you need it

Availability

Built-in redundancy and self-healing recovery ensure service continuity of DaaS

Scalability

MongoDB ensures that you can scale your DaaS to store all your enterprise data and serve the most intensive workloads and demanding users

Workload Isolation

Run operational apps while also serving analytics and BI to unlock critical insights in real time – all on a single data platform

Data Locality

Distribute your MongoDB cluster globally for worldwide DaaS coverage and regulatory compliance

MongoDB gives you the freedom to run anywhere

Portability

MongoDB runs the same everywhere – on-prem, on your developers’ laptops, in the cloud, or as an on-demand, fully managed Database as a Service

Global Coverage

Deploy a MongoDB cluster across the globe – or turn to MongoDB Atlas, our Database as a Service, for coverage in 50+ regions of all the major cloud providers

No Lock-In

Get the benefits of a multi-cloud strategy and avoid vendor lock-in – or if you want, run MongoDB yourself on-prem

Use Cases

Single View

DaaS is perfectly suited to generating a Single View of your business. When you unify your enterprise data and make it available as Data as a Service, the next step is to build an application to expose a single view of that data to those who need it. Better real-time visibility across the business, improved customer service, and insight for more intelligent cross-sell and up-sell opportunities are all within reach.

Analytics

Providing Data as a Service doesn’t just support operational applications. It can also power the the analytics that make sense of your data – faster than a traditional data warehouse. Whether you’re analyzing your unified enterprise data set for business insights, running real-time analytics to take action based on algorithms, or reviewing usage patterns to inform application roadmaps, an Operational Data Layer can serve analytical needs with the appropriate workload isolation to ensure that there is no performance impact on production workloads.

Mainframe Offload

Mainframes and other legacy systems aren’t suited for modern applications. Rigidity, downtime requirements, and high costs mean that you’re held back from innovating for the business. By implementing an Operational Data Layer in front of your legacy systems, you can build new apps faster, deliver great performance with high availability, meet new regulatory demands, and make it drastically easier to serve mainframe data to new digital channels – all while reducing MIPS and hardware upgrade costs.

And More

Building a mobile application to reach your customers any place, any time? Putting machine learning to work on your enterprise data? Building recommendation engines, adding social components to your UI, or personalizing content in real time? These applications, and any others you need to build, benefit from being able to access Data as a Service. What innovation could you power with all of your enterprise data easily and securely available in one place?
HSBC’s data assets are growing rapidly – from 56 PB in 2014 to 93 PB in 2017. Customers are demanding more, regulators are asking for more, and the business is generating more. In order to make trading data available to a multitude of new digital services, HSBC implemented an Operational Data Layer to become the single source of truth. The ODL, powered by MongoDB, enables HSBC’s development and architecture teams to meet the board’s strategy of using technology to make the bank “simpler, faster, and better”
RBS implemented Data as a Service – which they call an Enterprise Data Fabric – in order to improve data quality, reduce duplication, and simplify architectures to become leaner. The results? Cost reduction, plans to decommission hundreds of legacy servers, an environment of collaboration and data sharing, and the ability to develop new applications in days, rather than weeks or months on the old systems
“Data Fabric provides data storage, query and distribution as a service, enabling application developers to concentrate on business functionality.”
Alight Solutions (formerly part of Aon PLC) provides outsourced benefits administration for close to 40 million employees from over 1,400 organizations, but retrieving customer data from multiple frontend and backend source systems meant high mainframe MIPS costs, scaling difficulties, and high query latency. Moving to Data as a Service delivered from an ODL on MongoDB reduced query latency by 250x for better customer experience, lowered peak mainframe consumption to reduce costs, and unlocked new business innovation.
Barclays is solving one of the hardest challenges facing any enterprise: a true 360 degree view of the customer with an ODL that gives all support staff a complete single view of every interaction a customer has had with the bank. This is helping Barclays drive customer interactions to new digital channels and improve the customer experience.

HSBC’s data assets are growing rapidly – from 56 PB in 2014 to 93 PB in 2017. Customers are demanding more, regulators are asking for more, and the business is generating more. In order to make trading data available to a multitude of new digital services, HSBC implemented an Operational Data Layer to become the single source of truth. The ODL, powered by MongoDB, enables HSBC’s development and architecture teams to meet the board’s strategy of using technology to make the bank “simpler, faster, and better”

RBS implemented Data as a Service – which they call an Enterprise Data Fabric – in order to improve data quality, reduce duplication, and simplify architectures to become leaner. The results? Cost reduction, plans to decommission hundreds of legacy servers, an environment of collaboration and data sharing, and the ability to develop new applications in days, rather than weeks or months on the old systems
“Data Fabric provides data storage, query and distribution as a service, enabling application developers to concentrate on business functionality.”

Alight Solutions (formerly part of Aon PLC) provides outsourced benefits administration for close to 40 million employees from over 1,400 organizations, but retrieving customer data from multiple frontend and backend source systems meant high mainframe MIPS costs, scaling difficulties, and high query latency. Moving to Data as a Service delivered from an ODL on MongoDB reduced query latency by 250x for better customer experience, lowered peak mainframe consumption to reduce costs, and unlocked new business innovation.

Barclays is solving one of the hardest challenges facing any enterprise: a true 360 degree view of the customer with an ODL that gives all support staff a complete single view of every interaction a customer has had with the bank. This is helping Barclays drive customer interactions to new digital channels and improve the customer experience.

Resources

A guide to the technology, development, deployment, and processes required for a single view of your business
Core concepts, schema design, application development, and data migration considerations when evaluating MongoDB vs. relational databases
An introduction to microservices, their advantages, and what technologies are required for this architecture pattern
Get in touch to learn more about how to implement Data as a Service at your organization, review reference architectures, and more