Twitter's 'Starling' Released as Open Source
Twitter has a warm spot for innovative simplicity and an open approach to technology development. We make use of open source software when it makes sense and we think it brings good karma to contribute back to the open source community whenever possible.
However, our open approach is more than just good karma. Twitter, Inc. is committed to building a reliable social messaging utility which people trust enough to use every day. Gaining trust means showing our work. When a technology is shared, conversations and understanding form around it.
Our open approach is very much driven by Twitter engineers like Blaine Cook. Blaine coded the distributed queue server Twitter uses to route vast numbers of messages in the background so front-end response time can remain quick.
Starling is a light-weight persistent queue server that speaks the MemCache protocol. It was built to drive Twitter's backend, and is in production across Twitter's cluster. There's a little more about Starling on the Twitter Developer Blog. And here is the Starling page at RubyForge.
However, our open approach is more than just good karma. Twitter, Inc. is committed to building a reliable social messaging utility which people trust enough to use every day. Gaining trust means showing our work. When a technology is shared, conversations and understanding form around it.
Our open approach is very much driven by Twitter engineers like Blaine Cook. Blaine coded the distributed queue server Twitter uses to route vast numbers of messages in the background so front-end response time can remain quick.
Starling is a light-weight persistent queue server that speaks the MemCache protocol. It was built to drive Twitter's backend, and is in production across Twitter's cluster. There's a little more about Starling on the Twitter Developer Blog. And here is the Starling page at RubyForge.
4 Comments:
Nice work. Hopefully I will not see the blue bird as much any more :)
Hi,
I've tried to write this message to your 'request' mail but, as I got no answer, I'll try this blog:
Recently, I've found a twitter profile with my name, my picture and my studio's website link. Unfortunately, it's not mine - someone else took my identity and registered a false identity at your website.
I'd like to ask you to help solving this problem. My name is Gustavo Piqueira and my (real) email is gustavo@rexnet.com.br
Thanks for your cooperation, hope you understand the number of problems of having a false profile can cause.
Best regards
Gustavo
A question. Is Starling a fundamentally different solution from the proxy service that AssetBar proposed on February 8?
Have you checked out ThruDB's persistent queuing service? It seems to achieve similar aims - very high throughput, open source and persistent.
Post a Comment
Links to this post:
Create a Link
<< Home