AWS offers the Amazon API Gateway supports the creation and publication of an API for web applications, as well as its monitoring and maintenance. The Amazon API Gateway is able to support thousands of API calls concurrently and provides traffic management, as well as monitoring and access control.
$0.90
Per Million
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…
N/A
PayPal Payments Pro
Score 8.3 out of 10
N/A
PayPal Payments Pro is an enterprise-class ecommerce payment solution, that provides payment processing security to build a professional-grade ecommerce site. It can be configured to meet business needs and works across devices. Users can tap into over 390 million active customer accounts around the globe.
Nginx is a powerful tool but configuring, running and maintaining but Nginx will never be a competitive advantage for our business. API Gateway is powerful because it is managed and does what we need out-of-the-box. Nginx is used more widely in the community; it may be easier …
Experienced a lack of available programming languages while working on a minor project. I had to halt the project and wait for it to be added later. It took ages and had a hit on our productivity. It has a centralized management system which helps and an easy interface which helps to manage multiple tasks in case of large-scale operations and projects.
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.
Paypal is great for personal payments as well as business payments for ecommerce of for paying monthly memberships. It is a user friendly software that needs little expertise to get used to. For larger payments, the fees become high therefore it is more suitable for payments of upto few hundred dollars.
API Gateway integrates well with AWS Lambda. This allows us to build a web server in the language and framework of our choice, deploy it as a Lambda function, and expose it through API Gateway.
API Gateway manages API keys. Building rate limiting and request quota features are not trivial (or interesting).
API Gateway's pricing can be very attractive for services that are accessed infrequently.
PayPal offers me the option of converting my currency deposited in my account to another currency, so I can complete all kinds of payments and send money to employees who are in another country for business reasons.
The mobile phone application is too fast, I can make payments to my employees in a matter of seconds without having to wait for the web version to load.
Scheduled payments are great. PayPal allows me to add a list of contacts to my PayPal Business account, and after adding the contacts, I can schedule payments for a specific day and time. It's easier to make automated payroll payments with PayPal.
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.
Sometimes the UX flow would not deliver the customer back to our site, leaving orders in limbo "Pre-approved" status. The customer would call days later asking why we hadn't shipped it.
The PayPal logo on the checkout page can be kind of large and obtrusive.
They mention new features and programs on their login page, but it's hard to find any details on them deeper in the software.
It is a great product very reliable and stable for connecting various aws services like we connected with lambda function and it is working very well, never faced any issue after the setup. It also saves out lots of money as well as time after we implemented the automatic ec2 server recovery system
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
We always had a great experience with the AWS support team. They were always on time and very dependable. It was a good partnership while we worked to resolve our issues.
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.
Customer service representatives were unable to explain why customer in Australia were unable to make payments using our link. It turned out that customers in Australia must create an account. PayPal's user interface did not reveal this to our customers in Australia. There was plenty about this issue appearing in online forums and PayPal customer service couldn't explain this. This change in PayPal's usability happened between April and May of 2021 and was done without notice to vendors (like us).
When we tested Azure API Management at the time, it had serious connectivity issues, it was very unstable, and it needed to do a lot using the command line. Comparing with the AWS solution, which was more mature, and the fact that we have services in use on AWS, we ended up choosing to continue using AWS products. This so as not to run the risk of increasing latency in accesses, and of some functionality not working, due to being developed yet.
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
I don't think there's really any competition here. There's Venmo (also owned by PayPal) who is now offering business accounts, but it still isn't quite the same. The closest thing in terms of ease of use would be Apple Pay or Google Pay (and there are a handful of others out there, but we offer Apple and Google Pay). As a business, I prefer Apple or Google Pay to PayPal Payments, but we offer either Google or Apple Pay, PayPal, and credit card options and PayPal is always right up there with credit cards. I don't foresee us ever getting rid of PayPal Payments as an option, but we do try to only offer it on request for higher ticket items or high dollar installment purchases.
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.
