MongoDB

MongoDB's unmatched flexibility and scalability are what I liked best about it. MongoDB has changed the game for me as someone who deals with continually evolving data formats and requirements. The document-based architecture enables me to store data in a manner that closely resembles the entities and connections seen in the real world, making it highly intuitive and simple to use. The dynamic schema gives me the flexibility I need to iterate quickly by allowing me to modify and develop my data model without being constrained. MongoDB's extraordinary capacity to scale has proven invaluable in helping me manage increasing data volumes and high-performance applications with ease. With MongoDB, I have the flexibility to scale horizontally with sharding or vertically with replica sets to match my changing demands. Additionally, data retrieval and analysis are now a snap because to the robust query language, numerous indexing options, and aggregation architecture.

If I had to pick one thing about MongoDB that I disliked the least, it would be the steep learning curve that comes with its sophisticated capabilities and intricate setups. MongoDB is a strong and feature-rich database that offers a variety of capabilities that may take some time and work to completely understand and efficiently use.

I like the Atlas Cloud solution. It enables various tricks and cross-integrations of single database between multiple apps (containers) with simple user management - for a reasonable price.

I cannot get over this Atlas Compass UX issue - I want to open at least two "tabs" with collections at the same time. This is not possible and even worse, when you switch between collections, thee state is completely reset.

So I'm compiling the search query carefully with all the commas, brackets and identifiers, I often need to search for ID from another collection or maybe from the same collection. When i change collection scope -> BAM! The whole query is gone :( The input should retain its actual value...

Second "issue": When it comes to schema changes in living DB, sometimes it behaves unexpectedly (no error, no data). Maybe I'm doing something wrong, but I would like to know it...

It is Universal and is compatible with many different applications.

Not sure of what kind of storage space that it will require or consume.