Skip to content


My feedback

1 result found

  1. 41 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Database » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Atul commented  · 

    You can put a disclaimer that 16 MB is recommended but Customer should be able to configure this value to whatever he wants 64 MB, 128mb or whatever, knowing the performances implications. If We, the customers are ready to compromise on other things like performance what problem MongoDb should have?

    Last year only, we started using mongo db. We were super happy in the begining. But almost after 3 months, We came to know this limitation and one of our Collection is at risk due to this limitation.
    We have a Position document. multiple Employees can be assigned to this Position. In a large org there could be a million employees. All the changes in Position document as well as in nested document of employees array are revisioned.
    I don’t wanna go in much details. But, 16 MB seems super scary as our world is growing more and more data. You can not put a limit. Rather than asking your customers counter questions why do we need more than 16 mb, please make it configurable and put a recommendation of 16 mb. Otherwise, we are left with no choice but to decommision mongoDb from our tech stack.

    Atul supported this idea  · 

Feedback and Knowledge Base