Neat. I have my own take on this concept[1] using Redis pub/sub instead of queues. Tradeoffs involve being able to lose data if endpoints aren't connected, but you do get the benefit of having multiple inputs and outputs on one stream, which was important for my use case.

[1] https://github.com/whee/rp

FWIW, Anveo is pretty cheap for this sort of thing. You could even do your workflow without much custom work: http://anveo.com/consumer/features.asp?code=personalize_call

(Unaffiliated, just a customer.)

How much do you pay per month? Do you use it for your cellphone?

I use it much like one would use Google Voice; forwarding to my cell phone and a couple of SIP phones with some call flow stuffs. A DID with unlimited incoming is $2/mo. With the e911 charge and outbound minutes I pay ~$3-$4/mo total.

You may be interested in http://camelcamelcamel.com/ for this sort of thing. Uses Amazon to track historical high and low price points so you can get a good idea of when to expect sales. You can set up a trigger to notify you when it reaches a certain price, too.

SEEKING WORK - Remote or Rochester, NY

Small projects, sub-projects, pieces of larger work preferred. I love a good bug hunt.

Recently used languages include Python, Go, and Perl, but I am very flexible here.

My most recent project is built with Mojolicious and PostgreSQL (https://everyminder.com/). Currently working with Django -- bonus points if you need help there. I also have experience integrating 3rd party services such as Mailgun and Stripe.

GitHub: https://github.com/whee/ Email: brian@smaertness.net

SEEKING WORK - Remote or Rochester, NY

Small projects, sub-projects, pieces of larger work preferred. I love a good bug hunt.

Recently used languages include Go, Perl, and Python, but I am very flexible here.

I have some experience with Rails, but most recently Mojolicious (built https://everyminder.com/). My recent interest is Django -- bonus points if you need help there. I also have experience integrating 3rd party services such as Mailgun and Stripe.

GitHub: https://github.com/whee/ Email: brian@smaertness.net

Started working on and launched Everyminder, a web app to handle infrequent maintenance tasks I always forget about: https://everyminder.com/

It's currently pretty basic, but I have lots of neat stuff on my todo list -- should be a fun ride.

I think you are analyzing too early. If this project is tackling a problem you haven't solved before, think of your first implementation as a prototype. You likely don't understand the problem until you have spent time solving it.

After you have something that works, you will have a good feeling for what you should've written the first time.

Personally, I don't abstract until I need it. Writing code because you "probably will need it later" can cause unnecessary work and be a distraction.