Putting it All Together : a Technology Stack on top of a (Neo4j) Graph Database The above technology stack is explained in this short video . (UPDATED Mar. 2024) For many practical use cases, one needs a full data-management solution, not just a database. So, armed with the Schema Layer discussed in the previous part , the next natural step is to add an API and possibly a UI . This article is part 6 of a growing, ongoing series on Graph Databases and Neo4j The API Layer / Data Manager The API Layer ("Data Manager") is in some ways the most straightforward layer - because the "heavy lifting" is done by the Schema Layer. I've been involved in projects that utilized an inadequate Schema Layer - and in those situations the API Layer ends up taking on an immense amount of responsibility that don't logically belong there; the end result being a lot of difficult, error-prone and non-modular development that feels like "pulling teeth"! By co