Thoughts from the Wet Coast
The musings of an ASP.NET Developer from Canada's We(s)t Coast
In 1736 Leonhard Euler established the foundations of Graph Theory the basis of Graph databases when he was challenged by the citizens of Konigsberg to solve a problem with the layout of their city.
I have had an interest in Graph databases for a while. In fact, a couple of years ago I presented a session on Graph Databases and Neo4j in particular at the DNN Con conference held in West Palm Beach. Graph Databases fill an important place in the array of Database options, both relational (SQL) and non-relational (NoSQL), available to us as developers. But what are Graph Databases? And what are the Graph Database implementations available to us. In this series of blog posts I will explore these topics in some detail and I invite you to join me as I learn about this important topic in the age of Social Media.
In my investigation of the Neo4j database I will now turn my attention to the Neo4j browser.
Once Neo4j is installed there will be a small executable that can be used to start the Neo4j database server.
In this blog post I am going to return to my investigation of the graph database Neo4j. So far I have done a brief introduction to Neo 4j and I have shown how easy it is to install Neo 4j in an Azure VM.
Over the last couple of years I have been trying to get a handle on the “new” database technologies lumped together under the NoSQL banner. In that respect I have posted several articles to this blog.
More recently my focus has shifted from looking at NoSQL databases as a group to diving in deeper to a few select “NoSQL” databases. The one that intrigues me most is Neo4j – a graph database.
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.