Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-8549

Modernize Data Explorer Backend

XMLWordPrintableJSON

    • Developer Tools
    • Not Needed
    • Hide

      Docs Sync: Not yet scheduled
      Docs Update: Planning docs

      Show
      Docs Sync: Not yet scheduled Docs Update: Planning docs
    • Atlas Dedicated, Cloud Security, IAM, SRE
    • Hide
      SRE: Will need to consult with SRE for deploying a regionalized macroservice. And will need SRE help for routing calls to the macroservice.

      Security: Needed security input while scoping (this is already done now)

      IAM: No actual work needed from IAM, but may need to consult with IAM about AuthN service.

      Atlas Dedicated: We'll need PR reviews on CLOUDP-244055
      Show
      SRE: Will need to consult with SRE for deploying a regionalized macroservice. And will need SRE help for routing calls to the macroservice. Security: Needed security input while scoping (this is already done now) IAM: No actual work needed from IAM, but may need to consult with IAM about AuthN service. Atlas Dedicated: We'll need PR reviews on CLOUDP-244055
    • To Do
    • Modernize Data Explorer Backend
    • Hide

      Engineer(s): 4
      YYYY-MM-DD: Target date set to / on track for / updated to YYYY-MM-DD

      on track

      • Rational for any project delays/change in end date, if applicable
      • Known risks or blockers:
        • Once this is released, any folks that need to switch over to Database Auditing from Activity Feed events may experience a performance degradation. We will need to make sure we are prepared to handle any customer reports / complaints that come in.
      • Completed over the last 2 weeks:
        • Deployed service to QA
        • Some major refactoring to support all cluster tiers
        • Adding a bunch of metrics in preparation for production deployment
        • Implementing updates to backing DB in order to store connection count for rate limiting, and caching X.509 certificates
      • Focus over the next 2 weeks
        • Deploying to production
          • Configuring auto-scaling
          • Figuring out a standard deployment process, getting the team familiar with it
        • Finishing backing DB updates
        • Add more metrics, create alerts for the service
        • Implement Activity Feed support (only for "new session" events)
      • Anything else to share?
      Show
      Engineer(s): 4 YYYY-MM-DD : Target date set to / on track for / updated to  YYYY-MM-DD on track Rational for any project delays/change in end date, if applicable Known risks or blockers: Once this is released, any folks that need to switch over to Database Auditing from Activity Feed events may experience a performance degradation. We will need to make sure we are prepared to handle any customer reports / complaints that come in. Completed over the last 2 weeks: Deployed service to QA Some major refactoring to support all cluster tiers Adding a bunch of metrics in preparation for production deployment Implementing updates to backing DB in order to store connection count for rate limiting, and caching X.509 certificates Focus over the next 2 weeks Deploying to production Configuring auto-scaling Figuring out a standard deployment process, getting the team familiar with it Finishing backing DB updates Add more metrics, create alerts for the service Implement Activity Feed support (only for "new session" events) Anything else to share?

      Epic Summary

      Summary

      When using MongoDB, there are at least 2 options for viewing and querying the data stored in the database. The first is the Mongo shell, a command-line tool that allows you to type your query and see the results with an entirely textual interface. The second is using an interactive GUI. There is a desktop version of this GUI named Compass and a web version named Data Explorer (DE).

       

      Both Compass and DE share much of their UI, but have entirely different back-ends for getting the user’s query from the UI to the database. This project is the first step toward unifying the two tools and focuses on the back-end for DE. Currently, DE has to tell a background process (the Automation Agent) that is running on the same machine as the MongoDB instance what query it wants to run, then wait for the agent to perform the query and return results. This project will remove that background process from the equation entirely, allowing DE to (basically) directly communicate with the MongoDB instance to perform the user’s queries.

       

      This change should simplify the architecture, bringing it more in line with what Compass does.

            Assignee:
            simon.zhu@mongodb.com Simon Zhu
            Reporter:
            crystal.horn@mongodb.com Crystal Horn
            Sarah Simpers Sarah Simpers
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: