BidNow has been significantly updated to leverage many pieces of the Windows Azure Platform, including many of the new features and capabilities announced at PDC and that are a part of the Windows Azure SDK 1.3. This list includes:
- Windows Azure (updated)
- Updated for the Windows Azure SDK 1.3
- Separated the Web and Services tier into two web roles
- Leverages Startup Tasks to register certificates in the web roles
- Updated the worker role for asynchronous processing
- SQL Azure (new)
- Moved data out of Windows Azure storage and into SQL Azure (e.g. categories, auctions, buds, and users)
- Updated the DAL to leverage Entity Framework 4.0 with appropriate data entities and sources
- Included a number of scripts to refresh and update the underlying data
- Windows Azure storage (update)
- Blob storage only used for auction images and thumbnails
- Queues allow for asynchronous processing of auction data
- Windows Azure AppFabric Caching (new)
- Leveraging the Caching service to cache reference and activity data stored in SQL Azure
- Using local cache for extremely low latency
- Windows Azure AppFabric Access Control (new)
- BidNow.Web leverages WS-Federation and Windows Identity Foundation to interact with Access Control
- Configured BidNow to leverage Live ID, Yahoo!, and Facebook by default
- Claims from ACs are processed by the ClaimsAuthenticationManager such that they are enriched by additional profile data stored in SQL Azure
- OData (new)
- A set of OData services (i.e. WCF Data Services) provide an independent services layer to expose data to difference clients
- The OData services are secured using Access Control
- Windows Phone 7 (new)
- A Windows Phone 7 client exists that consumes the OData services
- The Windows Phone 7 client leverages Access Control to access the OData services
For more details and to download Code sample of BidNow, Check this link
No comments:
Post a Comment