Disregarding database bottle-necks, how should an ASP.NET MVC application be designed to scale on AppHarbor if load starts affecting response time?
Scaling
Discussions are closed to public comments.
If you need help with AppHarbor please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
#1 Posted by rune Support staff on 15 Apr, 2011 12:38 AM
Hi Petrus,
It should be designed so that it can be run from multiple web servers. This means that certain considerations regarding for instance session state and file storage may become relevant. In order to serve files from multiple web servers you would have to store the files in a central location such as S3 in order to be able to serve it consistently. Sessions also shouldn't be dependent on machine keys etc that are specific to the web server it's running at.
Please note that the ability to scale out on multiple web servers is currently not exposed through the user interface though.
If you got some more specific things you would like us to elaborate we'll be happy to help you out!
Best,
Rune
rune closed this discussion on 15 Apr, 2011 12:38 AM.