Is it possible to use MongoDB in case of over 200 fields?

Question

MySQL

Hello. There is a certain entity (more specifically, an organization), which includes approximately 250 fields. These fields can and should be structured, so it will turn out something like this - one entity \u003d one dock with 2-3 levels in depth (arrays or nested documents, rather the second one). Question - the choice towards MongoDB in this case is how much expedient? The choice is due to the fact that the document-oriented database, in this case MongoDB, reflects the domain model in ... if I may say so in this context, in a "native" form, plus there should be a lot of data (not BigData yet, but MapReduce is extremely useful), plus this is a denormalized data model, and as part of the tasks that will be performed when working with this database, this is also a plus. But isn't that too many fields for Mongo?
PS: It's just that if this is still a large number and the answers will be like "split into collections" (and in this case the goal is to get one collection), then it will be easier to take those DBMS that were originally made normalized and design a database t.s. "classic" way, as far as I understand. Correct me if wrong. Thanks in advance.

Answer 1

It's not about the number of fields, but about the size of the document. MongoDb has a limit of 16 megabytes.
docs.mongodb.org/manual/reference/limits