Might make sense to stick with JS to start with for the sake of simplicity.
I actually wrote a Node.js PaaS that I never open sourced & periodic short lived jobs was one of my use-cases.
Let's continue via email.
Re:Ask HN: Idea Sunday
by notduncansmith on Sunday April 20, 2014 @06:34PM
(#7618737)
Hey guys, too late to get in on this discussion? Sounds really cool and something I could see myself using a lot.
hello at duncanmsmith.com
It would definitely need to include:
* Web code editor for jobs (JS, Python, Ruby, Perl, Go, etc., etc.)
* Results served over an authenticated API (e.g., servicename.com/api/<username>/<jobname>/files/result.csv would get you the latest result.csv file generated by your script, .../<jobname>/20140419/files/result.csv would get you yesterday's, etc.)
* Jobs could probably be both scheduled (i.e., cron-like) or triggered via a webhook