Amazon EC2 Auto Scaling helps users maintain application availability and allows users to automatically add or remove EC2 instances according to definable conditions.
N/A
Microsoft IIS
Score 7.2 out of 10
N/A
Microsoft IIS is an application server and infrastructure.
On the servers with fixed resources, Microsoft IIS was installed. In terms of storage capacity, the server has a predetermined limit. It's possible to run out of money before the next billing cycle begins. A higher price tag or more resources may be necessary to ensure …
Microsoft IIS
No answer on this topic
Features
Amazon EC2 Auto Scaling
Microsoft IIS
Application Servers
Comparison of Application Servers features of Product A and Product B
If you need to establish a system right away, in the past it took weeks or months to request a quote from the vendor and receive the equipment. Now, with Amazon EC2 in less than tens of minutes or hours, you can create a test environment and test it without any inconvenience.
Publishing applications or websites is easy with Microsoft IIS. You don't need external software or complicated tutorials involving command lines and editing configuration files. On other hand, sometimes the troubleshooter needs a high knowledge of Windows Server, Registry, and tools to debug the application. If you need to host non-Microsoft technology as PHP pages or have a low budget, I recommend IIS equivalent software as Apache.
A big advantage that we use all the time is reviewing the logs that automatically get generated in IIS. It has helped us troubleshoot various problems in our applications over the years.
IIS integrates really well with Visual Studio and TFS. We are able to quickly deploy new applications and changes to applications when requested by the business.
IIS has proven that it is easy to configure and maintain with minimal effort.
We have no intention to replace all applications running on top of the IIS platform. Not all applications support other platforms and not all support staff are skilled in Linux/Apache platform support. Whereas IIS may not be the best performing or most secure web platform available, for the aforementioned reasons, it is impossible not to continue use of this product.
Usability is good since we already know how AWS works. For those that are new it might be a little bit confusing at the beginning but they are improving it at a fast pace. Even though AWS keeps changing the user interface constantly, it is still powerful, understandable and easy to use. For technical people, they still offer the CLI.
As I've mentioned earlier, Microsoft IIS is very simple and easy to use. The user interface is a little bit overloaded with a huge number of different options, but once you have a little clue of what you are doing and what you need - no issues at all.
ARR (application request routing) in Microsoft IIS Server enables the web-admins to increase the web app reliability and availability through the rule based routing and load balancing of HTTP requests which in turn provides highly available server. IIS 7.0 Manager also provides kernel as well as user mode caching for faster performance and in case if the server fails, the IIS server has good amount of details logged in its log files which help understand and debug the cause quickly. Load balancing facilitates IIS server to fight against availability issues.
In my experience, I have never had significant issues with IIS performance. Sometimes I've experienced issues with loading time, but it is mostly related to the web site code. However Amazon, Microsoft and Google providing free cloud services with very limited resources, and in that scenario, "heavy" websites on IIS could be the issue. In other situations - performance is good.
The platform works as is. The help and tutorials on the help page can help you to setup the entire platform without problems, and also provides help on a huge variety of problems. Amazon also provides support plans. We have the basic support plan, but Amazon offers three support tiers, and we know that it works perfect.
As mentioned earlier there is so much documentation or guides or stack overflow questions out there that someone will have faced the same or very similar scenario to what you are going through that you will almost certainly find a solution to what you are after.
The main reason is our total infra is created on AWS and we tend to use the natural service by AWS rather than third party tools, which has more advantages when the auto scaling interacts with other AWS services and its way easy to configure when we compare it with counter parts like Autoscale from Microsoft Azure.
Apache is java. Java is unnecessary complex. No developer wants to invest in learning all the hundreds of text based configuration files to get something done. Also, apache gives you the most evil and un-usable user interface possible. [Microsoft] IIS makes [life] after development easy, which is already complex enough to be bothered by something as mundane as exposing your work over the internet.
Microsoft IIS Server is scalable if the underlying server configuration is done correctly. Use x64 edition v/s 32bit and using 32bit mode application pools are some of the tweaks to be done to make the IIS server scalable. There are too many small configurations need to be carried out in order to make a highly scalable IIS server hence not giving full score in this area.
We will devote more time to development than server administration, but we will require additional time if you migrate from another ecosystem.
Fault detection and reporting are automated in the old server, and bandwidth is fixed per month, but everything is manageable automatically. We only pay for the resources we use.
After some months, we met our return on investment (ROI).
