NGINX vs. Twilio

[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.

Incentivized

Twilio is well suited to sending SMS reminders to prospects on the lead-up to sales appointments. This has helped us improve attendance rates for these meetings. We also use Twilio to communicate with these prospects post-meeting to make offers on products and services and for feedback on their meeting.

Incentivized

• 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)!

Incentivized

• Easy to see my team in one place, when they log in and out and what call status they are in.
• Twilio is a simple, user friendly way to log in and out of work activities.
• Excellent services and support.
• The omnichannel feature which allows agents to get request from all channels.

Incentivized

• 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.

• Segment’s email identifier is case-sensitive, which is ridiculous because emails themselves are not case-sensitive. This means that if I send a capitalized email address in an identify call, it will create a duplicate user rather than matching it with the lowercase email. I think this is a technical oversight that should be corrected.
• I’d like to see more information about the eventual transition of existing Frontline customers to Twilio Flex
• I’d like to see some integrations between Twilio Studio and OpenAI or another open source LLM to provide automated responses, if this hasn’t been done already
• I would like to be able to drag and move the actual lines connecting the steps in Twilio Studio, sometimes mine can get pretty messy
• I think a Bug Report form would be beneficial for developers

Incentivized

Great value for the product

Incentivized

Unless we can get this handled quickly -- less than 1 week -- we will likely switch to another provider who, in my opinion, we'll have to spend close to $3,000 in development time to build a new integration for texting. Our clients need texting and I feel Twilio has failed us miserably.

Incentivized

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.

Incentivized

Twilio has well documented APIs and examples. There are several tutorials, videos and Q&As regarding their services. So, usability is very good. I must say that advanced knowledge of telephony, API/Programming and error-handling is essential to make good use of Twilio. It's not just plug-and-play unless you are integrated with a system that has all of the programming built for it.

Incentivized

The problem tends to be us, the user, rather than Twilio. We don't reach out to support fast enough (spend time struggling), but when we have, they've solved our issue immediately. We are rural, so there are signal issues to accommodate, however, we find that a few staff on a few cellular networks can triangulate where we all have signal to put up a sign.

Incentivized

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.

Incentivized

I have not had to communicate with Twilio support in the last 3 years but my past experience with them has been very positive. They replied to my previous requests promptly and kept me well informed to resolve my inquiries. With their documentation that's available, I hardly imagine why anyone would need to contact support since it's all there in a concise and easy to understand format. It would probably take you longer to type out a support ticket than to just open their doc websites.

Incentivized

The developer APIs and SDKs are super easy to follow.

Incentivized

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

Incentivized

Twilio was referred to me by a business colleague, and I can't be more thankful! Twilio has helped my Facebook page by leaps and bounds, and I haven't even considered trying another chat option for my page. It is easy to set up, and customer service is quick to answer any and all questions you may have. I highly recommend it!

Incentivized

Being in South Africa, direct local currency support would be nice

Incentivized

• 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.

Incentivized

• It helps drive the adoption of multi-factor authentication by making second-factor authentication quick and easy.
• Decreases the number of times a user spends migrating to a new device from an old one.
• Enables easy access to second-factors of authentication by offering multi-device support, making multi-factor authentication painless.

Incentivized