Skip to content

Darin

My feedback

1 result found

  1. 70 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

    15 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
    Darin commented  · 

    This one issue is the primary if not sole reason why we're looking to move from Mongo to Postgres. Yes, we can change our data model to work within the 16MB limit. But that means modifying significant amounts of existing code. As long as we're going to modify significant amounts of corporate-wide code to handle this, we may as well move to a relational model which would entirely eliminate all size restrictions.

    If this were bumped up to 32MB, it would likely stave off any move we might contemplate for years, long enough that Mongo could move again up to 64MB. But the reality is that as long as there is a limit, people will hit it, even sparingly, and if Mongo cannot handle it, people will be forced to make changes to work around this limit, and if we have to make changes, then it's an opportunity to revisit the costs and benefits of Mongo vs other options.

    Darin supported this idea  · 

Feedback and Knowledge Base