TARS is a Linux Foundation project. It is a high-performance RPC framework based on name service and Tars protocol, also integrated administration platform, and implemented hosting-service via flexible schedule.
Tars, aka TAF(Total Application Framework), has been used in Tencent since 2008. It supports C++, Java, Nodejs and PHP for now. This framework offers a set of solution for development, maintenance and testing, which making development, deployment and testing service efficiently. It integrated extensible protocol for encoding/decoding, high-performance RPC communication framework, name service, monitor, statistics and configuration. You can use it to develop your reliable distributed application based on microservice fast, and reach fully efficient service management.
Nowadays it's used by hundreds of bussiness in Tencent, services that developed base on TAF run on 16 thousands of machines.
See the detailed introduction SUMMARY.md.
For now it supports OS as below:
For now it supports following languages:
Tars is composed of many modules, scattered in many warehouses, and the basic framework version and language version can develop independently. In view of this, from version 2.1.0, the Framework version tag is printed on the tarsframework warehouse, no longer reflected in the tars warehouse
In addition, each component will have its own version. When there is a version dependency specification, each component will have its own version
|framework||Source code implementation of C++ language framework basic service|
|cpp||C++ language framework rpc source code implementation|
|java||java language framework rpc source code implementation|
|go||go language framework rpc source code implementation|
|nodejs||nodejs language framework rpc source code implementation|
|php||php language framework rpc source code implementation|
|tup||source code implementation of tup group protocol in each language|
|web||manage tars web source implementation|
The open-source protocol Tars used is BSD-3-Clause, see LICENSE.md.
：Code submit frequency
：React/respond to issue & PR etc.
：Well-balanced team members and collaboration
：Recent popularity of project
：Star counts, download counts etc.