AWS Glue VS Apache Camel

AWS Glue Reviews

Apache Camel Reviews

AWS Glue mentions (13)

• Build Your Movie Recommendation System Using Amazon Personalize, MongoDB Atlas, and AWS Glue

  AWS Glue is a fully managed extract, transform, and load (ETL) service that makes it easy to prepare and load data for analysis. It helps bridge the gap between our MongoDB Atlas data and the services we'll use for recommendation. - Source: dev.to / about 2 months ago

• Using Snowflake data hosted in GCP with AWS Glue

  AWS Glue is a fully managed extract, transform, and load (ETL) service provided by Amazon Web Services (AWS). It is designed to make it easy for users to prepare and load their data for analysis. AWS Glue simplifies the process of building and managing ETL workflows by providing a serverless environment for running ETL jobs. - Source: dev.to / 3 months ago

• How to check for quality? Evaluate data with AWS Glue Data Quality

  It is serverless data integration service to allow you to easily scale your workloads in preparing data and moving transformed data into a target location. - Source: dev.to / 10 months ago

• Deploying a Data Warehouse with Pulumi and Amazon Redshift

  So in the next post, we'll do that: We'll take what we've done here, add a few more components with Pulumi and AWS Glue, and wire it all up with a few magical lines of Python scripting. - Source: dev.to / over 1 year ago

• Serverless Event Driven AI as a Service

  Once it's in a Data Lake then you have different options depending on the analytics you need. For more advanced constant analytics then you could look into Amazon Kinesis Data Analytics instead of Firehose to S3, but for Ad-Hoc queries then this is where Glue and Athena come in. - Source: dev.to / over 1 year 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 / 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: about 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