NGINX, a business unit of F5 Networks, powers over 65% of the world's busiest websites and web applications. NGINX started out as an open source web server and reverse proxy, built to be faster and more efficient than Apache. Over the years, NGINX has built a suite of infrastructure software products o tackle some of the biggest challenges in managing high-transaction applications. NGINX offers a suite of products to form the core of what organizations need to create…
N/A
WSO2 API Platform
Score 9.4 out of 10
Enterprise companies (1,001+ employees)
WSO2 API Manager makes it possible for developers to both develop and manage APIs of different types. Unlike solutions which focus only on managing API proxies, WSO2 API Manager provides tools to develop APIs by integrating different systems as well. It supports a variety of API types from REST, SOAP, GraphQL, WebSockets, WebHooks, SSEs and gRPC APIs with specialized policies and governance for each different type. Being fully open source, its architecture and extensibility…
All of those are paid solutions with very good features, but they also offer dedicated scenarios for web application hosting. If you run applications on on-premises web servers and don't have a Microsoft licence agreement, Nginx is a very good and reliable option, based on …
In our organization, we use different solutions depending on if the database is on premise or in the cloud. We went from multiple solutions across different departments towards a more consolidated model to achieve standardization and economies of scale. We’ve mainly moved …
How does it compare? We use Apache ATP server and we also use Tom Cat also owned by Apache, but both Apache, ATP, and MKA. They are relatively older than GX and so they're one problem for Apache and MKA they need more power, more memory, and more space.
NGINX have higher market share which obviously show to us it is the preferred choice of most of the customers. Both of platform competes in the Web and Application server areas, but due the security features of NGINX be more flexible this in my opinion makes more sense.
Apache is a market leader but NGINX is new and has new features. Lightweight and can handle static requests. We use EC2 and I believe NGINX is more suited when it comes to scalability.
Providing better capabilities comparing the overall API lifecycle management, especially the availability of API Integration layer and a strong identity layer of their own which provides an end-to-end API ecosystem that would be advantageous in terms of a large software …
Nevatech Sentinet: The easiest API Manager available. No knowledge of how the product works internally needed! It works with C# (not java... with all it's config files... really? Java developers?). Great way to categorize API's into groups (domains). All of which is drama in …
[NGINX] is very well suited for high performance. I have seen it used on servers with 1k current connections with no issues. Despite seeing it used in many environments I've never seen software developers use it over apache, express, IIS in local dev environments so it may be more difficult to setup. I've also seen it used to load balance again without issues.
WSO2 is a unique product that provides pre-integrated components like Gateway, Integrator, identity management, etc. Hence it is best suited when the requirement is not just only publish the APIs but also to secure and transform the APIs. WSO2 can be an overhead if only Gateway is required, as there are other very lightweight gateways available in the market.
Straight-forward configuration format that users of all skill levels can learn, and yet is powerful enough for the huge breadth of features that Nginx provides.
Massive scale right out the box. We've never had a Nginx instance overwhelmed by requests, and if we did it would be trivial to spin up more Nginx instances to handle the load.
SSL termination means that we can deliver content over HTTPS without needing our individual services to require TLS support. This saves us a lot of time and headache while keeping us secure.
Nginx is open-source and free, meaning that anyone can use it to power their services, from individual projects to billion-dollar websites.
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.
Installation of this product is a hell. You need to be an expert to get this running together with WSO2 Analytics. It uses a really confusing method of "port + 1" to connect extra products. I guess this was meant to provide a handy way to add new WSO2 products. In reality you'll need to scroll through numerous config files to set this straight. If you use this out of the box, everything will work all right. But the moment you add SSL certificates, DNS names and you'll need special ports to configure your firewall, this product becomes unmaintainable.
The "Store" provides a nice way to group API's. However, the "Publisher" does not... if you have more than 30 API's searching for API's becomes really annoying.
The number of configs in this product is huge. As a developer myself, I've never seen (and definitely never created) a product that needed that much config files. Installation and maintenance of products should be stupidly simple, since no developer nor infrastructure person wants to learn something that "just" needs to be a tool.. opposed to being a whole new area of expertise. After using WSO2 API Manager for a while, we wanted to change the admin password... this should be simple enough, like just change the password in "Carbon." But nope. The whole WSO2 environment crashed. We just gave up. Too dangerous.
Why so many different "products"? Publisher, Store, Carbon, and numerous hidden interfaces. Analytics, ESB whatever... No wonder there are so many config files and port issues. Make it simple!!!
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
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.
All of those are paid solutions with very good features, but they also offer dedicated scenarios for web application hosting. If you run applications on on-premises web servers and don't have a Microsoft licence agreement, Nginx is a very good and reliable option, based on Linux distributions and available as freeware.
Nevatech Sentinet: The easiest API Manager available. No knowledge of how the product works internally needed! It works with C# (not java... with all it's config files... really? Java developers?). Great way to categorize API's into groups (domains). All of which is drama in WSO2. But Sentinel is really expensive... Mulesoft: Nice and clean. Again, no expert knowledge needed of how the product works internally. Like using word... or any other application, except WSO2. Have java developers never heard of exposing configurations through a user inyterface?? Mulesoft, however is really expensive. Azure: Not cheap!! And a chaotic interface too. But it pays! If you have a Microsoft account already, this is your next step. We chose WSO2 4 years ago because it was free... but we're moving to azure now. And we're very happy with that decision.
Our websites are noticeably faster, causing an increase in customer satisfaction.
Nginx has such a low memory/resource footprint that we save money from not needing multiple large, expensive servers.
Ability to load balance traffic, have server-redundancy, and have high-availability allows for 100% uptime and provides cost-effective solutions to alternatives that can cost a lot.