Delayed function invocation - cron jobs

[marktani]

For now, external services like webtask cron are a great alternative.

[kbrandwijk]

+1

[cameronk]

+1 as well

[codenprose]

+1

[ghost]

+1

[caeruscaerus]

+1
This would make building full apps so much simpler and maintainable.

[Aathi]

+1

[bayukp]

+1

[MarkLyck]

+1

[Zuzle]

+1

[the-simian]

+1 this is, in my mind, something essential to being able to fully replace a standard server with this architectural approach

[kbrandwijk]

Given how well Graphcool fits into a serverless architecture (AWS, webtask, or any of the other providers, useful for deploying resolver functions and other external endpoints as well), I strongly feel that making this built-in functionality should not be a priority.

[dardub]

@kbrandwijk Right now I have a scheduler in webtask.io, which means I have to have implementations for the same service split between two separate service providers. Maybe, I'm missing something, but this doesn't seem like good serverless architecture.

To add: Aside from missing a scheduler feature in graph.cool, I have no other reason to use webtask.io. That is why I believe it should be a high priority.

[jvbianchi]

Is this planned for 1.0 (#353)?

[marktani]

This issue has been moved to graphcool/graphcool-framework.

[kurt-o-sys]

+1

absolutely necessary. webtask cron isn't always a solution, if e.g. one needs to fetch new tokens (due to expiry dates) that are necessary to authorize api calls to external services. Please please...

[anaibol]

+1