Code Monkey Speaketh.
I would like to introduce an open source, Apache 2.0 licensed project of mine: https://github.com/CivicGraph/CivicGraph
CivicGraph is a versioned-graph data store - it retains all changes that its data (vertices and edges) have gone through to reach their current state. It supports point-in-time graph traversals,
In their 1996 paper published in ACM Transactions on Database Systems, Ghandeharizadeh et al. defined a formal algebra around Deltas[1] in a relational database. Their definition is actually generic enough to apply to any system whose state can be represented as a set of tuples, which is why it
Building on my previous post, where I emphasize the need for versioned graph databases, I explore a few of the possible approaches to designing one. This is not a ground-up approach that delves into the design of the database engine itself, but rather an overlay approach that can let us
Graph databases have become ubiquitous over the years due to their incredible representational and querying capabilities, when it comes to highly interconnected data. Wherever data has an inherent networked structure, graph databases fare better at storing and querying that data than other NoSQL databases as well as
I had previously written on how I fell in love with Node.js. Apart from the core docs, it was primarily the wonderful online tutorials that showed me the way when I was a complete newbie.
And so, for those who wish to take Node.js for a test ride,