Apache Portable Runtime VS Apache Camel

Apache Portable Runtime Reviews

Apache Camel Reviews

Apache Portable Runtime mentions (4)

• My review of the C standard library in practice

  There are many libraries available that you can use as a libc replacement instead of CCAN, if that’s what you prefer [1-3]. Taking on a beefy dependency like that can be overkill, though, if all you need is a linked list or dynamic array implementation. [1] http://library.gnome.org/devel/glib/ [2] http://apr.apache.org/ [3] https://libcork.io/. - Source: Hacker News / about 1 year ago

• Is there a custom "C Standard Library" out there?

  There are many. APR is one of them. APR stands for Apache Portable Runtime. It includes arrays(aprarray) and hash tables(aprhash), but not trees. Source: over 1 year ago

• A C Standard Library

  A library that already implements some of this called libapr is what I’d consider a good example of libraries of this Ilk. Source: over 2 years ago

• Git's list of banned C functions

  It's not really complacency: it's that the standard library is intentionally minimalistic to maintain portability and backwards compatibility. If you want sensible string handling, it's usually best to use a high level utility library like GLib(https://developer.gnome.org/glib/stable/) or Apache Portable Runtime(http://apr.apache.org/), or roll your own safe string type (preferably non-null terminating). - Source: Hacker News / about 3 years ago

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