How to implement this correctly in mongo?

Question

Iron

for example, there are users and there are coordinates. if I implemented it on a relational database, it would be 2 tables, mongo offers the idea of ​​storing coordinates directly in user. but as far as I read from this, there may be problems described here habrahabr.ru/post/231213
what are the disadvantages of storing "the old fashioned way" in two collections without nesting and fetching this with two consecutive queries?

Answer 1

If there is no HDD, definitely - 250GB
If there is an HDD, 120 may well be enough.

4gb ram

It would also be nice to add at least 4gb

Initially I looked at SAMSUNG 850 MZ-7LN120BW 120GB, but now I'm considering WD Blue WDS250G2B0A 250GB. The latter has better characteristics, although it is smaller.

Of course, the first one is better, but the second one will also work for a laptop, you won’t see much difference there.

Answer 2

SSD drive INTEL 545s Series SSDSC2KW256G8X1 256GB, 2.5", SATA III [ssdsc2kw256g8x1 958660] ~5500r
The most reliable device among all SSDs.

Answer 3

anyone
with a lower price
and a longer warranty (there is a year, there are three
for system 120, there is enough eye
for ssd file cleaning

Answer 4

You are facing a typical decomposition problem in nosql. It is necessary to decide depending on how this data will eventually be used. If you end up pulling out the entire collection often, then it makes sense to put all the data in users (if the data is not more than 16MB per document).