3 ms·
You're right, if you have a lot of code already committed to the SendGrid API then it makes sense that the saving would have to be large to warrant developer ti
by wlll 16y ago
You're right, if you have a lot of code already committed to the SendGrid API then it makes sense that the saving would have to be large to warrant developer time, but at some number of emails/month you reach a tipping point.
For new apps it's an easier decision.
- JeremyBanks 16y agoI think a large part of his point is that most software support's "the SendGrid API" by default, since it's SMTP. Ever for news apps that reduces the number of libraries easily available.
- wlll 16y agoPossibly, but you still need to background process the email sending for most apps even if you are sending via SMTP, and at that point an API call isn't too much to add, IMO.
- cagenut 16y agono you don't, you run an mta bound to 127.0.0.1 and smarthost out sendgrid/whatever-your-outbound-relay-is. this has been standard practice forever. if you quiz 10 sysadmins to name a single config variable for sendmail, most will answer "DS".* mta's have been doing asynchronous message queuing loooooong before it was cool with web developers. *note, the ones who go off on a tangent about mta holy war's are the bad ones