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…
[Google Domains is] very simplistic and easy to use, so it's very straightforward to register a new domain but it doesn't have some features that other services provide. Also, the integration with other Google Services and domain search tool is amazing.
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.
Google Domains is pretty good at pre-solving email faux pas such as reply all mishaps. Perhaps a built-in email monitoring tool such as knowing when a customer opens up an email would be good. You can get these features with integrations, but what if it was an internal Google product? Might be nice
Email masking was a bit difficult to figure out, but nothing you can't discover with a few Google sessions.
I wish I could see more insight into time zones that my customers are in, or scheduling calls on Gcal with timezone awareness. I know this is super hard to code around though.
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.
Because it is intuitively easy to use, like all of their products. The integration with other apps works seamlessly, and you can have a professional website within hours, rather than days, as with most hosting companies. The templates on the website builder for just about every business make it so simple that even I can do it!
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
I've never actually had to use support because everything has been very straightforward and I have not had a glitch. I have used Google's support for other items so I can only imagine that it's probably the same support which is decent. They do take a while to get back to you.
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.
GoDaddy is great, but what I really like about Google Domains when compared to GoDaddy is the ease of centralization. Our email, calendar, accounts, domain, etc was all handled in one place and that made things really easy. You could also access domains easily and quickly by being logged into your email, instead of worrying about yet another log in.
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
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.
