Temporal automates and manages workflows efficiently, offering resilience in distributed systems with features like retry and fault tolerance. Its capabilities in handling complex workflows and integrating with programming languages make it a valuable tool for managing diverse business logic.
Product | Market Share (%) |
---|---|
Temporal | 7.4% |
Camunda | 24.8% |
Flowable | 6.6% |
Other | 61.199999999999996% |
Title | Rating | Mindshare | Recommending | |
---|---|---|---|---|
Camunda | 4.1 | 24.8% | 89% | 77 interviewsAdd to research |
Control-M | 4.3 | 4.6% | 97% | 133 interviewsAdd to research |
Company Size | Count |
---|---|
Small Business | 7 |
Midsize Enterprise | 4 |
Large Enterprise | 6 |
Company Size | Count |
---|---|
Small Business | 98 |
Midsize Enterprise | 47 |
Large Enterprise | 269 |
Temporal excels in workflow orchestration, automating tasks across multiple platforms, and ensuring durability in asynchronous operations. It supports long-running workflows and simplifies handling distributed transactions, reducing boilerplate code. Temporal is noted for its durable execution and built-in retry policies, enhancing resilience. Despite its complexity and steep learning curve, it is valued for its integration with popular programming languages and relatively easy setup process, though it requires improvements in user-friendly features, documentation, community support, and security.
What are Temporal's key features?Temporal is implemented in sectors requiring robust workflow orchestration, such as managing data pipelines, API integration, and scheduling tasks. Organizations in a Kubernetes environment leverage it for its scalability and infrastructure management capabilities, securing integrations and enhancing reliability across IT operations.
Author info | Rating | Review Summary |
---|---|---|
Founder & CEO at Lanzar | 4.0 | We've used Temporal for eight months to automate financial and supply chain workflows, finding it scalable, cost-effective, and stable, though its UI lacks. It's saved us time and significant costs, despite a learning curve for junior developers. |
Senior Software Engineer at A.P. Moller - Maersk | 4.0 | As part of MoCS's platform engineering team, we found Temporal ideal for orchestrating workflows and managing API deployments. While it excels in handling complex workflows, it needs better visualization tools and improved documentation to reduce its steep learning curve. |
Software Engineer at Anchorage Digital | 4.5 | I use Temporal for workflow management primarily due to its ability to handle retries and ensure idempotence. However, its retro compatibility needs improvement as compatibility issues arise with new workflow changes, contrasting my previous use of RabbitMQ in personal projects. |
Backend Software Engineer at Fortics | 5.0 | I use Temporal to manage WhatsApp API messages, appreciating its retry system and availability. It efficiently handles microservice crashes. While scalability sometimes falters with complex workflows, switching to Cassandra improved it. Overall, it's cost-effective and worth the investment. |
Software Engineer at KONSTANTA PLUS, d.o.o | 4.5 | I am developing a SaaS platform with Temporal, valuing its durable execution and observability features. Though initially complex, especially with .NET workflows, Temporal simplifies retries and debugging, but could improve .NET support for adding workers and clients. |
Software Engineer (Backend) at One | 4.0 | We use Temporal for scheduling and event-triggering workflows, valuing its fault tolerance and monitoring features. Despite needing improvements in event tracking, it's superior to previous solutions like Airflow due to its flexibility and support for complex business logic. |
Senior Software Engineer at Dell Technologies | 4.0 | We adopted Temporal for our multi-language workflow orchestration across various platforms like AWS and Azure. It efficiently handles business logic but lacks built-in security features and clearer documentation, which complicates integration for new users. |
Software Developer at Groww | 4.5 | We use Temporal for managing long-running workflows, like callbacks received after a day or two. It handles continuous processes efficiently, although we experience issues with Temporal's versions and databases, especially older versions causing workflow terminations with Astra DB. |