Apache Samza
Apache Samza is a distributed stream processing framework that provides a simple API for building stateful stream processing applications. It integrates with Apache Kafka for messaging and supports both stream and batch processing.
Apache Samza publishes 3 APIs on the APIs.io network: Checkpoints API, Jobs API, and Tasks API. Tagged areas include Big Data, Hadoop, Kafka, Stream Processing, and Streaming.
The Apache Samza catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.
Apache Samza’s developer surface includes documentation, engineering blog, and 7 more developer resources.
Kin Score
APIs 3
Individual APIs this provider publishes, each with its own machine-readable definition.
Apache Samza Checkpoints API
The Checkpoints API from Apache Samza — 1 operation(s) for checkpoints.
Apache Samza Jobs API
The Jobs API from Apache Samza — 4 operation(s) for jobs.
Apache Samza Tasks API
The Tasks API from Apache Samza — 1 operation(s) for tasks.
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Apache Samza Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Apache Samza Finops
FINOPSFeatures 6
Notable capabilities this provider offers.
Kafka Integration
Native Apache Kafka consumer/producer for stream processing
YARN Execution
Runs on Apache YARN for resource management and fault tolerance
Stateful Processing
Local state stores with RocksDB for low-latency stateful computations
Exactly-Once Processing
Transactional state stores for exactly-once semantics
Flexible Deployment
Run on YARN, Kubernetes, or standalone
High Level API
Fluent API and SQL support for stream transformations
Semantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Apache Samza Context
JSON-LDSpectral Rules 2
Spectral governance rulesets for linting and validating these APIs.
Apache Samza API Rules
SPECTRALApache Samza API Rules
SPECTRALJSON Schema 8
Standalone JSON Schema definitions for this provider's data models.
CheckpointList
JSON SCHEMACheckpoint
JSON SCHEMAJobList
JSON SCHEMAJob
JSON SCHEMAJobStatus
JSON SCHEMAPartition
JSON SCHEMATaskList
JSON SCHEMATask
JSON SCHEMAScroll for all 8
JSON Structure 8
JSON Structure definitions describing this provider's data shapes.
Apache Samza Checkpoint List Structure
JSON STRUCTUREApache Samza Checkpoint Structure
JSON STRUCTUREApache Samza Job List Structure
JSON STRUCTUREApache Samza Job Status Structure
JSON STRUCTUREApache Samza Job Structure
JSON STRUCTUREApache Samza Partition Structure
JSON STRUCTUREApache Samza Task List Structure
JSON STRUCTUREApache Samza Task Structure
JSON STRUCTUREScroll for all 8
Examples 8
Example request and response payloads for these APIs.
Apache Samza Job Example
EXAMPLEApache Samza Task Example
EXAMPLEScroll for all 8
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers build with this provider.
Event Stream Processing
Real-time processing of Kafka event streams
Stateful Aggregations
Windowed aggregations over streaming data
Stream Joins
Join multiple Kafka streams for enrichment
Change Data Capture
Process CDC events from databases in real time
Integrations 4
Pre-built integrations with other platforms and tools.
Apache Kafka
Primary messaging system for Samza input and output streams
Apache YARN
Resource management and job scheduling on Hadoop
Apache Hadoop
HDFS integration for checkpoint storage
RocksDB
Embedded state store for local stateful processing
Resources
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API