Graph databases store data as nodes, properties and relations. If I need to retrieve some specific data from an object based upon a query, then I would need to retrieve multiple objects (as the query might have a lot of results).
Consider this simple scenario in object oriented programming in graph-databases:
I have a (graph) database of users, where each user is stored as an object. I need to retrieve a list of users living in a specific place (the place property is stored in the user object). So, how would I do it? I mean unnecessary data will be retrieved every time I need to do something (in this case, the entire user object might need to be retrieved). Isn’t functional programming better in graph databases?
This example is just a simple analogy of the above stated question that came to my mind. Don’t take it as a benchmark. So, the question remains, How great is object oriented programming in graph-databases?
Each node has attributes that can be mapped to object fields. You can do that manually, or you can use spring-data to do the mapping.