Integration with run-once services like AWS Lambda?

[jonnor]

JsJob computation style is oriented around small to medium "jobs", quite similar to that of AWS Lambda. Such services have the advantage that they are super elastic:

• billed by the second/millisecond
• built-in horizontal scaling
• very fast startup/teardown times

Integration could for instance be having a plug-and-play image that can run a headless browser (like PhantomJS) and execute JsJobs in same manner as self-hosting or standard cloud-hosting. This should be 100% compatible and transparent to the JsJob. Disadvantage is that browser startup may be significant, depending on typical size of job. Would need metrics for measuring how long it takes to judge the impact.

[bergie]

@jonnor however, some jobs will probably expect a browser context. We should somehow "flag" them

[jonnor]

Everything in JsJob is browser now, and this would (at least on its own) not change that.