{"id":64788,"date":"2022-06-02T09:00:43","date_gmt":"2022-06-02T09:00:43","guid":{"rendered":"https:\/\/www.cryptocabaret.com\/?p=64788"},"modified":"2022-06-02T09:00:43","modified_gmt":"2022-06-02T09:00:43","slug":"get-started-with-cadence-an-open-source-workflow-engine","status":"publish","type":"post","link":"https:\/\/www.cryptocabaret.com\/?p=64788","title":{"rendered":"Get started with Cadence, an open source workflow engine"},"content":{"rendered":"

Get started with Cadence, an open source workflow engine<\/span>
\nBen Slater<\/a><\/span>
\nThu, 06\/02\/2022 – 03:00<\/span><\/p>\n

\n
Register<\/a> or Login<\/a> to like<\/div>\n
Register<\/a> or Login<\/a> to like<\/div>\n<\/div>\n
\n

Modern applications require complicated interactions between long-running business processes, internal services, and third-party APIs. To say it’s been a challenge for developers is putting it mildly. Managing these processes means tracking complex states, preparing responses to asynchronous events, and communicating with often unreliable external dependencies.<\/p>\n

Developers typically take on these complex challenges with solutions that are just as convoluted, assembling unwieldy systems that leverage stateless services, databases, retry algorithms, and job scheduling queues. Because these complex systems obscure their own business logic, availability issues are common, often stemming from the application’s dependence on scattered and unproven components. Developer productivity is regularly sacrificed to keep these sprawling, troubled systems from collapsing.<\/p>\n

Designing a distributed application<\/h2>\n

Cadence solves these issues by offering a highly scalable fault-oblivious code platform. Cadence abstracts away the usual challenges of implementing fault tolerance and durability with its fault oblivious code.<\/p>\n

A standard Cadence application includes a Cadence service, workflow, activity workers, and external clients. If needed, it’s acceptable to co-locate the roles of workflow workers, activity workers, and external clients in a single application process.<\/p>\n

Cadence Service<\/strong><\/p>\n

\n
\"Image<\/div>\n
Image by: <\/span><\/p>\n

(Ben Slater, CC BY-SA 4.0)<\/p>\n<\/div>\n<\/article>\n

Cadence is centered on its multi-tenant service and the high scalability it enables. A strongly typed gRPC API<\/a> exposes all Cadence service functionality. A Cadence cluster can run multiple services on multiple nodes, including:<\/p>\n