Creating two special characters

How does electrical safety system work on ISS?

What (the heck) is a Super Worm Equinox Moon?

Why should universal income be universal?

What are some good ways to treat frozen vegetables such that they behave like fresh vegetables when stir frying them?

How much of a Devil Fruit must be consumed to gain the power?

How to convince somebody that he is fit for something else, but not this job?

How do I tell my boss that I'm quitting soon, especially given that a colleague just left this week

Is this toilet slogan correct usage of the English language?

What kind of floor tile is this?

Why does Carol not get rid of the Kree symbol on her suit when she changes its colours?

15% tax on $7.5k earnings. Is that right?

How to make money from a browser who sees 5 seconds into the future of any web page?

Why is the "ls" command showing permissions of files in a FAT32 partition?

Does "he squandered his car on drink" sound natural?

Review your own paper in Mathematics

What is the highest possible scrabble score for placing a single tile

Has the laser at Magurele, Romania reached a tenth of the Sun's power?

The Digit Triangles

Are Captain Marvel's powers affected by Thanos breaking the Tesseract and claiming the stone?

What's the name of the logical fallacy where a debater extends a statement far beyond the original statement to make it true?

Which was the first story featuring espers?

Mimic lecturing on blackboard, facing audience

What does "Scientists rise up against statistical significance" mean? (Comment in Nature)

MongoDB: Approach for storing frequently modified arrays

Best approach on storing/displaying sanitized dataBest Approach to storing chat history?Storing a music playlist, best approach?Approach to take regarding a field that is frequently re-computedstoring files on mongodbMongoDB storage of multi-dimensional arraysPreferred database solution for storing sensor dataMongoDB skipping 20 documents when storing in a variableBest approach for database designService Discovery for MongoDB

0

Need a piece of advice for storing a large number of references between Mongo entities that are frequently updated.

Some background:

• 1 event can have 100-1000 logs.


• 1 event can have 1-10 assets associated (assignment object).


• Logs are created per asset per event.


• Query pattern: find all logs by assignment (eventId and assetId).

Entities with their relations:

EVENT <-1--------------N-> LOG   

EVENT <-N--ASSIGNMENT--N-> ASSET

Mongo collections and documents:

event: { id, name, ... }

asset: { id, name, ... }

log: { id, eventId, metadata, ... }

assignment: { id, assetId, eventId, metadata, ... }

Here comes the question:

• What is the best way to store associations between logs and assignments (events and assets)? Note that those associations are updated frequently and concurrently.

Approach 1

Store logIds in assignment entity:

assignment: { id, assetId, eventId, logIds, ... }

Approach 2

Create a separate entity for holding a single reference between log and assignment:

assignmentLog: { assignmentId, logId }

---

Another approach ?

Any advice will be appreciated. Thanks.

database-design mongodb

share

asked 4 mins ago

Bogdan KobylynskyiBogdan Kobylynskyi

1011

New contributor

Bogdan Kobylynskyi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

0

Need a piece of advice for storing a large number of references between Mongo entities that are frequently updated.

Some background:

• 1 event can have 100-1000 logs.


• 1 event can have 1-10 assets associated (assignment object).


• Logs are created per asset per event.


• Query pattern: find all logs by assignment (eventId and assetId).

Entities with their relations:

EVENT <-1--------------N-> LOG   

EVENT <-N--ASSIGNMENT--N-> ASSET

Mongo collections and documents:

event: { id, name, ... }

asset: { id, name, ... }

log: { id, eventId, metadata, ... }

assignment: { id, assetId, eventId, metadata, ... }

Here comes the question:

• What is the best way to store associations between logs and assignments (events and assets)? Note that those associations are updated frequently and concurrently.

Approach 1

Store logIds in assignment entity:

assignment: { id, assetId, eventId, logIds, ... }

Approach 2

Create a separate entity for holding a single reference between log and assignment:

assignmentLog: { assignmentId, logId }

---

Another approach ?

Any advice will be appreciated. Thanks.

database-design mongodb

share

asked 4 mins ago

Bogdan KobylynskyiBogdan Kobylynskyi

1011

New contributor

Bogdan Kobylynskyi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

Need a piece of advice for storing a large number of references between Mongo entities that are frequently updated.

Some background:

• 1 event can have 100-1000 logs.


• 1 event can have 1-10 assets associated (assignment object).


• Logs are created per asset per event.


• Query pattern: find all logs by assignment (eventId and assetId).

Entities with their relations:

EVENT <-1--------------N-> LOG   

EVENT <-N--ASSIGNMENT--N-> ASSET

Mongo collections and documents:

event: { id, name, ... }

asset: { id, name, ... }

log: { id, eventId, metadata, ... }

assignment: { id, assetId, eventId, metadata, ... }

Here comes the question:

• What is the best way to store associations between logs and assignments (events and assets)? Note that those associations are updated frequently and concurrently.

Approach 1

Store logIds in assignment entity:

assignment: { id, assetId, eventId, logIds, ... }

Approach 2

Create a separate entity for holding a single reference between log and assignment:

assignmentLog: { assignmentId, logId }

---

Another approach ?

Any advice will be appreciated. Thanks.

database-design mongodb

share

asked 4 mins ago

Bogdan KobylynskyiBogdan Kobylynskyi

1011

New contributor

Bogdan Kobylynskyi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

EVENT <-1--------------N-> LOG   

EVENT <-N--ASSIGNMENT--N-> ASSET

event: { id, name, ... }

asset: { id, name, ... }

log: { id, eventId, metadata, ... }

assignment: { id, assetId, eventId, metadata, ... }

assignment: { id, assetId, eventId, logIds, ... }

assignmentLog: { assignmentId, logId }

share

asked 4 mins ago

Bogdan KobylynskyiBogdan Kobylynskyi

1011

New contributor

Bogdan Kobylynskyi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share

asked 4 mins ago

Bogdan KobylynskyiBogdan Kobylynskyi

1011

New contributor

Bogdan Kobylynskyi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 4 mins ago

Bogdan KobylynskyiBogdan Kobylynskyi

1011

New contributor

Bogdan Kobylynskyi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 4 mins ago

Bogdan KobylynskyiBogdan Kobylynskyi

1011