💬 [DISCUSSION] Should we move to microservices?

[github-actions]

Context

With all the coupling issues in our monolith, should we consider breaking this into microservices?

Arguments For

• TaskService is too coupled to everything
• Scaling issues with the monolith
• Team velocity is decreasing
• Independent deployment of components

Arguments Against

• We're a small team (3 people)
• Added operational complexity (K8s, service mesh, distributed tracing)
• Migration effort is significant
• Risk of distributed monolith

Questions

1. What would the service boundaries be?
2. Do we have the infrastructure knowledge?
3. What's the migration timeline?

Looking for discussion before we decide.

cc: @kevin @jennifer @david

[github-actions]

🎯 Triage report

Discussion issue asking whether to migrate from the current monolith to microservices. Lists arguments for (coupling, scaling, velocity) and against (small team of 3, operational complexity, migration risk). This is an architectural decision that needs team alignment, not a coding task.

📊 Assessment

Dimension	Value	Reasoning
Type	Task	Architectural planning discussion.
Labels	question	Open-ended architectural question seeking team input.
Coding agent	Not suitable	Architectural decision requiring team consensus, business context, and tradeoff analysis — not a coding task.

🔗 Similar issues

• 🟠 [TECH DEBT] TaskService is a God Class (670+ lines) - needs refactoring #16 (related) — God Class refactoring in 🟠 [TECH DEBT] TaskService is a God Class (670+ lines) - needs refactoring #16 is a prerequisite regardless of architecture direction; reducing coupling first would lower migration cost if microservices are chosen.

💡 Notes and suggestions

Before deciding: quantify the actual scaling pain (RPS, latency, memory). With a 3-person team, microservices operational overhead is significant. Consider a modular monolith (domain-separated packages with clear module boundaries) as an intermediate step. Address existing tech debt (#16, #19, #20) first regardless of architecture direction.

Generated by Daily Issue Triage · 95.1 AIC · ⌖ 18.2 AIC · ⊞ 5.4K · ◷

Add this agentic workflows to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/daily-issue-triage.md@1c6668b751c51af8571f01204ceffb19362e0f66