Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · Strangler Fig Migration (TypeScript, NestJS, Express, PostgreSQL, Redis, Docker)
stack-profile:strangler-fig-migrationa5c.ai
Search record views/
Record · tabs

Available views

II.Record viewspp. 1 - 1
overviewjsongraph
II.
StackProfile overview

stack-profile:strangler-fig-migration

Reference · live

Strangler Fig Migration (TypeScript, NestJS, Express, PostgreSQL, Redis, Docker) overview

A migration architecture implementing the Strangler Fig pattern to incrementally replace a legacy monolith with modern TypeScript services. An Express reverse proxy intercepts all traffic, routing requests to either the legacy system or new NestJS microservices based on feature flags and path matching. Redis caches routing decisions and shared session state between old and new systems. PostgreSQL serves both the legacy schema and new service schemas, with CDC (change data capture) keeping them synchronized during the transition. Docker Compose orchestrates the complete hybrid environment locally. The tradeoff is maintaining two systems simultaneously with careful data consistency management, but the pattern eliminates big-bang migration risk.

StackProfileOutgoing · 21Incoming · 0

Attributes

displayName
Strangler Fig Migration (TypeScript, NestJS, Express, PostgreSQL, Redis, Docker)
description
A migration architecture implementing the Strangler Fig pattern to incrementally replace a legacy monolith with modern TypeScript services. An Express reverse proxy intercepts all traffic, routing requests to either the legacy system or new NestJS microservices based on feature flags and path matching. Redis caches routing decisions and shared session state between old and new systems. PostgreSQL serves both the legacy schema and new service schemas, with CDC (change data capture) keeping them synchronized during the transition. Docker Compose orchestrates the complete hybrid environment locally. The tradeoff is maintaining two systems simultaneously with careful data consistency management, but the pattern eliminates big-bang migration risk.
composes
  • language:typescript
  • framework:nestjs
  • library:express
  • library:ioredis
  • library:prisma
  • library:bullmq
  • tool:docker
  • tool:docker-compose
  • language:sql

Outgoing edges

applies_to2
  • domain:software-engineering·DomainSoftware Engineering
  • domain:backend·DomainBackend
composed_of9
  • language:typescript·LanguageTypeScript
  • framework:nestjs·FrameworkNestJS
  • library:express·LibraryExpress
  • library:ioredis·Libraryioredis
  • library:prisma·LibraryPrisma
  • library:bullmq·LibraryBullMQ
  • tool:docker·ToolDocker
  • tool:docker-compose·ToolDocker Compose
  • language:sql·LanguageSQL
follows_workflow2
  • workflow:strangler-fig-migration·WorkflowStrangler Fig Migration
  • workflow:legacy-migration-sprint·WorkflowLegacy Migration Sprint
requires_skill_area5
  • skill-area:strangler-fig-pattern·SkillAreaStrangler Fig Migration
  • skill-area:parallel-run-migration·SkillAreaParallel-Run Migration
  • skill-area:schema-evolution·SkillAreaSchema Evolution
  • skill-area:middleware-design·SkillAreaMiddleware
  • skill-area:database-migrations-zero-downtime·SkillAreaZero-Downtime Database Migrations
used_by_role3
  • role:architect·RoleArchitect
  • role:backend-engineer·RoleBackend Engineer
  • role:tech-lead·RoleTech Lead

Incoming edges

None.

Related pages

No related wiki pages for this record.

Shortcuts

Open in graph
Browse node kind