Data is a team sport, but it's often difficult for everyone on the team to participate. For a long time the mantra of data tools has been "by developers, for developers", which automatically excludes a large portion of the business members who play a crucial role in the success of any data project. Quilt Data was created as an answer to make it easier for everyone to contribute to the data being used by an organization and collaborate on its application. In this episode Aneesh Karve shares the journey that Quilt has taken to provide an approachable interface for working with versioned data in S3 that empowers everyone to collaborate.
- Hello and welcome to the Data Engineering Podcast, the show about modern data management
- Truly leveraging and benefiting from streaming data is hard - the data stack is costly, difficult to use and still has limitations. Materialize breaks down those barriers with a true cloud-native streaming database - not simply a database that connects to streaming systems. With a PostgreSQL-compatible interface, you can now work with real-time data using ANSI SQL including the ability to perform multi-way complex joins, which support stream-to-stream, stream-to-table, table-to-table, and more, all in standard SQL. Go to dataengineeringpodcast.com/materialize today and sign up for early access to get started. If you like what you see and want to help make it better, they're hiring across all functions!
- Your host is Tobias Macey and today I'm interviewing Aneesh Karve about how Quilt Data helps you bring order to your chaotic data in S3 with transactional versioning and data discovery built in
- How did you get involved in the area of data management?
- Can you describe what Quilt is and the story behind it?
- How have the goals and features of the Quilt platform changed since I spoke with Kevin in June of 2018?
- What are the main problems that users are trying to solve when they find Quilt?
- What are some of the alternative approaches/products that they are coming from?
- How does Quilt compare with options such as LakeFS, Unstruk, Pachyderm, etc.?
- Can you describe how Quilt is implemented?
- What are the types of tools and systems that Quilt gets integrated with?
- How do you manage the tension between supporting the lowest common denominator, while providing options for more advanced capabilities?
- What is a typical workflow for a team that is using Quilt to manage their data?
- What are the most interesting, innovative, or unexpected ways that you have seen Quilt used?
- What are the most interesting, unexpected, or challenging lessons that you have learned while working on Quilt?
- When is Quilt the wrong choice?
- What do you have planned for the future of Quilt?
- From your perspective, what is the biggest gap in the tooling or technology for data management today?
- Thank you for listening! Don't forget to check out our other shows. Podcast.__init__ covers the Python language, its community, and the innovative ways it is being used. The Machine Learning Podcast helps you go from idea to production with machine learning.
- Visit the site to subscribe to the show, sign up for the mailing list, and read the show notes.
- If you've learned something or tried out a project from the show then tell us about it! Email firstname.lastname@example.org) with your story.
- To help other people find the show please leave a review on Apple Podcasts and tell your friends and co-workers
- Quilt Data
- UW Madison
- Docker Swarm
- FinOS Perspective
- CDK == Cloud Development Kit
- Shadow IT
- Delta Lake
- Apache Iceberg