Live data from Hacker News

Scribe: Transporting petabytes per hour via a distributed, buffered queueing

engineering.fb.com

1–10 of 44 posts

Re: Scribe: Transporting petabytes per hour via a distributed, buffered queueing

#4

Keep in mind the network cost of petabytes per hour cross continent. Those of us who don't own our own cross-ocean fiber can't afford to design systems like this.

Never underestimate the bandwidth of a cargo ship full of SSDs.

(I'm paraphrasing an old, old joke.)

Re: Scribe: Transporting petabytes per hour via a distributed, buffered queueing

#6
post #5

Naming is hard! Facebook used to have a _different_ Scribe ( https://en.wikipedia.org/wiki/Scribe_(log_server) ). We used it at a company I worked for, but it had long-since been deprecated, so I was confused when I saw this Scribe.

This is the same scribe. Facebook closed-sourced it because it was too hard to maintain an open version and a version that addresses Facebook's needs.

Re: Scribe: Transporting petabytes per hour via a distributed, buffered queueing

#7
post #3

Keep in mind the network cost of petabytes per hour cross continent. Those of us who don't own our own cross-ocean fiber can't afford to design systems like this.

Sounds like a startup idea.

Level 3 and Vodafone have a bit of a first mover advantage here

Re: Scribe: Transporting petabytes per hour via a distributed, buffered queueing

#8
post #4

Keep in mind the network cost of petabytes per hour cross continent. Those of us who don't own our own cross-ocean fiber can't afford to design systems like this.

Never underestimate the bandwidth of a cargo ship full of SSDs. (I'm paraphrasing an old, old joke.)

Fairly high latency though I guess.
Post reply on HN