“A 图表数据库——转换成一个或一个“;RDBMS”
新4j站点似乎暗示,无论在RDBMS中你能做什么,你都可以在新4j做。
在选择“新南”为“新南”之前,我需要回答一些疑虑。
我对新奇感兴趣。
- ability to do quickly modify data "schema"
- ability to express entities naturally instead of relations and normalizations
- ...which leads to highly expressive code (better than ORM)
这是我对其特征感兴趣的诺塞克解决办法,而不是高业绩。
Question: Does Neo4j present any issues that may make it unsuitable as a RDBMS replacement?
我特别关切的是:
- is there any DB feature I must implement in application logic? (For example, you must implement joins at application layer for a few NoSQL DBs)
- Are the fields "indexed" to allow a lookup faster than O(n)?
- How do I handle hot backups and replication?
- any issues with "altering" schema or letting entities with different versions of the schema living together?