archrip 0.2.6 → 0.2.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -53,10 +53,18 @@ DDD / Clean Architecture / Hexagonal (use `"layout": "concentric"`):
|
|
|
53
53
|
- Flutter (Clean): External(0) → Data Sources(1) → Repositories(2) → Use Cases(3) → Domain(4)
|
|
54
54
|
- Note: Ports are interfaces **defined by the domain** — they belong near domain core, not at the adapter layer. Adapters implement/use Ports from the outside.
|
|
55
55
|
|
|
56
|
+
CQRS / Event-Driven:
|
|
57
|
+
- CQRS: External(0) → Command Handlers / Query Handlers(1) → Application Services(2) → Domain(3). Command and Query sides share the same layer structure but separate models
|
|
58
|
+
- Event Sourcing: External(0) → Command Handlers(1) → Event Store(2) → Projections(3) → Read Models(4)
|
|
59
|
+
- Event-Driven (Motia, Temporal, etc.): External(0) → API Steps(1) → Event Steps(2) → Services(3) → Domain(4)
|
|
60
|
+
|
|
56
61
|
Serverless / Microservices:
|
|
57
62
|
- SST/Lambda: External(0) → API Gateway(1) → Lambda Handlers(2) → Services(3) → Domain(4)
|
|
58
63
|
- Microservices: External(0) → Gateway/BFF(1) → Service Boundaries(2) → Internal Services(3) → Shared Domain(4)
|
|
59
64
|
|
|
65
|
+
Modular Monolith:
|
|
66
|
+
- Generic: External(0) → Module APIs(1) [public interfaces] → Module Internal Services(2) → Shared Kernel / Domain(3)
|
|
67
|
+
|
|
60
68
|
For unlisted frameworks: group by directory responsibility and apply the abstract rule above.
|
|
61
69
|
|
|
62
70
|
## Phase 4: Read Key Files
|
|
@@ -53,10 +53,18 @@ DDD / Clean Architecture / Hexagonal (use `"layout": "concentric"`):
|
|
|
53
53
|
- Flutter (Clean): External(0) → Data Sources(1) → Repositories(2) → Use Cases(3) → Domain(4)
|
|
54
54
|
- Note: Ports are interfaces **defined by the domain** — they belong near domain core, not at the adapter layer. Adapters implement/use Ports from the outside.
|
|
55
55
|
|
|
56
|
+
CQRS / Event-Driven:
|
|
57
|
+
- CQRS: External(0) → Command Handlers / Query Handlers(1) → Application Services(2) → Domain(3). Command and Query sides share the same layer structure but separate models
|
|
58
|
+
- Event Sourcing: External(0) → Command Handlers(1) → Event Store(2) → Projections(3) → Read Models(4)
|
|
59
|
+
- Event-Driven (Motia, Temporal, etc.): External(0) → API Steps(1) → Event Steps(2) → Services(3) → Domain(4)
|
|
60
|
+
|
|
56
61
|
Serverless / Microservices:
|
|
57
62
|
- SST/Lambda: External(0) → API Gateway(1) → Lambda Handlers(2) → Services(3) → Domain(4)
|
|
58
63
|
- Microservices: External(0) → Gateway/BFF(1) → Service Boundaries(2) → Internal Services(3) → Shared Domain(4)
|
|
59
64
|
|
|
65
|
+
Modular Monolith:
|
|
66
|
+
- Generic: External(0) → Module APIs(1) [public interfaces] → Module Internal Services(2) → Shared Kernel / Domain(3)
|
|
67
|
+
|
|
60
68
|
For unlisted frameworks: group by directory responsibility and apply the abstract rule above.
|
|
61
69
|
|
|
62
70
|
## Phase 4: Read Key Files
|
|
@@ -53,10 +53,18 @@ DDD / Clean Architecture / Hexagonal (use `"layout": "concentric"`):
|
|
|
53
53
|
- Flutter (Clean): External(0) → Data Sources(1) → Repositories(2) → Use Cases(3) → Domain(4)
|
|
54
54
|
- Note: Ports are interfaces **defined by the domain** — they belong near domain core, not at the adapter layer. Adapters implement/use Ports from the outside.
|
|
55
55
|
|
|
56
|
+
CQRS / Event-Driven:
|
|
57
|
+
- CQRS: External(0) → Command Handlers / Query Handlers(1) → Application Services(2) → Domain(3). Command and Query sides share the same layer structure but separate models
|
|
58
|
+
- Event Sourcing: External(0) → Command Handlers(1) → Event Store(2) → Projections(3) → Read Models(4)
|
|
59
|
+
- Event-Driven (Motia, Temporal, etc.): External(0) → API Steps(1) → Event Steps(2) → Services(3) → Domain(4)
|
|
60
|
+
|
|
56
61
|
Serverless / Microservices:
|
|
57
62
|
- SST/Lambda: External(0) → API Gateway(1) → Lambda Handlers(2) → Services(3) → Domain(4)
|
|
58
63
|
- Microservices: External(0) → Gateway/BFF(1) → Service Boundaries(2) → Internal Services(3) → Shared Domain(4)
|
|
59
64
|
|
|
65
|
+
Modular Monolith:
|
|
66
|
+
- Generic: External(0) → Module APIs(1) [public interfaces] → Module Internal Services(2) → Shared Kernel / Domain(3)
|
|
67
|
+
|
|
60
68
|
For unlisted frameworks: group by directory responsibility and apply the abstract rule above.
|
|
61
69
|
|
|
62
70
|
## Phase 4: Read Key Files
|