It’s very similar to using an SQS + EventBridge + AWS Lambda stack, but uses worker pools to process functions instead of isolated function invocations. Some features that Hatchet offers:
1. Publish, react to, and query events using the Events API [1]
2. You can define services via `worker.NewService` which can run a set of methods. For example, you can define a `users` service which schedules user notifications, creates a user sandbox environment, processes user events, etc.
3. It’s designed to be modular, so you can plug in your own task queue implementation or event storage repository. I built it using Postgres and RabbitMQ, but would love to support better event storage via Clickhouse and other message queues.
4. Workflows are declarative, which means you define the structure of your workflow when registering them with the Hatchet engine. This means that each workflow run is predictable and executes an immutable workflow version.
It currently only supports a Go SDK but Typescript and Python are on the near-term roadmap.
Looking forward to hearing any questions or feedback you have!