temporal
Task
temporal | Task | |
---|---|---|
16 | 113 | |
9,886 | 10,017 | |
2.8% | 1.7% | |
9.9 | 9.6 | |
5 days ago | 7 days ago | |
Go | MDX | |
MIT License | 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.
temporal
-
Rethinking Serverless with Flame
I don't know if I agree with the argument regarding durability vs elastic execution. If I can get both (with a nice API/DX) via something like Temporal (https://github.com/temporalio/temporal), what's the drawback here?
-
Who's hiring developer advocates? (December 2023)
Link to GitHub -->
-
temporal VS laravel-workflow - a user suggested alternative
2 projects | 23 Aug 2023
-
Scaling Temporal: The Basics
However, as we mentioned, each shard needs management. Part of the management includes a cache of Workflow histories for that shard. We can see the History pods’ memory usage is rising quickly. If the pods run out of memory, Kubernetes will terminate and restart them (OOMKilled). This causes Temporal to rebalance the shards onto the remaining History pod(s), only to then rebalance again once the new History pod comes up. Each time you make a scaling change, be sure to check that all Temporal pods are still within their CPU and memory requests—pods frequently being restarted is very bad for performance! To fix this, we can bump the memory limits for the History containers. Currently, it is hard to estimate the amount of memory a History pod is going to use because the limits are not set per host, or even in MB, but rather as a number of cache entries to store. There is work to improve this: github.com/temporalio/temporal/issues/2941. For now, we’ll set the History memory limit to 8GB and keep an eye on them—we can always raise it later if we find the pod needs more.
-
Temporal .NET – Deterministic Workflow Authoring in .NET
Correct, the workflow's guarantee to always complete executing independent of hardware failures is dependent on the database not losing data. You host your workflow code with Temporal's Worker library, which talks to an instance of the Temporal Server [1], which is an open-source set of services (hosted by you or by Temporal Cloud), backed by Cassandra, MySQL, or Postgres. [2] So for instance increasing Cassandra's replication factor increases your resilience to disk failure.
[1] https://github.com/temporalio/temporal
[2] https://docs.temporal.io/clusters#persistence
-
Mandala: experiment data management as a built-in (Python) language feature
Re:graph frameworks - thanks for the pointers, hadn't heard about them! I'd heard of temporal which I believe provides a similar memoization capability with the purpose of not losing work in workflows that failed partway through?
-
temporal VS javactrl-kafka - a user suggested alternative
2 projects | 2 Feb 2023
-
Temporal PHP SDK: Scalable and resilent workflow orchestration on PHP
Documentation
-
Developers and Distributed Systems and Dinosaurs, Oh MY!!!
Personally I am leveraging the knowledge and momentum of Replay to dive into the Python SDK, build out a couple of applications to deepen my knowledge around Workflows, Activities, and metrics, and continue inhaling knowledge via the monthly meetup, the application development guide, and documentation. By next year I’ll experience the conference, not as one new to Temporal, but as an expert—maybe even as one of the people helping with the architecture review or running a Birds of a Feather; if anything, I know I look forward to seeing YOU at next year’s event!
- Building financial integration with Cadence in doordash
Task
-
Show HN: Workflow Orchestrator in Golang
So many tools in this space! This one looks a little bit like go-task, but it seems maybe better for production workflows because if timeout support, while go-task seems more aimed to command line work/makefile replacement.
—-
https://github.com/go-task/task
-
Essential Command Line Tools for Developers
View on GitHub
- Task: A task runner / alternative to GNU Make
-
Using Make – writing less Makefile
A similar tool is `task` https://taskfile.dev/ . It is quite capable and also a single executable. I've grown to quite like it.
-
What’s with DevOps engineers using `make` of all things?
check out tasks - a bit of a learning curve but arguably more powerful imo
-
Go Development with Hot Reload Using Taskfile
That's when I came across taskfile.dev. Task is an automation tool designed to be more accessible than other options, such as GNU Make.
-
Poetry (Packaging) in motion
Full disclosure, I did not review Conda or Hatch fully. Not that there is anything explicitly wrong with either of them. Conda is too specific to the scientific community for my general taste. Hatch seems to go well with Conda and also uses the PyProject manifest as well. It's nice that it gives you several built in tools, similar to commit hooks, but I tend to like to roll my own via a Taskfile and run them with Poetry.
-
Building RESTful API with Hexagonal Architecture in Go
Taskfile is a tool for streamlining repetitive development tasks. It helps automate activities like building, testing, and deploying applications. Unlike Makefile, Taskfile uses YAML for configuration, making it more readable and user-friendly.
-
We built the fastest CI in the world. It failed
9. We test everything with another promotion which runs make targets which build docker containers to run python scripts (pytest)
This is also built by a complicated web of wildcarded makefile targets, which need to be interoperable and support a few if/else cases for specific components.
My plan is to migrate all of this to something simpler and more straightforward, or at least more maintainable, which is honestly probably going to turn into taskfile[0] instead of makefiles, and then simple python scripts for the glue that ties everything together or does more complex logic.
My hope is that it can be more straightforward and easier to maintain, with more component-ized logic, but realistically every step in that labyrinthine build process (and that's just the open-source version!) came from a decision made by a very talented team of engineers who know far more about the process and the product than I do. At this point I'm wondering if it would make 'more sense' to replace it with a giant python script of some kind and get access to all the logic we need all at once (it would not).
[0] https://taskfile.dev/
-
Exploring GCP With Terraform: Setting Up The Environment And Project
task - a task runner and a replacement for make
What are some alternatives?
argo - Workflow Engine for Kubernetes
just - 🤖 Just a command runner
cadence - Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
doit - task management & automation tool
gocelery - Celery Distributed Task Queue in Go
goreleaser - Deliver Go binaries as fast and easily as possible
flyte - Scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks.
boilr - :zap: boilerplate template manager that generates files or directories from template repositories
DurableTask - Durable Task Framework allows users to write long running persistent workflows in C# using the async/await capabilities.
JobRunner - Framework for performing work asynchronously, outside of the request flow
Workflow Core - Lightweight workflow engine for .NET Standard
taskctl - Concurrent task runner, developer's routine tasks automation toolkit. Simple modern alternative to GNU Make 🧰