Jaiku goes Open Source: a Case Study

In a matter of hours, Google announced 3 major cuts relating to HR (Recruiting Organization & Engineering) and Products. Fortunately, the search giant decided to spare Jaiku, a similar microblogging service to Twitter, by releasing its code under the Apache license and porting it to the Google App engine.

This move reflected one of the solutions proposed in my previous post on “How to make our Life 2.0 eternal“, in which we agreed that open sourcing a service would make better sense than putting an end to it. Google’s decision to keep Jaiku alive as an Open Source platform will benefit the infant Jaiku community and present the service with unpredictable opportunities when external developers join force.

When we plan new engineering projects at Twitter, we measure our requirements against the capabilities of open source offerings, and prefer to use open source whenever it makes sense. By this approach, much of Twitter is now built on open source software.

In the recent post:”Building on Open Source“, Twitter has summarized the role that Open Source software plays in the company, and released two of its projects: Kestrel, a message queue server we use to asynchronously connect many of the services and functions underlying the Twitter product and Cache-Money, an elegant write-through caching plugin for Ruby on Rails, as Open Source. In all likelihood, unless a revenue stream can be realized, in the worst scenario Twitter will go Open Source, one step in the right direction.

Ideas?

This entry was posted in open source, web services and tagged , , , , , , , , , . Bookmark the permalink.

One Response to Jaiku goes Open Source: a Case Study

  1. Dan says:

    Actually, in the worst scenario Twitter gets bought by Facebook :)

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>