tylertreat

11 ms·

91.
FIFO, Exactly-Once, and Other Costs(bravenewgeek.com)
1 points by tylertreat 9y ago|0 comments
92.
Systems Software Research is Irrelevant (2000) [pdf](herpolhode.com)
2 points by tylertreat 9y ago|1 comments
93.
Are We There Yet: The Go Generics Debate(bravenewgeek.com)
6 points by tylertreat 9y ago|2 comments
94.
Adventures in bit arrays/SIMD (Go)(engineering.rain.services)
3 points by tylertreat 9y ago|0 comments
95.
Engineering Empathy(bravenewgeek.com)
4 points by tylertreat 9y ago|0 comments
96.
The Future of Ops(bravenewgeek.com)
5 points by tylertreat 9y ago|0 comments
97.
Show HN: Kaput.io – hot takes on systems(kaput.io)
6 points by tylertreat 10y ago|1 comments
98.
Pain-Driven Development: Why Greedy Algorithms Are Bad for Engineering Orgs(bravenewgeek.com)
2 points by tylertreat 10y ago|0 comments
99.
Fast Topic Matching(bravenewgeek.com)
1 points by tylertreat 10y ago|0 comments
100.
Considerations for Building Reliable Systems(bravenewgeek.com)
3 points by tylertreat 10y ago|0 comments
101.
Benchmarking Commit Logs(bravenewgeek.com)
1 points by tylertreat 10y ago|0 comments
102.
You Are Not Paid to Write Code(bravenewgeek.com)
328 points by tylertreat 10y ago|167 comments
103.
Shit Rolls Downhill(bravenewgeek.com)
2 points by tylertreat 11y ago|0 comments
104.
Abstraction Considered Harmful(bravenewgeek.com)
2 points by tylertreat 11y ago|0 comments
105.
So You Wanna Go Fast?(bravenewgeek.com)
95 points by tylertreat 11y ago|35 comments
106.
by tylertreat 11y ago
Performance mainly, I think. Benchmarking against UUID v4 shows a ~175% speedup.
107.
NUID – An entropy friendly and highly performant unique identifier generator(github.com)
40 points by tylertreat 11y ago|18 comments
108.
Benchmarking Message Queue Latency(bravenewgeek.com)
50 points by tylertreat 11y ago|9 comments
109.
From the Ground Up: Reasoning About Distributed Systems in the Real World(bravenewgeek.com)
34 points by tylertreat 11y ago|0 comments
110.
Show HN: Bench – A generic latency benchmarking library(github.com)
37 points by tylertreat 11y ago|0 comments
111.
Infrastructure Engineering in the 21st Century(bravenewgeek.com)
1 points by tylertreat 11y ago|0 comments
112.
Probabilistic algorithms for fun and pseudorandom profit(slideshare.net)
20 points by tylertreat 11y ago|1 comments
113.
by tylertreat 11y ago
Curious how this compares to gnatsd: https://github.com/nats-io/gnatsd
114.
You Own Your Availability(bravenewgeek.com)
1 points by tylertreat 11y ago|0 comments
115.
Breaking and entering: lose the lock while embracing concurrency, part 2(techblog.workiva.com)
25 points by tylertreat 11y ago|0 comments
116.
Muxy – Simulating real-world distributed system failures(github.com)
2 points by tylertreat 11y ago|0 comments
117.
by tylertreat 11y ago
A latency/throughput benchmark comparing the two is effectively comparing the latency/throughput of a socket from A to B. The same benchmark for NATS would be a socket from A to NATS and NATS to B. Obviously the latency of going o
118.
by tylertreat 11y ago
> * clustering - what kinds of clusters are supported? How do they scale? Do they favor availability or consistency? There is no persistence so consistency is irrelevant. NATS does everything in the name of availability to the point of d
119.
by tylertreat 11y ago
Well, for one, there is no streaming socket API, just HTTP. I suspect the 5 reads/sec limit on shards is mainly due to multitenancy, but I could see this increasing in the future. Amazon has already improved the latency of Kinesis a fa
120.
by tylertreat 11y ago
In my experience, Kinesis' performance makes it a nonstarter for low-latency systems and use cases with many consumers. Shards are limited to 5 reads/sec, so consumers are heavily throttled. Producers also have significant put lat

More ›