# ServiceWeaver/weaver

Programming framework for writing and deploying cloud applications.

Repository: https://github.com/ServiceWeaver/weaver
Canonical: https://ross.abutalabs.com/products/weaver
Homepage: https://serviceweaver.dev
Language: Go
License: Apache-2.0
License Family: permissive
Archived: true
Last push: 2025-11-20T00:44:21+00:00

## Health v2 (maintenance only)
Score: 10/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 53, release rhythm 8, longevity 95
- inputs: {"age_days": 1337, "days_push": 287, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: archived
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4821, forks 262 (observed 2026-08-28T04:09:00.524338+00:00)

## What it is
Service Weaver is a Go programming framework for writing, deploying, and managing distributed cloud applications as modular components. Components are written as regular Go interfaces and can be co-located in one process or split into replicated microservices across machines with a single deploy command.

## Use cases
- write distributed Go apps without hand-writing RPC or serialization code
- run an app locally with go run then deploy the same binary to GKE or Kubernetes
- split a modular monolith into microservices along component boundaries
- autoscale and replicate components to match load
- test and debug distributed applications on a local machine
- get built-in logging, metrics, and tracing for distributed components

## When to choose
- you are starting a new Go distributed application and want components deployable as a monolith or microservices
- you want to avoid writing networking, serialization, and service discovery boilerplate
- you deploy to Kubernetes or GKE and want single-command deploys
- you want type-safe cross-component communication guaranteed by the Go type system

## When to avoid
- you are starting a new project today - the project entered maintenance mode in December 2024 and the repository is slated for archival
- you need a framework with active community development and long-term support
- you cannot rewrite parts of an existing application, since adoption requires restructuring code around Weaver components
- you need polyglot support - the framework is Go-centric

## Facets
- artifact type: framework
- maturity: maintenance
- function: rpc, serialization, microservices, deployment, logging, monitoring, tracing, testing, routing
- domain: microservices, cloud-computing, backend, developer-tools
- platform: go, windows, cloud, cross-platform
- tags: distributed-applications, component-framework, monolith-to-microservices, google, archived-project, linux, macos, kubernetes

## Member repositories
- ServiceWeaver/weaver (main) score 10

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:09:00.524338+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:18:31.930157+00:00, confidence not recorded.
  - readme: https://github.com/ServiceWeaver/weaver (fetched 2026-08-28T04:09:00.524338+00:00, sha 9aa5e7ad1b22)
  - homepage: https://serviceweaver.dev (fetched 2026-08-29T09:01:25.338253+00:00, sha 796e0cf8bdeb)
  - site_page: https://serviceweaver.dev/docs.html (fetched 2026-08-29T09:01:25.347593+00:00, sha dca73873bcab)
- Data as of 2026-08-30T08:39:29.467469+00:00.