Amazon Web Services vs. Twilio SendGrid

One of the scenarios I can think of is to Deploy a web application that may experience fluctuating traffic. AWS EC2 and Elastic Beanstalk allow for quick deployment and easy scaling accommodating traffic spikes without downtime. Next thing is to analyze large datasets for business insights. AWS services like EMR (Elastic MapReduce) and Redshift enable efficient processing and analysis of big data with minimal setup. Now for one of the scenarios where is less appropriate is if we want to host a simple static website, for basic sites using a dedicated hosting service like GitHub Pages or Netlify may be simpler and most effective than AWS

Incentivized

Twilio SendGrid is well suited for those organizations who need to send mass emails very often to their prospects and customers and thus may be wary of a reliable tool that can do that without affecting domain reputation. It may be less suited for organizations which do not have say more than 10,000 target prospects and thus may rely only on 1:few ABM for sending emails.

Incentivized

• Starting an instance and accessing it for testing purpose, demo or production deployment its always easy.
• All the things which are available over AWS are pretty well managed and easy to use.
• You might find everything you required for an product and other development over AWS.
• Its suitable for both either an enterprise or an startup
• Various resources and documentation are available in case you struck somewhere.

Incentivized

• Managing email lists / audiences is easy with features like groups and segments.
• They provide pre-built email templates that are very easy to modify. It is also super easy to create new email templates with their drag-and-drop email builder.
• Provides clear / easy-to-read analytics of email campaigns.
• I can easily import large email contact lists all at once or add a user manually one-at-a-time, when needed.

Incentivized

• If there is one thing I think AWS needs improvement on, it is the administration dashboard. It can be a nightmare to use especially when trying to access billing. This could be made better, honestly, as there should be a simplified way to access simple admin features.
• While AWS was fairly easy to integrate into our solutions, it is not as easy to use without some IT knowledge. The dashboards are complicated and designed for someone who is computer savvy. If you are just want to keep track of billing, for example, you may need to take a course or spend a few hours with someone being walked through the admin console.
• AWS does tend to be slow at times. If you do not have a fast internet connection, it can take time to access services that are hosted on AWS. This is not always the case but we have had clients complain about this if they are trying to access a service from multiple points (IP addresses). The only real fix we found was to make our files cache to another server and only keep current data accessible to clients.

Incentivized

• Not necessarily their Email API but their email in general - they are currently in beta for automated email sequences but are still bare bones. Much more work is needed before it can be used mainstream and be able to convert everything to SendGrid.
• Helping with warming up our dedicated IP for the best-sending score.
• We seem to hit the promotions folder a decent amount (maybe the IP problem above) and even a lot of their emails hit my spam or promotions folder (whether they be transactional or marketing) which isn't a great sign when trusting an ESP.
• Transactional email sequences would be a huge plus.
• Now that Twilio owns SenGrid, having an integrated platform where you could see all our transactional emails together.
• Better reporting and split reporting between transactional and marketing emails.

Incentivized

We are almost entirely satisfied with the service. In order to move off it, we'd have to build for ourselves many of the services that AWS provides and the cost would be prohibitive. Although there are cost savings and security benefits to returning to the colo facility, we could never afford to do it, and we'd hate to give up the innovation and constant cycle of new features that AWS gives us.

Amazon Web Services is a great tool when it comes to middle size organizations like us. It provides multiple tools and functionalities in low costs. The best feature we have to pay as we go. No financial burden on company for the unused instances. It also comes with greater level of security such as two level authorization such as multi factor authorization.

It has the potential to be really cool. However, it feels as if it was created by developers for developers (and I work with developers, yet even for me the instrument was somewhat not easy to use - just read SendGrid's help manuals...) However, if you are into data and your way of thinking is more mathematical rather than lyrical, you'll enjoy this instrument

Incentivized

Availability is very good, with the exception of occasional spectacular outages.

AWS does not provide the raw performance that you can get by building your own custom infrastructure. However, it is often the case that the benefits of specialized, high-performance hardware do not necessarily outweigh the significant extra cost and risk. Performance as perceived by the user is very different from raw throughput.

The customer support of Amazon Web Services are quick in their responses. I appreciate its entire team, which works amazingly, and provides professional support. AWS is a great tool, indeed, to provide customers a suitable way to
immediately search for their compatible software's and also to guide them in a
good direction. Moreover, this product is a good suggestion for every type of
company because of its affordability and ease of use.

Incentivized

Twilio SendGrid Email API is everything we want it to be, and we have no reason to look for any other solution. Features and pricing match exactly what we need. As developers for SaaS products, Twilio SendGrid Email API provides a great service. I hope that they stay this way and don't inflate the service with too many marketing oriented features, because there are other tools for that and Twilio SendGrid Email API is a API for sending email first and foremost.

Incentivized

The API's were very well documented and was Janova's main point of entry into the services.

Amazon Web Services is well suited when we have a huge amount of data to store, process, manipulate and get meaningful information out of. It is also suitable when we need very fast data retrieval from the database. They provide a superior product at a fair price which allows us to further our goals and push the limits of what we are capable of as a team / company.

Incentivized

Sendgrid has a lot of features that other providers have and a few more - like the dynamic template builder, which AWS SES doesn't have. We choose the provider based on the scenario of use and the provider we're using. If we're going to be making regular changes to a template, then we'd go with Sendgrid, as the changes will be easier to make and don't necessarily require developer intervention.

Incentivized

• AWS has lowered our employee cost, because you don't have to hire Network/Server Admins to manage infrastructure.
• Increased productivity by incorporating Continuous Integration with AWS and our development life cycle.
• Increased customer confidence by being able to provide HIPAA level security in our development and production environments

Incentivized

• As it was cheaper than the transactional service we previously used, it saved costs.
• The API was relatively easy to work with so it helped us ship the service and test it quickly.
• We still use the transactional email service, even though we recognize its limits as it meets our immediate needs.

Incentivized