MongoDB

MongoDB is a place to keep your data, and what makes it different is the shape. Most databases work like a spreadsheet, where every row has the same columns and must fill them in. MongoDB keeps each record on its own instead, in a small block called a document that carries only the fields it needs.

A product catalogue shows why that matters, because a shoe has a size and a colour while a laptop has a processor and a screen size. A bag of coffee shares neither, since what it needs is a roast date. Push all three into one table and you get dozens of columns that sit empty for almost every product, which is the mess MongoDB avoids. There the shoe stores shoe things and the laptop stores laptop things.

That freedom has a price, and it is the part nobody warns you about. Nothing stops two records from disagreeing, so one product saves its price as the number 100 while the next saves it as the text "100". Both go in without a complaint. Then somebody sorts the catalogue by price and the list comes out wrong, because text is compared letter by letter, so "100" lands before "9". The rules have not disappeared. They only moved into the software your team writes, which is more work rather than less. That is why Linkysoft agrees those rules on day one of a web application project, because fixing a million old records later is a bad week.

So MongoDB fits when the records really are different, such as product catalogues, form answers, activity logs and anything whose shape changes with the business. It fits badly where the data is tidy and the sums must be exact, which is why a table database is safer for invoices and payments. Plenty of systems therefore run both. A shop system such as Storek carries the catalogue that keeps changing shape beside the money that must never round wrong.

Ask any supplier one question before you sign, which is what happens when a field changes meaning next year. If the answer is that they just write a new field, ask who fixes the old records. Then ask the same about the phone, because a mobile app that works offline keeps documents on the handset for days. Some of those handsets still run last year's version, so Linkysoft treats this as a design question, not a database one. The answer usually decides whether the second year is calm or painful.