D
воркфлоу энджин?
Size: a a a
2021 January 13
ΛВ
его на сиплюсплюс
не, он жи сказал что там уходят от плюсов и будет скала фепе дистага
ΛВ
в ебабабике писал
ΛВ
правда описание непонятно
спарк?
D
а еще одомунтуа рассказывал идею оркестровки на скала с категориями
D
спарк?
airflow скорее
D
просто тема душная
D
куча решений и многие в облаке как услуга
ΛВ
аирфлоу тоже давно пора заменить чем-то
ᛒ
аирфлоу тоже давно пора заменить чем-то
аирфлоу пердежа де гоуса
D
An example use case for ZIO Flow might be capturing, approving, and processing expenses, with churn handover, reminders, and escalation. Another example might be assigning a ticket to an agent (with backups if the agent becomes unavailable or is terminated), with automated escalation, reminders, and resolution. Both of these use cases require the ability to orchestrate multiple fallible systems over a potentially indefinite period of time.
w
An example use case for ZIO Flow might be capturing, approving, and processing expenses, with churn handover, reminders, and escalation. Another example might be assigning a ticket to an agent (with backups if the agent becomes unavailable or is terminated), with automated escalation, reminders, and resolution. Both of these use cases require the ability to orchestrate multiple fallible systems over a potentially indefinite period of time.
Спасибо, но кол-во звезд удручает. Вы этим пользуетесь?
ΛВ
куча решений и многие в облаке как услуга
John A. De Goes, CEO of Ziverge, explains the impetus behind ZIO Flow: “Orchestrating complex, long-running business logic across human agents and cloud services is tedious and error prone, because you have to worry about failures, migrations, retries, rollbacks, auditing, security, and so much more.”
Mr. De Goes continues, “With ZIO Flow, we want to make it trivial to declare, test, and deploy bulletproof distributed workflows that power complex orchestration logic.”
Mr. De Goes continues, “With ZIO Flow, we want to make it trivial to declare, test, and deploy bulletproof distributed workflows that power complex orchestration logic.”
w
John A. De Goes, CEO of Ziverge, explains the impetus behind ZIO Flow: “Orchestrating complex, long-running business logic across human agents and cloud services is tedious and error prone, because you have to worry about failures, migrations, retries, rollbacks, auditing, security, and so much more.”
Mr. De Goes continues, “With ZIO Flow, we want to make it trivial to declare, test, and deploy bulletproof distributed workflows that power complex orchestration logic.”
Mr. De Goes continues, “With ZIO Flow, we want to make it trivial to declare, test, and deploy bulletproof distributed workflows that power complex orchestration logic.”
ущерб читаемости, и не в ботлнеке (сам таким иногда страдаю)
ᛒ
ну вода
велком в мир маркетинга миллионера из зевердж
D
John A. De Goes, CEO of Ziverge, explains the impetus behind ZIO Flow: “Orchestrating complex, long-running business logic across human agents and cloud services is tedious and error prone, because you have to worry about failures, migrations, retries, rollbacks, auditing, security, and so much more.”
Mr. De Goes continues, “With ZIO Flow, we want to make it trivial to declare, test, and deploy bulletproof distributed workflows that power complex orchestration logic.”
Mr. De Goes continues, “With ZIO Flow, we want to make it trivial to declare, test, and deploy bulletproof distributed workflows that power complex orchestration logic.”
киллер фича где
Oℕ
Это одна из моих специализаций была в САПе
D
это все уже есть