<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>aws-glue on Mahesh Veerabathiran</title><link>https://maara.dev/tags/aws-glue/</link><description>Recent content in aws-glue on Mahesh Veerabathiran</description><generator>Hugo -- gohugo.io</generator><managingEditor>maaraoffl@gmail.com (Maara)</managingEditor><webMaster>maaraoffl@gmail.com (Maara)</webMaster><lastBuildDate>Tue, 22 Jun 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://maara.dev/tags/aws-glue/index.xml" rel="self" type="application/rss+xml"/><item><title>Accelerate AWS Glue development using local setup</title><link>https://maara.dev/post/aws-glue-local-development/</link><pubDate>Tue, 22 Jun 2021 00:00:00 +0000</pubDate><author>maaraoffl@gmail.com (Maara)</author><guid>https://maara.dev/post/aws-glue-local-development/</guid><description>&lt;p>AWS Glue is a serverless ETL service offering that has a pre-built Apache Spark environment for distributed data processing. It makes developers life easy; simply write code and execute while AWS Glue take care of managing infrastructure, job execution, bookmarking &amp;amp; monitoring. That being said, AWS Glue is not just a managed Spark cluster, it has a component library for most common ETL tasks. But the challenge is how to leverage such capabilities during our local development. Fortunately, it is possible and I am happy to share my learning.&lt;/p></description></item></channel></rss>