"Could you say more about why Bump's implementation of network-based queued logging is "hacked-up" while facebook's (by implication) isn't?"
Well, mainly because Scribe was purpose-built to do log aggregation on a large scale, and has nice features to prevent data loss in the event of network and node failure. It's also pretty well-tested at this point, given its origins and community. Check the wiki to which I linked.
I didn't mean my comment to imply anything negative. I was just trying to point out to the parent comment that there's now a better option than rolling a custom log aggregator on top of Redis. That may not have been true when you started your system. Mea culpa.
Comments
Could you say more about why Bump's implementation of network-based queued logging is "hacked-up" while facebook's (by implication) isn't?
To answer your question, simply put, no one here had heard about Scribe.
"Could you say more about why Bump's implementation of network-based queued logging is "hacked-up" while facebook's (by implication) isn't?"
Well, mainly because Scribe was purpose-built to do log aggregation on a large scale, and has nice features to prevent data loss in the event of network and node failure. It's also pretty well-tested at this point, given its origins and community. Check the wiki to which I linked.
I didn't mean my comment to imply anything negative. I was just trying to point out to the parent comment that there's now a better option than rolling a custom log aggregator on top of Redis. That may not have been true when you started your system. Mea culpa.