6 ms·
It adds complexity to a narrow use case. If it wouldn't be narrow neo4j wouldn't need to lay off stuff. Your examples do not refute this
by Delemono 4y ago
It adds complexity to a narrow use case.
If it wouldn't be narrow neo4j wouldn't need to lay off stuff.
Your examples do not refute this
- inkyoto 4y ago> It adds complexity to a narrow use case. It also simplifies the unnecessary complexity in many cases, and I have witnessed both. Just like one should not use an expensive Zeiss microscope to hammer nails into a concrete wall as a hammer substitute, one perhaps ought not to stick a graph database everywhere where it does not belong. Engineering (including software) is about selecting the appropriate tooling for each job. > If it wouldn't be narrow neo4j wouldn't need to lay off stuff. I fail to see how the two are related. If a company struggles with the execution of their incumbent business model, perhaps it is not necessarily related to the product (may or may not be though)?