Incubation: Looking glass -Progression to Windows Azure

Patrice PellandPrincipal Dev Manager, Microsoft Corp.

Social Monitoring – Incubation• Social Monitoring incubation project codename Looking Glass

• Silverlight 4 application, Windows Phone 7 application and iPhone/iPadapplication – Code Reuse.

• Progression of the back end from

• Windows Server 2008 R2 with WCF Services, SQL 2008 R2

• Windows Azure (Web Roles and Worker Roles), SQL Azure

• Windows Azure (Web Roles and Worker Roles), SQL Azure, Azure Storage (Table Store, Blob storage)

WP 7 Application

Code Re-Use Explorations• Since Silverlight is X-Platform and X-Browsers we

were able to have our project run (with the SL download) across browsers and cross OS.

• Worked on PCs, Mac OSx and Linux (via Moonlight)

• Worked on iPhone/iPad via Monotouch

• Kept 85% of the code to have the code run on

iPhone/iPad and Linux.

Back End Progression – Phase 1

Why it did not scale?• Regular Social APIs with limitations on # of

calls

• Generic Data Acquisition Service

• No partitioning

Back-End Progression – Phase 2

Scalability issues still there for the back end…

• Crawling became more scalable with worker queues

• Still not the complete data corpus and not fast enough to query – Full text index and tag indexes

Bing Data Agg.LGData Aggregators

LG SQL Azure

Bing IndexersLGIndexers Sentiment

Processing

CDN (xaps, jpg, png, css, …)Web Roles WCFWeb Roles

LG Worker Role Media Posting

Incubation v2.0 Phase 3

Visualization Services

LG – LMIData Agg.

Bing + LGData AggregatorsInternet

LG Azure

Bing Azure

Sentiment Processing

Azure Blob Storage –

Backup Index

Conclusion…

• Moving to Azure was cost effective

• Reliable, scalable and available

• Changing the approach to using indexers gave us a more interesting and complex query and filtering capability.