What’s New in Streamkap: Read-Only Snapshot and Heartbeat Support
Oli Dinov
July 18, 2025
TL;DR
• Read-only snapshot mode enables zero-impact backups from read replicas without modifying the source database. • Heartbeat events keep connectors responsive even when source tables have low activity. • Use read-only mode for compliance-sensitive environments and heartbeats to prevent replication lag in quiet data scenarios.
We’ve introduced two new features to improve connector reliability and support more database environments:

🔒 Read Only Snapshot Support
Connectors can now be configured to operate in read-only mode
✅ Zero-impact backups – avoids load and locks on the primary.
💸 Cost efficiency – snapshot from cheaper or isolated infrastructure.
⚡ Faster test environments – quick cloning without write interference.
👉 Ideal for read replicas or any write-restricted database.
✔️ Enabled via
Set ʀᴇᴀᴅ ᴏɴʟʏ = ʏᴇs during connector setup
✔️ How it works
‣ Snapshots are taken without modifying the source database
‣ No signal tables or locks required
‣ Safe to use in read-only or compliance-sensitive environments
🫀 Read Only Heartbeat Events
❤️ Always responsive – connectors stay active even when source tables are quiet
🧠 Better visibility – consistent health checks and status visibility
⚡ Faster issue detection – detect broken connections without waiting for data
👉 Ideal for low-activity sources or intermittent traffic
✔️ Enabled via
Toggle ʜᴇᴀʀᴛʙᴇᴀᴛ in the connector settings
✔️ How it works
‣ Periodically emits a lightweight event from the connector
‣ Helps prevent replication lag or stuck offsets
‣ Keeps connectors healthy in quiet data environments
These updates are available now across all connectors. Drop your feedback or questions—we’re listening!
Oli Dinov
LinkedInAuthor Bio
Product Marketing Manager at Streamkap
Published
July 18, 2025
TL;DR
• Read-only snapshot mode enables zero-impact backups from read replicas without modifying the source database. • Heartbeat events keep connectors responsive even when source tables have low activity. • Use read-only mode for compliance-sensitive environments and heartbeats to prevent replication lag in quiet data scenarios.
Related blog posts
Will AI Replace Zapier? How MCP Threatens 8,000+ Integrations
Chegg's stock plunged 89% due to AI disruption. Now MCP threatens Zapier's 8,000+ integrations - will they adapt or decline?
What’s New in Streamkap: 🧊 Apache Iceberg Connector
Real-time lakehouse, simplified with Apache Iceberg and Streamkap
Why LLMs Fail at SQL: The Case for Semantic Layers
Why LLMs fail at business data questions - your data warehouse doesn't speak business language. Semantic layers might be the key.