role-database:streaming-databases

Provide operational guidance for 14 streaming databases and platforms.

14|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/rnavarych/alpha-engineer --skill role-database-streaming-databases
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: role-database:streaming-databases
Source: https://github.com/rnavarych/alpha-engineer/tree/main/plugins/roles/role-database/skills/streaming-databases
Command: npx skills add https://github.com/rnavarych/alpha-engineer --skill role-database-streaming-databases

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides deep operational guidance for a wide array of streaming databases and messaging platforms, enabling efficient implementation of real-time data pipelines.

Core Features & Use Cases

  • Platform Expertise: Covers Kafka, Pulsar, Redpanda, NATS, Flink, Materialize, RisingWave, Kinesis, Event Hubs, Pub/Sub, and EventStoreDB.
  • Use Case: Implement an event sourcing architecture using EventStoreDB, or build a real-time analytics dashboard with Flink and Materialize, or set up a high-throughput message bus with Kafka or Pulsar.

Quick Start

Use the role-database:streaming-databases skill to get guidance on setting up Kafka exactly-once semantics for a producer.

Frequently Asked Questions about role-database:streaming-databases

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

FAQPage Schema
How do I implement exactly-once delivery semantics in Kafka?▼

Configuring Kafka exactly-once delivery requires setting transactional producer IDs and isolation levels to prevent duplicate messages in real-time event streaming pipelines. This provides specific producer configuration guidance to guarantee message processing semantics.

What is the best way to build a real-time analytics dashboard with Flink and Materialize?▼

Building a real-time analytics dashboard with Flink and Materialize involves streaming data through Flink for processing and Materialize for incremental view maintenance. This provides architectural pattern implementation guidance for high-throughput data pipelines.

How does CDC compare across Kafka, Pulsar, and Redpanda for event streaming?▼

Comparing CDC across Kafka, Pulsar, and Redpanda involves evaluating partition sizing, throughput, and exactly-once delivery guarantees for event streaming. This provides platform comparison guidance to help select the right messaging bus for your data pipeline.

Can I use EventStoreDB to implement an event sourcing architecture?▼

EventStoreDB supports implementing event sourcing architectures by persisting domain events as an immutable stream for state reconstruction. This provides operational guidance for configuring event streams and building reliable real-time data pipelines.

When do I need to use partition sizing in streaming databases?▼

Partition sizing is needed in streaming databases to balance throughput, parallelism, and consumer processing limits for high-volume real-time analytics. This provides configuration guidance to prevent bottlenecks and optimize event streaming pipelines.