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

Roles


The following are the roles in Neo4j:

  • No role
  • Reader
  • Editor
  • Publisher
  • Architect
  • Admin

They are ordered by ascending possibilities, with admin being the most powerful. When created, users have no role, then an admin grants authorization level via roles.

The possibilities for each role are ascending and are based on those of the previous role. Let's browse the possibilities of each role:

  • No role: This is the default role. It allows you to change one's password and see one's details. It doesn't allow much, and will make users sing, don't leave me this way.
  • Reader: A reader can read the whole graph.
  • Editor: An editor can read and modify the existing data for the whole graph. An editor can create new nodes with existing labels and existing properties, and new relations with existing names.
  • Publisher: A publisher can create new nodes, new labels, and new relations.
  • Architect: An architect has control over the indexes of the graph and over the constraints (CREATE and DROP).
  • Admin: An admin can also create...