Creating php cloud applications
Download as PPTX, PDF0 likes4,250 views
This document discusses different types of cloud computing including public cloud, hybrid cloud, and private cloud. It also discusses programmable resources in Microsoft Azure like the Azure CLI tools and Chef. Other topics covered include scaling out vs scaling up, Windows Azure Web Sites internals like request processing and deployment, supported PHP versions, decoupling application components, and using the Windows Azure SDK for PHP.
![{
"require": {
"microsoft/windowsazure": "*"
},
"repositories": [
{
"type": "pear",
"url": "http://pear.php.net"
}
],
"minimum-stability": "dev"
}](https://image.slidesharecdn.com/creatingphpcloudapplications-130515145629-phpapp01/85/Creating-php-cloud-applications-27-320.jpg)
![use WindowsAzureCommonServicesBuilder;
use WindowsAzureCommonServiceException;
use WindowsAzureServiceBusmodelsBrokeredMessage;
$serviceBusRestProxy = ServicesBuilder::getInstance()
->createServiceBusService(SERVICE_BUS_CONNECTION_STRING);
// SERVICE_BUS_CONNECTION_STRING:
// Endpoint=https://[sb-namespace].servicebus.windows.net;
// SharedSecretIssuer=[sb-issuer];
// SharedSecretValue=[sb-access-key]](https://image.slidesharecdn.com/creatingphpcloudapplications-130515145629-phpapp01/85/Creating-php-cloud-applications-28-320.jpg)
Creating php cloud applications
- 3. Types of Cloud Public Cloud Hybrid Cloud Private Cloud
- 7. Programmable Resources Windows Azure Cross Platform CLI Tools
- 8. Windows Azure CLI Tools http://aka.ms/Azure-SDK-Tools Chef http://aka.ms/Chef
- 9. Scale Out, over Scale Up
- 10. Scale Out vs. Scale Up
- 12. Windows Azure Web Sites Internals Request Process Flow for New (Cold) Sites
- 13. Windows Azure Web Sites Internals Request Process Flow for Existing (Hot) Sites
- 14. Windows Azure Web Sites Internals FTP and Web Deploy Deployment Process Legend
- 15. Windows Azure Web Sites Internals Git Deployment Process Legend
- 16. Supported PHP Versions 5.4.0 5.3.13 Default Support Customized Support Change configurations with .user.ini Load extensions via PHP_Extensions AppSetting Bin deploy specific PHP Runtime Configure FastCGI Handler in Web Site Configuration Uses local php.ini file for extensions and configurations
- 17. Load Balanced Web Site Windows Azure Web Sites
- 20. Tightly Coupled
- 21. Tightly Coupled
- 22. Loosely Coupled
- 23. Loosely Coupled
- 24. Loosely Coupled
- 25. Loosely Coupled
- 26. Windows Azure SDK for PHP GitHub: http://aka.ms/AZURESDK-PHP Developer Center: http://aka.ms/Develop-PHP
- 27. { "require": { "microsoft/windowsazure": "*" }, "repositories": [ { "type": "pear", "url": "http://pear.php.net" } ], "minimum-stability": "dev" }
- 28. use WindowsAzureCommonServicesBuilder; use WindowsAzureCommonServiceException; use WindowsAzureServiceBusmodelsBrokeredMessage; $serviceBusRestProxy = ServicesBuilder::getInstance() ->createServiceBusService(SERVICE_BUS_CONNECTION_STRING); // SERVICE_BUS_CONNECTION_STRING: // Endpoint=https://[sb-namespace].servicebus.windows.net; // SharedSecretIssuer=[sb-issuer]; // SharedSecretValue=[sb-access-key]
- 29. // Create message $message = new BrokeredMessage(); $message->setBody($msg); // Send message $serviceBusRestProxy ->sendQueueMessage(QUEUE_NAME, $message);
- 30. Message Me Windows Azure Service Bus Queue
- 31. Cost, Agility and Reliability
- 33. Cory Fowler Windows Azure Technical Evangelist @SyntaxC4 blog.syntaxc4.net http://joind.in/8168 Questions? Three truths of cloud computing: hardware fails, software has bugs and people make mistakes
- 34. Resources aka.ms/TEK13-Azure aka.ms/Tek13-Azure-Code aka.ms/WAWS-Cheat aka.ms/WAWS-PHP-Troubleshoot aka.ms/Develop-PHP aka.ms/AZURESDK-PHP aka.ms/WA-Silverlining
Editor's Notes
- #13: SetupThis slide will outline the process by which new Windows Azure Web Sites are provisioned and created when a customer submits a new site request.Request ProcessTraffic comes into the Azure load balancer(fade in ARR) Hits the ARR load balancer (extended to support WAWS)(fade in Runtime SQL) Talks to the runtime database to find out which web server the traffic should be routed to(fade in Web Server) Stores metadata about each siteStores data about individual server load and memory usageUpdates every 30 secondsTraffic is routed to the appropriate web serverWhen the traffic hits the web server, it makes a call back to the runtime SQL database to verify the requested site should served from it (added security functionality)(fade in storage controller) If the site is valid, a map is made to the storage controller defining the content of the siteConfig files are generated and saved(fade in web site SQL) If you chose to have a linked database for your site, the linkage to your site’s database is set up automatically(fade in traffic arrow) Traffic then sent back to the Azure load balancer and then the requesting client sees the output
- #14: SetupThis slide will outline the process by which requests are handled to Windows Azure Web Sites that have already been provisioned.Request ProcessTraffic comes into the Azure load balancer(fade in ARR) Hits the ARR load balancer, which has a list of where sites live and how to direct traffic to themTraffic is routed to the appropriate web server(fade in web server) Traffic is routed to the web server. (fade out web server, fade in multiple web server instances) If the site has multiple instances, traffic is dynamically routed to the least-utilized server(fade in storage controller) Site content is loaded from the storage controller to the web server that was hit(fade in web site SQL) If you chose to have a linked database for your site, data is exchanged between the site and it’s database during the request(fade in traffic arrow) Traffic then sent back to the Azure load balancer and then the requesting client sees the output
- #15: SetupThis slide will outline the process by which requests are handled to Windows Azure Web Sites that have already been provisioned.Request ProcessTraffic comes into the Azure load balancer(fade in ARR) Hits the ARR load balancer, which has a list of where sites live and how to direct traffic to themTraffic is routed to the appropriate web server(fade in web server) Traffic is routed to the web server. (fade out web server, fade in multiple web server instances) If the site has multiple instances, traffic is dynamically routed to the least-utilized server(fade in storage controller) Site content is loaded from the storage controller to the web server that was hit(fade in web site SQL) If you chose to have a linked database for your site, data is exchanged between the site and it’s database during the request(fade in traffic arrow) Traffic then sent back to the Azure load balancer and then the requesting client sees the output
- #16: SetupThis slide will outline the process by which requests are handled to Windows Azure Web Sites that have already been provisioned.Request ProcessTraffic comes into the Azure load balancer(fade in ARR) Hits the ARR load balancer, which has a list of where sites live and how to direct traffic to themTraffic is routed to the appropriate web server(fade in web server) Traffic is routed to the web server. (fade out web server, fade in multiple web server instances) If the site has multiple instances, traffic is dynamically routed to the least-utilized server(fade in storage controller) Site content is loaded from the storage controller to the web server that was hit(fade in web site SQL) If you chose to have a linked database for your site, data is exchanged between the site and it’s database during the request(fade in traffic arrow) Traffic then sent back to the Azure load balancer and then the requesting client sees the output