Apache HTTP Server vs. NGINX vs. SwaggerHub

As I mentioned earlier, the Apache HTTP Server has a small disadvantage compared to the competition (NGINX) in terms of performance. If you run websites that really have a lot of visitors, NGINX might be the better alternative.

On the other hand, the Apache HTTP Server is open source and free. Further functionalities can be activated via modules. The documentation is really excellent.

Incentivized

Nginx is well-suited for any web server scenarios, such as web applications, backend or reverse proxy for both application and HTTP requests, and distribution. It is less appropriate for Windows-based applications that run directly on a Windows Server host. In any case, it is very easy to manage, through separate conf files for each application or site you want to host with it.

Incentivized

ReadyAPI and SwaggerHub are a match made in heaven. Being able to so easily import the API directly into ReadyAPI and then being able to generate a test suite from the API is my favorite part of these softwares. We have rather large services so building out the API can take some time

Incentivized

• Street Cred: Apache Web Server is the Founder for all of Apache Foundation's other projects. Without the Web Server, Apache Foundation would look very different. That being said, they have done a good job of maintaining the code base, and keeping a lot of what makes Apache so special
• Stability: Apache is rock-solid. While no software is perfect, Apache can parse your web sources quickly and cleanly.
• Flexibility: Need to startup your own Webpage? Done. Wordpress? Yup. REST Endpoint? Check. Honeypot? Absolutely.

Incentivized

• Very low memory usage. Can handle many more connections than alternatives (like Apache HTTPD) due to low overhead. (event-based architecture).
• Great at serving static content.
• Scales very well. Easy to host multiple Nginx servers to promote high availability.
• Open-Source (no cost)!

Incentivized

• Treating the design as documentation ensures that we have consistent and well defined APIs
• API consumers can export the swagger definition or code stubs to use within their development environment
• We can iterate through multiple versions of a definition privately before making a version publicly available

Incentivized

• The default configurations which comes with Apache server needs to get optimized for performance and security with every new installation as these defaults are not recommended to push on the production environment directly.
• Security options and advanced configurations are not easy to set up and require an additional level of expertise.
• Admin frontend GUI could be improved to a great extent to match with other enterprise tools available to serve similar requirements.

Incentivized

• Customer support can be strangely condescending, perhaps it's a language issue?
• I find it a little weird how the release versions used for Nginx+ aren't the same as for open source version. It can be very confusing to determine the cross-compatibility of modules, etc., because of this.
• It seems like some (most?) modules on their own site are ancient and no longer supported, so their documentation in this area needs work.
• It's difficult to navigate between nginx.com commercial site and customer support. They need to be integrated together.
• I'd love to see more work done on nginx+ monitoring without requiring logging every request. I understand that many statistics can only be derived from logs, but plenty should work without that. Logging is not an option in many environments.

• The user interface could be more improved to sustain with other similar tools in the market.
• Beneficial if we have better integration with third party softwares.
• Nice to have ability to download the documentation in usable formats.

Incentivized

Great value for the product

Incentivized

This tool is really easy to use and configure. Consumes very less system resources. It is highly modular and configurable. You can easily use it with other tools like certbot for SSLs. You can configure basic security with configuration and headers

Incentivized

I give this rating because there is so much Apache documentation and information on the web that you can literally do anything. This has to do with the fact that there is a huge Open Source community that is beyond mature and perhaps one of the most helpful to be found. The only thing that should hold anyone back from anything is that they can not read. RTFM, my friend. And I must say that the manual is excellent.

Incentivized

Community support is great, and they've also had a presence at conferences. Overall, there is no shortage of documentation and community support. We're currently using it to serve up some WordPress sites, and configuring NGINX for this purpose is well documented.

Incentivized

I has a lot more features, except that IIS is more integrated in a Windows environment. But now with .net core also possible from Apache it would work anywhere really. Only in a full Windows environment where full integration is needed I would chose to go for IIS. Otherwise Apache it is.

Incentivized

I have found that [NGINX] seems to perform better throughout the years with less issues although I've used Apache more. I would definitely recommend [NGINX] for any high volume site and I've seen this to usually be the case from most provided web hosts who will pick [NGINX] over alternatives

Incentivized

The only other product we looked at was Postman. But we liked the SwaggerHub UI & the integrations it has with the AWS API gateway. Though Postman has some other great features like the ability to write test cases & execute them, SwaggerUI was more convenient to document & share them.

Incentivized

• Works as intended, so it's less to worry about.
• Works great on elastic environments (like EC2).
• As an Open Source project, you can get support for almost any problem you can have.
• Configuration files, while powerful, can be tricky to dominate for some.

Incentivized

• By using Nginx, we can host multiple web services on a single server, keeping our infrastructure costs lower.
• Nginx maintains our HTTPS connections, allowing us to keep our promise to our customers that their data is safe in transit.
• Due to Nginx's extremely low failure rate, our web addresses always return something meaningful, even when individual services go down. In sense, this means we are "always online" and allows us to maintain brand and support our customers even in the face of catastrophe.

Incentivized

• Faster API development lifecycle.
• Reduced discussion time when building a new vital API endpoint.
• Complete documentation which makes the new team member onboarding process easier.

Incentivized