kappa-architecture

Process and replay events from durable logs using stream-only data architectures.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/hung-phan/system-skills --skill kappa-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kappa-architecture
Source: https://github.com/hung-phan/system-skills/tree/main/skills/system-review/references/architecture-patterns/kappa-architecture
Command: npx skills add https://github.com/hung-phan/system-skills --skill kappa-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires flink, spark, kafka, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a framework for building stream-only data architectures, reducing complexity by consolidating batch and streaming pipelines into one code path.

Core Features & Use Cases

  • Single Code Path: Unifies batch and streaming logic into one codebase, simplifying maintenance and development.
  • Replay and Reprocessing: Enables efficient reprocessing of data from a durable log for debugging, analysis, and backfilling.
  • Use Case: Ideal for financial services, where consistent and reproducible data processing is crucial. For example, use Kappa to replay payment transactions for reconciliation or debugging.

Quick Start

Analyze your payment processing system using the kappa-architecture skill by replaying transaction data and reviewing findings.

Frequently Asked Questions about kappa-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is kappa architecture and how does it unify batch and stream processing?

Kappa architecture is a stream-only data architecture that consolidates batch and streaming pipelines into a single code path. It processes and replays events using durable logs to simplify maintenance and ensure consistent event-driven data processing.

How do I replay and reprocess events from a durable log for backfilling?

Reprocessing events from a durable log involves replaying historical transaction data through the same streaming code path. This enables efficient data backfilling, debugging, and analysis without maintaining separate batch processing logic.

Do I need Flink, Spark, or Kafka to implement a stream-only data architecture?

Yes, implementing this stream-only data architecture requires Flink, Spark Structured Streaming, or Kafka Streams. These frameworks provide the necessary stream processing capabilities and durable log integration for replaying events.

When should I use kappa architecture instead of lambda architecture for event-driven systems?

Use kappa architecture when you need a single code path for both batch and streaming to reduce complexity. It is ideal for event-driven systems like financial services requiring reproducible data processing and transaction reconciliation.

Can I use Kafka Streams for replaying payment transactions and debugging?

Yes, Kafka Streams can process and replay payment transactions from durable logs. This approach supports consistent debugging and reconciliation by reprocessing the exact event stream through a unified code path.