Tag: backend
All the articles with the tag "backend".
Scope Every Read: Confidential Docs in a Shared Bucket
Per-matter prefixes, short-lived signed URLs, database-checked reads, and redacted logs for confidential documents in multi-tenant GCP apps.
The Reply Arrived Twice. The Record Updated Once.
Inbound replies and webhooks must link to the right record exactly once, and generated drafts must wait for a human. Two mechanisms from production systems: key on the sender id, hold behind a gate.
The Code Changed. The Description Had to Survive It.
Code changes flow back into the knowledge graph the generator reads: changed files only, merge not replace, both artifacts patched. Freshness as write back, not retrieval ranking.
Stripe Holds the Subscription. Your Database Holds a Copy.
Subscription state, idempotent Stripe webhooks and tenant scoped billing tables drawn from multi-tenant platform and ledger work.
The Policy Was Enabled. One Role Still Read Across Tenants.
Auditing Supabase Row Level Security for a multi-role SaaS pilot, testing tenant isolation role by role with the service key outside the test path.
The App Balanced the Ledger. The Database Refused the Write.
Enforcing double-entry balance, integer minor units and append-only audit in Postgres with constraints that refuse the forbidden write.
The Browser Never Sees the Token. The Edge Function Holds It.
Read-only social API integration through Supabase Edge Functions in Deno and TypeScript, with tokens sealed server side and scoped to the minimum.
The App Called OpenAI Directly. The Gateway Should Have Been in Between.
Putting a Go gateway in front of a Python RAG service to route across providers, stream safely, enforce per-customer budgets and cache without hiding failures.