4 ms·
Quick feedback: Would love to see some sort of architecture overview in the docs The top-level docs have a section on "Deploying workers" but I think there ar
by anentropic 2y ago
Quick feedback:
Would love to see some sort of architecture overview in the docs
The top-level docs have a section on "Deploying workers" but I think there are more components than that?
It's cool there's a Helm chart but the docs don't really say what resources it would deploy
https://docs.hatchet.run/self-hosting/docker-compose https://docs.hatchet.run/self-hosting/docker-compose
...shows four different Hatchet services plus, unexpectedly, both a Postgres server and RabbitMQ. Can't see anywhere that describes what each one of those does
Also in much of the docs it's not very clear where the boundary between Hatchet Cloud and Hatchet the self-hostable OSS part lies
- gabrielruttner 2y agoThanks for this feedback, we'll add some details and an architecture diagram. The simplest way to run hatchet is with `hatchet-lite`[0] which bundles all internal services. For most deployments we recommend running these components separately hence the multiple services in the helm chart [1]. RabbitMQ is now an optional dependency which is used for internal-service messages for higher throughput deployments [2]. Your workers are always run as a separate process. [0] https://docs.hatchet.run/self-hosting/hatchet-lite https://docs.hatchet.run/self-hosting/hatchet-lite [1] https://docs.hatchet.run/self-hosting/improving-performance#scaling-the-hatchet-engine https://docs.hatchet.run/self-hosting/improving-performance#... [2] https://hatchet.run/launch-week-01/pg-only-mode https://hatchet.run/launch-week-01/pg-only-mode edit: missed your last question -- currently self-host includes everything in cloud except managed workers