Apache Samza vs Feldera
Apache Samza
samza.apache.orgFeldera
feldera.comSide by side
| Figure | Apache Samza | Feldera |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 2 |
| Spec score · Streaming Analytics Software | 7.8 (#11) | 7.8 (#12) |
| Spec score · Stream Processing Software | 7.8 (#13) | 7.8 (#14) |
| Deployment | Samza supports deployment on YARN, Kubernetes, or as a standalone library, and its documentation describes running applications across public clouds, containerized environments, and bare-metal hardware. | Feldera offers Docker for local development, testing, and prototyping, a free online sandbox, and an enterprise offering for production. |
| Purpose | Apache Samza is a distributed stream-processing framework for building stateful applications that process data in real time from multiple sources. | Feldera is an incremental view maintenance engine that keeps SQL views in sync with changing data and works alongside a lakehouse or warehouse. |
| Security | The background documentation says Samza works with YARN, which supports Hadoop’s security model, and uses Linux cgroups for resource isolation. | The Trust Center lists SOC 2 Type 1 and Type 2 compliance and offers access to security documentation, including a penetration test report and SOC 2 report. |
Plans
In their own words
Apache Samza
Apache Samza is a free, open-source distributed framework for applications that process data from multiple sources in real time. It supports stateless and stateful workloads, using a scalable, fault-tolerant state store for retained application state. Developers can use the high-level Streams API, lower-level Task API, Samza SQL or an Apache Beam API; Beam support for Python and Go is described as work in progress. Java and Scala applications can embed Samza as a lightweight client library. Built-in integrations include Apache Kafka, AWS Kinesis, Azure Event Hubs, Elasticsearch and Apache Hadoop, with custom sources also supported. Samza runs on YARN, Kubernetes or as a standalone library across public-cloud, containerized and bare-metal environments. Host affinity and incremental checkpointing help recover tasks and their state after failures. Processing is at least once. The project supports SQL processing and event-time windows, and its documentation describes applications with several terabytes of state and thousands of cores. Samza is self-hosted on Linux and distributed as source artifacts and through Maven; there is no binary release at this time.
Feldera
Feldera is an incremental view maintenance engine that keeps SQL views current as input data changes, for use alongside a lakehouse or warehouse. Instead of rebuilding a full dataset after each change, it updates views in proportion to the change. It supports SQL window functions and recursive queries. Documented inputs include Kafka, Google Pub/Sub, NATS, PostgreSQL, AWS S3, Delta Lake, and Apache Iceberg; outputs include Kafka, Delta Lake, PostgreSQL, Redis, DynamoDB, Snowflake, and Iceberg, with several output connectors marked experimental. The free open-source edition runs as a single node and container, supports all connectors and datasets larger than memory, and includes community support through Slack. Docker is available for local development, testing, and prototyping, alongside a free online sandbox. Enterprise runs on a customer-provided cloud or Kubernetes cluster and adds multi-node deployments, fault tolerance, resource isolation, and dedicated support. Its documentation says data stays on the customer's premises. Enterprise pricing is custom, and pipeline scale-out is listed as coming soon.