Domain-driven architecture for Azure Functions with GraphQL/REST, MongoDB (Mongoose), and OpenTelemetry. This repo contains the API app, domain, infrastructure, and local dev services.
Getting Started: Our Docusaurus website will help you get started in running and contributing to CellixJS
-
Full local dev (lints, builds, starts Azurite, emulators, and the OwnerCommunity app):
pnpm run dev
-
Simulate CI pipeline (lints, builds, tests, sonarcloud scan, quality gate):
pnpm run verify
-
Start only the API app:
pnpm run start:api
-
Start the UI (frontend):
pnpm run start:ui-community
-
Start emulators individually:
# MongoDB in-memory replica set pnpm run start-emulator:mongo-memory-server # OAuth2/OIDC mock server pnpm run start-emulator:auth-server
- Build all workspaces:
pnpm run build - Build affected packages only:
pnpm run build:affected - Lint all:
pnpm run lint - Lint affected packages only:
pnpm run lint:affected - Format all:
pnpm run format - Tests:
pnpm run testpnpm run test:affected(affected packages only)pnpm run test:coveragepnpm run test:coverage:affected(affected packages only)pnpm run test:integrationpnpm run test:serenitypnpm run test:unitpnpm run test:watch(typically run per workspace package)
- Verify build locally:
pnpm run verify
This monorepo uses Turborepo for optimized builds and testing:
- Selective Builds: Only affected packages are built/tested in CI
- Remote Caching: Shared build cache across team and CI (when configured)
- Local Caching: Faster subsequent builds on your machine
- Package Categories:
- Frontend:
ui-*packages - Backend: All other packages (excluding mock servers)
- Frontend:
For detailed setup and usage, see TURBOREPO.md.
- Architecture docs and ADRs in
docusaurus/decisions
- Install recommended VSCode extensions for best developer experience.
- Use built-in tasks to run the Functions host and watch builds.
The CI/CD pipeline uses intelligent change detection to deploy only affected components:
- Backend/API: Deploys when API-related packages change
- Frontend/UI: Deploys when UI packages change
- Docs: Deploys when documentation changes
- Infrastructure: Deploys when Bicep templates, pipeline configs, or infrastructure code changes
In rare cases where external Azure DevOps configuration changes need deployment (variable groups, service connections, environment settings), or when you want to manually force deployment of specific packages, use the force deploy mechanism:
The .force-deploy file is a configuration file that sets environment variables to control manual deployment overrides:
#!/bin/bash
# .force-deploy configuration file for CellixJS monorepo
# Set FORCE_DEPLOY_* flags to control manual deployment overrides
# Set to 'true' to force deployment, 'false' to disable
FORCE_DEPLOY_API=false
FORCE_DEPLOY_UI=false
FORCE_DEPLOY_DOCS=false
# Developers: Change any value to 'true' to force deployment of that package
# Example:
# FORCE_DEPLOY_API=true
# FORCE_DEPLOY_UI=true
# FORCE_DEPLOY_DOCS=trueTo force deployment of specific packages:
- Edit
.force-deployand set the desiredFORCE_DEPLOY_*variable(s) totrue - Commit and push the changes to trigger the pipeline
- The pipeline will deploy the selected packages even if no changes are detected
- Optionally reset the variables to
falseafter successful deployment
Important: The pipeline parses this file directly and respects the FORCE_DEPLOY_* variables, overriding change detection logic for the specified packages.
---
config:
layout: elk
---
flowchart BT
%% Keep two top-level groups for clarity
subgraph ocom
direction TB
%% API and services
ocom_api["@ocom/api"]
ocom_api_graphql["@ocom/api-graphql"]
ocom_api_rest["@ocom/api-rest"]
ocom_api_application_services["@ocom/api-application-services"]
ocom_api_context_spec["@ocom/api-context-spec"]
ocom_api_event_handler["@ocom/api-event-handler"]
ocom_api_domain["@ocom/api-domain"]
ocom_api_persistence["@ocom/api-persistence"]
ocom_api_ds_mongoose_models["@ocom/api-data-sources-mongoose-models"]
%% Infra services (OCom)
ocom_service_mongoose["@ocom/service-mongoose"]
ocom_service_blob_storage["@ocom/service-blob-storage"]
ocom_service_otel["@ocom/service-otel"]
ocom_service_token_validation["@ocom/service-token-validation"]
%% Local dev + UI
ocom_service_oauth2_mock_server["@ocom/service-oauth2-mock-server"]
ocom_service_mongodb_memory_server["@ocom/service-mongodb-memory-server"]
ocom_ui_community["@ocom/ui-community"]
end
subgraph cellix
direction TB
cellix_api_services_spec["@cellix/api-services-spec"]
cellix_data_sources_mongoose["@cellix/mongoose-seedwork"]
cellix_domain_seedwork["@cellix/domain-seedwork"]
cellix_event_bus_seedwork_node["@cellix/event-bus-seedwork-node"]
end
%% Dependencies (left -> right for cleaner routing)
%% Cellix base
cellix_data_sources_mongoose --> cellix_domain_seedwork
cellix_data_sources_mongoose --> cellix_event_bus_seedwork_node
%% OCom -> Cellix
ocom_api_ds_mongoose_models --> cellix_data_sources_mongoose
ocom_api_domain --> cellix_domain_seedwork
ocom_api_domain --> cellix_event_bus_seedwork_node
ocom_api_persistence --> cellix_domain_seedwork
ocom_api_persistence --> cellix_event_bus_seedwork_node
ocom_api_persistence --> cellix_data_sources_mongoose
ocom_service_mongoose --> cellix_api_services_spec
ocom_service_mongoose --> cellix_data_sources_mongoose
ocom_service_blob_storage --> cellix_api_services_spec
ocom_service_otel --> cellix_api_services_spec
ocom_service_token_validation --> cellix_api_services_spec
%% OCom internal
ocom_api_persistence --> ocom_api_domain
ocom_api_persistence --> ocom_api_ds_mongoose_models
ocom_api_context_spec --> ocom_api_persistence
ocom_api_context_spec --> ocom_service_token_validation
ocom_api_application_services --> ocom_api_context_spec
ocom_api_application_services --> ocom_api_domain
ocom_api_application_services --> ocom_api_persistence
ocom_api_event_handler --> ocom_api_domain
ocom_api_event_handler --> ocom_api_persistence
ocom_api_graphql --> ocom_api_application_services
ocom_api_graphql --> ocom_api_context_spec
ocom_api_rest --> ocom_api_application_services
ocom_api_rest --> ocom_api_context_spec
%% Composition
ocom_api --> cellix_api_services_spec
ocom_api --> ocom_api_context_spec
ocom_api --> ocom_api_application_services
ocom_api --> ocom_api_graphql
ocom_api --> ocom_api_persistence
ocom_api --> ocom_api_rest
ocom_api --> ocom_service_blob_storage
ocom_api --> ocom_service_mongoose
ocom_api --> ocom_service_otel
ocom_api --> ocom_service_token_validation
%% Keep these as standalone to avoid clutter
ocom_service_oauth2_mock_server
ocom_service_mongodb_memory_server
ocom_ui_community
This section preserves prior setup notes and commands for reference as the repo evolved.
npm i -D concurrently
npm init -w ./packages/api-graphql
npm install @as-integrations/azure-functions @apollo/server graphql @azure/functions -w api-graphql
npm init -w ./packages/api-event-handler
npm init -w ./packages/api-services
npm init -w ./packages/api-rest
npm install @azure/functions -w api-rest
npm init -w ./packages/api-data-sources-domain
npm init -w ./packages/service-otel
npm install @azure/monitor-opentelemetry -w service-otel
npm init -w ./packages/api-persistence
npm init -w ./packages/event-bus-seedwork-node
npm install --save-dev @tsconfig/node20 @tsconfig/node-ts vitest @vitest/coverage-v8Do you find CellixJS useful? Give us a ⭐ star on GitHub!
Found a bug? Need a feature? Raise an issue or submit a pull request.
Have feedback? Leave a comment in CellixJS discussions on GitHub
![@sourcery-ai[bot]](https://cdn.statically.io/img/avatars.githubusercontent.com/in/48477?s=64&v=4){kind=small}
