← Overview
Quiz

MMGIS — concepts quiz

Twelve big-picture questions on how MMGIS is shaped — architecture, decisions, seams, interactions, and tradeoffs. Each question has a review that explains why the answer is right and what each wrong pick would have implied.

Pick an answer for each question. Once you commit, the review explains why the right answer is right and what each other option would have implied. Your progress saves locally — close the tab and come back later.

0 of 12 answered
  1. Question 1
    Architecture

    What is the deployment shape of MMGIS in production?

  2. Question 2
    Seams

    Configure is a separate React 17 SPA and Essence is a React 16 SPA — they share no bundle and no React tree. So how does Essence actually learn what missions, layers, and tools to render?

  3. Question 3
    Decisions

    What forces Essence to be bundled by a custom CRA-eject Webpack 5 pipeline rather than something simpler like plain Vite or stock CRA?

  4. Question 4
    Decisions

    Why does Essence keep two 2D map engines — Leaflet and deck.gl — instead of consolidating on one?

  5. Question 5
    Decisions

    Why is Configure built as a separate React 17 SPA at /configure rather than as another panel inside Essence?

  6. Question 6
    Seams

    How does MMGIS authenticate requests crossing the browser-backend seam?

  7. Question 7
    Interactions

    What is L_ in the Essence codebase, and how do other modules interact with it?

  8. Question 8
    Interactions

    What roles does the mmgisAPI object play in the system?

  9. Question 9
    Tradeoffs

    Why does MMGIS use a plugin-drop directory convention (e.g., *Plugin-Tools*) instead of a registry file that explicitly lists installed plugins?

  10. Question 10
    Tradeoffs

    Why is the MMGIS WebSocket a noServer: true upgrade attached to the main HTTP server, and why does it broadcast every message to every client?

  11. Question 11
    Architecture

    Every backend feature under API/Backend/ follows the same shape. What is it, and what does it tell you about the backend?

  12. Question 12
    Architecture

    MMGIS keeps two database handles to one Postgres database — what are they, and why both?