The logo looks like a recoloured Telegram logo [0]. I'd recommend you change it before this gets big to avoid trademark shenanigans.
[0]: https://telegram.org
Show HN: A Node.js open source library to send transactional notifications
11–18 of 18 posts
Re: Show HN: A Node.js open source library to send transactional notifications
#12Are 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.
Yes thanks, using something like node-cron can resolve your problem.
Re: Show HN: A Node.js open source library to send transactional notifications
#13The logo looks like a recoloured Telegram logo [0]. I'd recommend you change it before this gets big to avoid trademark shenanigans. [0]: https://telegram.org
Which looks like http://fontawesome.io/icon/paper-plane/
I don't think our logo harms them in any way.
Re: Show HN: A Node.js open source library to send transactional notifications
#14We just wrote something similar, using RabbitMQ (https://github.com/richthegeek/beatrix) as the main manager for things.
Seems like retries and delays are not part of this, but I guess they are added easily enough to the individual queue system used. Any desire to build them into it? Retries should be easy enough if you're happy to modify the bodies, although delays are not so easy (we're using the 'delayed message exchange' plugin for Rabbit to do this currently).
Maybe some built-in/example queue integrations (Rabbit, Redis, etc)?
Also, it's not super clear to me how you might host the SMS/Push/email/whatever provider on a different process/system to the publisher?
But it looks lovely and clean! Major props!
Re: Show HN: A Node.js open source library to send transactional notifications
#15We just wrote something similar, using RabbitMQ ( https://github.com/richthegeek/beatrix ) as the main manager for things. Seems like retries and delays are not part of this, but I guess they are added easily enough to the individual queue system used. Any desire to build them into it? Retries should be easy enough if you're happy to modify the bodies, although delays are not so easy (we're using the 'delayed message…
Very nice, queue integration examples are one of my next steps. I didn't include the queue inside the lib to give the choice to users, but I intended to write a few ones. Would you want code one? About the consumer, it's running on the same instance than the producer for more simplicity (but you can always run instances that only do consumer job).
Re: Show HN: A Node.js open source library to send transactional notifications
#16ahh this looks awesome! will try it out. I love the fact that you can use any queue with this <3
Re: Show HN: A Node.js open source library to send transactional notifications
#17Shameless plug here.. I've been working on a service that kinda solves a similar problem, called Postways [1].
Even though Postways also provides a unified API for sending email, SMS and mobile push, the main focus of Postways is actually on managing the message templates. When you work with a team where not everyone is a developer, updating the actual message text can be a major problem, especially when the message text is in source code or various different places.
Re: Show HN: A Node.js open source library to send transactional notifications
#18Earlier quoted context omitted.
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.
I would really suggest clarifying what you mean somewhere then because I don't think anyone would interpret it that way.