Apache Camel VS gRPC

Apache Camel Reviews

gRPC Reviews

Apache Camel mentions (12)

• Ask HN: What is the correct way to deal with pipelines?

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

• Why messaging is much better than REST for inter-microservice communications

  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 / about 1 year ago

• Can I continuously write to a CSV file with a python script while a Java application is continuously reading from it?

  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

• S3 to S3 transform

  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

• 🗞️ We have just released our JBang! catalog 🛍️

  🐪 Apache Camel : Camel JBang, A JBang-based Camel app for easily running Camel routes. - Source: dev.to / over 1 year ago

gRPC mentions (86)

• Golang: out-of-box backpressure handling with gRPC, proven by a Grafana dashboard

  gRPC, built on HTTP/2, inherently supports flow control. The server can push updates, but it must also respect flow control signals from the client, ensuring that it doesn't send data faster than what the client can handle. - Source: dev.to / 29 days ago

• Delving Deeper: Enriching Microservices with Golang with CloudWeGo

  While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future. - Source: dev.to / 2 months ago

• Dart on the Server: Exploring Server-Side Dart Technologies in 2024

  The Dart implementation of gRPC which puts mobile and HTTP/2 first. It's built and maintained by the Dart team. Grpc is a high-performance RPC (remote procedure call) framework that is optimized for efficient data transfer. - Source: dev.to / 3 months ago

• How to Build & Deploy Scalable Microservices with NodeJS, TypeScript and Docker || A Comprehesive Guide

  gRPC is a high-performance, open-source RPC (Remote Procedure Call) framework initially developed by Google. It uses Protocol Buffers for serialization and supports bidirectional streaming. - Source: dev.to / 3 months ago

• Actual SSH over HTTPS

  In general, tunneling through HTTP2 turns out to be a great choice. There is a RPC protocol built on top of HTTP2: gRPC[1]. This is because HTTP2 is great at exploiting a TCP connection to transmit and receive multiple data structures concurrently - multiplexing. There may not be a reason to use HTTP3 however, as QUIC already provides multiplexing. I expect that in the future most communications will be over... - Source: Hacker News / 4 months ago