HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
datawire
quark
Python2015–2016
datawire / quark · Archived

quark

Quark is a specialized language for defining and implementing communication protocols in multiple languages.

2Distinct people
3Mentions
0Explicit recommenders
97GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Quark is a specialized language for defining and implementing communication protocols in multiple languages.

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:56:07 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 week3 dated mentions

Observed mentions: 2015-12-18 19:53:30 UTC to 2016-03-01 06:49:15 UTC. Weeks start Monday, UTC.

012015-12-14 00:00:00 UTC to 2015-12-21 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 142015-12-21 00:00:00 UTC to 2015-12-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-28 00:00:00 UTC to 2016-01-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-04 00:00:00 UTC to 2016-01-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-11 00:00:00 UTC to 2016-01-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-18 00:00:00 UTC to 2016-01-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 182016-01-25 00:00:00 UTC to 2016-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-01 00:00:00 UTC to 2016-02-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-08 00:00:00 UTC to 2016-02-15 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-02-15 00:00:00 UTC to 2016-02-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-22 00:00:00 UTC to 2016-02-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-29 00:00:00 UTC to 2016-03-07 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 29

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 142015-12-14 00:00:00 UTC2015-12-21 00:00:00 UTC101
Dec 212015-12-21 00:00:00 UTC2015-12-28 00:00:00 UTC000
Dec 282015-12-28 00:00:00 UTC2016-01-04 00:00:00 UTC000
Jan 42016-01-04 00:00:00 UTC2016-01-11 00:00:00 UTC000
Jan 112016-01-11 00:00:00 UTC2016-01-18 00:00:00 UTC000
Jan 182016-01-18 00:00:00 UTC2016-01-25 00:00:00 UTC000
Jan 252016-01-25 00:00:00 UTC2016-02-01 00:00:00 UTC000
Feb 12016-02-01 00:00:00 UTC2016-02-08 00:00:00 UTC000
Feb 82016-02-08 00:00:00 UTC2016-02-15 00:00:00 UTC101
Feb 152016-02-15 00:00:00 UTC2016-02-22 00:00:00 UTC000
Feb 222016-02-22 00:00:00 UTC2016-02-29 00:00:00 UTC000
Feb 292016-02-29 00:00:00 UTC2016-03-07 00:00:00 UTC101

What Hacker News says

3 sources
Here's what I've seen: 1. HTTP/JSON, with resiliency semantics layered on via SmartStack, Hystrix, or DIY library. 2. GRPC/protobuf. Haven't seen anyone other than Google run this in production, and Google doesn't really use gRPC (they use Stubby). 3. Finagle/Thrift. Twitter and some other folks use this. 4. Async message bus. Not as popular because it's not point-to-point, but it works. It's technically not RPC so it requires a different architectural approach that lots of people aren't willing to adopt. 5. Super fancy custom RPC protocol. Uber does this, for example. As does Google. You need lots of engineering to do this well, though. <plug> We've seen these design patterns over and over again, which is why we're building Quark (github.com/datawire/quark) which is a language for you to build your own custom RPC protocol (case #5 or to
Read the rest
a lesser extent #1). We're also building Datawire Connect on top of Quark which gives you resilient RPC semantics in a way that's compatible with your existing tech stack. </plug>
In Ask HN: What do you use for microservice RPC?

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.