incubator-dolphinscheduler VS workflows-samples

rewrite.xml service.xml API /dolphinscheduler/api dolphinscheduler API Dolphinscheduler the provided scheduling system UI supports fast scheduling of DAG by dragging and dragging Retrieve data for the specified attribute search query POST dolphinscheduler/login If you want to learn more api for dolphinscheduler, please refer here https://dolphinscheduler.apache.org/en-us/docs/latest/user_doc/guide/open-api.html

Join the Community There are many ways to participate and contribute to the DolphinScheduler community, including: Documents, translation, Q&A, tests, codes, articles, keynote speeches, etc. We assume the first PR (document, code) to contribute to be simple and should be used to familiarize yourself with the submission process and community collaboration style. So the community has compiled the following list of issues suitable for novices: https://github.com/apache/dolphinscheduler/issues/5689 List of non-newbie issues: https://github.com/apache/dolphinscheduler/issues?q=is%3Aopen+is%3Aissue+label%3A%22volunteer+wanted%22 How to participate in the contribution: https://dolphinscheduler.apache.org/en-us/community/development/contribute.html GitHub Code Repository: https://github.com/apache/dolphinscheduler Official Website:https://dolphinscheduler.apache.org/ Mail List:dev@[email protected] Twitter:@dolphinschedule YouTube:https://www.youtube.com/channel/UCmrPmeE7dVqo8DYhSLHa0vA Slack:https://s.apache.org/dolphinscheduler-slack Contributor Guide:https://dolphinscheduler.apache.org/en-us/community/index.html Your Star for the project is important, don’t hesitate to lighten a Star for Apache DolphinScheduler ❤️

Corresponds to PR: 9840 link https://github.com/apache/dolphinscheduler/pull/9840

The official website of the Apache DolphinScheduler project can be found at: https://github.com/apache/dolphinscheduler

GitHub Code Repository: https://github.com/apache/dolphinscheduler

So the community has compiled the following list of issues suitable for novices: https://github.com/apache/dolphinscheduler/issues/5689

Have you seen this? https://cloud.google.com/workflows

Cloud Workflows: A serverless workflow orchestration service

Workflows can trigger actions, like Cloud Run Jobs, in a sequence of steps. The Workflows product waits for the job to complete, fail, or time out before it moves on to the next step. It uses polling to check on the job, so there may be a delay between the job finishing and the next step.

Has anyone integrated firestore/realtime database together with GCP workflows? What was your use case? How was your experience with it? Why have you decided to go that way?

In the past few years, YAML (http://yaml.org) has become an essential part of software, particularly for infrastructure-as-code tools. Yaml at the heart of kubernetes configuration, kubernetes-inspired APIs like Google's config connector, and a number of workflow systems like Google Cloud Workflows and Github Actions.

If your routine is just a bunch of API calls, you can also replace steps 1-2 with Workflows.

I have come at this problem from a bit of a different angle by asking what is the closest I can possibly get to the hypothetical dream state of everything is automated, autoscaling blah blah blah as possible with the absolute smallest budget in terms of not only actual costs but time budget as well.

I only know the GCP ecosystem kind of well so I don't fully know to what extent these things exist in AWS and Azure but there I think there is a really nice path you can get on with the serverless route that skips K8s entirely but keeps you very well aligned in case you ever need to "upgrade" or get out of the GCP ecosystem.

I write very stock standard gRPC services and then put them onto Cloud Run (which has a very Heroku like workflow) and stick https://cloud.google.com/api-gateway in front of things and now my API is running on the exact same setup as any other service Google is running in production. Huge amounts of logic get moved out of my code base as a result.

If you are also willing to write your APIs a fairly particular way https://google.aip.dev/ it starts to become trivial to integrate other things like https://cloud.google.com/workflows, https://cloud.google.com/pubsub and https://cloud.google.com/tasks which is traditionally where a lot of the "state" and weirdly complicated logic previously lived in my code. I'm now not really writing any of that.

Now it's all declarative where I just say what I want to happen and I don't have to think about much else beyond that because it too is using that same internal GCP infrastructure to handle all the complicated parts around what to do when things go wrong.

But to me they are all extremely heavily aligned with the K8s path so the lock in certainly doesn't feel as scary.

Google Workflows combines Google’s cloud services and APIs to help developers build reliable large-scale applications, process automation, and deploy machine learning and data pipelines.

Lately, I build a system using Cloud Workflows which can combine Google Cloud Services such as Cloud Functions and Cloud Run. Sometimes, I was in a situation where I want to examine more efficiently using logs on Cloud Logging when debugging or daily monitoring.

Look at Cloud Workflows for simple workflows