tarscloud/tars

★ 10,080C++Audience · developerComplexity · 4/5LicenseSetup · hard

Mindmap

mindmap
  root((TARS))
    Core Features
      RPC calls
      Service discovery
      Config management
    Languages
      C++ and Java
      Go and Node.js
      PHP
    Operations
      Admin console
      Monitoring stats
      Fleet deployment
    Audience
      Backend engineers
      Platform teams

mindmap root((TARS)) Core Features RPC calls Service discovery Config management Languages C++ and Java Go and Node.js PHP Operations Admin console Monitoring stats Fleet deployment Audience Backend engineers Platform teams

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Build a fleet of microservices in C++, Java, Go, Node.js, or PHP that call each other using RPC as if they were local functions.

USE CASE 2

Deploy and monitor thousands of service instances through the built-in web administration console without separate tooling.

USE CASE 3

Add centralized monitoring, statistics collection, and configuration management to a distributed system in one framework.

Tech stack

C++JavaGoNode.jsPHP

Getting it running

Difficulty · hard Time to first run · 1day+

Requires deploying the TARS registry, name service, and admin platform, Docker images available but infra coordination is non-trivial.

Use freely for any purpose including commercial use, keep the copyright notice and do not use Tencent's name to endorse your products.

In plain English

TARS is a framework for building distributed services, originally developed at Tencent under the name TAF (Total Application Framework). Tencent has used it internally since 2008, and services built on it have run across more than 16,000 machines. It is now hosted under the Linux Foundation as an open-source project. At its core, TARS provides RPC (remote procedure call), which is a way to let one service on one machine call a function on another machine across a network as if it were a local call. The framework handles the low-level communication, encoding and decoding of messages, and service discovery (finding where services are running) through a built-in name service. It also bundles monitoring, statistics collection, and centralized configuration management so these do not need to be wired up separately. TARS supports five programming languages: C++, Java, Go, Node.js, and PHP. Each language has its own client and server libraries that share the same wire protocol, so services written in different languages can talk to each other. The repository is organized as a collection of submodules, one per language plus shared infrastructure, a web-based administration console, and protocol tooling. The administration platform gives operators a single place to deploy services, view metrics, and manage configuration across a fleet of machines. This covers the operational side of running many microservices without needing to jump between separate tooling for each concern. TARS runs on Linux, macOS, and Windows. Installation can be done from source or via Docker images, with documentation at tarscloud.github.io. The license is BSD-3-Clause.

Copy-paste prompts

Prompt 1

Using the TARS Go client and server libraries, write a service definition and RPC handler that accepts a user ID and returns a user profile from a remote service.

Prompt 2

How do I deploy a new TARS microservice using the administration console and configure it to be discovered by an existing C++ TARS service?

Prompt 3

Show me how TARS service discovery works so that a Node.js service can find and call a Java service automatically without hardcoded addresses.

Prompt 4

Using TARS's built-in monitoring, add request count and p99 latency collection to my Go service with minimal code changes.

Open on GitHub → Explain another repo

← tarscloud on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.