[As community content, this post reflects the views and opinions of the particular author and does not necessarily reflect the official stance of Neo4j.]
Over the past few years, Neo4j has become the standard for efficiently modeling graph-based data.
In addition, the use of Node.js in building flexible service infrastructures on top of Neo4j graph databases and serving the necessary HTML and static resources enables developers to build great applications.
As with other technologies, the data model and service design predetermines how well your application performs in production. But what if you’re already running your application in production and you realize that in some cases it’s running slowly?
In this post I’ll explain how to monitor a sample Node.js application using an underlying graph data model residing in a Neo4j database in real time.