Optimizing to the extreme

Thursday 04.05.2017

We are currently transitioning from a combination of a MongoDB and a Elastic Seach into using Neo4J. This allows us to look up data with reations in a faster fashion than we have been able to do earlier.

As part of this transition, we needed to implement several plugins for use with Neo4J, to compenasate for missing functionality. One of these plugins ws a recommendation plugin. As can be seen from the screenshot below, there are a lot that can be done with a little bit of optimization. One call went from 2917ms to sub 1ms. This result is representative for how a few changes often results in large changes when fetching data from Neo4J.