title: Neo4j/Graph DBS Performance for Rapidly Updated/Changing Nodes/Relations
body: <p>I'm currently in the early processes of evaluating and building a recommendation engine for a project I'm working on. I currently have data stored in Redshift and I was considering using using Neo4j to build my engine. However due to the nature of my project requiring essentially realtime updates and deletion of nodes and relationships I am concerned about about losing performance over time. Essentially a new product will only last up for a an hour or so before being removed and in order for it to scale will require new nodes (products) to be created, new relations (users who viewed product), and just a quickly for these to be deleted as they are no longer online.</p>
  
  <p>Any thoughts on the applicability of neo4j/Graph DBs for this would be much appreciative. </p>