Windows Azure Versioning Strategies

  • 160 views
Uploaded on

Windows Azure application versioning strategies

Windows Azure application versioning strategies

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
160
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Versioning Strategies Pavlo Revenkov EPAM Cloud Computing Competency Center Email: pavlo_revenkov@epam.com Skype: rp_risingstar
  • 2. Cloud Services Slots 2 Production Instance #1 v1.0 contoso.cloudapp.net Customer Instance #2 Staging Instance #1 v1.1 {guid}.cloudapp.net QAs Developers Instance #2
  • 3. Benefits PRO 3 CONTRA - Customer isolated environment - Shared scaling policies - Built-in swap capability - One environment for QAs and Devs - Shared billing - No artifacts filtering
  • 4. Different Cloud Services 4 Instance #1 contosoqa1.cloudapp.net QA Instance #2 Instance #1 contosodev1.cloudapp.net Developers Instance #2
  • 5. Comparison PRO 5 CONTRA - Isolated environments - Shared billing - Independent scaling policies - No artifacts filtering - No swap capability
  • 6. Different Subscriptions Instance #1 Instance #2 contosoqa1.cloudapp.net QA $ 350 Instance #1 Instance #2 6 Instance #1 Instance #2 contosodev1.cloudapp.net contoso.cloudapp.net Developers Customer $ 420 $ 610
  • 7. Comparison PRO 7 CONTRA - Isolated environments - No swap capability - Independent scaling policies - Support - Independent billing - Artifacts filtering
  • 8. SQL Azure Federations Tenant #2 Tenant #1 Contoso Schema v1.x Schema v2.x 8 Schema v1.0.x Tenant #2 Tenant #1 Application Application Customer #1 Customer #2 Customer #1 Customer #2 Customer #3
  • 9. SQL Azure Federations METADATA VERSIONING TENANT VERSIONING - Single metadata database - Multiple metadata database - 150 Gb per tenant - 150 Gb per version - Tenant routing - Tenant and Schema routing Familiar versioning tools can be used: - .NET Migrator - SQL Compare - etc. 9
  • 10. WCF-contracts 10 Instance #1 v1.x IServiceA Customer #1 IServiceAProxy Instance #2 Single endpoint scenario: - Support multiple versions per one contract Customer #2 IServiceA2Proxy - One endpoint per instance
  • 11. WCF-contracts 11 IServiceA Instance #1 v2.x Customer #1 IServiceAProxy IServiceA2 Instance #2 Multiple endpoints scenario: - One endpoint for one contract Customer #2 IServiceA2Proxy - Multiple endpoints at one instance
  • 12. References 12 How to Manage Cloud Services:  windowsazure.com/en-us/documentation/articles/cloud-services-how-to-manage/ WCF Versioning Strategies:  msdn.microsoft.com/en-us/library/ff384251.aspx Versioning SQL Azure:  social.technet.microsoft.com/wiki/contents/articles/7894.versioning-windowsazure-sql-database-schemas-by-using-federations.aspx
  • 13. Questions? 13