Twin Cities Cloud Computing User Group

In Part 1 of this series I described the problem we're trying to solve with Project Thor. In Part 2 I walked through the assumptions and business requirements. In this part I'm simply going to lay out the technincal requirements. So, without further ado, here you go:

Technical Requirements
  1. The Thor Service will be developed to run on the Windows Azure Fabric
  2. The Thor Services will be architected to support supplemental services to be added to the application as needed
  3. The Thor Services will be architected securely
  4. The Thor Services will be designed to be stateless
  5. The Thor Services will be designed to support different Exchange Providers
  6. The Thor Services will be designed to support both on premise as well as BPOS implementations of Exchange
  7. The Thor Services will include PowerShell scripts necessary to deploy and manage the Thor Services themselves

In the next part of this series I'll actually demo (via Screencast) a prototype of Thor to give you an idea of what we're going for.

Stay tuned...

(P.S. sorry for the odd formatting, Ning is a little limited when it comes to formatting one's blog posts)

Tags: azure, exchange, tag, thor

Comment

You need to be a member of Twin Cities Cloud Computing User Group to add comments!

Join Twin Cities Cloud Computing User Group

© 2010   Created by Adam Grocholski.   Powered by .

Badges  |  Report an Issue  |  Terms of Service