# Thinking With Graphs

Go to any other vendor, read any other discussion on graph stores and you'll be told that working with a large graph is all about *traversals*. You need to "think like a vertex", they'll say.

Sure, this works for large graphs, but only if they're simple. Working with complex graph structures this way will make your head explode. This is a serious shortcoming - because complex structures are where a Graph Database is most useful.

When you work with ** GraphBase**, you work with

**graphs**. GraphBase stores data as one large

**graph**. Data is delivered to GraphBase as small

**graphs**, a query to GraphBase returns data as a

**graph**and the smallest transactional unit is a

**graph**.

Even at the application level, it often makes sense to work with graphs, rather than objects. A graph can carry much richer information about the chunk of data you're working with.

GraphBase graph-manipulation tools also mean that data in graph form can be manipulated with dramatically-less code than is required for objects, "rows" and other traditional application data structures.

You can, for example, ** and()** your graphs. Or you can turn them into a list of objects with a single method. Take a quick look at the

**Java API**to see just now much simpler working with graphs can be.

Oh, and you can ditch that bloated ORM or other mapping layer - it's no longer required.