The document discusses architectural decisions for building applications in Windows Azure. It covers key concepts like multi-tenant vs single-tenant architectures, database design choices, authentication and authorization options, and scalability strategies. Technologies discussed include Windows Azure storage, SQL Azure, and identity frameworks that can be used. Overall strategies for cost optimization like statelessness and asynchronous operations are also presented.

1. Arhitecturi de aplicatii in windows azure Mihai Tătăran Director, H.P.C. Consulting Microsoft MVP Mihai.tataran@hpc-consulting.ro http://www.hpc-consulting.ro/index.php/blog/ http://codecamp.ro

2. Despre … Mihai H.P.C. Consulting Microsoft MVP Codecamp: http://codecamp.ro Voi

3. Tags Software as a Service Windows Azure Arhitecturi de aplicatii Deployment Identitate

4. Strategiaarhitecturalapentruaplicatii in Cloud “Aplicatieinstalataca un serviciugazduit in nor siaccesataprin internet” Line of business, e.g.: SalesForce Consumer, e.g.: Hotmail, *-mail  Software-as-a-Service Breaking change … in modelul de business, in modul de realizaresi in modul de operare a aplicatiilor

5. Modificareamodelului de business Aplicatia nu maista la client Operareaaplicatiei nu o mai face vendor-ul Crestereaprofitabilitatii: scalare, specializare Long Tail… The Long Tailhttp://www.wired.com/wired/archive/12.10/tail.html

6. Costurile de operare (on premises)

7. Costurile de operare (SaaS)

8. SaaS Crestereaprofitabilitatii Economy of scale Specializare

9. DeciziiArhitecturale Multi / Single – tenant? Cum rezolviproblemaunorserviciidiferite per client?

11. Deciziiarhitecturale Baza de date 1 instantapefiecare client? 1 instanta, cu schema per client? 1 singurainstanta? Cum rezolviproblemaunor date diferiteca schema de la un client la altul? Dar problemasecuritatii?

12. Deciziiarhitecturale Autentificareasiautorizarea Vendorul Clientiivendorului: Active Directory?, altceva?, nimic? Utilizatorii (clientiiclientului): Facebook?, Gmail?, LiveID?

15. Deciziiarhitecturale Scalabilitate State-less Operatiicostisitoare (I/O) asincrone Resource pools (conexiunidb, threads) Caching

16. Tehnologie

17. Windows Azure Scurtadefinire

18. CLOUD COMPUTING INFRASTRUCTURE PLATFORM SOFTWARE AS A SERVICE AS A SERVICE AS A SERVICE IT as a Service

19. Private (On-Premise) Infrastructure (as a Service) Platform (as a Service) Types of Clouds You manage Applications Applications Applications You manage Runtimes Runtimes Runtimes Security & Integration Security & Integration Security & Integration Databases Databases Databases You manage Servers Servers Servers Virtualization Virtualization Virtualization Server HW Server HW Server HW Storage Storage Storage Networking Networking Networking

20. Windows Azure Cloud Service Anatomy Worker Role 1 Web Role Web Role Web Role 1 (IIS) Port 80 LB Web Role 2 (IIS) Port 8080 Worker Role 2 VM Role Windows Azure Storage (Table, Blob, Queue) SQL Azure

21. Comparison of Role Types Web Role : The Role Is Hosted On IIS 7.5 Worker Role : The Role Is an executable (you can create your own web server, host a database, …) VM Role : The role is the VM. Use Windows services, scheduled tasks, etc. You configure and maintain the OS. Admin Web / Worker Role VM Role Web / Worker Role Abstraction (i.e. Less IT & Less Plumbing Code) Control

22. Windows Azure - costuri Compute (per instanta de rol) SQL Azure (per instanta de DB) Windows Azure storage (per # tranzactii) Date transportate in / out http://www.microsoft.com/windowsazure/offers/default.aspx

23. Deciziiarhitecturale – alegereatehnologiilor Win Azure storage: BLOB, Queue SQL Azure Microsoft Extensibility Framework Windows Identity Foundation App Fabric Access Control Service (Active Directory Federation Services) ASP.NET MVC – Authorization attributes

24. Resurse http://www.microsoft.com/windowsazure/

25. ?