On 11/22/24 1:52 AM, Roger Oberholtzer wrote:
I see I left out the link to the place that has made installing MongoDB a requirement for me:
That was what the next bit was about. There are literally millions of openly available images with feature annotations available.
I ran across it as a dependency to eGroupWare which now "incorporates" RocketChat and a couple of other components that rely on mongodb. I've since run across a mongo dependency in another handful of web-apps. I see where it makes sense for things like chat or log messages (that many apps log in json). With a noSQL database, you don't need to know or validate the fields, just add another document. Then from the query side, you just query the fields you are interested in, and if a document contains a match, it's returned, even though there may be another 1/2 of the documents that don't even have the queried field. It's not a problem, they are just simply not returned. So instead of all records in a table in SQL having to have the identical fields (columns) and be apples-to-apples type records, in noSQL you can have apples, bananas, grapefruits and double-decker busses in the same collection. While the learning curve is as broad for both types of databases, it's not nearly as steep to get started storing things in noSQL. Once you can store one document, you can store them all without having to tailor code for each new collection. It's like a database-light approach. -- David C. Rankin, J.D.,P.E.