Experience and knowledge sharing on cloud development and guiding the developers and companies to how take the first step towards cloud adoption.

1. Developer Journey to
Microsoft Azure
14/01/2015
Thuru

2. Scenario 1
Third
party AS2
endpoint
VM BizTalk Server VM SQL Server
Internet
On premise application

3. Things to consider
 VMs are in same region (same DC as usual placing and same affinity groups for same rack to by
pass AGG LB traffic)
 VIPs should be reserved and kept (VMs shouldn’t be de allocated)
 Multi tenant support based on the business domain.

4. Scenario 2
Web sites
Azure blob
storage
(ingest)
Azure blob
storage (output)
CDN
SQL Azure
Media service
encoder
Table
Storage

5. Things to consider
 Websites reduce the maintenance and very easy deployment.
 Standard package for custom domain support and TLS
 Different tenancy level at different layer
 SQL Azure is very cheap compared full server licensing cost.
 Blob and table storage very cheap (only LRS is used in this case)
 Media services (expensive component in this domain, shared transcoder and dedicate 2 streaming endpoints)
 CDN
 Consider storage transaction cost
 Azure egress charges
 Azure search not used 
 Scheduler added later ;)

6. Scenario 3
Web sites
Management APIs
VM + Custom SQL
Server Enterprise
License

7. Things to consider
 VMs offer greater flexibility on software customizations
 Management APIs let us programmatically control Microsoft Azure services.
 Websites are very powerful
 Accounts, subscriptions, service administrators and co administrators
 Microsoft Azure EA **

8. Pricing and SLA
http://azure.microsoft.com/en-us/pricing/
http://en.wikipedia.org/wiki/High_availability