Likelihood to Recommend Best suited for fast development with a fundamental emphasis on object orientation Prohibitive costs for very small integration projects Read full review [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.
Read full review Pros Easy to use: The simplicity of its programming language allows fast learning. Visual environment to generate complex code. Robust: A fall of the system will not be a problem. Never again will information of the transactions in progress be lost. Never more messages lost. Connect to the world: The most popular connection is possible to implement quickly. FTP, File folder, TCP, SMPT, REST.... all method are ready to use. Only define "where" and "how" Read full review 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)! Read full review Cons Given that Ensemble and Cache are one of if not the only true fully object orientated database/development technologies for massive transactional data systems its customizability is extensive and it just comes down to the creativity of the developer to get the products to pretty much do whatever they want to do with it. However, this is not necessarily obvious to newcomers to the technology. The developer community could do with greater participation from the software developers/application specialists and engineers within InterSystems. More extensive documentation and greater access to proven working solutions particularly in the realm of some of the lesser known or new and upcoming technologies. Read full review 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. Read full review Likelihood to Renew Great value for the product
Read full review Usability Front end proxy and reverse proxy of Nginx is always useful. I always prefer to Nginx in overall usability when you have application server and database or multiple application servers and single database i.e. clustered application . Nginx provides really good features and flexibility which helps the system administrator in case of troubleshooting and also from the administration perspective . Also, Nginx doesn't delay any request because of internal performance issues.
Read full review Support Rating I have yet to raise an issue with InterSystems WRC that they have been unable to resolve to my satisfaction in the 20+ years that I have worked with their products.
Read full review John Reeve Principal, Lead developer, Lead designer
Read full review Alternatives Considered Mirth is another integration platform that we have used but its development, in Java, made us always create new methods every time a new product was integrated. Every connection process had to be developed from the beginning and it was not easy to reuse code. Nor did it allow us to have an extensive catalog of HL7 messaging, having to perform the validation of each and every one of its fields manually.
Read full review We have used Traffic, Apache, Google Cloud Load Balancing and other managed cloud-based load balancers. When it comes to scale and customization nothing beats Nginx. We selected Nginx over the others because
we have a large number of services and we can manage a single Nginx instance for all of them we have high impact services and Nginx never breaks a sweat under load individual services have special considerations and Nginx lets us configure each one uniquely Read full review Return on Investment We have integrated 5 laboratories in a treatment monitoring system in less than a month of development. Being able to integrate the following in a period no longer than a week. Read full review Nginx has decreased the burden of web server administration and maintenance, and we are spending less time on server issues than when we were using Apache. Nginx has allowed more people in our company to get involved with configuring things on the web server, so there's no longer a single point of failure ("the Apache guy"). Nginx has given us the ability to handle a larger number of requests without scaling up in hardware quite so quickly. Read full review ScreenShots InterSystems Ensemble Screenshots