I have synchronization services created using .Net WCF, .net 4.0, SQL Server 2008 and hosted on a Windows service.
Below is some custom implementation that we have completed:
The user database connection pool populated at the beginning of the application, as well as the cleanup thread that goes through the application life cycle.
User sessions, because the application was not intended to be deployed in IIS and BasicHTTPBinding, were used, so a user session was completed. Consequently, the Cleaup thread also works to clear inactive sessions.
[Specific table] Cache. There is a specific table in the database that uses high frequency, so we implemented our own cache in order to avoid too many calls to the database, this cache starts at the beginning of the application.
Given the above points, please offer me the following:
Is this application suitable for deployment in IIS? (I thought that an application deployed in IIS only survives in action and stops when it is idle, so caching, merging will be lost and reinitialized).
Is Amazon EC2 suitable for this; OR Should I register for an instance of Windows EC2? please instruct me about this (I have never used ec2 before and had a lot of information about it)
Is Failover Clustering Supported?
-?
Windows Azure, ?