iceberg-python VS helm

Have you tried out PyIceberg yet? It's a pure Python implementation and it works pretty well. It supports a SQL Catalog as well as an In-Memory Catalog via a baked in SQLite SQL Catalog.

https://py.iceberg.apache.org/

Access data in Amazon S3 Tables using PyIceberg through the AWS Glue Iceberg REST endpoint - demonstrates how to access Iceberg tables stored in S3 Tables using PyIceberg, a Python library for programmatic access to Iceberg table metadata as well as to table data in Iceberg format [hands on]

PyIceberg - Python library for Apache Iceberg

PyIceberg Docs

In a previous article, we implemented an Iceberg catalog using SingleStore and JDBC. Another way that we can create the catalog is using PyIceberg. In this article, we'll see how.

Iceberg is working hard to support pure python[0] / rust[1] workflows without Spark. Following Tabular's acquisition [2], I hope it still moves in this direction at the same clip.

We're using iceberg + duckdb to power analytics in our app[3] and I'm really happy with the combo.

0 - https://github.com/apache/iceberg-python

1 - https://github.com/apache/iceberg-rust

2 - https://x.com/thisritchie/status/1800522255426072647

3 - https://www.definite.app/

You don't need a Spark deployment. The first reference implementations for reading and writing were in Spark.

Now, with PyIceberg, there is read support in Python. Write support should be merged very soon - https://github.com/apache/iceberg-python/pull/41

Helm's first major release in six years, v4, is now available. In this article, I'll explore the key changes: switching from 3-Way Merge to Server-Side Apply, support for WASM plugins, improved resource readiness tracking, content-based chart caching, and more.

Helm GitHub Repository

Ready to try it out? Getting started with the operator is straightforward. You can use a local Kubernetes cluster such as minikube or kind and use Helm for installation.

To get to a working deployment of the proposed app, though, you would probably need to learn at least a dozen different k8s concepts. Here’s a short list of what you might need: a Deployment to describe Pods in a ReplicaSet along with a Service, Ingress and Ingress Controller to hook up your domain. Helm to install Cert Manager so you can get SSL working. You’ll likely need to learn about plenty more along the way.

HELM

Install Docker, Minikube & Helm on your local machine

Some of the brightest minds came together to set up the Cloud Native Compute Foundation and championed the concept of GitOps. This brought about yet another major shift in developer mindsets, and allowed techies to be more declarative with their infrastructure and focus solely on the what; the responsibility of how was abstracted away with the new technologies on the horizon. With Kubernetes widely adopted for container orchestration at scale in the cloud, Helm surfaced as the package manager for deployments to k8s clusters. The packages came to be known as Charts and could be deployed with predictability and consistency. This was a step in the right direction, but still included a little bit of ClickOps. Thanks to CNCF yet again, tools like Flux and Argo CD alleviated that pain aptly, and it became possible to manage Helm deployments in a declarative manner. As one can tell, this is already a lot to deal with for a developer who's supposed to write code for implementing business logic.

Package Management: Helm charts simplify application deployment and configuration management. Over 2,000 community charts provide pre-configured applications, while organizations maintain internal chart repositories for proprietary software. Helm best practices ensure secure and maintainable deployments.

kubectl and helm installed on your machine