featr-io Migration Plan
Summary
- Total Subsystems: 3
- Total Repositories to Create: 3
- Estimated Duration: 15 minutes
- Repository Visibility:
private
Subsystems Inventory
| Subsystem Path | Proposed Repository Name | Category | Language | Est. LOC | Architectural Reasoning |
|---|---|---|---|---|---|
client/ | app-ui | Frontend/UI Layer | Next.js/TS | ~2,000 | Core feature-rich application dashboard. |
landing/ | marketing-ui | Frontend/UI Layer | Next.js/TS | ~1,000 | High-performance, SEO-optimized landing site + MARKETING.json. |
server/ | api-service | Backend Service | Go | ~3,500 | High-concurrency API service; efficient resource usage + Makefile. |
Dependency Graph
Architectural Notes
- Go Backend: Retaining Go for the
api-serviceensures high performance and low operational costs, which is a core value proposition of Featr. - Next.js Frontend: Provides a modern, responsive user experience with excellent SEO capabilities for the marketing site and fast interactions for the app.
- Independent Scalability: By separating the UI layers, we can scale the marketing site separately from the application dashboard.
Next Steps
- Create repositories in the
featr-ioorganization. - Initialize git for each subsystem.
- Push code to the new remotes.