HackerTrans
TopNewTrendsCommentsPastAskShowJobs

wilhelmw

no profile record

Submissions

Running Services with Knative and Kong

blog.direktiv.io
1 points·by wilhelmw·5 lat temu·0 comments

Show HN: Encrypting server-side emails using serverless workflows

blog.direktiv.io
1 points·by wilhelmw·5 lat temu·0 comments

Show HN: Building AWS machines using Terraform WITHOUT a Terraform environment

blog.direktiv.io
1 points·by wilhelmw·5 lat temu·0 comments

Show HN: Direktiv new VSCode plugins and Direktiv-in-a-box

blog.direktiv.io
5 points·by wilhelmw·5 lat temu·0 comments

Show HN: Direktiv adding your own serverless custom plugins (any language)

blog.direktiv.io
2 points·by wilhelmw·5 lat temu·0 comments

Show HN: Building a simple serverless workflow using Docker containers

wilhelm-wonigkeit.medium.com
4 points·by wilhelmw·5 lat temu·0 comments

Launch HN: Direktiv: Event-Driven Serverless Container Workflows

18 points·by wilhelmw·5 lat temu·2 comments

comments

wilhelmw
·4 lata temu·discuss
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

- JSON structured data is passed to the containers using HTTP protocol on port 8080

- direktiv uses a primitive state declaration specification to describe the flow of the orchestration in YAML, or users can build the workflow using the workflow builder UI

- direktiv uses jq JSON processor to implement sophisticated control flow logic and data manipulation through states

- Workflows can be event-based triggers (Knative Eventing & CloudEvents), cron scheduling to handle periodic tasks, or can be scripted using the APIs

- Integrated into Prometheus (metrics), Fluent Bit (logging) & OpenTelemetry (instrumentation & tracing)

If you have time please try and jump on Slack to give us feedback!
wilhelmw
·5 lat temu·discuss
I'll send on the note to the team - they're very proud of it!
wilhelmw
·5 lat temu·discuss
Yep, every public cloud provider has their own implementation of serverless workflows. But we wanted to make Direktiv cloud and vendor agnostic (as much as possible) and therefore decided to use container executions as our action runtimes. The idea is that a user can standardise on containers as opposed to different "functions as a service" from multiple providers.