SlideShare a Scribd company logo

Cloud and Windows Azure

•
•
Radu Vunvulea
Radu Vunvulea

The document introduces cloud computing and cloud services. It defines cloud computing as using computing resources delivered over a network as a service. It then provides information about Radu Vunvulea and his background. The document outlines an agenda to cover cloud computing topics but does not fill in the agenda items. It also includes sections on cloud characteristics, cloud providers, market forecasts, Azure components, execution models, machine sizes, data management, queues, caching, and other Azure services.

Related slideshows

Windows azure camp
Windows azure campWindows azure camp
Windows azure camp
 
Oracle Java Cloud Service JCS (and WebLogic 12c) - What you Should Know
Oracle Java Cloud Service JCS (and WebLogic 12c) - What you Should KnowOracle Java Cloud Service JCS (and WebLogic 12c) - What you Should Know
Oracle Java Cloud Service JCS (and WebLogic 12c) - What you Should Know
 
Windows Azure Virtual Machines
Windows Azure Virtual MachinesWindows Azure Virtual Machines
Windows Azure Virtual Machines
 
1 of 51
Introduction to Cloud Era Radu Vunvulea vunvulear@gmail.com http://vunvulearadu.blogspot.com
Cloud and Windows Azure
Cloud computing is the use of computing resources (hardware and software) that are delivered as a service over a network (typically the Internet). Source: Wikipedia
Who am I? { “name” : “Radu Vunvulea, “company” : “iQuest”, “userType” : “enthusiastic” “technologies” : [ “.NET”, “JS”, “Azure”, “Web”, “Mobile”, “SL” ], “blog” : “vunvulearadu.blogspot.com”, “email” : ”vunvulear@gmail.com”, “socialMedia” : { “twitter” : “@RaduVunvulea”, “fb” : “radu.vunvulea” } }
Agenda • ? • ? • ? • ? • ? • ? Agenda
Cloud computing is the use of computing resources (hardware and software) that are delivered as a service over a network (typically the Internet). Source: Wikipedia
Test patterns • Pass/Fail Patterns • Data Driven Test Patterns • Performance Patterns • Simulation Patterns • Stress-Test Patterns • ….
Five essential characteristics 1. On-demand self-service 2. Broad network access 3. Resource pooling 4. Rapid elasticity 5. Measured service
Five essential characteristics 1. On-demand self-service 2. Broad network access 3. Resource pooling 4. Rapid elasticity 5. Measured service
Five essential characteristics 1. On-demand self-service 2. Broad network access 3. Resource pooling 4. Rapid elasticity 5. Measured service
Five essential characteristics 1. On-demand self-service 2. Broad network access 3. Resource pooling 4. Rapid elasticity 5. Measured service
Five essential characteristics 1. On-demand self-service 2. Broad network access 3. Resource pooling 4. Rapid elasticity 5. Measured service
Cloud and Windows Azure
Cloud and Windows Azure
Cloud and Windows Azure
Test patterns
Cloud is offered by … • Microsoft • Google • Amazon • Hewlett-Packard • IBM • CenturyLink/Savvis • Verizon/Terremark • Joyend • Citrix • Bluelock • Vmware • Rackspace • Salesforce
Market forecast
Components of Windows Azure • Microsoft • Google • Amazon • Hewlett-Packard • IBM • CenturyLink/Savvis • Verizon/Terremark • Joyend • Citrix • Bluelock • Vmware • Rackspace • Salesforce
Execution models
Web Sites • Easy to deploy • No OS management • Scaling • Monitoring • Publish from different source controls • Support different technologies (PHP, node.js, .NET) • Low cost support – shared mode • Reserved mode – dedicated instance • Each site run in an isolated environment
Web Roles • Used to host application composed from multiple tiers • Each web-role is scalable independently • In comparison with Azure Websites, a lot of custom configuration can be done • Network isolation • Any kind of framework can be used in this machines
Worker role • Perfect place to run long running task • Can be used with success with web-roles for tasks that run in background • Cannot be used to host a web application • In the moment when the “WHEN(TRUE)” ends the worker role process stop • Can be seen as a process that can execute a specific type for an infinite period of time
Virtual Machine • Can be used to install any kind of operating system from Windows to Linux • Build in support and images available for different versions of Linux  and Windows. • Custom machines can be created with our own VHD • Build in support for MongoDB, MySQL, Cassandra, certificates • Migration from on-premise to cloud and cloud to on-premise can be done using VHD
Size of the machines Disk Space for Disk Space for Local Storage Allocated Virtual Local Storage CPU Cores Memory Resources in Bandwidth Machine Size Resources in a Web and (Mbps) VM Role Worker Roles ExtraSmall Shared 768 MB 19,480 MB 20 GB 5 Small 1 1.75 GB 229,400 MB 165 GB 100 Medium 2 3.5 GB 500,760 MB 340 GB 200 Large 4 7 GB 1,023,000 MB 850 GB 400 ExtraLarge 8 14 GB 2,087,960 MB 1890 GB 800
Data management
SQL Database • Relational database based on SQL Server • It is almost like SQL Server from on-premises • BUT: • We don’t have support for distributed transactions • Each table have to contain at least one cluster index • We cannot attaché a database • We don’t have support for jobs • Double check the total cost of a having a SQL Database – there are a lot of times when we can use Table Storage Service
Table Storage Service • Store any kind of serializable data • You don’t need any kind of complex data structure or SQL knowledge. • Is not a relational database • In the same table you can have more than one type of entity • Each entity from can have maximum 252 properties + 3 default • The maximum size of total tables cannot accede 100.000 GB (100TB) • The maximum size of an entity can be 1MB
Windows Azure Blob Storage • It is used when we need to store large amount of data (0011100110) • We can store: images, videos, backup data… any kind of data • Maximum size 100TB • ETag – unique version of each blob. Is updated when content is written to the blob • The maxim size of a blob in emulator is 2 GB
Windows Azure Blob Storage • Block blobs • Support multi-upload of blocks in parallel • When updating a block, the old version is not override until you commit it • Can be used for large files • Page blobs • Collection of pages of 512b • Can be accessed by an offset • Can be used when the content is changing very often • We cannot change a block blob to a page blob or a page blob to a block blob
Windows Azure Queues • It is very similar with a named queue from Windows • You can update the message from a queue • Operations: peek, insert, deleting, getting • Remark: getting a message don’t remove the message from queue • Message is persisted until someone will consume it • Queue maximum size: 100TB
Windows Azure Queues
Visual Studio Support and Azure Emulator
Hadoop • When we need to analyze big data • Logs, payment information from banks, M2M data, historical information • There is no relational database • Hadoop Distributed File System • Apache Open Source Project
How does the system works • Microsoft • Google • Amazon • Hewlett-Packard • IBM • CenturyLink/Savvis • Verizon/Terremark • Joyend • Citrix • Bluelock • Vmware • Rackspace • Salesforce
Why we need another messaging system beside Windows Azure Queues?
Windows Azure Service Bus • Microsoft • Google • Amazon • Hewlett-Packard • IBM • CenturyLink/Savvis • Verizon/Terremark • Joyend • Citrix • Bluelock • Vmware • Rackspace • Salesforce
More than a simple Queue • Death Letter support • Order of messages • Duplicate messaging detection • Transaction, Sessions • Multi-distribution mechanism • Filtering support
How does it work • Microsoft • Google • Amazon • Hewlett-Packard • IBM • CenturyLink/Savvis • Verizon/Terremark • Joyend • Citrix • Bluelock • Vmware • Rackspace • Salesforce
Shared Access Signature
Shared Access Signature • Provide a method to offer access to different resources from storage account • You can provide access to resources without requiring a user to authenticate • It is a simple way to control and manage who have access to your storage • The base of this mechanism is a custom token • You can add, remove and change a SAS at runtime • Each policy is defined by a unique id • The validity of a SAS can be limited (time base)
Windows Azure Caching • Nice feature: you pay only the machine computation • All the content is in the machine memory • 2 types of caching: • Dedicated roles • Co-located roles (shared memory between application and cache) • Cache cluster support (only in combination with a storage account) • Maximum size of a cache is 14 GB (limited by the memory size of VM role) • Each item can have an expiration date • Built in support for storing web session in the cache
Caching Service • Offer build in caching mechanism • Can be accessed by anybody from anywhere based on the namespace • Maximum size is 4 GB • Is more expensive than Windows Azure Caching but can be accessed from any location • This caching mechanism is offered as a service • It is similar with Caching Server from on-premise servers
Azure Access Control Service
Azure Access Control Service (ACS) • Provide us a mechanism to authenticate users from different identify providers: FB, Google, Y!, Live … even custom identify providers and Active Directory (2.0+) • Is based on a claim based authentication • You never work with user credentials • Depending on the provider, you can access different information about user • You don’t need anymore to implement a user management mechanism • BUT, if you need, you will need to define roles and store user id’s
Windows Azure Mobile Services
Add-ons
Media Services
Media Services • The based action that can be done is: content streaming • Ingest – first step when content is uploaded (upload and encryption) • Encoding – Process the media content (change the encoding, converting and transform) – we can use only supported formats • Protect – encryption of live streaming using a built-in mechanism • Streaming – send content to consumers (even Apple HTTP Live Streaming is supported) • Support for CDN (Azure and 3th party CDN’s are supported). • Supported devices: Android, iOS, ,Mac, Windows Phone, Windows 8, X-box, embedded devices, dedicated devices
Question Answers
THE END Radu Vunvulea vunvulear@gmail.com http://vunvulearadu.blogspot.com

More Related Content

Cloud and Windows Azure

  • 1. Introduction to Cloud Era Radu Vunvulea vunvulear@gmail.com http://vunvulearadu.blogspot.com
  • 3. Cloud computing is the use of computing resources (hardware and software) that are delivered as a service over a network (typically the Internet). Source: Wikipedia
  • 4. Who am I? { “name” : “Radu Vunvulea, “company” : “iQuest”, “userType” : “enthusiastic” “technologies” : [ “.NET”, “JS”, “Azure”, “Web”, “Mobile”, “SL” ], “blog” : “vunvulearadu.blogspot.com”, “email” : ”vunvulear@gmail.com”, “socialMedia” : { “twitter” : “@RaduVunvulea”, “fb” : “radu.vunvulea” } }
  • 5. Agenda • ? • ? • ? • ? • ? • ? Agenda
  • 6. Cloud computing is the use of computing resources (hardware and software) that are delivered as a service over a network (typically the Internet). Source: Wikipedia
  • 7. Test patterns • Pass/Fail Patterns • Data Driven Test Patterns • Performance Patterns • Simulation Patterns • Stress-Test Patterns • ….
  • 8. Five essential characteristics 1. On-demand self-service 2. Broad network access 3. Resource pooling 4. Rapid elasticity 5. Measured service
  • 9. Five essential characteristics 1. On-demand self-service 2. Broad network access 3. Resource pooling 4. Rapid elasticity 5. Measured service
  • 10. Five essential characteristics 1. On-demand self-service 2. Broad network access 3. Resource pooling 4. Rapid elasticity 5. Measured service
  • 11. Five essential characteristics 1. On-demand self-service 2. Broad network access 3. Resource pooling 4. Rapid elasticity 5. Measured service
  • 12. Five essential characteristics 1. On-demand self-service 2. Broad network access 3. Resource pooling 4. Rapid elasticity 5. Measured service
  • 17. Cloud is offered by … • Microsoft • Google • Amazon • Hewlett-Packard • IBM • CenturyLink/Savvis • Verizon/Terremark • Joyend • Citrix • Bluelock • Vmware • Rackspace • Salesforce
  • 19. Components of Windows Azure • Microsoft • Google • Amazon • Hewlett-Packard • IBM • CenturyLink/Savvis • Verizon/Terremark • Joyend • Citrix • Bluelock • Vmware • Rackspace • Salesforce
  • 21. Web Sites • Easy to deploy • No OS management • Scaling • Monitoring • Publish from different source controls • Support different technologies (PHP, node.js, .NET) • Low cost support – shared mode • Reserved mode – dedicated instance • Each site run in an isolated environment
  • 22. Web Roles • Used to host application composed from multiple tiers • Each web-role is scalable independently • In comparison with Azure Websites, a lot of custom configuration can be done • Network isolation • Any kind of framework can be used in this machines
  • 23. Worker role • Perfect place to run long running task • Can be used with success with web-roles for tasks that run in background • Cannot be used to host a web application • In the moment when the “WHEN(TRUE)” ends the worker role process stop • Can be seen as a process that can execute a specific type for an infinite period of time
  • 24. Virtual Machine • Can be used to install any kind of operating system from Windows to Linux • Build in support and images available for different versions of Linux  and Windows. • Custom machines can be created with our own VHD • Build in support for MongoDB, MySQL, Cassandra, certificates • Migration from on-premise to cloud and cloud to on-premise can be done using VHD
  • 25. Size of the machines Disk Space for Disk Space for Local Storage Allocated Virtual Local Storage CPU Cores Memory Resources in Bandwidth Machine Size Resources in a Web and (Mbps) VM Role Worker Roles ExtraSmall Shared 768 MB 19,480 MB 20 GB 5 Small 1 1.75 GB 229,400 MB 165 GB 100 Medium 2 3.5 GB 500,760 MB 340 GB 200 Large 4 7 GB 1,023,000 MB 850 GB 400 ExtraLarge 8 14 GB 2,087,960 MB 1890 GB 800
  • 27. SQL Database • Relational database based on SQL Server • It is almost like SQL Server from on-premises • BUT: • We don’t have support for distributed transactions • Each table have to contain at least one cluster index • We cannot attaché a database • We don’t have support for jobs • Double check the total cost of a having a SQL Database – there are a lot of times when we can use Table Storage Service
  • 28. Table Storage Service • Store any kind of serializable data • You don’t need any kind of complex data structure or SQL knowledge. • Is not a relational database • In the same table you can have more than one type of entity • Each entity from can have maximum 252 properties + 3 default • The maximum size of total tables cannot accede 100.000 GB (100TB) • The maximum size of an entity can be 1MB
  • 29. Windows Azure Blob Storage • It is used when we need to store large amount of data (0011100110) • We can store: images, videos, backup data… any kind of data • Maximum size 100TB • ETag – unique version of each blob. Is updated when content is written to the blob • The maxim size of a blob in emulator is 2 GB
  • 30. Windows Azure Blob Storage • Block blobs • Support multi-upload of blocks in parallel • When updating a block, the old version is not override until you commit it • Can be used for large files • Page blobs • Collection of pages of 512b • Can be accessed by an offset • Can be used when the content is changing very often • We cannot change a block blob to a page blob or a page blob to a block blob
  • 31. Windows Azure Queues • It is very similar with a named queue from Windows • You can update the message from a queue • Operations: peek, insert, deleting, getting • Remark: getting a message don’t remove the message from queue • Message is persisted until someone will consume it • Queue maximum size: 100TB
  • 33. Visual Studio Support and Azure Emulator
  • 34. Hadoop • When we need to analyze big data • Logs, payment information from banks, M2M data, historical information • There is no relational database • Hadoop Distributed File System • Apache Open Source Project
  • 35. How does the system works • Microsoft • Google • Amazon • Hewlett-Packard • IBM • CenturyLink/Savvis • Verizon/Terremark • Joyend • Citrix • Bluelock • Vmware • Rackspace • Salesforce
  • 36. Why we need another messaging system beside Windows Azure Queues?
  • 37. Windows Azure Service Bus • Microsoft • Google • Amazon • Hewlett-Packard • IBM • CenturyLink/Savvis • Verizon/Terremark • Joyend • Citrix • Bluelock • Vmware • Rackspace • Salesforce
  • 38. More than a simple Queue • Death Letter support • Order of messages • Duplicate messaging detection • Transaction, Sessions • Multi-distribution mechanism • Filtering support
  • 39. How does it work • Microsoft • Google • Amazon • Hewlett-Packard • IBM • CenturyLink/Savvis • Verizon/Terremark • Joyend • Citrix • Bluelock • Vmware • Rackspace • Salesforce
  • 41. Shared Access Signature • Provide a method to offer access to different resources from storage account • You can provide access to resources without requiring a user to authenticate • It is a simple way to control and manage who have access to your storage • The base of this mechanism is a custom token • You can add, remove and change a SAS at runtime • Each policy is defined by a unique id • The validity of a SAS can be limited (time base)
  • 42. Windows Azure Caching • Nice feature: you pay only the machine computation • All the content is in the machine memory • 2 types of caching: • Dedicated roles • Co-located roles (shared memory between application and cache) • Cache cluster support (only in combination with a storage account) • Maximum size of a cache is 14 GB (limited by the memory size of VM role) • Each item can have an expiration date • Built in support for storing web session in the cache
  • 43. Caching Service • Offer build in caching mechanism • Can be accessed by anybody from anywhere based on the namespace • Maximum size is 4 GB • Is more expensive than Windows Azure Caching but can be accessed from any location • This caching mechanism is offered as a service • It is similar with Caching Server from on-premise servers
  • 45. Azure Access Control Service (ACS) • Provide us a mechanism to authenticate users from different identify providers: FB, Google, Y!, Live … even custom identify providers and Active Directory (2.0+) • Is based on a claim based authentication • You never work with user credentials • Depending on the provider, you can access different information about user • You don’t need anymore to implement a user management mechanism • BUT, if you need, you will need to define roles and store user id’s
  • 49. Media Services • The based action that can be done is: content streaming • Ingest – first step when content is uploaded (upload and encryption) • Encoding – Process the media content (change the encoding, converting and transform) – we can use only supported formats • Protect – encryption of live streaming using a built-in mechanism • Streaming – send content to consumers (even Apple HTTP Live Streaming is supported) • Support for CDN (Azure and 3th party CDN’s are supported). • Supported devices: Android, iOS, ,Mac, Windows Phone, Windows 8, X-box, embedded devices, dedicated devices
  • 51. THE END Radu Vunvulea vunvulear@gmail.com http://vunvulearadu.blogspot.com

Editor's Notes

  1. COM
  2. COM
  3. COM
  4. COM
  5. COM
  6. COM
  7. COM
  8. COM
  9. COM
  10. COM
  11. COM
  12. COM
  13. COM
  14. COM
  15. COM