ODM Standardisation Initiative

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Multiple
    • None
    • odm-standardisation
    • Not Needed
    • None
    • None
    • None
    • None
    • Hide

      Summary of necessary driver changes

      MongoDB will maintain a public framework that provides developers with a consistent, transparent view of feature support across MongoDB's key Object-Document Mappers (ODMs). Previously, developers choosing an ODM had no reliable way to determine whether a specific MongoDB capability such as Vector Search or Queryable Encryption  was supported, unsupported, or planned in their ODM of choice, often discovering gaps only after committing to a stack. The framework, published on GitHub, documents feature coverage across MongoDB's most critical ODM ecosystems, explains the reasoning behind gaps where a feature is not yet available, and provides expected timelines for roadmap items, giving developers the information they need to make informed decisions before they write a line of code.

      Commits for syncing spec/prose tests

      • N/A

      Context for other referenced/linked tickets

      • N/A

      Acceptance Criteria:

      • Each of the ODM Guidelines is reviewed.
      • For a specific ODM owned by a team, the individual <ODM_name>.md file has been reviewed to accurately reflect reality and known future plans with regards to the features spanning the guidelines. 
      • For any changes, the standard PR review process in DBX should be used. 

      References: 

       

      Show
      Summary of necessary driver changes MongoDB will maintain a public framework that provides developers with a consistent, transparent view of feature support across MongoDB's key Object-Document Mappers (ODMs). Previously, developers choosing an ODM had no reliable way to determine whether a specific MongoDB capability such as Vector Search or Queryable Encryption  was supported, unsupported, or planned in their ODM of choice, often discovering gaps only after committing to a stack. The framework, published on GitHub , documents feature coverage across MongoDB's most critical ODM ecosystems, explains the reasoning behind gaps where a feature is not yet available, and provides expected timelines for roadmap items, giving developers the information they need to make informed decisions before they write a line of code. Commits for syncing spec/prose tests N/A Context for other referenced/linked tickets N/A Acceptance Criteria: Each of the ODM Guidelines is reviewed. For a specific ODM owned by a team, the individual <ODM_name>.md file has been reviewed to accurately reflect reality and known future plans with regards to the features spanning the guidelines.  For any changes, the standard PR review process in DBX should be used.  References:   Github repo   Memo: ODM Guidelines PD: ODM Standardization Framework  
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket was split from DRIVERS-3292, please see that ticket for a detailed description.

            Assignee:
            Unassigned
            Reporter:
            TPM Jira Automations Bot
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None
              None