Conviro: Connecting Subscription State to Product Access
How I think about Conviro’s billing architecture: subscription truth, feature access, recoverable updates and explainable decisions.
Backend Architecture 3 min read
Backend Architecture
Webhooks, outbox patterns, tenant isolation, concurrency and the other design decisions that decide whether a system is safe to retry.
7 posts
Moventoro: Keeping Transport Teams on One Order Lifecycle
How I approach Moventoro’s shared order lifecycle across planning, warehouse operations, drivers, tracking and administration.
Backend Architecture 3 min read
Streaming LLM Responses: Cancellation and Backpressure Matter
A reliable streaming response needs explicit lifecycle events, bounded buffering, upstream cancellation, and a clear policy for partial answers.
Backend Architecture 3 min read
The Transactional Outbox Closes One Gap, Not Every Gap
Use an outbox to connect database changes with event publication, then address duplicate delivery, ordering, and external side effects separately.
Backend Architecture 3 min read
Designing Webhooks for Duplicates and Delayed Events
Build webhook receivers that verify input, accept work durably, handle duplicate deliveries, and reconcile state when events arrive late.
Backend Architecture 3 min read
Tenant Isolation Has to Follow the Data
Why tenant isolation must extend through database queries, caches, background jobs, retrieval, and support tooling in a SaaS application.
Backend Architecture 3 min read
Making n8n Workflows Safe to Retry
A workflow can fail after its external action succeeds. Design retries around business operations, checkpoints, and explicit failure states.
Backend Architecture 3 min read