Making Spark Cloud Native At Data Mechanics

Data Engineering Podcast

Tobias Macey에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Tobias Macey 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.

3y ago 40:15

MP3•에피소드 홈

저장한 시리즈 ("피드 비활성화" status)

When? This feed was archived on January 17, 2023 09:15 (1+ y ago). Last successful fetch was on December 12, 2022 17:37 (1+ y ago)

Why? 피드 비활성화 status. 잠시 서버에 문제가 발생해 팟캐스트를 불러오지 못합니다.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Summary

Spark is one of the most well-known frameworks for data processing, whether for batch or streaming, ETL or ML, and at any scale. Because of its popularity it has been deployed on every kind of platform you can think of. In this episode Jean-Yves Stephan shares the work that he is doing at Data Mechanics to make it sing on Kubernetes. He explains how operating in a cloud-native context simplifies some aspects of running the system while complicating others, how it simplifies the development and experimentation cycle, and how you can get a head start using their pre-built Spark container. This is a great conversation for understanding how new ways of operating systems can have broader impacts on how they are being used.

Announcements

Hello and welcome to the Data Engineering Podcast, the show about modern data management
When you’re ready to build your next pipeline, or want to test out the projects you hear about on the show, you’ll need somewhere to deploy it, so check out our friends at Linode. With their managed Kubernetes platform it’s now even easier to deploy and scale your workflows, or try out the latest Helm charts from tools like Pulsar and Pachyderm. With simple pricing, fast networking, object storage, and worldwide data centers, you’ve got everything you need to run a bulletproof data platform. Go to dataengineeringpodcast.com/linode today and get a $100 credit to try out a Kubernetes cluster of your own. And don’t forget to thank them for their continued support of this show!
Firebolt is the fastest cloud data warehouse. Visit dataengineeringpodcast.com/firebolt to get started. The first 25 visitors will receive a Firebolt t-shirt.
Atlan is a collaborative workspace for data-driven teams, like Github for engineering or Figma for design teams. By acting as a virtual hub for data assets ranging from tables and dashboards to SQL snippets & code, Atlan enables teams to create a single source of truth for all their data assets, and collaborate across the modern data stack through deep integrations with tools like Snowflake, Slack, Looker and more. Go to dataengineeringpodcast.com/atlan today and sign up for a free trial. If you’re a data engineering podcast listener, you get credits worth $3000 on an annual subscription
Your host is Tobias Macey and today I’m interviewing Jean-Yves Stephan about Data Mechanics, a cloud-native Spark platform for data engineers

Interview

Introduction
How did you get involved in the area of data management?
Can you start by giving an overview of what you are building at Data Mechanics and the story behind it?
What are the operational characteristics of Spark that make it difficult to run in a cloud-optimized environment?
How do you handle retries, state redistribution, etc. when instances get pre-empted during the middle of a job execution?
- What are some of the tactics that you have found useful when designing jobs to make them more resilient to interruptions?
What are the customizations that you have had to make to Spark itself?
What are some of the supporting tools that you have built to allow for running Spark in a Kubernetes environment?
How is the Data Mechanics platform implemented?
- How have the goals and design of the platform changed or evolved since you first began working on it?
How does running Spark in a container/Kubernetes environment change the ways that you and your customers think about how and where to use it?
- How does it impact the development workflow for data engineers and data scientists?
What are some of the most interesting, unexpected, or challenging lessons that you have learned while building the Data Mechanics product?
When is Spark/Data Mechanics the wrong choice?
What do you have planned for the future of the platform?

Contact Info

Parting Question

From your perspective, what is the biggest gap in the tooling or technology for data management today?

Links

The intro and outro music is from The Hug by The Freak Fandango Orchestra / CC BY-SA

351 에피소드

#Tech #Tobias Macey #Machine Learning