I think from what you describe, you don't need a RDBMS. That is usually only needed in
1. existing systems that are already built on an RDBMS that are used from multiple applications and reporting systems 2. huge amounts of read-only properties, including BLOB/CLOB 3. loads of reporting queries that only run aggregations of the data Michael On Tue, Aug 28, 2018 at 12:15 AM, Kim Prince <k...@kimprince.com> wrote: > I am planning to build an application which relies heavily on a directed > graph (similar to a social graph). > > There is no doubt that Neo4j will be required, but I'm having trouble > deciding if I will also require an RDBMS. Is there an easy way for me to > get a feel for this, other than just building the thing with Neo4j, and > introducing the RDBMS if/when I reach a choke point? > > Some details of the planned application are as follows: > > - Designed for 10's of thousands of users, if not 100's of thousands > - Business logic implemented using MVC (Laravel) > - Some mobile traffic, some desktop, access via an API > - Most DB activity will be reading from the graph > - Not a lot of reporting required > > There will be around 8 types of entities that I will definitely implement > as node types. The primary focus of the application is the relationships > between these nodes. If I incorporate an RDBMS, it will require around 30 > tables for the remaining entities and their relationships. > > Any advice? > > -- > 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 neo4j+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Join our new Community Site & Forum <https://community.neo4j.com> -- 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 neo4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
