Thanks Benjamin.
I can now connect on what you explained about schema.
Schema less is in terms of a Node and i [wrongly] assumed it for the Graph.
Now coming to application architecture problem.
as we know that we cannot freeze our architecture due to ever changing
requirements, what we can do to
That is a problem in your applications architecture. If you use MySQL and
have a on-to-many relation between A and B, and now you need to store an
entity C between A and B, you've got to alter the schema and run an update
on all entries.
(if you can tell us a solution that works in SQL, than the
I am still confused with *schema-less nature.*
As as can see it, still Neo4j gives us tightly coupled architecture.
Imagine the Graph grows big as the project progresses and one day we got
a new requirement which makes us to introduce new node between existing
structure.
Now this will
Truth spoken. Couldn't agree more with you.
On Monday, June 4, 2012 10:22:31 AM UTC-4, Johnny Weng Luu wrote:
>
> I personally think that all kind of data should/could be saved in a graph
> database.
>
> The world is one big graph and data is usually representing real world
> entities.
>
> Johnn
