Akamai Technologies, headquartered in Boston, offers a Akamai: a content delivery network (CDN).
N/A
NGINX
Score 9.1 out of 10
Mid-Size Companies (51-1,000 employees)
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…
Nginx works on basic operating system principles and what I like the most about it is that even after being feature-rich and easily customizable it uses minimum resources.
Akamai is a well-established brand name with a great product. It meets and many time exceeds the needs for global content delivery and security management layer at the edge. Fine grain security tuning seems cumbersome as the definition of the app keeps changing. It also requires an investment of time for the setup which doesn't necessarily make sense for smaller scale scenarios. Some products offered by AWS, Azure or the Google Cloud can be more tightly integrated with cloud provider offerings thus easier to configure.
[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.
Content offloading - once rules are set up within Akamai you don't need to even think about how many images or large JavaScript or CSS files (for example) are being served from your own estate, Akamai takes care of it all via rules that are quick, easy and flexible.
Page caching - for pages that don't change very often Akamai allows you to set up rules, quickly and easily, to serve up your page content for you, which takes even more load away from your origin servers.
Quick rollback - the Akamai system allows easy testing of rules and changes via a staging system, and also offers a quick rollback option, which is perfect for the rare occasions when something has been set up incorrectly.
The interface in their control centre could be a bit more user-friendly with some of the settings in places that you wouldn't expect them to be. The search offsets this problem to an extent but it's still sometimes slower than you'd like to find what you are looking for.
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.
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.
Their support documents are excellent and provide a lot of useful information for all their services. The only reason I didn't give them a 10 is that the time it takes for them to respond to an issue could be slightly faster.
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.
We've used -- and considered -- a whole number of CDN offerings. The good news is that almost all of the CDN products on the market are terrific, and will pay for themselves via increased customer satisfaction and lower monthly hosting bills. For some cases, we're still more likely to suggest CloudFlare (which has a free tier) or an integrated offering from a cloud provider, like Cloudfront.
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
Akamai RoI improved over a period of times since it comes with heavy costs, however global deliveries in over 100 counties and global web platforms usage helps improve RoI
With the complex UI challenges, ROI could be impacted negatively when you have to invest in operations and time.
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.
