Skip to content

Dependencies & Cycles — MIT Learn

Generated 2026-06-24 13:33 UTC · c4gen dev

Coupling between MIT Learn and the rest of the SOA. The matrix and cycles below come from the deterministic witan-code graph extraction; the candidate edges are raw graph findings that still need human confirmation.

Cross-service dependency matrix (curated)

Depends on → …on these systems
mit-learn micromasters, mitxonline

Cycles

Dependency cycles detected

  • mit-learn → mitxonline → mit-learn

Interpreting graph candidates

Cross-repo edges are matched by normalized endpoint path. Two services that both define e.g. /api/v0/users/me/, or a client checked into a repo for load testing, produce phantom edges. Confirm each candidate against the actual client/route code before treating it as a real runtime dependency.

Candidate edges (graph-derived, unverified)

Consumer → Provider Contract sample Source of truth
micromasters → mit-learn (calls 1 endpoint) /api/v0/profiles/${userUsername}/ static/js/lib/api.js
mit-learn → mitxonline (calls 9 endpoints) /api/v0/baskets/, /api/v0/users/${username}/, /api/v0/users/me/ load_testing/backend/client/v0/api.ts
mitxonline → mit-learn (calls 1 endpoint) /api/v0/users/me/ frontend/public/src/lib/queries/users.js

Fragile / noteworthy linkages

  • celery-default → media-feeds: Fetch feeds + scrape — YouTube, podcasts, Medium, OL events, Sloan Aura
  • data-platform → postgres: Reverse-ETL write (Hightouch) — ProgramCertificate rows (public DB access)