Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

In-Memory Technologies: Meeting Healthcare's Fast Data Challenges (Part 1)

DZone's Guide to

In-Memory Technologies: Meeting Healthcare's Fast Data Challenges (Part 1)

Modern healthcare has many demanding requirements for the storage and querying of data. Ignite provides a range of capabilities that can meet these needs perfectly.

· Big Data Zone ·
Free Resource

Hortonworks Sandbox for HDP and HDF is your chance to get started on learning, developing, testing and trying out new features. Each download comes preconfigured with interactive tutorials, sample data and developments from the Apache community.

This is a two-part series on the use of fast data in healthcare and how in-memory technologies such as Apache Ignite can meet the requirements and challenges of the healthcare industry. In this first part, we will focus on identifying some of the key challenges in healthcare. In the next part, we will discuss a healthcare case study and see how Apache Ignite and GridGain solved a customer’s problem.

Introduction

Healthcare is big business and involving a very wide range of applications, such as electronic health record management, drug discovery, and health insurance claims. Apache Ignite is perfectly suited to these applications. Figure 1 shows a high-level view of the Apache Ignite in-memory computing platform.

Image title

Figure 1: Apache Ignite in-memory computing platform

We can see in Figure 1 that at its heart, Apache Ignite is a distributed memory-centric data storage platform. It supports ACID semantics and powerful processing APIs including SQL, compute, key/value, and transactions. Ignite’s memory-centric approach enables it to use memory for high throughput and low latency. However, it can also utilize local disks or SSDs to provide durability and fast recovery.

One of Ignite’s major strengths is that memory is treated as fully functional storage, not just as a caching layer. For example, Apache Ignite can function in pure in-memory mode, in which case it can be treated as an in-memory database (IMDB) and in-memory data grid (IMDG) at the same time. However, when persistence is turned on, Ignite begins to function as a memory-centric system where most of the processing happens in memory, but the data and indexes are persisted to disk. Compared to traditional disk-based relational systems or NoSQL systems, Ignite is strongly consistent, horizontally scalable, and supports both SQL and key-value processing APIs. In Figure 1, we can also see that Ignite can be integrated with third-party database systems and external storage. In addition to Healthcare, Apache Ignite caters for a wide range of use cases.

Fast Data in Healthcare

Healthcare applications may cover a wide range of uses. However, there are several areas that are of particular importance and have been highlighted in a recent report from Stanford Medicine.

Today, there is a greater focus on precision medicine and personalization. This will aid more accurate diagnostics for many serious medical conditions, such as tumors and cancers, disorders of nerves and the nervous system, and diseases and abnormalities of the heart. Increasingly, there are better tools available that allow more collaboration between different parts of the healthcare system. Furthermore, clinical research can enable speedier drug discovery and the treatment of complex or rare diseases. We will discuss a customer involved with drug discovery work in Part 2 of this blog series. Apache Ignite provides distributed storage that allows huge quantities of data to be stored to support these requirements for precision medicine and clinical research. Figure 2 shows Ignite’s distributed storage architecture. Ignite’s Data Grid can be viewed as a distributed partitioned hash map with every cluster node owning a portion of the overall data. As more cluster nodes are added, more data can be stored.

Image title

Figure 2: Distributed storage

Since more patient-specific data is available today through the use of health wearables, home monitors, and smartphones, managing streams of data and complex event processing will be required. The Internet of Things (IoT) is also very applicable to healthcare applications. Personalized data will improve the patient experience. Apache Ignite supports adapters and connectors for various streaming technologies and Figure 3 shows an example software stack for IoT applications that use open-source software from the Apache Software Foundation. Ignite has powerful in-memory capabilities and APIs, as previously mentioned.

Image title

Figure 3: Streaming and complex event processing

Finally, the use of predictive models allows healthcare providers to anticipate, diagnose, and treat diseases earlier. This can provide improved patient health and cost savings. The use of machine learning can help in the development of more detailed patient health risk profiles and also allow earlier intervention and treatment. Patients can receive more personalized treatments for serious health conditions. Apache Ignite ships with a machine learning grid, as shown in Figure 4, with a range of machine learning algorithms that support both local and distributed processing. Since many machine learning models may need to be created and tested, the ability to use distributed processing and the power of the cluster enables more models to be evaluated, providing faster insights and saving time and resources.

Image title

Figure 4: Machine learning grid

Summary

Modern healthcare has many demanding requirements for the storage and querying of various types of data. Apache Ignite provides a range of capabilities that can meet these needs perfectly. In the next part of this blog series, we will see how a customer has been able to benefit from using Apache Ignite and GridGain for drug discovery.

Hortonworks Community Connection (HCC) is an online collaboration destination for developers, DevOps, customers and partners to get answers to questions, collaborate on technical articles and share code examples from GitHub.  Join the discussion.

Topics:
apache ignite ,healthcare ,fast data ,big data ,data analytics ,rdbms ,nosql ,scalability ,data grid ,tutorial

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}