Why I'm moving Lerna projects to .NET projects?
summary
Claim: moving a small personal Lerna monorepo into .NET reduces context switching and makes single‑maintainer work practical. Implementation detail: a simple self‑hosted password/secret service is rebuilt in .NET, containerized with Docker, pushed to Amazon ECR and deployed to AWS (referred to as iws/app router). Architecture decision: a monolithic two‑tier app for ease of management, with plans to apply Clean Architecture and incrementally modularize; CI/CD pipelines exist and the app is already deployed and running.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:22Project goals
- 3:46Tech stack challenges
- 5:13Migration strategy
- 6:38Monolithic .NET
- 8:01Deployment status
- 9:03Migration steps
- 9:45Lessons learned
related talks
29mModularity and Monorepositories
28mKeynote - Nx and Lerna: Integrated vs Package-Based Monorepos
25mLerna Reborn
19mKeynote: Why Monorepos
09mOpening Remarks
48mMicrofrontend Architecture – technical implementation.
01h 13mArchitecting complex JavaScript setups for large scale enterprise projects
24mIsomorphic Business Logic