cron VS proposals

Features - Supports Slack Apps using Socket Mode - Easy definitions of commands and their input - Built-in help command - Bot responds to mentions and direct messages - Simple parsing of String, Integer, Float and Boolean parameters - Customizable, intuitive and with many examples to follow - Replies can be new messages or in threads - Replies can be ephemeral, scheduled, updated or deleted - Supports Slash Commands and Interactive Messages - Supports context.Context - Supports middlewares & grouping of commands - Supports Cron Jobs using https://github.com/robfig/cron - Handlers run concurrently via goroutines - Full access to the Slack API github.com/slack-go/slack

You could this https://github.com/robfig/cron

This will print "Valid cron expression: */20 * * * *" to the console. You can find more information about this library, including installation instructions, on its GitHub page: https://github.com/robfig/cron

I used robfig/cron on each of the workers. I only had on the order of ~10 workers so polling was not an issue.

There are many excellent open-source projects on GitHub, where the code is transparent and available to everyone. As software developer, we can learn a lot from them including software engineering, unit testing, coding style standardization, etc. We can even find issues by looking into their code, and submit pull requests to contribute to tech communities. Today we are going to dig into the source code of a popular Golang open-source project on GitHub, robfig/cron, which is small and with clear annotations, and is very suitable for new developers to learn how to read and analyze source code.

Now let's implement the core of task scheduler, cron job. We will be using robfig/cron, a reputable cron library written in Go.

# Hello Everyone! Ive built this cronjob library after the trusted: https://github.com/robfig/cron.

I suggest this library.

You can take inspiration on cron lib, create a Job i's a function that you give a channel for quit action, and a probably cancel function (from background.WithCancel) for cancel running asynchronous task. You can have a scheduling worker if you decouple a great task to multiple job that listen to a channel that emit event.

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.

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.

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.

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.

Hmmm I got confused by the name. I thought it's related to https://temporal.io/

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."

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.

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.)

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.