From 220d38d2d1f5b8888dc11cce05572cd930ae30d1 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
<161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Wed, 8 Apr 2026 17:39:55 +0000
Subject: [PATCH] docs(arch): autonomous evolution of architecture blueprints
- Fix stray Markdown snippet in hexagonal-architecture/implementation-guide.md.
- Fix duplicate mapping link and add missing BFF section to architectures/readme.md.
Co-authored-by: beginwebdev2002 <102213457+beginwebdev2002@users.noreply.github.com>
---
.../implementation-guide.md | 9 ----
architectures/readme.md | 45 +++++++++++++++++--
2 files changed, 42 insertions(+), 12 deletions(-)
diff --git a/architectures/hexagonal-architecture/implementation-guide.md b/architectures/hexagonal-architecture/implementation-guide.md
index 7b40da0..ba5078d 100644
--- a/architectures/hexagonal-architecture/implementation-guide.md
+++ b/architectures/hexagonal-architecture/implementation-guide.md
@@ -186,15 +186,6 @@ export class User {
this.status = 'INACTIVE';
}
}
-```
-
- @Column()
- public status: 'ACTIVE' | 'INACTIVE';
-
- public deactivate(): void {
- this.status = 'INACTIVE';
- }
-}
```
### ⚠️ Problem
diff --git a/architectures/readme.md b/architectures/readme.md
index d3f2bba..8be955a 100644
--- a/architectures/readme.md
+++ b/architectures/readme.md
@@ -471,9 +471,6 @@ src/
[](#)
**Description:** An architectural style where independently deliverable frontend applications are composed into a greater whole. This enables multiple teams to work simultaneously without stepping on each other's toes, making scaling enterprise frontends deterministic.
-**📖 Map of Patterns:** [Go to Backend-For-Frontend (BFF) Guidelines](./backend-for-frontend/readme.md)
-
-
**📖 Map of Patterns:** [Go to Micro-frontends Guidelines](./micro-frontends/readme.md)
**Architecture Diagram & Folder Tree:**
@@ -510,3 +507,45 @@ workspace/
- **Languages:** 
TypeScript.
- **Patterns / Principles:** Module Federation, Event-Driven Communication.
- **Tools:** Webpack 5, Vite.
+
+---
+
+### 12. Backend-For-Frontend (BFF)
+[](#)
+
+**Description:** A pattern where a separate backend service is created for each specific frontend application or interface type, rather than having a single general-purpose API backend for all clients. This allows the backend to be optimized for the specific needs of the frontend.
+**📖 Map of Patterns:** [Go to Backend-For-Frontend (BFF) Guidelines](./backend-for-frontend/readme.md)
+
+**Architecture Diagram & Folder Tree:**
+```mermaid
+graph TD
+ Web[Web Client] --> BFF_Web[BFF Web]
+ Mobile[Mobile Client] --> BFF_Mobile[BFF Mobile]
+ BFF_Web --> MS1[Microservice 1]
+ BFF_Web --> MS2[Microservice 2]
+ BFF_Mobile --> MS1
+ BFF_Mobile --> MS2
+
+ %% Added Design Token Styles for Mermaid Diagrams
+ classDef default fill:#e1f5fe,stroke:#03a9f4,stroke-width:2px,color:#000;
+ classDef component fill:#e8f5e9,stroke:#4caf50,stroke-width:2px,color:#000;
+ classDef layout fill:#f3e5f5,stroke:#9c27b0,stroke-width:2px,color:#000;
+
+ class Web component;
+ class Mobile component;
+ class BFF_Web component;
+ class BFF_Mobile component;
+```
+
+```text
+src/
+├── 📁 routes/ # Route definitions mapped to controllers
+├── 📁 controllers/ # Handles incoming requests from specific clients
+├── 📁 services/ # Aggregates data from multiple downstream APIs
+└── 📁 clients/ # Logic to call downstream Microservices
+```
+
+**Best Compatibility:**
+- **Frameworks:** NestJS, Express.js.
+- **Languages:** TypeScript, Node.js.
+- **Patterns / Principles:** API Gateway, Microservices, API Composition.