EVERYTHING XIAOMI
Get listed
Side by side

Apache Samza vs Arroyo

Apache Samza logo

Apache Samza

6.0#17 in stream processing softwareFree plan
Free planAPILinuxSelf-hosted
Visit
Arroyo logo

Arroyo

8.0#1 in stream processing softwareFrom $5 a month
Free planWebAPILinuxmacOS
Visit

What both publish

FactApache SamzaArroyo
DeploymentSamza 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.Arroyo can run as a single binary, Docker container or Kubernetes deployment, with SQLite for local use and Postgres recommended for distributed production.
Founded20132022
PurposeApache Samza is a distributed stream-processing framework for building stateful applications that process data in real time from multiple sources.Arroyo is a distributed stream processing engine for stateful computations on data streams, with sub-second results.
ScaleThe documentation says Samza has been used in applications with several terabytes of state and thousands of cores.Arroyo says it can scale to millions of events per second and supports horizontal and vertical rescaling.
SupportThe project directs users to a user mailing list subscribed to by Samza users, contributors, and committers.The deployment guide invites users rolling out clusters to contact [email protected] or ask questions on Discord.

Apache Samza plans

  • Apache SamzaFree

Arroyo plans

  • Arroyo open-sourceFree
  • Open-source Arroyo EngineFree
  • Cloudflare Workers Paid with Pipelines$5 a month

Pick Apache Samza if…

Samza suits developers building real-time stream-processing applications in Java or Scala who can manage a self-hosted deployment. Its range of APIs and integrations may also fit teams processing data from multiple sources.

Pick Arroyo if…

Arroyo suits teams building stateful stream-processing pipelines with SQL and Rust extensions. A single-node cluster is intended for testing and development; production calls for a distributed deployment.

Charts they share