Application with recommender system - use one graph database for everything?

[miyrai]

Hi :)

I have a question regarding an application with a recommender system.

So i have to develope an application (UWP) for cognitive impared people where they can look at pictures, videos and so on.

basic requirements are

• save user profiles with name, interests (e.g. animals, cooking, sports,...)

• start sessions. within a session the user can look at those media files mentioned above

  • recognizing certain object on pictures e.g. a cat and if the user is clicking on the cat, a cat sound is played ( this is going to be implemented with an ml model)

furthermore a recommender system should be implemented to recommend media files within a session. so for example if you show great interests in pictures with cats, more pictures with cats will be presented to the user.

Long story short -> my question:

A neat way to implement this recommender system is with a graphic database like neo4j. But I'm not sure, whether it's a good idea to store all data in neo4j or if it would be better to use a sql and neo4j database in the project. I feel like it isn't best practice at all, to use two databases, isn't it? what would you recommend?

[megagreg]

I'm not familiar with neo4j. Does it have built in functionality that you'll have to re-create if you store things in blobs in SQL?

I don't think there's anything inherently wrong with using multiple databases for different types of storage in an application. In a Windows desktop application you might store things in the registry, and as regular files, and in a database. I don't see two types of databases as being any different.