backend architecture

Other Community

Skill notes

Step 1: Understand the Context

Question · Why It Matters What does the service do? · Defines domain boundaries and API surface What is the expected scale? (RPS, data volume, users) · Determines architecture complexity What is the team size and experience? · Pragmatic technology selection What are the integration points? (databases, queues, external APIs) · Shapes infrastructure design

Step 2: Select Architecture Style

Style · Best For · Complexity · Team Size Modular monolith · Most new services, unclear domain boundaries · Low-Medium · 1-10 Microservices · Well-understood domains, independent deploy needs, large org · High · 10+ Serverless (functions) · Event-driven, sporadic traffic, glue logic · Low · 1-5 CQRS + Event Sourcing · Audit-heavy, complex domain, high-read scalability · Very High · 5+

Step 3: Apply Platform-Specific Patterns

Spring Boot (Java / Kotlin) Recommended structure: Key components: Concern · Recommended Approach Dependency injection · Spring IoC (constructor injection preferred)

Step 4: Design the Data Layer

Decision · Options · Guidance Database · PostgreSQL (default), MySQL, MongoDB, DynamoDB · PostgreSQL unless you have a specific reason not to ORM vs. raw SQL · ORM for CRUD-heavy, raw SQL for complex queries · Use both — ORM for simple ops, raw for performance-critical Migration · Flyway/Liquibase (Java), Alembic (Python), Prisma Migrate, golang-migrate · Always version-controlled, always forward-only

Step 5: Design Cross-Cutting Concerns

Concern · Implementation Error handling · Consistent error response format, domain exceptions mapped to HTTP codes Logging · Structured JSON logs, correlation IDs, log levels (no PII in logs) Observability · OpenTelemetry traces + Prometheus metrics + structured logs Health checks · /health/live (process alive) + /health/ready (dependencies ready)

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js · Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Understand the Context

Question · Why It Matters What does the service do? · Defines domain boundaries and API surface What is the expected scale? (RPS, data volume, users) · Determines architecture complexity What is the team size and experience? · Pragmatic technology selection What are the integration points? (databases, queues, external APIs) · Shapes infrastructure design

02
Step 2: Select Architecture Style

Style · Best For · Complexity · Team Size Modular monolith · Most new services, unclear domain boundaries · Low-Medium · 1-10 Microservices · Well-understood domains, independent deploy needs, large org · High · 10+ Serverless (functions) · Event-driven, sporadic traffic, glue logic · Low · 1-5 CQRS + Event Sourcing · Audit-heavy, complex domain, high-read scalability · Very High · 5+

03
Step 3: Apply Platform-Specific Patterns

Spring Boot (Java / Kotlin) Recommended structure: Key components: Concern · Recommended Approach Dependency injection · Spring IoC (constructor injection preferred)

04
Step 4: Design the Data Layer

Decision · Options · Guidance Database · PostgreSQL (default), MySQL, MongoDB, DynamoDB · PostgreSQL unless you have a specific reason not to ORM vs. raw SQL · ORM for CRUD-heavy, raw SQL for complex queries · Use both — ORM for simple ops, raw for performance-critical Migration · Flyway/Liquibase (Java), Alembic (Python), Prisma Migrate, golang-migrate · Always version-controlled, always forward-only

05
Step 5: Design Cross-Cutting Concerns

Concern · Implementation Error handling · Consistent error response format, domain exceptions mapped to HTTP codes Logging · Structured JSON logs, correlation IDs, log levels (no PII in logs) Observability · OpenTelemetry traces + Prometheus metrics + structured logs Health checks · `/health/live` (process alive) + `/health/ready` (dependencies ready)

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.