Book Image

Architecting Data-Intensive Applications

By : Anuj Kumar
Book Image

Architecting Data-Intensive Applications

By: Anuj Kumar

Overview of this book

<p>Are you an architect or a developer who looks at your own applications gingerly while browsing through Facebook and applauding it silently for its data-intensive, yet ?uent and efficient, behaviour? This book is your gateway to build smart data-intensive systems by incorporating the core data-intensive architectural principles, patterns, and techniques directly into your application architecture.</p> <p>This book starts by taking you through the primary design challenges involved with architecting data-intensive applications. You will learn how to implement data curation and data dissemination, depending on the volume of your data. You will then implement your application architecture one step at a time. You will get to grips with implementing the correct message delivery protocols and creating a data layer that doesn’t fail when running high traffic. This book will show you how you can divide your application into layers, each of which adheres to the single responsibility principle. By the end of this book, you will learn to streamline your thoughts and make the right choice in terms of technologies and architectural principles based on the problem at hand.</p>
Table of Contents (18 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Graph stores


So far, we've talked about storing data in a columnar store and looked at HBase as an example of a columnar store. But there are use cases, which are increasing by the day, that require data to be connected in order to find relationships between them.

We will be discussing two types of stores that are most prevalent in the market these days:

  • Property graph stores
  • Semantic graph databases (RDF Stores or TripleStores)

One of the key characteristics of both these types of Graph Stores is that they are designed to store linked data.

But before we go deeper into the difference between different types of Graph Stores, let’s look at a Use Case for using a Graph Store.

We will take an example of Bank Fraud and look at how Graph Databases can help detect and prevent fraud in the bank. This example is taken and adopted from Neo4j Blogs.

Background of the use case

 Millions of dollars are lost in banking and insurance institutions due to fraud. Traditional methods of fraud-detection are no longer...