Home
Work
Services
Blog
Skills
Certifications
Experience
Contact

© 2026 · Scalable backend systems, data platforms, and production architecture.

https://ngohuyhoang.com

Home
Blog
Architecture
Architecture review loops for delivery teams

Contents

Computer Science Fundamentals
Web
Databases
Distributed Systems
System Design
- Rate Limiting at Scale: Algorithms, Redis Patterns, and Distributed CoordinationLevel: IntermediateBudding. A working explanation I still expect to revise.
- Zero Trust Architecture: Identity Is the New PerimeterLevel: IntermediateBudding. A working explanation I still expect to revise.
Architecture
AI Engineering
- LLM Fundamentals
  - RAG Pipeline Design: Chunking, Retrieval, Reranking, and GenerationLevel: IntermediateBudding. A working explanation I still expect to revise.
  - LLM Evaluation Frameworks: How to Actually Measure What Your Model DoesLevel: IntermediateBudding. A working explanation I still expect to revise.
- Agentic Workflows
  - Building Agentic Workflows on Azure AI Foundry with MCP Servers in .NETLevel: AdvancedBudding. A working explanation I still expect to revise.
DevOps and DeliveryElective

Computer Science Fundamentals
Web
Databases
Distributed Systems
System Design
- Rate Limiting at Scale: Algorithms, Redis Patterns, and Distributed CoordinationLevel: IntermediateBudding. A working explanation I still expect to revise.
- Zero Trust Architecture: Identity Is the New PerimeterLevel: IntermediateBudding. A working explanation I still expect to revise.
Architecture
AI Engineering
- LLM Fundamentals
  - RAG Pipeline Design: Chunking, Retrieval, Reranking, and GenerationLevel: IntermediateBudding. A working explanation I still expect to revise.
  - LLM Evaluation Frameworks: How to Actually Measure What Your Model DoesLevel: IntermediateBudding. A working explanation I still expect to revise.
- Agentic Workflows
  - Building Agentic Workflows on Azure AI Foundry with MCP Servers in .NETLevel: AdvancedBudding. A working explanation I still expect to revise.
DevOps and DeliveryElective

Architecture review loops for delivery teams

Small review loops keep architecture decisions explicit while teams keep shipping.

Level: Intermediate[I]●●●◆Evergreen. Reviewed and stable enough to rely on.1 min read

Planted: 2025-10-19
Last tended: 2025-10-19

Progress

Team collaborating around a whiteboard during an architecture planning meeting

Read first

System DesignLevel: Intermediate

Architecture reviews work best when they are lightweight and recurring.

Use a loop that teams can sustain:

Weekly: capture one decision and one risk.
Bi-weekly: review trade-offs with product and operations.
Monthly: retire stale assumptions and update diagrams.

Next up

Next in the path: Service Mesh Patterns: What the Sidecar Actually Buys You

In this branch

Service Mesh Patterns: What the Sidecar Actually Buys You
Event-Driven Architecture: Tradeoffs You Need to Accept Before You Commit
CQRS and Saga Pattern in .NET: Building Reliable Distributed Workflows

Previous: Zero Trust Architecture: Identity Is the New Perimeter Next: Service Mesh Patterns: What the Sidecar Actually Buys You