go:architecture:clean_arch
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| go:architecture:clean_arch [2026/01/30 01:28] – [V. Processing Flow (Request → Response)] phong2018 | go:architecture:clean_arch [2026/01/30 01:33] (current) – [2. Application Layer — Usecase Orchestration] phong2018 | ||
|---|---|---|---|
| Line 85: | Line 85: | ||
| ===== V. Processing Flow (Request → Response) ===== | ===== V. Processing Flow (Request → Response) ===== | ||
| + | <code text> | ||
| Client (gRPC / HTTP Request) | Client (gRPC / HTTP Request) | ||
| ↓ | ↓ | ||
| Line 101: | Line 102: | ||
| ↓ | ↓ | ||
| Database / External Service | Database / External Service | ||
| + | </ | ||
| ===== VI. Detailed Layer Examples ===== | ===== VI. Detailed Layer Examples ===== | ||
| Line 115: | Line 116: | ||
| File location: | File location: | ||
| - | < | + | < |
| internal/ | internal/ | ||
| - | </ | ||
| <code go> type AddPointRepository interface { FetchProcessingOrders( ctx context.Context, | <code go> type AddPointRepository interface { FetchProcessingOrders( ctx context.Context, | ||
| Line 146: | Line 146: | ||
| < | < | ||
| internal/ | internal/ | ||
| + | |||
| </ | </ | ||
| - | <code go> type PointAddUsecase struct { repo domain.AddPointRepository } | + | <code go> |
| + | type PointAddUsecase struct { repo domain.AddPointRepository } | ||
| func (u *PointAddUsecase) Execute(ctx context.Context) error { | func (u *PointAddUsecase) Execute(ctx context.Context) error { | ||
go/architecture/clean_arch.1769736515.txt.gz · Last modified: by phong2018
