direktiv VS cronitor-airflow

That went okay, but there is still the startup problem - it took ages to run the lifecycle hook, plus it won't function on Kubernetes nodes with no internet access. At Direktiv were are using Knative a lot as well which does not support lifecycle events. So, my plan was to create a container using the Ollama image as base with the model pre-downloaded.

When deciding which option to choose, consider your specific environment, requirements, and preferences. At Direktiv, we typically opt for Contour due to its simplicity. However, your choice may vary depending on your use case and infrastructure setup.

So being completely transparent, we're the creators of Direktiv (https://github.com/direktiv/direktiv). We're genuinely curious to have users who have previously used Airflow and other DAGs (mentioned in here is Argo workflows) try Direktiv and give us more feedback.

- direktiv runs containers as part of workflows from any compliant container registry, passing JSON structured data between workflow states.

If you want a portable step functions take a look at https://github.com/vorteil/direktiv developers are very helpful and responsive

Another update to our Direktiv event-driven serverless workflow engine - but this one focused on development. Release v0.3.1 included some bug fixes, improved stability and security enhancements, but more notably:

We've previously posted on our serverless workflow / automation engine called Direktiv and wanted to share a couple of updates:

Is anybody out there doing anything interesting with Airflow monitoring?

At my startup Cronitor we have an Airflow sdk* that makes it pretty easy to provision monitoring for each DAG, but essentially we are only monitoring that a DAG started on time and the total time taken.

* https://github.com/cronitorio/cronitor-airflow