Print Page | Close Window

Azure Scaling

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2010
Forum Discription: For .NET 4.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=2593
Printed Date: 29-Jul-2026 at 8:35pm


Topic: Azure Scaling
Posted By: Andrew
Subject: Azure Scaling
Date Posted: 29-Mar-2011 at 3:00pm
I'm interested in any experience regarding the azure deployment.
 
The goal is to host a multi tenant Devforce-Silverlight-Application with several SQL-Azure databases behind.
The databases have a range from 200 MB up to 6 GB.
 
 
1. Does DevForce scale within Azure when I add new instances?
2. Is there a recommended or minimum type of instance maybe regarding to the memory?
3. Are there any other known issues that I have to take within Azure when hosting the Devforce-Silverlight-Application?
 
Thank you


Replies:
Posted By: kimj
Date Posted: 30-Mar-2011 at 10:12am

DevForce is actually unaware (for the most part) that the application is load balanced.  It "scales" in that the EntityServers will be running on as many instances as you've got.  None of the EntityServers knows about the others.

An EntityServer is almost stateless, so the memory requirements should not be high.  I say "almost", because there is metadata loaded, and user "session" information, but all of this will be recreated as needed on a new instance.
 
The only known issue is that you can't use Push with Azure, because it's not stateless.
 
Also remember that you must have a Data Center license, and to set the serverSettings sessionEncryptionKey to the same value on every instance.

Posted By: Andrew
Date Posted: 30-Mar-2011 at 2:05pm
Hi Kim,
 
this sounds very good for the Azure-future.
Data Center license together with DevForce Universal is already purchased.
I have set the sessionEncryptionKey long time before to a certain value within the serversettings.
Am I right that this value will be used for every instance then?
 
Thanks
Andrew

Posted By: kimj
Date Posted: 30-Mar-2011 at 2:26pm
Oh sorry, I wasn't thinking.  Yes, the settings in your one web.config will be what's deployed to all instances.   So the sessionEncryptionKey only needs to be set once.


Print Page | Close Window