0
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#• W...
Add-ons
Databases and caching
E-mail• 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...
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/add...
BizSpark SF Lightning Talk: "PaaS and Deploying To The Cloud" by Rune Soerensen
Upcoming SlideShare
Loading in...5
×

BizSpark SF Lightning Talk: "PaaS and Deploying To The Cloud" by Rune Soerensen

407

Published on

Presentation from November 2011 BizSparkSF Meetup entitled "Tools, Tools and More Tools!" http://www.bizsparksf.com/events/34653282/

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
407
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • The fastest and easiest way to deploy and scale .NET applications in the cloudRuns on Amazon Web servervicesGet up and running in minutesOpen platform:Several integrations points with third party services
  • Takes 15 secondsBuilds sourceRuns unit testsDeploy if everything checks out
  • Awesome toolIntegrates easily with AppHarbor (pic below)Automatic deploy on subsequent pushes
  • Build API: for providing source code from your own service
  • Example of Build API useDeploy a maintenance page when neededBuild by @anglicangeekOpen source
  • Deployed branches: Master, default, trunkPerfect for testing branches before code reviewUses gallio for testingGreat for open source project
  • Automatically send notification of build status to your Twitter profileTweetHarborAPI for building your own
  • When app is installed on application servers
  • * Install add-ons in a couple of seconds* Automatically configures application / libraries* Connect powerful functionality and services with you apps
  • MySQLMS SQLMongoDBMemcachedRedisCouchDB
  • Cloud-enabled logging with LogentriesLoad and performance testing with Blitz
  • Instances may crashApps may be moved to other intances when upgrading software
  • Scale up and down in secondsAutomatically load balancedIncreased HTTP concurrency and failover
  • Easily roll back to a previous buildRevert in seconds
  • Transcript of "BizSpark SF Lightning Talk: "PaaS and Deploying To The Cloud" by Rune Soerensen"

    1. 1. Platform as a Service Deploying to the cloud
    2. 2. What is PaaS• Complete application stack• Pay only for what you use• Elastic scaling• No server setup or maintenance
    3. 3. No vendor lock-in• Builds standard .NET based project types• No AppHarbor specific code• Easily migrate apps
    4. 4. Deployment
    5. 5. GitHub integration
    6. 6. Mercurial, SVN and TFS• Build API
    7. 7. Maintenance manager
    8. 8. Continuous Integration• Only deploys “default” branches
    9. 9. Service hooks• TweetHarbor• Hook API
    10. 10. 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
    11. 11. Add-ons
    12. 12. Databases and caching
    13. 13. E-mail• Use SMTP4Dev locally
    14. 14. Logging and Performance
    15. 15. Designing for the cloud• Keep in mind that: – Apps are deployed to multiple instances – Can be moved to other servers at any time
    16. 16. Design implications• Don’t use local storage• Don’t use instance session state• Self-contained app packages (bin-deploy)
    17. 17. Scaling
    18. 18. Release management
    19. 19. 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
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×