Microsoft IIS vs. Payara Server

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.

Incentivized

- If the application is very large then the Payara server is suitable and in the case of a small application, we can choose Micro Payara. - Micro payara is very well suited for microservice architecture. - Fully Jakarta compliance. - Very good performance.

Incentivized

• 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.

Incentivized

• Small memory footprint.
• Fully JEE compliant with an exceptional administration console.
• Very good performance.

Incentivized

• Angular/node apps don't run on IIS, or at least we never figured out how. Rather we ended up using nginx.
• There are still occasional memory leaks - check your recycle settings!
• If you have very heavy usage for web APIs, IIS requires regular restarts for reasons unknown.

Incentivized

• Issues that are logged in Payara GitHub forum need to address on time, but it keeps on postponing fixing those issues.

Incentivized

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.

Incentivized

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.

Incentivized

As mentioned before it has an amazing configuration console. You can practically do anything from there and even update the program or install new features on the fly.

Incentivized

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.

Incentivized

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.

Incentivized

As mentioned before, its performance capabilities were one of the reasons we used them. It interacts with mass mail software and we see no performance impact. It handles everything pretty well and pretty fast.

Incentivized

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.

Incentivized

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.

Incentivized

- As I said before, Payara has full Jakarta compliance and provide up-to-date technology stack upgrade. - Easy to install and upgrade. - Very less configuration setting. - Default ready-to-use production domain is available, which can be spun up to use in production.

Incentivized

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.

Incentivized

• Allowing us to internally host our monitoring websites allows quick access to data that can be quite hidden, saving developer time.
• It was inexpensive compared to more bulky solutions saving upfront cost.
• It’s easy to install and enable allowing more developer savings.

Incentivized

• Can host multiple application on single VM.
• Helps managed service team reduces their time on installation and up-gradation ( upgrading it to a new Payara server is very simple).
• We can opt for Payara or Micro Payara based on the application size.

Incentivized