How openedx/enterprise-access works
Project type and purpose
• This is a Python/Django-based, modular monolith service (“enterprise-access”) that exposes REST-style APIs and BFF endpoints, processes background work via Celery, and produces/consumes Kafka events.
• Its core goal is to manage enterprise user access to content (assignments, subsidies, provisioning, billing) and integrate with upstream systems (LMS, catalog, e-commerce, license manager) plus analytics (Segment) and payment (Stripe).
File structure
• Top-level: manage.py, WSGI, Celery entrypoint, Docker and Devstack config.
• “enterprise_access/apps/…” contains a suite of Django apps (core, api, bffs, content_assignments, subsidy_access_policy, subsidy_request, provisioning, customer_billing, enterprise_groups, events, track, workflow).
• Each app defines models, serializers, views/endpoints, admin, tasks, management commands, migrations, and tests.
• There are OpenAPI specs (api.yaml, api-compact.yaml) driving API definitions.
• Celery is configured in celery.py; Kafka/event consumption in management commands and event bus packages.
• External clients under apps/api_client for talking to LMS, catalog, e-commerce, etc.
• Settings split by environment (base, devstack, production, test).
README for additional insights
• Service runs on Django + Gunicorn in Docker; leverages Devstack for local dependencies (Kafka, Postgres, Redis).
• It consumes and produces “openedx-events” topics via edx_event_bus_kafka.
• Analytics events dispatched via track_event (Segment).
• Management commands exist to test and bootstrap event flows.