Experience · Backend · Active

sfdc backend

NestJS BFF for External SFDC, acting as the public product boundary while orchestrating auth, datasource, metadata, reporting and visibility services.

• NestJS
• Prisma
• PostgreSQL
• @nestjs/swagger

Spec sheet

Repository path

sfdc-external/backend

Runtime

NestJS BFF with Prisma

Public surface

Same-origin /api on sfdc host

Delegations

Auth to platform-auth-service, Salesforce runtime to platform-connectors-service

Responsibilities

• Expose product-specific API contracts to the frontend.
• Own ACL, visibility, apps catalog, metadata, audit, reports and dashboards logic.
• Translate technical connector contracts into product-facing behavior.
• Normalize Salesforce contact lookups and report/dashboard runtime requests behind backend endpoints.
• Keep Salesforce SDK logic out of the product repository itself.

Interfaces and contract surface

• Same-origin /api
• GET /api/health
• Internal service-to-service calls to Core services
• Runtime report and dashboard execution endpoints
• Structured Salesforce lookup endpoints

Consumers

• sfdc frontend

Dependencies and external touchpoints

• platform-auth-service
• platform-connectors-service
• @sfdc-external/shared
• PostgreSQL

Notes

• The backend is intentionally the only public boundary for the experience.
• Recent refactors keep heavy runtime implementations in *.runtime.ts files with thin public exports.

Source references

• sfdc-external/backend/package.json
• sfdc-external/README.md
• docs/architecture-current.md