neoq VS starlark-go

I just want to commend OP - if they’re here - for choosing an int64 for job IDs, and MD5 for hashing the payload in Neoq, the job library linked [0] from the article.

Especially given the emphasis on YAGNI, you don’t need a UUID primary key, and all of its problems they bring for B+trees (that thing RDBMS is built on), nor do you need the collision resistance of SHA256 - the odds of you creating a dupe job hash with MD5 are vanishingly small.

As to the actual topic, it’s fine IFF you carefully monitor for accumulating dead tuples, and adjust auto-vacuum for that table as necessary. While not something you’d run into at the start, at a modest scale you may start to see issues. May. You may also opt to switch to Redis or something else before that point anyway.

[0]: https://github.com/acaloiaro/neoq

Neoq (https://github.com/acaloiaro/neoq) is a background job processor for Go.

Yes, another one. It began from my desire to have a robust Postgres-backed job processor. What I quickly realized was that the interface in front of the queue was what was really important. This allowed me to add both in-memory and Redis (provided by asynq) backends behind the same interface. Which allows dependent projects to switch between different backends in different settings/durable requirements. E.g. in-memory for testing/development, postgres when you're not running Google-scale jobs, and Redis for all the obvious use cases for a Redis-backed queue.

This allows me to swap out job queue backends without changing a line of job processor code.

I'm familiar with the theory that one shouldn't implement queues on Postgres, and to a large extent, I disagree with those theories. I'm confident you can point out a scenario in which one shouldn't, and I contend that those scenarios are the exception rather than the rule.

I created a background processor called Neoq (https://github.com/acaloiaro/neoq) that is likely to interest you.

This is exactly the thesis behind neoq: https://github.com/acaloiaro/neoq

Starlark in go https://github.com/google/starlark-go is a great way to combine the best of both, the ease of use of Python and the simplicity of go.

I have been building a platform for deploying internal web applications using this approach https://github.com/claceio/clace. Use Starlark to configure the application, the platform itself is built in go.

The big unknown is your task definition: what does user-defined logic look like? If you're expecting go code, that's gonna need some cleverness because of the compiled nature of it. There's a node runtime implemented in go if you want to provide sandboxed javascript (check the source of k6.io, it's the main one I know that uses it). If you want to provide building blocks and let them compose them, starlark might be a good choice.

Another one of those (with broader language support) is the Starlark language, which has a Go implementation: https://github.com/google/starlark-go

Every config format gets as complex to be touring complete in the end. We had similar problems and eventually got rid of that complexity and switched to starlark (the bazel config language), was a huge benefit for the tools. https://github.com/google/starlark-go "Starlark is a dialect of Python intended for use as a configuration language. Like Python, it is an untyped dynamic language with high-level data types, first-class functions with lexical scope, and garbage collection."

Direct link to the Go implementation of Starlark: https://github.com/google/starlark-go

For a Python-like syntax, https://github.com/google/starlark-go is the language used in Babel. It's very mature, but since it is used in a massive mature project with a specific purpose, it doesn't move fast or drift from the spec of its Java-based sibling. It doesn't have exception try except blocks or some other features you might expect, but for short extension logic, it might be exactly what you want with the stability you can depend upon.

Context: https://github.com/google/starlark-go/blob/cfacd890221418a2dc2c736f7b5e3476c38709b1/starlark/int_posix64.go

Thus envd is more like Dockerfile, while it uses a simplified python dialect starlark https://github.com/google/starlark-go as the build language.

Use Go (mostly for starlark-go)