Windows Azure Team 9

1
Windows AzureTeam 9

• Ben Holland
• Bao Nguyen
• Eric Petrowiak
• Barret Schloerke

2
Problem Statement

• Windows Azure (Cloud hosting platform) is new and
  bugs need to be found
• Playing the role of 3rd party developer to design
  and implement a web system which should then be
  migrated to the Microsoft Azure Cloud.
•  
• Must use
• Silverlight
• Azure, Microsoft SQL, RIA Services

3
Requirements

• Create an application that tests Azures
  capabilities and general issues
• Cloud Hosting Power
• Security/Personalized Information
• Integration with application
•  
• Use Required Systems
• Windows Azure
• Silverlight
• RIA
•  
• Document cloud migration issues
• At the same time choose a challenging project
  that we can enjoy working on

4
Project Proposal

• A Personalized Reader
• Fetches articles or blog posts that matches your
  search criteria
•  
• This differs from other search engines
• Our system allows for passive users
• Searches specific stories on specific domains
• Proactive search apposed to reactive (on demand)
• Users history/results are saved

5
Concept Diagram
6
Development Environments

• Visual Studio 2008
• .NET framework
• Silverlight
• RIA
• Azure SQL
• Subversion
• Virtual Machines with remote access

7
Customer Functional Requirements

• Must be hosted on the Azure Platform
• Must use Silverlight for the user view
• Must use RIA Services to perform the middle tier
  operations
• Must be a user centric applications which
  includes user profiles
•  
• Ability to iteratively update application once
  already installed on Azure

8
Customer Non-Functional Requirements

• User security (profile and user data is private)
•  
• Project must scale with user traffic
  appropriately (throttling)
•  
• Background operation of fetching materials is
  efficient (third party libraries and throttling)

9
Architectural Sequence Diagram
10
Sequence Diagrams
11
(No Transcript)
12
(No Transcript)
13
(No Transcript)
14
(No Transcript)
15
Demo

• Show Demo of Cloud Reader Application
•  
• Login Functionality           
• Atomic CRUD Operations

16
Design Constraints

• How to add different search engines?  
•     (Modularization)
• How do different search engines return results? 
•     (Hierarchical interfaces, Results -gt
  ImageResult, TextResult)
• How can we throttle the processing usage? 
•     (Thresholds for computed time to complete
  queues) 
•  
• How can we limit exceeding our allocated storage
  resources?
•     (User quotas)

17
Technical Approaches (Overview)
18
Technical Approaches (Entity Framework)
19
Technical Approaches (Server Side Framework)
20
Testing Description

• Automated unit tests 
•     (Entity CRUD Operations, Search engine
  queries)
• Visual inspection 
•     (Interface interaction)
• Stress/Performance testing 
•     (High/Medium/Low load testing, throttling
  inspection)

21
Measurable Milestones

• Twitter working on one account
• More than one data source working
• Migrate application to Microsoft Azure Cloud
• Full Scale Testing / Real Time Interaction
•  
• Ability to demonstrate throttling abilities

22
Risks

•  Learning Curve (New technology,
  confusing/conflicted documentation)
•  
• Server side processing
• Interface Usability (Silverlight issues)
•  
• Third Party API limitations (Rate limiting on
  Twitter, Digg, Reddit, ect.)
• Migrating to Azure Cloud (Compatibility issues)
•  
• Client does not want the application instead,
  they want to know the difficulties we faced

23
Project Resource Costs

• Project Hosting (break down on following slide)
• Microsoft has provided student software site
  licenses
•  Visual Studio IDE
•  Microsoft SQL Server
•  Windows Server

24
Hosting Costs
25
Conclusion

• A lot of progress has been made and we about on
  par with our original aggressive goals.

26
Conclusion

• Positive Feedback from Microsoft
•  
• Positive Feedback from Adviser
•  
• Working Demo produced to perform atomic CRUD
  operations on entities and user account
  authentication
•  
• Progress is starting on the background server
  operations

27
Plan for Next Semester

• Labels
• "Creating a Label", "Saving a Label", and
  "Editing a Label"
• 4/30/2010
• Rules
• "Scheduling Rules", "Rule Based Searching", "view
  Results", "Remove Results", and "Remove Label"
• 5/31/2010
• Validation and Throttling
• 6/30/2010
• Rule Support
• 7/31/2010
• Search Digg and Twitter
• 9/30/2010
• Stress Test
• 10/31/2010
• Final Documentation