4 ms·
why would one consider this over something more established such as Temporal, also I see Maestro is written in Java vs Temporal's Go
by meliora245 2y ago
why would one consider this over something more established such as Temporal, also I see Maestro is written in Java vs Temporal's Go
- iamspoilt 2y agoThat's also my question.
- robryan 2y agoNetflix also uses temporal: https://temporal.io/in-use/netflix https://temporal.io/in-use/netflix
- tiffanyh 2y agoIs Temporal still alive? (website doesn't resolve for me) EDIT: I found the GitHub page https://github.com/temporalio/temporal https://github.com/temporalio/temporal
- sjansen 2y agoThe site loads fine for me. See also: https://downforeveryoneorjustme.com/temporal.io https://downforeveryoneorjustme.com/temporal.io
- troebr 2y agoDidn't they rewrite some of Temporal's core in rust?
- sjansen 2y agoThey (re)wrote most of the client SDKs on a Rust core, but the Temporal server is still written in Go.
- aimazon 2y agoisn’t Maestro an alternative to Airflow, not Temporal? Temporal isn’t a workflow orchestrator. There’s some overlap on the internals but they’re different designs for different use cases.
- trustno2 2y agoTemporal's go is... something. They used to use Java (I think), then they switched to Go, and the Go is very Java-like. Or maybe I just don't know Fx. https://github.com/temporalio/temporal/blob/main/service/matching/fx.go#L53 https://github.com/temporalio/temporal/blob/main/service/mat... The issue we hit with Temporal - again and again - is that it's very under-documented, and it's something you install at the core of your business, yet it's really hard to understand what is going on, through all the layers and through the very obtuse documentation. Maestro has... no documentation? OK Temporal wins by default.