You don't need to use a graph w/Neo4j - you can treat it like a standard document store, using the new-style schema indexes for lookups. Although, if that was all you were doing, I'd call a lot of things into question.
~A On Tue, Jun 24, 2014 at 10:47 PM, Clark Richey <[email protected]> wrote: > Any thoughts here? I too am interested to hear how people are storing > non-graph data like users. > > -------------------- > Clark Richey, CTO > FactGem > 240-252-7507 <//240-252-7507> > [email protected] > > > > > Need immediate assistance? Please try: > > Cate Downing, Assistant Beth Price, Assistant > [email protected] [email protected] > 614.325.2404 <//614.325.2404> 614.365.0740 > <//614.365.0740> > > This message and any included attachments are property of FactGem and > its affiliates, and are intended only for the addressee(s). The information > contained herein may include trade secrets or privileged or otherwise > confidential information. Unauthorized review, forwarding, printing, > copying, distributing, or using such information is strictly prohibited and > may be unlawful. If you received this message in error, or have reason to > believe you are not authorized to receive it, please promptly delete this > message and notify the sender by e-mail. Thank you. > > On June 24, 2014 at 10:24:03 AM, Alex Frieden ([email protected]) wrote: > > Well I actually DON'T want another database, was asking more how people > got around adding another infrastructure component/best practice for > implementing it in neo + node.js > > > On Tue, Jun 24, 2014 at 10:19 AM, Lasse Westh-Nielsen < > [email protected]> wrote: > >> 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. >> > > > > -- > Alexander Frieden > > -- > 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. > -- 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.
