Based on our record, Apache Camel should be more popular than Cadence Workflow. It has been mentiond 12 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Emit events from your primary DB (postgres, etc.) to something like kafka or rabbitmq and then catch that in your search engine. There's also some end-to-end solutions like temporal (temporal.io) or cadence (https://cadenceworkflow.io/). Source: over 1 year ago
You should definitely check Uber Cadence https://cadenceworkflow.io/. Source: almost 2 years ago
Cadence: https://cadenceworkflow.io. - Source: Hacker News / almost 2 years ago
Dear community, I will be please to get your feedback to choose a schedule engine in 2022 in microservice context. On this field they are at least 2 challengers to me, ¹ nomad from hashicorp and ² cadence from uber. While kubernetes lead this field. Source: over 2 years ago
There's cadence which is made by Uber: https://cadenceworkflow.io/. Source: over 2 years ago
"correct" is a value judgement that depends on lots of different things. Only you can decide which tool is correct. Here are some ideas: - https://camel.apache.org/ - https://www.windmill.dev/ Your idea about a queue (in redis, or postgres, or sqlite, etc) is also totally valid. These off-the-shelf tools I listed probably wouldn't give you a huge advantage IMO. - Source: Hacker News / 8 months ago
This reminds me more of Apache Camel[0] than other things it's being compared to. > The process initiator puts a message on a queue, and another processor picks that up (probably on a different service, on a different host, and in different code base) - does some processing, and puts its (intermediate) result on another queue This is almost exactly the definition of message routing (ie: Camel). I'm a bit doubtful... - Source: Hacker News / over 1 year ago
Since you're writing a Java app to consume this, I highly recommend Apache Camel to do the consuming of messages for it. You can trivially aim it at file systems, message queues, databases, web services and all manner of other sources to grab your data for you, and you can change your mind about what that source is, without having to rewrite most of your client code. Source: over 1 year ago
For a simple sequential Pipeline, my goto would be Apache Camel. As soon as you want complexity its either Apache Nifi or a micro service architecture. Source: over 1 year ago
🐪 Apache Camel : Camel JBang, A JBang-based Camel app for easily running Camel routes. - Source: dev.to / over 1 year ago
Activiti - Activiti is a light-weight workflow and Business Process Management (BPM) Platform targeted at...
StatCounter - StatCounter is a simple but powerful real-time web analytics service that helps you track, analyse and understand your visitors so you can make good decisions to become more successful online.
Camunda - The Universal Process Orchestrator
Histats - Start tracking your visitors in 1 minute!
Apache Airflow - Airflow is a platform to programmaticaly author, schedule and monitor data pipelines.
AFSAnalytics - AFSAnalytics.