DSL vs Workflow-as-code (Wac) - which is right? #541
Replies: 5 comments 20 replies
-
Yes, in Temporal you write workflows as code, but you can run any DSL on top of Temporal. There is a Java sample that runs our DSL on top of Temporal here. We are also working on out-of-box integration with Java SDK (repo still private atm but will be public soon) and if there is adoption will add it for TypeScript and Go SDKs as well in the future. As far as how you should write your workflows, thats really up to you. Here is a blog I wrote that kinda talks about pros/cons of major used ways of writing workflows. |
Beta Was this translation helpful? Give feedback.
-
@globalflea let me know if you want to be added to our currently private repo for Temporal integration (Java). No need to contribute, but maybe you can get some ideas about a possible Go impl, and I can add you to slack channel where the discussions are happening as well. Also feel free to ping me or @antmendoza with questions about integration. |
Beta Was this translation helpful? Give feedback.
-
This is awesome I would like to not have the Java dependency and just run Temporal with the DSL. If there is any interest in this I am happpy to contribute. I am not sure yet but I imagine I need to write a bridge between Temporal and the DSL ? |
Beta Was this translation helpful? Give feedback.
-
I'd really like all of your help with the Temporal integration work. Can you please give indication on how much time per week you would be able to work on this (just ballpark is enough) and what SDK you want to help with and let's start planning for this. |
Beta Was this translation helpful? Give feedback.
-
Guys, I'm starting soon! Since I didn't want to use graylog because it uses Java (I think it's heavy) and uses elasticsearch for searches, I think it's expensive to maintain an elastic cluster. So in this project he uses Atlas Search (lucene). And next week I'm going to start this project! Sorry I'm late getting started, but I had other demands I needed to fulfill! |
Beta Was this translation helpful? Give feedback.
-
in another discussion with tsurdilo, he shared a youtube video when the serverless spec was implemented on temporal.io (#526)
I watched the video and was intrigued by temporal.io, as it provides a lot of the fundamental features required for long-running workflows. Digging a little deeper, however, i found that temporal introduces the concept of "Workflow as code" (as with a lot of other "... as code" recently). This seems to be a big contrast to the DSL approach and i am now wondering if the DSL approach still make sense - i.e. which is better DSL or Workflow-as-code (WaC)??
Beta Was this translation helpful? Give feedback.
All reactions