-1

We are planning to migrate Data from AuroraDB to AWS neptune (property Graph). we have table in AuroraDB with 3.5 million records, and which has relationship with other five tables. if I have to create all the records as Vertices result in 3.5 million vertices and it has relationship with other five table, each record will have 5 Edges for 5 other tables, then the edges will result in 3.5 million (records in one table ) * 5 (each records have relationship with other 5 tables) results in above 10 million.

How we can reduce this Edges and is there anything i am doing wrong?

James Z
  • 12,209
  • 10
  • 24
  • 44
Harish
  • 11
  • 3
  • 1
    People living outside India aren't going to understand what are lakhs and crores. Please don't use Indian words here. – James Z Sep 01 '21 at 14:01
  • Please clarify your specific problem or provide additional details to highlight exactly what you need. As it's currently written, it's hard to tell exactly what you're asking. – Community Sep 06 '21 at 07:24
  • I got the response from Kevin and it is acceptable – Harish Sep 06 '21 at 07:50
  • Please mark the answer as accepted in that case so others can see there is an accepted answer. Many thanks. – Kelvin Lawrence Sep 14 '21 at 23:49

1 Answers1

2

In general it is reasonable to consider a row in a relational table as a vertex in a graph where each column becomes a property. It is likewise reasonable to consider converting what would be joins in the relational model to edges in the graph model. A graph with 3.5 million vertices and ~10 million edges is not that big, so in terms of size nothing of concern. However, data modelling generally works best if the approach is not just to mirror the exact relational model as a graph but rather to consider the types of questions (queries) you need to the graph to answer. It may be that changes to the data model will make that easier and more efficient. Without knowing more about the exact use case and questions you need the graph to answer that is about the best advice I can offer.

Kelvin Lawrence
  • 14,674
  • 2
  • 16
  • 38