18

Graph Data Platforms: A Brief Introduction

 4 years ago
source link: https://neo4j.com/blog/graph-data-platforms-a-brief-introduction/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

(Neo4j Blog)←[:BACK]

Graph Data Platforms: A Brief Introduction

Dave Packer, Vice President, Product Marketing Dec 21 < 1 min read


You may have heard that graph database technology underpins the latest in machine learning and AI. But what are graph data platforms and why are they rapidly becoming the first choice for application development? Can a shift in database technology really make a big difference?

In this first blog of our two-part series on graph data platforms, we discuss what graphs are good for and explore several graph use cases.
Graph Data Platforms

Relational databases dominate the market with their ability to store structured data in tabular models. While relational databases have their place, their rigid structures fail to adapt easily to the complexity of data, its context and its interconnections.

Relational databases are simply the wrong tool for many new business challenges. Real-time recommendations rely on connected data; in the relational world, this requires linking many tables. Relational databases strain under that load while users wait impatiently.

In the past decade alone, the data landscape has shifted significantly. Perhaps it’s time to consider new ways of tackling the evolving data landscape and how it’s managed.

What Are Graph Databases Good For?

Graph database technology is specifically designed and optimized for highly interconnected datasets to identify patterns and hidden connections.

Graph data stores are intuitive because they mirror the way the human brain thinks and maps associations via neurons (nodes) and synapses (relationships).

A graph database efficiently stores and queries connected data in a node-and-relationships format. As a result, graph technology excels at problems where there is no a priori knowledge of path length or shape by using graph storage and infrastructure to find neighboring data efficiently.

The most common graph use cases and solutions include:
  • Fraud Detection & Analytics: Real-time analysis of data relationships is essential to uncovering fraud rings and other sophisticated scams.
  • Artificial Intelligence & Machine Learning: Artificial intelligence (AI) winners and losers will be decided based on who harnesses context within data for a true competitive advantage.
  • Real-Time Recommendation Engines: Graph-powered recommendation engines help companies personalize products, content and services by building a contextualized map of offers using both historical and real-time data.
  • Knowledge Graphs: Connecting everything you know is half the battle. Knowledge graphs tap into your organization’s institutional memory. Moreover, knowledge graphs are the basis for many natural language processing (NLP) and AI solutions.
  • Network & Database Infrastructure Monitoring: Graph databases are inherently more suitable than RDBMS for making sense of complex interdependencies central to managing networks, data centers, cybersecurity and IT infrastructure.
  • Master Data Management (MDM): The schema-optional graph database model allows you to organize and manage your master data with flexibility. It also lets you harness real–time insights and a 360° view of your customers, products and employees.

What these use cases have in common is that their success requires solving complex problems with dynamic and interconnected datasets. To this end, we should reframe the question, “What are graph databases good for?” as a technical one.

Viewed through a technological lens, graph databases tackle the most harrowing of data problems – ones that often linger at the root of project failures and delays. These include:

  • Vastly different views of the data model between business and technology teams, which result in misunderstanding and miscommunication.
  • Lack of schema flexibility and adaptability, making it hard to respond to changing business requirements both during a project and after a system has gone live.
  • The “JOIN problem” which occurs when queries become so tangled that even powerful databases with massive amounts of hardware resources grind to a halt in their attempts to bring the resulting data together.

With the right choice of technologies, graph databases introduce a new way of looking at data by promising to significantly address all of these issues. They seek to take you beyond handling sheer volumes of relatively simple data and towards revealing the interconnected complexities latent in your data – and deriving bottom-line value from them.

Traditional Technology Choices Do Not Consider How Data Is Interrelated

Today’s data and applications require elasticity, agility, speed and interconnectivity. Despite the name, relational databases are not well-suited for modeling and storing today’s highly connected and agile datasets. RDBMS demand slow and expensive schema redesigns that hurt agile software development processes and hinder your ability to scale and innovate quickly.

Traditional RDBMS technology has a difficult time expressing and revealing how real and virtual entities are related. Columns and rows aren’t how data exists in the real world. Rather, data exists as rich objects and the relationships between those different objects.

Graph-Database-Depiction.png

The theory of connected networks (graph theory) has been a mathematical discipline for nearly three centuries, but few technologies have harnessed these theoretical models for the purpose of data storage and analysis.

Early on, a handful of companies have truly tapped into the power of graph technology as the driver of their businesses, including Google, Facebook, LinkedIn and Microsoft as well as upstarts like Airbnb and Uber. Well-established entities such as NASA, eBay, UBS and many of their peers use graph technology to improve their customer experiences and increase their competitiveness.

Today, graph-powered applications are used by more than 75% of the Fortune 500, including:

  • 7 of the world’s top 10 retailers
  • 3 of the top 5 aircraft manufacturers
  • 8 of the top 10 insurance companies
  • All of North America’s top 20 banks
  • 8 of the top 10 automakers
  • 3 of the world’s top 5 hotels
  • 7 of the top 10 telcos

These successes serve as a strong indicator of graph technology’s impact on both innovation and the bottom line.

Conclusion

As we have shown, graph database technology is specifically designed and optimized for highly interconnected datasets to identify patterns and hidden connections. Next week, in the conclusion of this two-part series, we will explain how graph data platforms work and what that will mean for you.


Recommend

  • 44
    • www.tuicool.com 5 years ago
    • Cache

    A Brief Introduction To F#

    F# is a strongly-typed so-called general purpose programming language running on the .NET platform. Unless other popular .NET languages such as C#, it explicitly favors a functional-first programming style. F# has...

  • 16

    GPT-3 101: a brief introduction It has been almost impossible to avoid the GPT-3 hype in the last weeks. This article offers a quick introduction to its architecture, use cases already available, as well as some...

  • 9
    • blog.erlang.org 4 years ago
    • Cache

    A brief introduction to BEAM

    A brief introduction to BEAM October 20, 2020 · by John Högberg . This post is a brief primer on BEAM, the virtual machine that executes user code in the Erlang Runtime System (ERTS). It’s intended...

  • 12
    • cuda-chen.github.io 4 years ago
    • Cache

    Brief Introduction of miniSEED and libmseed

    Brief Introduction of miniSEED and libmseed Feb 10, 2020 I am working on a project about seismic wave analysis these days. For reading data containing seismic waves, it comes up to several forma...

  • 9
    • codingadventures.me 4 years ago
    • Cache

    A Brief Introduction to Docker

    A Brief Introduction to Docker ~ Coding AdventuresSkip to main content

  • 15

    A Brief Introduction to Probability & Statistics I've studied probability and statistics without experiencing them. What's the difference? What are they trying to do? This analogy helped: Probability

  • 3
    • ryanschultz.com 4 years ago
    • Cache

    Jel: A Brief Introduction

    Jel: A Brief Introduction Jel (which bills itself “the un-Zoom...

  • 8

    (Neo4j Blog)←[:BACK] Graph Data Platforms: Collections vs. Connections Dave Packer,...

  • 11

    A Brief Introduction for sudo alternatives -- doas and polkit Mar 1, 2021 Introduction sudo is a commonly used linux command which grants a command with root permission tem...

  • 20

    Introduction to the Graph Data Structure It is time for us to learn about the Graph data structure. This particular data structure is used in so many applications and has so much going for it, an entire field of study exis...

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK