You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If users of platform-app make use of state.meta to access things like the runId, there's not much we can do about it on microservice... in that sense, it is possible to write jobs which run on platform but not on microservice. I think that's always going to be possible, and we'll have even less control over how folks build and pass around state on their own implementations.
However, I think that including a last_success timestamp is arguably valuable enough to be shared between platform and microservice... it's very useful for keeping a "cursor" between runs, allowing a cron job to access only resources that have been created/updated since the last_success -ful run of the job.
Thoughts?
The text was updated successfully, but these errors were encountered:
If users of
platform-app
make use ofstate.meta
to access things like therunId
, there's not much we can do about it onmicroservice
... in that sense, it is possible to write jobs which run onplatform
but not onmicroservice
. I think that's always going to be possible, and we'll have even less control over how folks build and pass aroundstate
on their own implementations.However, I think that including a
last_success
timestamp is arguably valuable enough to be shared betweenplatform
andmicroservice
... it's very useful for keeping a "cursor" between runs, allowing a cron job to access only resources that have been created/updated since thelast_success
-ful run of the job.Thoughts?
The text was updated successfully, but these errors were encountered: