Introduction In the previous post, you were introduced to Temporal and its main building blocks, ZIO Temporal , and the Content Sync Platform we’re developing. In this post, we’ll develop your own Workflows and Activities! A quick reminder: Activity is all the hard work and technical details. Activities perform error-prone operations (such as interactions with external systems and APIs), complex algorithms, etc. Workflow is the business process definition represented as code.
Introduction Do you spend a lot of time making your applications resilient: dealing with distributed state and locks, migrating from sync to async communication, adding retries, tracing? That’s a usual programming routine that we, as engineers, must care about. On the other hand, it shifts our focus to technical issues instead of the original business problem. Can we change the status quo? Are there any tools to help us struggle less and to be more productive?
Hello there, my name is Vitalii, and this is my first blog post 👋 I’m passionate about software engineering (especially Scala, but also like Python). The things I feel the most interested in are Functional Programming, Data Engineering, Distributed Systems in general, Workflow Management Systems, etc. I believe software engineering (and functional programming in particular) should be: Principled but practical Pragmatic enough but still enjoyable Inclusive and welcoming for newcomers! First time on this website?