nginx vs ngrok: What are the differences?
nginx: A high performance free open source web server powering busiest sites on the Internet. nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018; ngrok: Securely expose a local web server to the internet and capture all traffic for detailed inspection and replay. ngrok is a reverse proxy that creates a secure tunnel between from a public endpoint to a locally running web service. ngrok captures and analyzes all traffic over the tunnel for later inspection and replay.
nginx can be classified as a tool in the "Web Servers" category, while ngrok is grouped under "localhost Tools".
"High-performance http server" is the primary reason why developers consider nginx over the competitors, whereas "Easy to use" was stated as the key factor in picking ngrok.
nginx and ngrok are both open source tools. It seems that ngrok with 16.5K GitHub stars and 2.87K forks on GitHub has more adoption than nginx with 9.11K GitHub stars and 3.44K GitHub forks.
Airbnb, Uber Technologies, and Spotify are some of the popular companies that use nginx, whereas ngrok is used by Bannerman, a2c systems, and F.biz. nginx has a broader approval, being mentioned in 8676 company stacks & 2560 developers stacks; compared to ngrok, which is listed in 26 company stacks and 16 developer stacks.
What is nginx?
What is ngrok?
Want advice about which of these to choose?Ask the StackShare community!
What are the cons of using nginx?
What tools integrate with nginx?
What tools integrate with ngrok?
The original API performed a synchronous Nginx reload after provisioning a zone, which often took up to 30 seconds or longer. While important, this step shouldn’t block the response to the user (or API) that a new zone has been created, or block subsequent requests to adjust the zone. With the new API, an independent worker reloads Nginx configurations based on zone modifications.It’s like ordering a product online: don’t pause the purchase process until the product’s been shipped. Say the order has been created, and you can still cancel or modify shipping information. Meanwhile, the remaining steps are being handled behind the scenes. In our case, the zone provision happens instantly, and you can see the result in your control panel or API. Behind the scenes, the zone will be serving traffic within a minute.
Nginx serves as the loadbalancer, router and SSL terminator of cloudcraft.co. As one of our app server nodes is spun up, an Ansible orchestration script adds the new node dynamically to the nginx loadbalancer config which is then reloaded for a zero downtime seamless rolling deployment. By putting nginx in front or whatever web and API servers you might have, you gain a ton of flexibility. While previously I've cobbled together HAProxy and Stun as a poor man's loadbalancer, nginx just does a much better job and is far simpler in the long run.
Used nginx as exactly what it is great for: serving static content in a cache-friendly, load balanced manner.
It is exclusively for production web page hosting, we don't use nginx internally, only on the public-facing versions of static sites / Angular & Backbone/Marionette applications.
We use NGINX both as reverse HTTP proxy and also as a SMTP proxy, to handle incoming email.
We previously handled incoming email with Mandrill, and then later with AWS SES. Handling incoming email yourself is not that much more difficult and saves quite a bit on operational costs.