bbromhead
Joined 14 years ago
Joined 14 years ago
It provides works on both HTTP (including GET based posting) and DNS (including posting) as the two transport mechanisms. Giving agents in constrained environments flexible options for circumventing certain controls.
What largely started off as a half baked idea / half joke turned into a fun project that explored a wide range of concepts from DNS tunneling to economic schelling points.
There is already some minor agent activity, but from mostly people pointing their own agents at it. We will see if it ever gets discovered by agent swarms from some of the larger AI labs!
Check out https://www.instaclustr.com/careers
We work with companies like Doordash, Atlassian, Sonos and Dream 11 running some of their most important databases at massive scale.. and these are just the ones we can mention.
On top of that we are in Canberra :) Though if you wanna stay in Sydney or Melbourne that's cool to!
https://www.instaclustr.com/blog/2016/10/19/patched-cassandr...
For any given replication factor in Cassandra, overhead remains the pretty much the same irrespective of whether you have 300 or 3 nodes. So should the latency.
On top of that both BigTable and Cassandra use SSTables to store the data on disk (with all the compactiony goodness that goes with them), so I'm even more surprised that the difference in latency is so huge.
Would love to see the scripts for the benchmarks! I don't want to take away from a great product launch and I'm sure BigTable kicks arse in certain areas that Cassandra doesn't... I'm just surprised at the differences in latency.
http://googlecloudplatform.blogspot.com/2014/03/cassandra-hi...
How did the latency for Cassandra on their cloud platform increase by 200ms from a year ago?