Graylog Reviews

Apache Camel Reviews

Graylog mentions (2)

• Enhancing API Observability Series (Part 2): Log Analysis

  Graylog: Supports various log sources and formats, providing real-time search, analysis, and visualization functionalities. - Source: dev.to / 4 months ago

• Join us June 24 at 11:00 AM EDT: "All Things Configured” Discord Show with our founder, Lennart Koopman

  Join our new Graylog Community Discord channel for our new chat/call-in show, “All Things Configured”. Our founder, Lennart Koopman, will host the show with Jeff Darrington, Senior Technical Marketing Manager, as his guest. Jeff’s well-known to many of you as the star of our Graylog How-To series of videos and blog posts on Graylog.org. Get a jump on the event, which will be live on Friday, June 24 at 11:00 AM EDT. Source: about 2 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 / 10 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 / over 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