A redundant AWS ingestion path that preserves call events independently and supports idempotent recovery.
Role: Backend & cloud engineer
Primary
Call webhooks
Primary system
Redundant
Lambda
RDS store
Idempotent replay
Role
Backend & cloud engineer
Platform
AWS Lambda + RDS
Pattern
Redundant ingestion
Overview
After a data-loss incident, call events needed a second, independent record. I designed and built a separate ingestion path that stores call-platform webhooks in its own database and can replay them into the primary system.
Ingestion and recovery paths
Call platform webhooksAircall
Primary systemExisting ingestion
AWS Lambda receiverIndependent path
Amazon RDS event store
Idempotent recoverySkips existing records
Primary system restored
Simplified view. External Service Data Processing
What I owned
A Lambda-based webhook receiver writing call events to a dedicated RDS store.
An idempotent recovery workflow that restores missing records after an outage.
Duplicate protection so recovery never re-creates records that already exist.
Engineering challenges
Recovery that is safe to rerun
A recovery job may run more than once. Recovery is idempotent: replays skip records that already exist in the primary system.
Stack
AWS LambdaAmazon RDSWebhooksAircallIdempotency
Try another colour palette
Amobot
Adil’s personal AI assistant. Answers come only from this portfolio and resume.
Hi, I’m Amobot, Adil’s personal AI assistant. Ask me about his work, projects, experience or skills.
Questions are processed by Google Gemini. Please don’t share personal information.