Lucene + Joins == RDBMS?

Now that Lucene supports joins (at indexing time and at querying time) can one use Lucene as a databse (a NoSQL one, with Eventual Consistency)?

Lucene + Joins == RDBMS?

Now that Lucene supports joins (at indexing time and at querying time) can one use Lucene as a databse (a NoSQL one, with Eventual Consistency)?

Lucene + Joins == RDBMS?

Now that Lucene supports joins (at indexing time and at querying time) can one use Lucene as a databse (a NoSQL one, with Eventual Consistency)?

Nested Entities and calculation on leaf entity property – SQL or NoSQL approach

I am working on a hobby project called Menu/Recipe Management.

Nested Entities and calculation on leaf entity property – SQL or NoSQL approach

I am working on a hobby project called Menu/Recipe Management.

Nested Entities and calculation on leaf entity property – SQL or NoSQL approach

I am working on a hobby project called Menu/Recipe Management.

Nested Entities and calculation on leaf entity property – SQL or NoSQL approach

I am working on a hobby project called Menu/Recipe Management.

Nested Entities and calculation on leaf entity property – SQL or NoSQL approach

I am working on a hobby project called Menu/Recipe Management.

Would a model like this translate well to a document or graph database?

I’m trying to understand what types of models that I have traditionally persisted relationally would translate well to some kind of NoSQL database. Suppose I have a model with the following relationships:

Would a model like this translate well to a document or graph database?

I’m trying to understand what types of models that I have traditionally persisted relationally would translate well to some kind of NoSQL database. Suppose I have a model with the following relationships: