-
Notifications
You must be signed in to change notification settings - Fork 863
Delayed function invocation - cron jobs #142
Comments
+1 |
+1 as well |
+1 |
1 similar comment
+1 |
+1 |
+1 |
+1 |
+1 |
1 similar comment
+1 |
+1 this is, in my mind, something essential to being able to fully replace a standard server with this architectural approach |
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. |
@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. |
Is this planned for 1.0 (#353)? |
This issue has been moved to graphcool/graphcool-framework. |
+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... |
+1 |
For now, external services like webtask cron are a great alternative.
The text was updated successfully, but these errors were encountered: