direktiv
proposals
direktiv | proposals | |
---|---|---|
13 | 60 | |
464 | 63 | |
1.5% | - | |
10.0 | 4.2 | |
4 days ago | 4 days ago | |
TypeScript | ||
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
direktiv
-
Preloading Ollama Models
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.
-
Knative Serverless in 2024
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.
-
Lessons Learned from Running Apache Airflow at Scale
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.
- Encrypting server-side emails using serverless workflows using Direktiv
- Encrypting server-side emails using serverless workflows
-
Step Functions Wait Loop w/ Timeout Feature
If you want a portable step functions take a look at https://github.com/vorteil/direktiv developers are very helpful and responsive
-
Direktiv: Docker development environment, VSCode plugin & Infrastructure-as-a-Chatbot
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:
-
Update to our serverless workflow engine Direktiv
We've previously posted on our serverless workflow / automation engine called Direktiv and wanted to share a couple of updates:
proposals
-
Is there an alternative for Airflow for running thousands of dynamic tasks?
Check out temporal.io open source project. It was built at Uber for large scale business-level processes. So any data pipelines are low-rate use cases by definition.
-
KuFlow as a Temporal.io-based Workflow Orchestrator
With KuFlow it is also possible to work with serverless workflows apart from Temporal.io, we explain it in this blog entry, but in summary, almost as a no-code tool, the correct use It would be a rather low-code tool; in just a matter of minutes with our drag-and-drop tool, you can have a workflow that interacts with one or more users of the organization.
-
How to handle background jobs in Rust?
Otherwise you may want to look into Kafka or Fluvio to ensure that task runs at least once. If you're doing something like batch operations as a background task, Temporal is another great option.
-
No-code or Workflow as code? Better both
The runtime is developed using Temporal, which is one of the main tools that we are currently using at KuFlow. Thanks to, all the workflow executions are robust: your application will be durable, reliable, and scalable.
-
Temporal Programming, a new name for an old paradigm
Hmmm I got confused by the name. I thought it's related to https://temporal.io/
-
Possible innovations in Event Sourcing frameworks.
Have you looked at temporal.io open source platform? It uses event sourcing as an implementation detail. But it greatly simplifies the user experience compared to "raw event sourcing."
-
After Airflow. Where next for DE?
Rewrite Airflow on top of temporal.io. This way, you get unlimited scalability and very high reliability out of the box and would be able to innovate on the features that matter for DE.
-
Show HN: Retool Workflows – Cronjobs, but better
Hi all, founder @ Retool here. Over the past year, we’ve been working on Retool Workflows; a fast way for engineers to automate tasks with code. We started building the product because we ourselves (as developers) were looking for something in-between writing cron jobs (which involves a lot of boilerplate) and Zapier (which oftentimes isn’t customizable enough, since it doesn’t _really_ support writing code).
Workflows is a code-first automation tool: you’re _expected_ to write code, but we handle all the boilerplate for you. For example: out-of-the-box integration with 80+ resources (you probably don’t want to be trying to figure out OAuth 2.0 with Salesforce!), monitoring and observability (so you can see the output of every run in the past, and immediately be notified if something goes wrong), and permissions (e.g. some Okta groups can see the outputs of Workflows, but can’t change the code itself).
Right now, the product is cloud-only, but we’re hard at work at an on-prem, self-hosted version (in a Docker image). If you’re interested in that version, feel free to email us at [email protected]. We aim to get it out in the next few weeks. Self-hosted Retool is responsible for a large portion of our usage today, and we’re excited to be supporting Workflows too.
All Retool plans now include 1GB of Workflows throughput, which we think is quite generous (80% of active Workflows users are below 1GB). We don’t bill by run at all, so you’re welcome to run as many workflows as you want.
We use a bunch of interesting technology for Workflows; we are, for example, using Temporal (https://temporal.io/) under the hood. That’s something we’re going to be writing a blog post about later. (We’ve been hard at work on the launch, hah.)
-
How KuFlow supports Temporal as a worfkows engine for our processes?
In such a diverse world, it would be boring to have a single way of doing things. That's why at KuFlow we support different ways to implement the logic of our processes and tasks. And in this post, we will talk about one of them, the orchestration through Temporal, which gives us a powerful way to manage our workflows.
- Library for manage tasks when make a workflow automation.
What are some alternatives?
direktiv-apps - Direktiv Application Containers
conductor - Conductor is a microservices orchestration engine.
states-language-cadence - States Language on Cadence
temporalite-archived - An experimental distribution of Temporal that runs as a single process
argo - Workflow Engine for Kubernetes
zenml - ZenML 🙏: Build portable, production-ready MLOps pipelines. https://zenml.io.
windmill - Open-source developer platform to turn scripts into workflows and UIs. Fastest workflow engine (5x vs Airflow). Open-source alternative to Airplane and Retool.
seldon-core - An MLOps framework to package, deploy, monitor and manage thousands of production machine learning models
toil - A scalable, efficient, cross-platform (Linux/macOS) and easy-to-use workflow engine in pure Python.
kubemq-community - KubeMQ is a Kubernetes native message queue broker
stepwise - Clojure AWS Step Functions library
nextjs-cron - Cron jobs with Github Actions for Next.js apps on Vercel▲