Exploring Graphs with Elixir

Defining a Graph Service API

Now let’s look at querying graphs.

The graph databases we’ll look at have web interfaces and support CRUD operations^[3] on graphs in their own graph stores. They all have their own APIs and data representations, which can be a bit of a burden when switching between these services.

Let’s define a common interface for these graph services. We can use the OTP behaviour pattern to define a set of callbacks which will be implemented by any module that adopts this behaviour. This allows us to define a graph service contract—an API.

We’re looking to create a simple interface with the following operations:

• graph_create/1
• graph_read/0
• graph_update/1
• graph_delete/0

And to these we’ll add an optional callback if supported by ...