I haven't used pg-boss, and feature-wise it looks very similar and is an impressive project.
The core difference is that pg-boss is a library while Hatchet is a separate service which runs independently of your workers. This service also provides a UI and API for interacting with Hatchet - I don't think pg-boss has those things, so you'd probably have to build out observability yourself.
This doesn't make a huge difference when you're at 1 worker, but having each worker poll your database can lead to DB issues if you're not careful - I've seen some pretty low-throughput setups for very long-running jobs using a database with 60 CPUs because of polling workers. Hatchet distributes in two layers - the "engine" and the "worker" layer. Each engine polls the database and fans out to the workers over a long-lived gRPC connection. This reduces pressure on the DB and lets us manage which workers to assign tasks to based on things like max concurrent runs on each worker or worker health.
It's pretty slow to open a page. Saw this in the console,
(index):62 cdn.tailwindcss.com should not be used in production. To use Tailwind CSS in production, install it as a PostCSS plugin or use the Tailwind CLI:
Honestly still trying to figure out what I'm even building, but I agree, the load time is pretty bad. Also I'm using the smallest instance of Postgress Google Cloud Run offers and I've never stress-tested it before :)
Hi many years ago I built something similar for a game framework called libgdx.
https://github.com/pyrossh/gdx-studio
Looks cool. But to get it completely working it takes a lot of time and effort. See overlap2d as well.
These days I just prefer writing plain code as I feel the generated code is not what I want.