Azure in Developer Perspective


Published on

My slide deck used in Cloud Computing Seminar, 4 December 2010, Universitas Atmajaya, Yogyakarta

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Azure in Developer Perspective

  1. 1. Developing Azure SolutionIn Developer PrespectivesRiza OktavianClient Development Specialist | Microsoft Innovation CenterYogyakarta, Indonesia
  2. 2. Azure for Developer Audiences Web Corporate ISV  Develop applications at  Extend existing and build  Accelerate SaaS solutions Internet scale new applications development  Focus on business logic and  Accelerate Innovation with  Deepen customer not operational constraints new IT flexibility relationships and continuously provide new  Use one platform for  Use consistent, familiar value expansive user experience programming models & and device support tools  Capture built-in multi- tenancy  Get started quickly using  Maintain enterprise your existing skills architecture & process  Inherent extensibility & governance integration features  Reach broad market with Microsoft Live properties  Integrate applications with partners across networks Flexibility Reliability Scalability Security Interoperability
  3. 3. Cloud Service Anatomy Web Role Web Role 1 (IIS) Worker Role 1 Web Role Port 80 LB Web Role 2 (IIS) Port 8080 Worker Role 2 Worker Role 2Windows Azure Storage SQL Azure Internet Services (Table, Blob, Queue)
  4. 4. Developing in Azure DifferencesAzure Solutions have a Cloud Project – Describes the platformAdditional Entry Points in the Execution PipelineUse RoleEnvironment Class for Infrastructure knowledgeAlways Copy referenced Assemblies
  5. 5. WorkerRole Call OrderWaWorkerHost process is started. Worker Role assembly is loaded and surfed for a class that derives from RoleEntryPoint. This class is instantiated. RoleEntryPoint.OnStart() is called. RoleEntryPoint.Run() is called. If the RoleEntryPoint.Run() method exits, the RoleEntryPoint.OnStop() method is called .
  6. 6. WebRole Call Order WaWebHost process is Global.Application_End() RoleEntryPoint.OnStop() started. is called. is called. Hostable Web Core is Hostable Web Core is The web application runs… activated. deactivated. Web role assembly is loaded and Global.Application_Start() WaWebHost process is RoleEntryPoint.OnStart() is called. stopped. is called.
  7. 7. SQL Databases MIC • aspnetdbWeb Application • MIC WCF Service Intranet Offices Location
  8. 8. SQL Databases MIC • aspnetdbAzure Application • MIC ServiceBus Service Intranet Offices Location
  9. 9. Demo Porting the Web into Azure ApplicationPAGE 9
  10. 10. Migrating SQL Server Data to SQL AzureUse the Azure Portal for initial creationUse SQL Server Management Studio 2008 R2 for managingSQL Azure databasesUse SQL Azure Migration Wizard v3.2 for analyzing andgenerating migration db scripts
  11. 11. Migrating Intranet Service to App FabricSBChange Service and Client implementationAdd a ServiceBus ReferenceCreate a Service Bus namepsaceGenerate a new Endpoint AddressUse a RelayBinding from Azure AppFabric SDKAdd a TransportClientEndpointBehavior for registering the Service to the Service Bus
  12. 12. Windows Azure DiagnosticsDeveloper Prespectives SDK component providing distributed monitoring & data collection for cloud apps Support Standard Diagnostics APIs Cloud-Friendly – Manage multiple role instances centrally Scalable – Built on Windows Azure Storage & used by scale-out Windows Azure platform components Developer In Control – What to collect & when to collect it
  13. 13. Development Best Practices Always develop in the Azure DevFabric first Make sure you copy local assemblies not in the Framework Use the _CSPACK_FORCE_NOENCRYPT_ to check if your package is valid Check application using Cloud Resources (Storage, Service and SQL Azure) Remove the use of Development Storage (in case some code uses it)
  14. 14. Azure Supporting TechnologyPHP, Java, othersPAGE 14
  15. 15. ConclusionAzure gives us fexibility in development• Specific Development API in Azure• Casual Development Scenario• Development Best Practices• Technology Supports in Azure
  16. 16. Thank you. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Internet Explorer and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.