Show HN: Memgraph – Transactional, in-memory, cypher-compatible graph database

Post by anualvis » Thu, May 14, 2020, 6:05 AM UTC

houzi wrote: post #40

micheldiz wrote: post #36

Earlier quoted context omitted.

Hi guys, I'm community support at Dgraph. Reading that question. I come to clarify some points. First of all, I don't particularly know Memgraph internally. So, I'll stick to Dgraph and related only. About Karimtr's reply 1. The graph model: Although Dgraph uses RDF as input data. Dgraph is not a Triple Store per se - and the RDF we have is a customized version, which means that it is not 100% compatible with any RDF…

I really like dgraph. Even amidst some rapid development for graphql integration, dev team has been quick to respond to issues. Was happy to see the continued Jepsen testing. Now that the frontend devs have gotten their attention, I hope dgraph plans to give the python community some love as well by improving the client API and asyncio support and even full integration with networkx.

Post by M_jolnir » Thu, May 14, 2020, 8:34 AM UTC

karimtr wrote: post #9

M_jolnir wrote: post #7

Would 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 e…

Post by zvone » Thu, May 14, 2020, 11:05 PM UTC

Post by greenrobot » Fri, May 15, 2020, 7:21 AM UTC

dtomicevic wrote: post #24

VRomanov89 wrote: post #19

How do you handle high-availability? Also, do you have some sort of persistency model for the community version which doesn't have HA?

Dominik from Memgraph here. Good questions! All editions of Memgraph persist data to the disk via write-ahead logging (WAL) and periodic snapshots for log compaction so even though Memgraph is designed to be in-memory first, data is always backed up to disk. If you enable asynchronous (periodic fsync) WAL, you can trade off a small window of durability for better performance. Before 1.0, Memgraph leveraged the RAFT c…