Microsoft IIS is an application server and infrastructure.
N/A
Payara Server
Score 9.0 out of 10
N/A
Payara Server is a fully supported, developer-friendly, open source application server. The vendor says Payara Server’s architecture is innovative, cloud-native and optimized for production deployments. The application server is built and supported by a team of DevOps engineers dedicated to the continued development and maintenance of the open source software and committed to optimizing Payara Server for production Java EE applications. Key features of Payara Server include: •…
N/A
Pricing
Microsoft IIS
Payara Server
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Microsoft IIS
Payara Server
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Microsoft IIS
Payara Server
Features
Microsoft IIS
Payara Server
Application Servers
Comparison of Application Servers features of Product A and Product B
IIS as a web application server is perfectly suited for .net, .net core, asp.net applications. Our core ESB runs on IIS and has hundreds of gigabytes of data moved through it every day spread across millions of transactions. We have other mission critical applications that deliver our results to patients and doctors relying on IIS web application servers. If you stay in the Microsoft development stack, IIS is a top tier, efficient, and reliable web server.
Payara Server is recommended for any type of jee and/or Spring application. Unless there are proprietary framework restrictions there is no reason for not using Payara. The pricing model for enterprise support is very nice and I would definitely recommend it. The case where it is least recommended is when you need a separate application server per service. In this case, there might be better options for this job even though I am not very sure and need to test more.
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.
In general, Microsoft IIS is an alright product. It comes natively with Windows Server. It has good enough GUI to set things up & tweak things around. Once properly setup, it runs stably enough. And with enough Powershell magic, having a CI/CD pipeline to automatically deploy a new version of the application is doable.
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.
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.
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.
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.
On Windows, Microsoft IIS is easier to implement and maintain than Apache web service. Normally if you need to host PHP or other apache native content on a Windows server, it's recommended to use WAMP or equivalent software to simplify the installation, administration, and configuration of resources. However, you can use Microsoft IIS and other web services on the same server, taking care to keep separate folders and port usage for each system.
- 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.
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.
Speed of development. You don't need to be an expert to expose your website through some DNS
Robust, there has never been any downtime because of IIS itself.
The ease of use can have (and has had) some negative impact because it's too easy to implement something, and then forget. When a server is taken down, those unthoughtful implementations come to light the hard way.
