Show HN: Memgraph – Transactional, in-memory, cypher-compatible graph database
1–10 of 48 posts
Re: Show HN: Memgraph – Transactional, in-memory, cypher-compatible graph database
#2Hey everyone, Memgraph CTO here. This is a massive milestone for us that took almost 3 years to reach and I would like to thank everyone who helped us get here! If you have any questions or feedback, I’ll be around all day to answer :D
Re: Show HN: Memgraph – Transactional, in-memory, cypher-compatible graph database
#3Congrats :)! How does this compare to Neo4J and what would be some typical use cases?
Re: Show HN: Memgraph – Transactional, in-memory, cypher-compatible graph database
#4Congrats :)! How does this compare to Neo4J and what would be some typical use cases?
Thank you! So, Memgraph is compatible with Cypher (http://www.opencypher.org) query language and Bolt protocol (https://boltprotocol.org) which means that existing tools and workloads will work. When it comes to the differences, because of our in-memory first approach, low-level implementation and optimizations Memgraph is more suitable for real-time analytical graph workloads. Please let me know if this makes sense or you would like to learn more about specific details. Out of curiosity, do you have an interesting real-time graph use-case?
Re: Show HN: Memgraph – Transactional, in-memory, cypher-compatible graph database
#5Can I use all NetworkX features and library functions from within memgraph, e.g. can I apply k_components to graph held within memgraph?
Re: Show HN: Memgraph – Transactional, in-memory, cypher-compatible graph database
#6Can I use all NetworkX features and library functions from within memgraph, e.g. can I apply k_components to graph held within memgraph?
Yes, Memgraph has an embedded Python interpreter so you can run any NetworkX graph algorithm or any other Python code. The code has access to the whole graph, so a bunch of options exists. The entire Python integration is still in the early days, and we have a bunch of plans on how to improve further. What Python libraries do you generally use?
Re: Show HN: Memgraph – Transactional, in-memory, cypher-compatible graph database
#7Would Memgraph be a good app to geolocate all of the data involved with a graph database?
Example: geolocate all of the electric distribution networks around the country7globe that interconnect with the values of the graph?
Re: Show HN: Memgraph – Transactional, in-memory, cypher-compatible graph database
#8Congrats :)! How does this compare to Neo4J and what would be some typical use cases?
Thank you! So, Memgraph is compatible with Cypher ( http://www.opencypher.org ) query language and Bolt protocol ( https://boltprotocol.org ) which means that existing tools and workloads will work. When it comes to the differences, because of our in-memory first approach, low-level implementation and optimizations Memgraph is more suitable for real-time analytical graph workloads. Please let me know if this makes se…
This looks awesome! How much Cypher does Memgraph support? Also, what are the difference compared with Neo4j's Cypher?
Re: Show HN: Memgraph – Transactional, in-memory, cypher-compatible graph database
#9Would Memgraph be a good app to geolocate all of the data involved with a graph database? Example: geolocate all of the electric distribution networks around the country7globe that interconnect with the values of the graph?
Karim from Memgraph here. Thanks for the questions. Are you referring to geospatial capabilities? If I understand correctly, you would like to add geospatial coordinates to specific elements in the graph (e.g. power stations, power lines etc) and be able to search and query for specific areas (e.g. countries, cities, etc)?
If that's the case, although we don't have direct support for Geospatial data format, you can easily encode it into your graph by setting coordinate as a property on your nodes and edges.
Does this answer your question?
Re: Show HN: Memgraph – Transactional, in-memory, cypher-compatible graph database
#10Earlier quoted context omitted.
Thank you! So, Memgraph is compatible with Cypher ( http://www.opencypher.org ) query language and Bolt protocol ( https://boltprotocol.org ) which means that existing tools and workloads will work. When it comes to the differences, because of our in-memory first approach, low-level implementation and optimizations Memgraph is more suitable for real-time analytical graph workloads. Please let me know if this makes se…
This looks awesome! How much Cypher does Memgraph support? Also, what are the difference compared with Neo4j's Cypher?
Memgraph supports more than 80% of openCypher TCK scenarios (https://github.com/opencypher/openCypher/tree/master/tck). For more details about the actual differences, please take a look here https://docs.memgraph.com/memgraph/reference-overview/differ.... The biggest difference is that Memgraph supports loading custom query modules implemented in almost any programming language and compiled into a dynamic library (.so file). Or, running query modules written as Python scripts.