Apache Camel VS RocketMQ

Apache Camel

• Show HN: Winglang – a new Cloud-Oriented programming language
  10 projects | news.ycombinator.com | 6 Dec 2023
• Ask HN: What is the correct way to deal with pipelines?
  4 projects | news.ycombinator.com | 21 Sep 2023

  "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/

  - https://github.com/huginn/huginn

  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.

• Is there something like airflow but written in Scala/Java?
  2 projects | /r/bigdata | 8 May 2023

  Apache Camel Apache Nifi Spring Cloud

• Why messaging is much better than REST for inter-microservice communications
  9 projects | news.ycombinator.com | 12 Feb 2023

  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 about the pitch because the solution is presented as enabling you to maintain synchronous style programming while achieving benefits of async processing. This just isn't true, these are fundamental tradeoffs. If you need a synchronous answer back then no amount of queuing, routing, prioritisation, etc etc will save you when the fundamental resource providing that is unavailable, and the ultimate outcome that your synchronous client now hangs indefinitely waiting for a reply message instead of erroring hard and fast is not desirable at all. If you go into this ad hoc, and build in a leaky abstraction that asynchronous things are are actually synchronous and vice versa, before you know it you are going to have unstable behaviour or even worse, deadlocks all over your system and the worst part - the true state of the system is now hidden in which messages are pending in transient message queues everywhere.

  What really matters here is to fundamentally design things from the start with patterns that allow you to be very explicit about what needs to be synchronous vs async (building on principles of idempotency, immutability, coherence, to maximise the cases where async is the answer).

  The notion of Apache Camel is to make all these decisions a first class elements of your framework and then to extract out the routing layer as a dedicated construct. The fact it generalises beyond message queues (treating literally anything that can provide a piece of data as a message provider) is a bonus.

  [0] https://camel.apache.org/

• Can I continuously write to a CSV file with a python script while a Java application is continuously reading from it?
  1 project | /r/AskProgramming | 1 Feb 2023

  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.

• S3 to S3 transform
  3 projects | /r/dataengineering | 21 Jan 2023

  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.

• 🗞️ We have just released our JBang! catalog 🛍️
  6 projects | dev.to | 23 Nov 2022

  🐪 Apache Camel : Camel JBang, A JBang-based Camel app for easily running Camel routes.

• 7GUIs of Java/Object Oriented Design?
  4 projects | /r/java | 19 Nov 2022
• System Design: Enterprise Service Bus (ESB)
  1 project | dev.to | 13 Sep 2022

  Apache Camel

• Advanced: Java, JVM and general knowledge
  1 project | /r/javahelp | 9 Sep 2022

  So, my advice is this. Expand your knowledge. Pursue higher education on topics you are familiar with, but also explore topics you are not. Read documentation, but question it. I just found out about something called Apache Camel today that I am excited to read up on. Why is it better than Spring? Is it really? What's happening here? This is always what excites me as a developer and engineer. There is so much to learn.

RocketMQ

We haven't tracked posts mentioning RocketMQ yet.
Tracking mentions began in Dec 2020.