2 ms·
Do you have any blog posts on task-queues and email sending/receiving? I'm trying to learn Phoenix and Elixir by rewriting an app I have that does just this. S
by tbrooks 11y ago
Do you have any blog posts on task-queues and email sending/receiving? I'm trying to learn Phoenix and Elixir by rewriting an app I have that does just this.
Sidekiq has been great as a background worker, but I'd like to try concurrency elsewhere.
- houshuang 11y agoJust wrote something on [sending errors by emails](http://reganmian.net/ http://reganmian.net/). The full code is here: https://github.com/houshuang/survey https://github.com/houshuang/survey, including my job module https://github.com/houshuang/survey/blob/master/lib/job_worker.ex https://github.com/houshuang/survey/blob/master/lib/job_work.... The code worked well for me, mostly because it registers errors and retries (I had problems with rate-limiting of Amazon SES), however it's not parallel right now. I will probably rewrite it to have a single module that gets tasks from the DB, and then dispatches it to workers, and I want to split it out into a separate library. Note that this was my first Elixir library and I was very much learning as I went along. Lot's of code that I want to refactor and extract.
- tbrooks 11y agoWow, this is awesome. Thanks for sharing!
- ghayes 11y agoIf you're curious about the framework as well, here's the source for an app I made for peer-to-peer file sharing in Phoenix: https://github.com/hayesgm/fuego https://github.com/hayesgm/fuego. You can try it out here: https://fuego.link https://fuego.link Phoenix has really been exciting to use. It's a great way to get introduced into the OTP system from Erlang (plus all of Erlang's modules), it's incredibly fast, and the immutable data structures make it easy to reason about your concurrent code. I would strongly suggest giving it a try.
- quantumtremor 11y agoReal realities. Can you believe it?!