# TarsCloud/Tars

Tars is a high-performance RPC framework based on name service and Tars protocol, also integrated administration platform, and implemented hosting-service via flexible schedule.

Repository: https://github.com/TarsCloud/Tars
Canonical: https://ross.abutalabs.com/products/tars
Language: C++
License: BSD-3-Clause
License Family: permissive
Topics: rpc-framework, high-performance, high-availability, microservice, tars-foundation, tars
Last push: 2026-07-18T07:34:15+00:00

## Health v2 (maintenance only)
Score: 65/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 93, release rhythm 8, longevity 100
- inputs: {"age_days": 3514, "days_push": 46, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 10077, forks 2066 (observed 2026-08-28T04:10:39.483196+00:00)

## What it is
Tars is a high-performance RPC framework based on name service and the Tars protocol, with an integrated administration platform and flexible scheduling for hosting services. Originally developed at Tencent, it supports multiple languages including C++, Java, Go, Node.js, and PHP for building and managing microservice-based distributed applications.

## Use cases
- build high-performance microservices in C++ or Java
- service discovery and RPC communication between distributed services
- deploy and manage microservices with an integrated admin platform
- monitor and collect statistics for distributed services
- develop multi-language microservice applications with a unified protocol

## When to choose
- you need a battle-tested, high-performance RPC framework with proven large-scale production use
- you want an integrated solution covering RPC, name service, monitoring, and configuration management
- your team works across C++, Java, Go, Node.js, or PHP and needs a common service framework
- you need built-in service governance and administration for microservices

## When to avoid
- you prefer lightweight, single-purpose RPC libraries like gRPC without a full platform
- your stack uses languages not supported by Tars
- you want a fully managed cloud service rather than self-hosted infrastructure
- your team cannot take on the operational complexity of deploying the Tars framework

## Facets
- artifact type: framework
- maturity: stable
- function: rpc, microservices, service-discovery, monitoring, serialization, deployment
- domain: microservices, backend, developer-tools
- platform: windows, cpp, jvm, php, go, self-hosted
- tags: tars-protocol, name-service, high-performance, tencent, linux-foundation, multi-language, service-governance, linux, macos, nodejs, docker

## Member repositories
- TarsCloud/Tars (main) score 65

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:10:39.483196+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-29T17:19:51.452214+00:00, confidence not recorded.
  - readme: https://github.com/TarsCloud/Tars (fetched 2026-08-28T04:10:39.483196+00:00, sha 9f852fe05538)
- Data as of 2026-08-30T08:39:29.467469+00:00.