How AppHarbor Works
- 1.You push .NET and Windows code to AppHarbor using Git, Mercurial, Subversion or Team Foundation Server with the complimentary Git service or through integrations offered in collaboration with Bitbucket, CodePlex and GitHub.
- 2.When AppHarbor receives your code it will be built by a build server. If the code compiles all unit tests contained in the compiled assemblies will be run. The result and progress of the build and unit test status can be monitored on the application dashboard. AppHarbor will call any service hooks that you add to notify you of the build result.
- 3.If everything checks out the application is deployed and configured on AppHarbor application servers. AppHarbor can scale an application vertically and horizontally within seconds for better request throughout, performance and failover. AppHarbor balance load across all instances running that application. Scaling an application gives higher request thoughput, redundancy in case of instance failure and better performance.
Application Runtime Environment
- 1.Users can access your application using a complimentary apphb.com subdomain or through any additional domains you add to the application. Additional domains must have DNS records pointing at AppHarbor. AppHarbor supports SSL.
- 2.AppHarbor balances load across instances running your application. In case an individual instance goes down or becomes unavailable, load is shifted to available instances. The load-balancers terminate SSL connections and handle HTTP compression. This lets application instances focus on running .NET code.
- 3.All infrastructure runs inside the Amazon Web Services cloud and is completely managed by AppHarbor. While the application servers are multi-tenant, the platform is architected to ensure that instances are completely compartmentalized and isolated. Applications can consume cloud-resources such as databases, caching and e-mail services from add-ons installed from the add-on catalog.