emerge/architecture-patterns
Knowledge base for architecture patterns, trade-offs, and selection criteria. Activates when recommending or evaluating architecture patterns like microservices, monolith, serverless, event-driven, CQRS, or hybrid approaches.
88
82%
Does it follow best practices?
Impact
99%
1.12xAverage score across 5 eval scenarios
Passed
No known issues
task.mdevals/scenario-1/
Architecture Recommendation for a B2B Project Tracking Startup
Problem Description
A small startup called TaskFlow is building a B2B project tracking tool — think lightweight project management for small consulting firms. They want to help consultants track billable hours, manage client deliverables, and produce status reports.
The founding engineering team is four people. All four are mid-to-junior level full-stack engineers who came from a large enterprise company where they used managed services for everything. None of them has operated infrastructure independently before. There is no dedicated DevOps, platform, or SRE function in the team — the engineers will handle deployment and operations themselves alongside feature development.
The product is in pre-launch. The team expects to start with a handful of pilot clients and grow slowly over the first year. They want to move fast in the early months to validate the product.
Your task is to produce an architecture recommendation for TaskFlow.
Output Specification
Write your recommendation to recommendation.md.