Platform as a Service
Deploying to the cloud
What is PaaS
• Complete application stack• Pay only for what you use• Elastic scaling• No server setup or maintenance
No vendor lock-in
• Builds standard .NET based project types• No AppHarbor specific code• Easily migrate apps
Deployment
GitHub integration
Mercurial, SVN and TFS
• Build API
Maintenance manager
Continuous Integration
• Only deploys “default” branches
Service hooks
• TweetHarbor• Hook API
Application servers
• Most common frameworks and libraries are installed.
• .NET 2.0 and 4.0• ASP.NET MVC 1, 2 and 3• F#• WCF services
Add-ons
Databases and caching
• Use SMTP4Dev locally
Logging and Performance
Designing for the cloud
• Keep in mind that:– Apps are deployed to multiple instances– Can be moved to other servers at any time
Design implications
• Don’t use local storage• Don’t use instance session state• Self-contained app packages (bin-deploy)
Scaling
Release management
Links• AppHarbor: https://appharbor.com• Github.com, bitbucket.org, codeplex.com• Add-ons: https://appharbor.com/addon• TweetHarbor: https://tweetharbor.apphb.com• MaintMan: https://maintman.apphb.com/ • Twitter: http://twitter.com/appharbor• Msysgit: http://code.google.com/p/msysgit/ • Gallio: http://www.gallio.org/ • Smtp4Dev: http://smtp4dev.codeplex.com/ • AppHarbor API docs: http://support.appharbor.com/kb/api• AppHarbor add-on docs: http://support.appharbor.com/kb/add-ons
Top Related