Book Image

Learning Neo4j 3.x - Second Edition

By : Jerome Baton
Book Image

Learning Neo4j 3.x - Second Edition

By: Jerome Baton

Overview of this book

Neo4j is a graph database that allows traversing huge amounts of data with ease. This book aims at quickly getting you started with the popular graph database Neo4j. Starting with a brief introduction to graph theory, this book will show you the advantages of using graph databases along with data modeling techniques for graph databases. You'll gain practical hands-on experience with commonly used and lesser known features for updating graph store with Neo4j's Cypher query language. Furthermore, you'll also learn to create awesome procedures using APOC and extend Neo4j's functionality, enabling integration, algorithmic analysis, and other advanced spatial operation capabilities on data. Through the course of the book you will come across implementation examples on the latest updates in Neo4j, such as in-graph indexes, scaling, performance improvements, visualization, data refactoring techniques, security enhancements, and much more. By the end of the book, you'll have gained the skills to design and implement modern spatial applications, from graphing data to unraveling business capabilities with the help of real-world use cases.
Table of Contents (24 chapters)
Title Page
Credits
About the Authors
Acknowledgement
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Summary


This chapter taught us why and how to create a Neo4j cluster with different kinds of servers. After the concepts, we saw how to build a cluster. We also saw the magic of the bolt+routing protocol.

You learned that we can grow from a cluster of several credit card-sized computers like Raspberry Pis (https://www.raspberrypi.org/) to a cluster made from several clouds (you'll need a strong credit card for that).

We also saw a disaster recovery procedure to which I'll add this tip:

Note

With any software, disaster recovery must always be team work. Otherwise, it is too easy to put the blame on one person because non-tech people need to act as inactivity makes them feel 'not in power' and blaming is so easy, as they believe failure should not have had happened first. No matter Murphy's law. If you are the one who understood what failed and how to solve the issue, and get the blame anyway instead the credit: change of shop. I saw firsthand that a client lost their best sysadmin as he got bored...