Service per Team
Each team is responsible for one or more business functions (e.g. business capabilities). A team owns a code base consisting of one or more modules. Its code base is sized so as to not exceed the cognitive capacity of team. The team deploys its code as one or more services. A…
- from
- Microservices
- added
- 2026-10-10
- likes
- 0
similar
-
Microservice Architecture martinfowler.com
Particular way of designing software applications as suites of independently deployable services.
-
Microservice Deployment patterns.arcitura.com
Deploys services as independent, autonomous units for improved scalability and resilience.
-
-
Distributed Capability patterns.arcitura.com
Breaks down a service capability into smaller, more manageable pieces.
-
Enterprise Inventory patterns.arcitura.com
Establishes a single, enterprise-wide inventory of services to maximize reuse and recomposition.
-
Solo-Engineer Stack github.com
Single Terraform repo wiring up Vercel + Supabase + Cloudflare + DigitalOcean as the indie-SaaS platform. One terraform apply provisions a Next.js project, a Supabase project with env vars piped to Vercel, a Cloudflare zone with R2 and Workers KV, and a DigitalOcean droplet…
Microservices › Organization Design / Team Dynamics: “Each team is responsible for one or more business functions (e.g. business capabilities). A team owns a code base consisting of one or more modules. Its code base is sized so as to not exceed the cognitive capacity of team. The team deploys its code as one or more services. A…”