docs(furniture-bff): add service boundary notes
This commit is contained in:
parent
fd2d61701d
commit
0d86a012b4
13
docs/architecture/bff-service-boundary.md
Normal file
13
docs/architecture/bff-service-boundary.md
Normal file
@ -0,0 +1,13 @@
|
||||
# Furniture BFF Service Boundary
|
||||
|
||||
## Purpose
|
||||
Preserve BFF as an edge adapter layer that depends on service contracts only.
|
||||
|
||||
## BFF Responsibilities
|
||||
- REST edge exposure
|
||||
- Service client adaptation
|
||||
- Correlation/tracing propagation
|
||||
|
||||
## Prohibited
|
||||
- Direct DAL access
|
||||
- Domain business decision ownership
|
||||
6
docs/migration/correlation-propagation-checks.md
Normal file
6
docs/migration/correlation-propagation-checks.md
Normal file
@ -0,0 +1,6 @@
|
||||
# Correlation Propagation Checks
|
||||
|
||||
## Checks
|
||||
- Correlation identifiers are preserved across BFF -> Service calls.
|
||||
- No new correlation behavior is introduced at edge.
|
||||
- Trace metadata pass-through remains stable.
|
||||
9
docs/migration/post-domain-contract-alignment.md
Normal file
9
docs/migration/post-domain-contract-alignment.md
Normal file
@ -0,0 +1,9 @@
|
||||
# Post-Domain Contract Alignment
|
||||
|
||||
## Goal
|
||||
Align BFF adapter usage with service contracts after domain extraction.
|
||||
|
||||
## Steps
|
||||
1. Map current BFF contract usage to updated service contracts.
|
||||
2. Keep edge contract behavior stable.
|
||||
3. Validate adapter compatibility.
|
||||
Loading…
Reference in New Issue
Block a user