Why should I use this skill?

If your app relies on services like Stripe for payments or Clerk for auth, this skill helps you build systems that automatically fix data mismatches caused by network issues, silent failures, or missed events.

Can this skill help with Stripe integration specifically?

Yes, it includes specific code patterns for checking Stripe subscription statuses against local records and fetching missed Stripe events using their API.

What are reconciliation patterns?

They are defensive programming strategies used to ensure that a local database remains synchronized with external sources of truth, especially when real-time updates like webhooks fail or are delivered out of order.

What tech stack is this for?

The architectural patterns are universal, but the skill provides TypeScript examples optimized for Node.js environments and Convex backend-as-a-service.

Does this replace webhooks?

No. It follows the 'webhooks for speed, reconciliation for correctness' principle, using webhooks for real-time updates and periodic reconciliation as a fallback safety net.

Reconciliation Patterns

Name: Reconciliation Patterns
Author: phrazzld

byphrazzld

•

Gestión de Bases de Datos

Automates data consistency and recovery between external services and local databases by handling webhook failures and event drift.

Acerca de

This skill provides specialized guidance and implementation patterns for maintaining eventual consistency between third-party services like Stripe or Clerk and your application's database. It addresses common distributed system challenges such as silent webhook failures, out-of-order delivery, and duplicate events by implementing defensive strategies like scheduled cron-job reconciliation, on-demand sync triggers, and idempotent event processing. It is an essential toolkit for developers building reliable fintech, SaaS, or identity-dependent applications.

Características Principales

Scheduled cron-job patterns for periodic state comparison
Diagnostic templates for detecting and logging data drift
Event replay strategies to recover missed external notifications
On-demand reconciliation for user-reported data drift
2 GitHub stars
Idempotent webhook handler patterns for safe event processing

Casos de Uso

Synchronizing user profiles and authentication state with providers like Clerk
Recovering data consistency after a system outage or webhook endpoint failure
Ensuring subscription status in your database matches Stripe's source of truth

Acerca de

Características Principales

Scheduled cron-job patterns for periodic state comparison
Diagnostic templates for detecting and logging data drift
Event replay strategies to recover missed external notifications
On-demand reconciliation for user-reported data drift
2 GitHub stars
Idempotent webhook handler patterns for safe event processing

Casos de Uso

Synchronizing user profiles and authentication state with providers like Clerk
Recovering data consistency after a system outage or webhook endpoint failure
Ensuring subscription status in your database matches Stripe's source of truth