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
There are two orchestration models for the durable workflow concept:
Central server (Temporal / Cadence)
Database only, clients/workers talk to the data store (go-workflows / DTFx)
Are there any big drawbacks of this DB-only model? It greatly simplifies things in practice to not require managing additional server components, but seems Temporal server must be solving for some issue. I couldn't find anything about this mentioned in the README. Would love to hear any thoughts on it!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
There are two orchestration models for the durable workflow concept:
Are there any big drawbacks of this DB-only model? It greatly simplifies things in practice to not require managing additional server components, but seems Temporal server must be solving for some issue. I couldn't find anything about this mentioned in the README. Would love to hear any thoughts on it!
Beta Was this translation helpful? Give feedback.
All reactions