Files
marketplaces/docs/architecture/foundation/Service-Standards.md
sdarbinyan 8d652c8259
Some checks failed
Architecture Governance / architecture (push) Has been cancelled
feat(platform): sprint 11.5 standardization
2026-07-09 02:29:12 +04:00

1.2 KiB

Service Standards

Status: Mandatory Date: 2026-07-03

Service Categories

  • Domain Service: business operations and rules.
  • Integration Service: external API/system communication.
  • Platform Service: cross-cutting platform concerns.

Rules

  • Services must have one clear responsibility.
  • Services should expose typed contracts only.
  • Services should avoid UI-specific formatting.
  • Services should not depend on component classes.
  • Shared services must not depend on feature modules.
  • Business decisions must not be driven by environment.* flags.
  • Environment values are limited to infrastructure concerns (API base URLs, provider strategy wiring, auth endpoint origins).

Facade Interaction

  • Components call facades.
  • Facades call services.
  • Services do not call UI components.

Stable Module Protection

  • Existing authentication, payment, authorization services remain behavior-compatible.
  • Wrap legacy stable behavior with adapters where needed.
  • No contract changes for auth/payment APIs.

Storage and Runtime Access

  • Browser storage access allowed only in approved service boundaries.
  • Prefer abstraction interfaces for storage access.
  • Never use storage APIs in UI components.