TweetDeck and Google App Engine: A Match Made in the Cloud

I'm Reza and work in London, UK for a startup called TweetDeck. Our vision is to develop the best tools to manage and filter real time information streams like Twitter, Facebook, LinkedIn and MySpace. We offer products like our TweetDeck desktop client built on Adobe AIR, and our iPhone application. We are happy to say that we use App Engine as key part in our backend.

We're a small startup, so early on we started to look for tools that would give us the biggest bang for our buck. Combined with the fact we love Python, we thought it might be worth taking a look at what Google App Engine had to offer. The first feature we started playing with was the mail sending facility.

It was easy! Sending mail was a single call-- no messing around. Combined with the fact that it was sent via tried-and-tested Google Mail servers, this meant that we had a simple mailing solution where we didn't have to deal with spam blacklists, mail retries or SPF records. We could really see App Engine being our sole email provider for transactional emails (new users and forgotten passwords), but also for newsletter-type mailing.

When we got started, our existing backend was hosted on Amazon EC2 and SimpleDB, and we knew that we needed a way for the two systems to communicate with each other. App Engine provides all the basic tools to define any sort of resources you want--but more importantly, it has the Python standard library. We implemented a small mail API, with authentication provided by an HMAC-SHA1 of the request information and a shared secret key. The API has been made extremely general: its JSON input format contains fields to send messages to blocks of email addresses that are either defined in the request itself, or which exist as a template in App Engine (templates are defined as strings in a Python module).

The whole setup currently works quite well. We're already extending our mailing system to use App Engine's task queues-- exposing a number of queues to break large mailing jobs into a series of subtasks, thus spreading mailing sending over a large period of time. We have plans to make an even tighter bridge between our EC2 systems and App Engine, which involves keeping our subscriber list entirely in App Engine, and adding and removing from that list as appropriate.

We also use App Engine for various other prototypes and smaller applications that are part of our product. We use it to serve our "TweetDeck Recommends" feed, and we've even developed small tools to apply TweetDeck fan badges on Twitter homepage backgrounds using the Imaging API! The lesson from us, of course, is that using something like App Engine doesn't have to mean everything runs on it. It's an extremely good platform for creating APIs or smaller parts of your application that do specific tasks, and do them well. Think of it as the UNIX metaphor applied to the Cloud.

We love that we've been able to grow the functionality that Tweetdeck provides by progressively using more of the cloud. App Engine provides the perfect platform to compose new services quickly, iterate on them in production, and scale with demand as Tweetdeck's install base grows. Thanks to App Engine and the cloud, there's nothing holding us back from tackling the needs of our user base.

Here is a video interview of Reza and the Tweetdeck team.

Guest Post by Reza Lotun @rlotun, TweetDeck

Satellite LTE Network Planned by PE Firm

Harbinger Capital Partners plans to deploy a LTE network over spectrum owned by a few satellite companies which would create an open wholesale wireless network available to anyone who wants to offer mobile broadband. The new network will rely initially on 23 MHz spectrum owned by SkyTerra (which is owned by Harbinger) and could later include spectrum from Terrestar Networks, another satellite firm in which Harbinger holds a stake.


The network could help ensure competition among the major wireless carriers because of the conditions the FCC has placed on the spectrum that the private equity firm plans to use as part an agreement to let Harbinger take control of SkyTerra. SkyTerra would be a wholesaler, and that traffic from the wireless carriers in the U.S. cannot comprise more than 25 percent of the traffic over the SkyTerra/Harbinger network. This means AT&T and Verizon could not buy up huge chunks of the network or spectrum to keep others off of it.

The planned network would launch before the end of 2011 and cover 9 million people (trials initially planned for Denver and Phoenix). Then cover 100 million people by the end of 2012, 145 million by the end of 2013 and at least 260 million people in the United States by the end of 2015. Harbinger said in its statements to the FCC that all major markets will be installed by the end of the second quarter of 2013.

However, the 36,000 base stations that Harbinger plans to use, along with the tower sites, backhaul, etc. with a terrestrial network will require billions of dollars. Verizon and Clearwire have already started building out their networks and are investing billions. It is hard to see how Harbinher could afford to do this. According to SkyTerra, the network will have no less than 23 MHz of spectrum, consisting of 8 MHz of 1.4 GHz terrestrial spectrum, access to 5 MHz of 1.6 GHz terrestrial spectrum and 10 MHz of MSS/ATC L-band spectrum. Through a cooperation agreement with Inmarsat and associated waivers of the Commission�s ATC rules, by 2013 Harbinger will have access to an additional 30 MHz of ATC spectrum.

It will be interesting to see how this turns out.