Live data from Hacker News

Show HN: A Node.js open source library to send transactional notifications

github.com

1–10 of 18 posts

Re: Show HN: A Node.js open source library to send transactional notifications

#4

Are there any well-tested Node.js libraries to do scheduling alongside something this? E.g., if I wanted to send the notifications once a week, etc.

I've used https://github.com/kelektiv/node-cron in the past, which could be run in the same process as the web app or in its own process. Works really well for recurring jobs.

Re: Show HN: A Node.js open source library to send transactional notifications

#5
post #2

from the docs this looks like a really practical library. The testing and dev tools look great. whats the backstory for this library?

Hi hitgeek, thanks for your comment. The backstory is quite simple, the initial plan was to make a saas api service, but we don't like cold calling so much, so it ended up as an open source project :)

Re: Show HN: A Node.js open source library to send transactional notifications

#7

What is a "transactional" notification? This doesn't seem to be explained anywhere in the README.

A notification that is sent based on some trigger. I think the terminology comes from email marketing https://sendgrid.com/blog/marketing-email-vs-transactional-e...

Re: Show HN: A Node.js open source library to send transactional notifications

#8
post #7

What is a "transactional" notification? This doesn't seem to be explained anywhere in the README.

A notification that is sent based on some trigger. I think the terminology comes from email marketing https://sendgrid.com/blog/marketing-email-vs-transactional-e...

That's what I assumed, but it would be nice if that were made explicit.

Re: Show HN: A Node.js open source library to send transactional notifications

#10
post #7

Earlier quoted context omitted.

A notification that is sent based on some trigger. I think the terminology comes from email marketing https://sendgrid.com/blog/marketing-email-vs-transactional-e...

That's what I assumed, but it would be nice if that were made explicit.

Thanks for the feedback. I added the word "transactional" to say that we can't send batches with the lib. Anyway it's not a hard limitation because you can always make a loop.
Post reply on HN