High Level Overview of Windows Azure- EPC Group

Please download to get full document.

View again

All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
 4
 
  1. ã Client Layer - Used by application to communicate directly with SQL Database. ã Services Layer – Gateway between Client layer and Platform layer. ã Platform…
Related documents
Share
Transcript
  • 1. • Client Layer - Used by application to communicate directly with SQL Database. • Services Layer – Gateway between Client layer and Platform layer. • Platform Layer – Includes physical servicers and services that support the Services layer. • Infrastructure Layer – IT administration of the physical HW and OS.
  • 2. Topics to Review • Windows Azure SQL Database • Architecture • Application Connectivity • Scalability • Windows Azure Table Storage • Architecture • Querying • Best Practices and Considerations • Cost • Transactions
  • 3. Application Connectivity Considerations And Best Practices • login: [login]@[server] • Idle connections • Long running transactions • DoS guard • Failover events • Throttling • Connection pooling and Retry logic • Latency introduced for updates • No cross-database dependencies
  • 4. A Seamless Offering from the Private Cloud to the Public Cloud
  • 5. Scalability Model For The Cloud Cloud Applications • Require Scale Beyond Scale-Up • Demand the Best Economics • Best Price/Performance • Elasticity + Pay-as-you-go
  • 6. Obstacles • Defining the Tenant • Establishing Tenant’s surrogate key • Elastic Scalability (Splits/Merges/Tenant Moving) • Application Lifecycle Management (Dev; Test; Deploy; Upgrades) • Overcoming limitations of existing tools & available features • Transient nature of connectivity
  • 7. Azure Storage Architecture
  • 8. Table Storage Concepts
  • 9. Table Details Not an RDBMS! Table Entities
  • 10. No Fixed Schema
  • 11. Querying
  • 12. Purpose of the PartitionKey Entity Locality • Entities in the same partition will be stored together • Efficient querying and cache locality • Endeavour to include partition key in all queries Entity Group Transactions • Atomic multiple Insert/Update/Delete in same partition in a single transaction Table Scalability • Target throughput – 20,000 tps/partition, several thousand tps/account • Windows Azure monitors the usage patterns of partitions • Automatically load balance partitions • Each partition can be served by a different storage node • Scale to meet the traffic needs of your table
  • 13. PARTITIONKEY (CATEGORY) ROWKEY (TITLE) TIMESTAMP MODELYEAR Bikes Super Duper Cycle … 2009 Bikes Quick Cycle 200 Deluxe … 2007 … … … … Canoes Whitewater … 2009 Canoes Flatwater … 2006 PARTITIONKEY (CATEGORY) ROWKEY (TITLE) TIMESTAMP MODELYEAR Rafts 14ft Super Tourer … 1999 … … … … Skis Fabrikam Back Trackers … 2009 … … … … Tents Super Palace … 2008 PARTITIONKEY (CATEGORY) ROWKEY (TITLE) TIMESTAMP MODELYEAR Bikes Super Duper Cycle … 2009 Bikes Quick Cycle 200 Deluxe … 2007 … … … … Canoes Whitewater … 2009 Canoes Flatwater … 2006 Rafts 14ft Super Tourer … 1999 … … … … Skis Fabrikam Back Trackers … 2009 … … … … Tents Super Palace … 2008 Partitions and Partition Ranges
  • Related Search
    We Need Your Support
    Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

    Thanks to everyone for your continued support.

    No, Thanks