In my previous career I worked for a while at a large UK-based media conglomerate, doing some social/ nosql stuff. Noone one my team would have dreamed of using a "proper" database for any of the stuff we did until the subject of authentication came up, and they all started saying things like "well, for username/ password we are going to need a structured, schema'ed database", in their most grown-up voices. To which my reply was, why the frack would we introduce another infrastructure component just for that. It was just another nail in the coffin as my contempt for them grew...
But anyway, I'll ask you the same: why? - Lasse PS: these are the same jokers that said we shouldn't rely on HTTPS in the cloud because uri and headers are sent in plaintext... On Tue, Jun 24, 2014 at 4:07 PM, Alex Frieden <[email protected]> wrote: > I currently have an app in node.js with neo4j under the hood. I would > like to allow users to log in. What have people done in the past? Use an > additional database? Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
