HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
TarsCloud
Tars
C++2019–2019
TarsCloud / Tars

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.

Explore on GitHubRead Hacker News discussions
3Distinct people
4Mentions
0Explicit recommenders
10.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval4 dated mentions

Observed mentions: 2019-12-17 02:30:34 UTC to 2019-12-19 08:05:56 UTC.

01232019-12-17 00:00:00 UTC to 2019-12-17 03:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 17, 00:002019-12-17 03:00:00 UTC to 2019-12-17 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-17 06:00:00 UTC to 2019-12-17 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-17 09:00:00 UTC to 2019-12-17 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-17 12:00:00 UTC to 2019-12-17 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-17 15:00:00 UTC to 2019-12-17 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-17 18:00:00 UTC to 2019-12-17 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-17 21:00:00 UTC to 2019-12-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-18 00:00:00 UTC to 2019-12-18 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-18 03:00:00 UTC to 2019-12-18 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 18, 03:002019-12-18 06:00:00 UTC to 2019-12-18 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-18 09:00:00 UTC to 2019-12-18 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-18 12:00:00 UTC to 2019-12-18 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-18 15:00:00 UTC to 2019-12-18 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-18 18:00:00 UTC to 2019-12-18 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-18 21:00:00 UTC to 2019-12-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-19 00:00:00 UTC to 2019-12-19 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-19 03:00:00 UTC to 2019-12-19 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-19 06:00:00 UTC to 2019-12-19 09:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsDec 19, 06:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 17, 00:002019-12-17 00:00:00 UTC2019-12-17 03:00:00 UTC110
Dec 17, 03:002019-12-17 03:00:00 UTC2019-12-17 06:00:00 UTC000
Dec 17, 06:002019-12-17 06:00:00 UTC2019-12-17 09:00:00 UTC000
Dec 17, 09:002019-12-17 09:00:00 UTC2019-12-17 12:00:00 UTC000
Dec 17, 12:002019-12-17 12:00:00 UTC2019-12-17 15:00:00 UTC000
Dec 17, 15:002019-12-17 15:00:00 UTC2019-12-17 18:00:00 UTC000
Dec 17, 18:002019-12-17 18:00:00 UTC2019-12-17 21:00:00 UTC000
Dec 17, 21:002019-12-17 21:00:00 UTC2019-12-18 00:00:00 UTC000
Dec 18, 00:002019-12-18 00:00:00 UTC2019-12-18 03:00:00 UTC000
Dec 18, 03:002019-12-18 03:00:00 UTC2019-12-18 06:00:00 UTC000
Dec 18, 06:002019-12-18 06:00:00 UTC2019-12-18 09:00:00 UTC000
Dec 18, 09:002019-12-18 09:00:00 UTC2019-12-18 12:00:00 UTC000
Dec 18, 12:002019-12-18 12:00:00 UTC2019-12-18 15:00:00 UTC000
Dec 18, 15:002019-12-18 15:00:00 UTC2019-12-18 18:00:00 UTC000
Dec 18, 18:002019-12-18 18:00:00 UTC2019-12-18 21:00:00 UTC000
Dec 18, 21:002019-12-18 21:00:00 UTC2019-12-19 00:00:00 UTC000
Dec 19, 00:002019-12-19 00:00:00 UTC2019-12-19 03:00:00 UTC000
Dec 19, 03:002019-12-19 03:00:00 UTC2019-12-19 06:00:00 UTC000
Dec 19, 06:002019-12-19 06:00:00 UTC2019-12-19 09:00:00 UTC303

What Hacker News says

4 sources
jayd16·Dec 19, 2019
According to this link it seems to be more than a wire protocol and seems more like a service mesh. https://github.com/TarsCloud/Tars/blob/master/Introduction.m... I see: -seems to be implemented as a library and not a sidecar? -a protobuf type protocol -client side load balancing with a name server -a consistent request queuing strategy -a web console for your services -unlike a service mesh, the scope seems to dip into things like service config -end to end request flow tracking? Hopefully someone familiar with it will flesh out the details.
In Tars: Tencent's microservice RPC framework, open-sourced to Linux Foundation

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.