# Ayush Basak

> Ayush Basak is a CTO, systems architect, and database engineer in Kolkata, India. He publishes first-principles material about backend engineering, distributed systems, PostgreSQL, cloud infrastructure, production AI, and AI-agent control planes.

Canonical site: https://www.ayushworks.xyz/
Preferred citation name: Ayush Basak
Also known as: Ayush Works; ayushbasak101; batxcode
Canonical biography: https://www.ayushworks.xyz/about-ayushbasak
Contact: basakayush942@gmail.com

## Primary pages

- [Home](https://www.ayushworks.xyz/): identity, current work, and publishing overview.
- [Biography](https://www.ayushworks.xyz/about-ayushbasak): professional and personal background.
- [Work](https://www.ayushworks.xyz/work): products, systems, and engineering responsibilities.
- [Engineering Blog](https://www.ayushworks.xyz/posts): long-form technical analysis.
- [Field Notes](https://www.ayushworks.xyz/field-notes): product, incident, management, and engineering stories.
- [Engineering Snippets](https://www.ayushworks.xyz/snippets): compact production patterns with invariants and trade-offs.
- [Systems Architecture](https://www.ayushworks.xyz/systems-architecture): architecture expertise hub.
- [Database Engineering](https://www.ayushworks.xyz/database-engineering): database expertise hub.
- [AI Infrastructure](https://www.ayushworks.xyz/ai): production AI and agent-system notes.

## Published articles and Field Notes

- [Securing Multi-Tenant Systems: From Request Identity to Data Deletion | ayushworks](https://www.ayushworks.xyz/security/multi-tenant-systems): A practical tenant-isolation guide covering authorization, PostgreSQL RLS, pooled connections, caches, queues, storage, resource limits, and offboarding.
- [Database Credential Rotation: How to Replace Secrets Without Breaking Connection Pools | ayushworks](https://www.ayushworks.xyz/posts/database-credential-rotation-needs-a-pool-rollout): A rollout protocol for rotating database credentials across cached secrets, connection pools, workers, rollback windows, and emergency revocation.
- [Kafka Poison Messages: Dead-Letter Queues Without Silent Data Loss | ayushworks](https://www.ayushworks.xyz/posts/kafka-poison-messages-need-an-ordering-policy): Design Kafka consumer recovery around offset ownership, durable quarantine, per-key ordering, and safe replay instead of endless retries.
- [PostgreSQL Deadlocks: Lock Ordering, Transaction Retries, and Safe Recovery | ayushworks](https://www.ayushworks.xyz/posts/postgresql-deadlocks-are-a-lock-ordering-problem): Reproduce a PostgreSQL deadlock, establish a lock-ordering contract, and design transaction retries that preserve business correctness.
- [RAG Access Control: What Happens After Document Permission Is Revoked? | ayushworks](https://www.ayushworks.xyz/posts/rag-permission-revocation-is-a-serving-contract): Design permission-aware RAG around query-time authorization, chunk provenance, answer caches, revocation windows, and adversarial tests.
- [S3 Presigned Uploads: Ownership, Overwrites, and Safe Finalization | ayushworks](https://www.ayushworks.xyz/posts/s3-presigned-uploads-need-a-finalization-protocol): Design direct-to-S3 uploads with server-owned object keys, constrained capabilities, quarantine, object verification, and idempotent finalization.
- [External Consistency Explained: Spanner, TrueTime, and Commit Wait | ayushworks](https://www.ayushworks.xyz/posts/external-consistency-has-a-latency-budget): What Spanner's TrueTime and commit wait teach architects about real-time ordering, multi-region writes, locality, and honest consistency requirements.
- [PostgreSQL Zero-Downtime Schema Migrations: A Production Guide | ayushworks](https://www.ayushworks.xyz/posts/postgresql-zero-downtime-schema-migrations): A production playbook for expand-backfill-contract migrations, PostgreSQL lock control, concurrent indexes, and safe constraint validation.
- [Kiro Flock Explained: Multi-Agent Coordination with S3 | ayushworks](https://www.ayushworks.xyz/posts/scaling-patterns-for-self-organizing-multi-agent-clusters-with-kiro): How kiro-flock coordinates Kiro CLI agents through shared S3 logs, and how to choose between peer coordination and a supervisor.
- [BM25 From First Principles: The Math, the Index, and Production Ranking | ayushworks](https://www.ayushworks.xyz/posts/bm25-search-ranking-from-first-principles): A rigorous guide to BM25 search ranking: derive IDF, term-frequency saturation, document-length normalization, calculate a score by hand, implement it, tune it, and place it inside a production retrieval stack.
- [The Best Fix Deleted a Workflow | ayushworks](https://www.ayushworks.xyz/field-notes/the-best-fix-deleted-a-workflow): We stopped automating an accidental process and removed the reason it existed.
- [Support Needed a Truthful Answer, Not Another Dashboard | ayushworks](https://www.ayushworks.xyz/field-notes/support-needed-a-truthful-answer): Turning an ambiguous asynchronous operation into a supportable product contract.
- [The Feature Flag Had No Owner | ayushworks](https://www.ayushworks.xyz/field-notes/the-feature-flag-had-no-owner): A temporary rollout control became permanent production state because nobody owned its removal.
- [The Migration Was Safe Until We Needed Rollback | ayushworks](https://www.ayushworks.xyz/field-notes/the-migration-was-safe-until-we-needed-rollback): A schema change passed forward tests but exposed that rollback was never part of the design.
- [We Made the Worker Faster and the Product Slower | ayushworks](https://www.ayushworks.xyz/field-notes/we-made-the-worker-faster-and-the-product-slower): A throughput improvement moved the bottleneck downstream and made the customer experience worse.
- [Continuous Batching Is a Scheduling Policy | ayushworks](https://www.ayushworks.xyz/posts/continuous-batching-is-a-scheduling-policy): Operate LLM continuous batching with explicit admission, fairness, prefill limits, cancellation, and tail-latency budgets.
- [Refresh-Token Rotation Is a Replay Detector | ayushworks](https://www.ayushworks.xyz/posts/refresh-token-rotation-is-a-replay-detector): Implement OAuth refresh-token families with atomic rotation, reuse detection, bounded grace, and grant-level revocation.
- [QUIC Migration Is Not Session Continuity | ayushworks](https://www.ayushworks.xyz/posts/quic-migration-is-not-session-continuity): Understand what QUIC connection migration preserves—and what application sessions, authorization, and idempotency must still guarantee.
- [S3 Multipart Uploads Need Garbage Collection | ayushworks](https://www.ayushworks.xyz/posts/s3-multipart-uploads-need-garbage-collection): Operate multipart uploads with idempotent completion, bounded retries, checksums, lifecycle cleanup, and explicit ownership.
- [PostgreSQL HOT Updates Are a Physical Design Contract | ayushworks](https://www.ayushworks.xyz/posts/postgresql-hot-updates-are-a-physical-design-contract): Increase PostgreSQL HOT updates by aligning indexes, fillfactor, row width, and update patterns with the heap page layout.
- [Technical Decision Models Compound | ayushworks](https://www.ayushworks.xyz/posts/technical-decision-models-compound): Build lasting engineering leverage by recording constraints, invariants, evidence, and reversibility—not memorizing tools.
- [AI-Generated Code Creates Review Debt | ayushworks](https://www.ayushworks.xyz/posts/ai-generated-code-creates-review-debt): Govern AI-assisted delivery by bounding change size, preserving authorship, testing behavior, and measuring review load.
- [RAG Quality Starts with Retrieval Evidence | ayushworks](https://www.ayushworks.xyz/posts/rag-quality-starts-with-retrieval-evidence): Debug retrieval-augmented generation by separating corpus, retrieval, context assembly, generation, and citation failures.
- [Embedding Upgrades Are Data Migrations | ayushworks](https://www.ayushworks.xyz/posts/embedding-upgrades-are-data-migrations): Roll out a new embedding model with versioned vectors, dual indexes, measured retrieval quality, and a reversible cutover.
- [gRPC’s HTTP/2 Transport Is Not the Reliability Model | ayushworks](https://www.ayushworks.xyz/posts/grpc-http2-is-not-reliability-model): Separate HTTP/2 multiplexing and flow control from deadlines, retries, idempotency, and overload policy in gRPC systems.
- [Copy-on-Write Moves Cost to the First Mutation | ayushworks](https://www.ayushworks.xyz/posts/copy-on-write-moves-cost-to-first-mutation): Use copy-on-write with an explicit model for page faults, write amplification, memory pressure, and snapshot lifetime.
- [Product Quantization Is a Recall–Memory Contract | ayushworks](https://www.ayushworks.xyz/posts/product-quantization-is-recall-memory-contract): Reason about IVFPQ through memory, candidate coverage, quantization error, reranking, and measured retrieval recall.
- [Bloom Filters Turn Memory into an Error Budget | ayushworks](https://www.ayushworks.xyz/posts/bloom-filters-turn-memory-into-error-budget): Size and operate Bloom filters from allowed false positives, expected cardinality, and downstream cost.
- [Adding Kafka Partitions Changes the Ordering Contract | ayushworks](https://www.ayushworks.xyz/posts/kafka-partitions-change-ordering-contract): Scale Kafka partitions without accidentally changing key affinity, consumer concurrency, and the order your product relies on.
- [Heartbeats Measure Silence, Not Failure | ayushworks](https://www.ayushworks.xyz/posts/heartbeats-measure-silence-not-failure): Design failure detection around suspicion, consequence, and recovery—not a magic heartbeat timeout.
- [Cursor Pagination Is a Consistency Contract | ayushworks](https://www.ayushworks.xyz/posts/cursor-pagination-is-a-consistency-contract): Design cursor pagination around stable ordering, snapshot choices, opaque tokens, deletion behavior, authorization scope, and property-based tests.
- [OpenTelemetry Baggage Is Untrusted Input | ayushworks](https://www.ayushworks.xyz/posts/opentelemetry-baggage-is-untrusted-input): Design trace-context propagation without leaking secrets, trusting forged metadata, or turning observability labels into an authorization channel.
- [A PodDisruptionBudget Is a Maintenance Contract | ayushworks](https://www.ayushworks.xyz/posts/pod-disruption-budgets-are-maintenance-contracts): Use Kubernetes disruption budgets with topology, rollout policy, capacity headroom, and drain tests instead of treating them as availability insurance.
- [A Read Replica Needs a Freshness Contract | ayushworks](https://www.ayushworks.xyz/posts/read-replicas-need-freshness-contracts): Design PostgreSQL replica routing around observable staleness, read-your-writes guarantees, recovery conflicts, and explicit fallback policy.
- [A Webhook Endpoint Is a Durable Inbox | ayushworks](https://www.ayushworks.xyz/posts/webhook-endpoints-are-durable-inboxes): Design webhook ingestion around raw-body authentication, durable acceptance, idempotent effects, unordered delivery, replay defense, and reconciliation.
- [Autoscaling Cannot Recover an Expired Deadline | ayushworks](https://www.ayushworks.xyz/posts/autoscaling-cannot-recover-expired-deadlines): Model HPA as a delayed feedback loop: metric lag, startup time, dependency capacity, stabilization, and the admission controls needed before new Pods arrive.
- [Your Lock Expired. Your Worker Did Not. | ayushworks](https://www.ayushworks.xyz/posts/fencing-stale-writers-at-the-storage-boundary): Understand stale-owner writes, monotonically increasing fencing tokens, atomic storage checks, and why leases alone cannot protect an external side effect.
- [Why a Prepared PostgreSQL Query Gets Slower After Warm-Up | ayushworks](https://www.ayushworks.xyz/posts/postgresql-prepared-plans-and-tenant-skew): Diagnose generic-plan regressions under tenant skew, compare real execution plans, and choose a scoped fix without disabling prepared statements everywhere.
- [A Shared Cache Key Is a Data-Isolation Boundary | ayushworks](https://www.ayushworks.xyz/posts/shared-cache-keys-are-data-isolation-boundaries): Audit authenticated HTTP caching through representation keys, private/no-store semantics, revocation windows, and two-user cache-hit tests.
- [Valid JSON Is Not Permission to Execute | ayushworks](https://www.ayushworks.xyz/posts/structured-ai-output-is-not-an-authorized-command): Separate AI output shape from factual evidence, authorization, freshness, and transactional execution using a concrete proposal-to-command boundary.
- [AI Agent Memory Is Governed State | ayushworks](https://www.ayushworks.xyz/posts/ai-agent-memory-is-governed-state): A production architecture for agent memory: provenance, consent, retention, retrieval boundaries, conflict resolution, evaluation, and deletion.
- [Rate Limiting Is Admission Control | ayushworks](https://www.ayushworks.xyz/posts/rate-limiting-is-admission-control): How identity, fairness, concurrency, Retry-After, distributed counters, and overload policy turn rate limits into a product reliability boundary.
- [Saga Compensation Is Not Rollback | ayushworks](https://www.ayushworks.xyz/posts/saga-compensation-is-not-rollback): Designing distributed workflows when completed side effects cannot be erased: semantic compensation, idempotency, orchestration, and manual resolution.
- [The OpenTelemetry Collector Is a Loss Budget | ayushworks](https://www.ayushworks.xyz/posts/opentelemetry-collector-is-a-loss-budget): How queues, retries, memory limits, persistent storage, and stateful processors determine which production evidence survives an outage.
- [PostgreSQL Replication Slots Are Retention Leases | ayushworks](https://www.ayushworks.xyz/posts/postgresql-replication-slots-are-retention-leases): How restart_lsn, catalog_xmin, retained WAL, slot invalidation, and consumer ownership turn replication slots into explicit capacity commitments.
- [JWT Verification Is a Key-Distribution System | ayushworks](https://www.ayushworks.xyz/posts/jwt-verification-is-key-distribution): How issuer binding, algorithm allowlists, JWKS rotation, cache policy, unknown key IDs, and outage behavior determine whether JWT verification is secure and available.
- [HTTP Early Data Is a Replay Boundary | ayushworks](https://www.ayushworks.xyz/posts/http-early-data-is-a-replay-boundary): A production guide to QUIC and TLS 0-RTT replay risk, idempotent operations, 425 Too Early, anti-replay limits, and safe rollout policy.
- [Filtered Vector Search Is a Recall Budget | ayushworks](https://www.ayushworks.xyz/posts/filtered-vector-search-is-a-recall-budget): Why HNSW and IVFFlat filters can return too few results, how iterative scans help, and how to measure recall per tenant instead of trusting latency alone.
- [Kubernetes Probes Are Failure Policy, Not Health Endpoints | ayushworks](https://www.ayushworks.xyz/posts/kubernetes-probes-are-failure-policy): Designing startup, readiness, and liveness probes around distinct recovery actions without turning dependency failures into restart storms.
- [PostgreSQL Synchronous Replication Is a Commit Contract | ayushworks](https://www.ayushworks.xyz/posts/postgresql-synchronous-replication-is-a-commit-contract): How synchronous_commit, quorum standbys, remote_apply, failure domains, and commit latency define the durability you actually sell to customers.
- [The Incident Needed an Owner, Not Another Channel | ayushworks](https://www.ayushworks.xyz/field-notes/the-incident-needed-an-owner-not-another-channel): Reducing coordination load, separating command from investigation, and making decisions reversible under pressure.
- [Prompt Caching Is a Context-Layout Problem | ayushworks](https://www.ayushworks.xyz/posts/prompt-caching-is-context-layout): How stable prefixes, tenant boundaries, invalidation, observability, and privacy turn prompt caching into AI infrastructure design.
- [The Microservice We Chose Not to Build | ayushworks](https://www.ayushworks.xyz/field-notes/the-microservice-we-chose-not-to-build): Preserving a domain boundary without paying for an independent service too early.
- [Every PostgreSQL Index Spends a Write-Amplification Budget | ayushworks](https://www.ayushworks.xyz/posts/postgresql-indexes-are-a-write-amplification-budget): How secondary indexes affect updates, HOT eligibility, page splits, vacuum work, and the operational cost of read optimization.
- [The Hardware Did Not Read the API Contract | ayushworks](https://www.ayushworks.xyz/field-notes/hardware-did-not-read-the-api-contract): Timing, partial truth, and designing software around a physical system that cannot be rolled back.
- [Kubernetes Termination Is a Distributed Protocol | ayushworks](https://www.ayushworks.xyz/posts/kubernetes-termination-is-a-distributed-protocol): Why SIGTERM, EndpointSlices, readiness, connection draining, and grace periods must be designed as one shutdown contract.
- [The Dashboard Was Green. The Customer Was Stuck. | ayushworks](https://www.ayushworks.xyz/field-notes/the-dashboard-was-green-the-customer-was-stuck): Why component health is not product health, and how to rebuild observability around a customer operation.
- [Kafka Exactly-Once Stops at the Side-Effect Boundary | ayushworks](https://www.ayushworks.xyz/posts/kafka-exactly-once-stops-at-side-effects): Where Kafka transactions provide atomicity, where they do not, and how to design external effects without magical guarantees.
- [The Demo That Changed the Roadmap | ayushworks](https://www.ayushworks.xyz/field-notes/the-demo-that-changed-the-roadmap): Discovering that correct software was answering the wrong question—and changing the roadmap before adding more machinery.
- [PostgreSQL Checkpoints Are Latency Events, Not Maintenance Events | ayushworks](https://www.ayushworks.xyz/posts/postgresql-checkpoints-are-latency-events): How checkpoint pacing, WAL pressure, full-page writes, and storage headroom shape PostgreSQL tail latency.
- [Tail Sampling Is a Memory Budget Disguised as an Observability Feature | ayushworks](https://www.ayushworks.xyz/posts/tail-sampling-is-a-memory-budget): How tail-based trace sampling buffers incomplete traces, routes spans consistently, makes late decisions, and fails under cardinality, bursts, and collector loss.
- [DNS Failover Is a Bounded-Staleness Protocol | ayushworks](https://www.ayushworks.xyz/posts/dns-failover-is-bounded-staleness): How recursive caches, TTL, negative caching, resolver behavior, health checks, and connection reuse determine the real recovery time of DNS-based failover.
- [Strongly Consistent Object Storage Still Needs Concurrency Control | ayushworks](https://www.ayushworks.xyz/posts/object-storage-needs-concurrency-control): Why S3 strong consistency does not prevent lost updates, and how conditional writes, immutable keys, checksums, versioning, and metadata transactions create safe object workflows.
- [A Kafka Rebalance Is a Coordination Protocol, Not a Consumer Restart | ayushworks](https://www.ayushworks.xyz/posts/kafka-rebalances-are-stop-the-world-coordination): How Kafka consumer ownership, eager and cooperative rebalancing, offset commits, static membership, and generation fencing shape correctness and availability.
- [PostgreSQL Vacuum Is Concurrency Control, Not Housekeeping | ayushworks](https://www.ayushworks.xyz/posts/postgresql-vacuum-is-concurrency-control): A mechanical guide to MVCC dead tuples, visibility horizons, autovacuum thresholds, transaction-ID freezing, wraparound, and the sessions that prevent cleanup.
- [The Architecture Is Not the Product | ayushworks](https://www.ayushworks.xyz/field-notes/the-architecture-is-not-the-product): A field note on choosing engineering boundaries for Saleslyt, Myotrek, healthcare services, and offline payments—and why the real constraint matters more than the impressive diagram.
- [A Raft Write Is Not Committed Just Because Most Replicas Have It | ayushworks](https://www.ayushworks.xyz/posts/raft-commit-is-not-replica-count): A mechanical deep dive into Raft terms, elections, log replication, the current-term commit rule, linearizable reads, persistence ordering, and ambiguous client outcomes.
- [Durable Workflows Do Not Remove the Need for Idempotency | ayushworks](https://www.ayushworks.xyz/posts/durable-workflows-do-not-remove-idempotency): How replay-based workflow engines recover orchestration, where activity ambiguity remains, and how to design deterministic workflows with idempotent effects.
- [LLM Serving Is KV-Cache Capacity Planning | ayushworks](https://www.ayushworks.xyz/posts/llm-serving-is-kv-cache-capacity-planning): A practical model for PagedAttention, continuous batching, admission control, and the latency-throughput trade-offs of production LLM inference.
- [Kubernetes Availability Is Placement Plus Disruption Policy | ayushworks](https://www.ayushworks.xyz/posts/kubernetes-availability-is-placement-plus-disruption): Why replicas alone do not create availability, and how topology spread, disruption budgets, probes, and capacity must form one failure-domain policy.
- [Serializable Isolation Is a Retry Protocol, Not a Checkbox | ayushworks](https://www.ayushworks.xyz/posts/serializable-isolation-is-a-retry-protocol): How PostgreSQL Serializable Snapshot Isolation prevents write skew, why serialization failures are correct behavior, and how to build bounded transaction retries.
- [AI Inference Routing Is Capacity Control | ayushworks](https://www.ayushworks.xyz/posts/ai-inference-routing-is-capacity-control): A production design for routing AI inference by task, risk, latency, cost, capability, evaluation evidence, and deterministic fallback—not model fashion.
- [Data Retention Is a System Design Problem | ayushworks](https://www.ayushworks.xyz/posts/data-retention-is-a-system-design-problem): A production architecture for retention policy, deletion guarantees, PostgreSQL partitioning, backups, derived data, legal holds, and verifiable erasure.
- [Incident Command Is a Distributed System | ayushworks](https://www.ayushworks.xyz/posts/incident-command-is-a-distributed-system): How CTOs can design incident response around explicit authority, shared state, bounded coordination, customer communication, and evidence-driven recovery.
- [Build vs Buy Is an Exit-Cost Decision | ayushworks](https://www.ayushworks.xyz/posts/build-vs-buy-is-an-exit-cost-decision): A practical CTO framework for evaluating software vendors through differentiation, operating cost, failure ownership, data portability, and credible exit paths.
- [Architecture Decisions Need Expiry Dates | ayushworks](https://www.ayushworks.xyz/posts/architecture-decisions-need-expiry-dates): A CTO-level operating model for architecture decisions: explicit context, measurable consequences, review triggers, ownership, and reversible migration paths.
- [Production AI Needs Release Gates, Not a Trust Score | ayushworks](https://www.ayushworks.xyz/posts/production-ai-risk-gates): A practical operating model for AI risk: use-case boundaries, eval gates, authority limits, observability, degradation, and accountable production release.
- [Kubernetes Requests Are an Economic Model | ayushworks](https://www.ayushworks.xyz/posts/kubernetes-resource-policy-capacity-governance): A CTO-level method for setting Kubernetes requests, limits, QoS, autoscaling, and capacity policy from workload evidence instead of copied YAML.
- [Tenant Isolation Should Not Depend on Every WHERE Clause | ayushworks](https://www.ayushworks.xyz/posts/postgresql-rls-tenant-isolation): A production guide to PostgreSQL row-level security: policy design, connection context, owner bypass, testing, performance, and operational safeguards.
- [An Error Budget Should Change the Roadmap | ayushworks](https://www.ayushworks.xyz/posts/error-budgets-engineering-investment-policy): How technical leaders turn SLOs and error budgets into an explicit policy for releases, reliability investment, incidents, and product tradeoffs.
- [Scale the Blast Radius, Not Just the Fleet | ayushworks](https://www.ayushworks.xyz/posts/cell-based-architecture-blast-radius): A CTO-level guide to cell-based architecture: partition keys, routing, migration, observability, and deciding when fault isolation earns its operational cost.
- [Feature Flags Are Production State | ayushworks](https://www.ayushworks.xyz/posts/feature-flags-are-production-state): A CTO-level operating model for typed evaluation, safe defaults, targeting privacy, rollout evidence, flag debt, kill switches, and control-plane failure.
- [Verify What You Deploy | ayushworks](https://www.ayushworks.xyz/posts/verify-what-you-deploy): A CTO-level software supply-chain design for immutable artifacts, SLSA provenance, Sigstore verification, admission policy, builder trust, and incident response.
- [Cache Invalidation Is a Consistency Protocol | ayushworks](https://www.ayushworks.xyz/posts/cache-invalidation-is-consistency-protocol): A production guide to cache-aside races, versioned keys, bounded staleness, invalidation delivery, stampede control, negative caching, and evidence of correctness.
- [PostgreSQL Connections Are a Capacity Budget | ayushworks](https://www.ayushworks.xyz/posts/postgresql-connections-are-capacity-budget): A production design for connection admission, pool sizing, PgBouncer modes, reserved capacity, queueing, and preventing autoscaling from overwhelming PostgreSQL.
- [Control Planes Must Fail Quietly | ayushworks](https://www.ayushworks.xyz/posts/control-planes-must-fail-quietly): A CTO-level architecture for separating control and data planes, bounding reconciliation, surviving stale configuration, and preventing management failures from becoming customer outages.
- [Cloud Cost Is an Architecture Metric | ayushworks](https://www.ayushworks.xyz/posts/cloud-unit-economics-for-architects): A CTO-level method for converting cloud bills into unit economics, ownership, cost attribution, capacity decisions, and engineering release gates.
- [AI Evals Are Release Engineering | ayushworks](https://www.ayushworks.xyz/posts/ai-evals-are-release-engineering): A CTO-level control plane for shipping AI systems with task-specific evals, regression gates, production feedback, safe rollout, and rollback evidence.
- [Evolve APIs Without Flag Days | ayushworks](https://www.ayushworks.xyz/posts/api-evolution-without-flag-days): A production migration protocol for compatibility envelopes, expand-contract changes, Protobuf schemas, events, observability, and deletion evidence.
- [Design Service Identity Before Buying a Service Mesh | ayushworks](https://www.ayushworks.xyz/posts/service-identity-before-service-mesh): A production design for workload identity, SPIFFE trust domains, short-lived credentials, authorization, rotation, and migration away from shared service secrets.
- [Backups Do Not Prove Recoverability | ayushworks](https://www.ayushworks.xyz/posts/backups-do-not-prove-recoverability): A CTO-level recovery design for RPO, RTO, PostgreSQL PITR, dependency order, restore drills, and evidence that the business can survive data loss.
- [Change Data Capture Is a Recovery Contract | ayushworks](https://www.ayushworks.xyz/posts/cdc-recovery-contract): A CTO-level guide to CDC snapshots, offsets, schema evolution, ordering, replay, lag, and proving downstream systems can recover without corrupting business state.
- [Durable AI Agents Need Workflow Semantics, Not Chat Loops | ayushworks](https://www.ayushworks.xyz/posts/durable-ai-agent-workflows): A production architecture for replayable agent state, idempotent tools, human approval, versioning, budgets, and recovery across long-running AI work.
- [Tenant Isolation Is a Data Model, Not a WHERE Clause | ayushworks](https://www.ayushworks.xyz/posts/multi-tenant-saas-isolation): A CTO-level guide to pooled and siloed SaaS tenancy, PostgreSQL row security, identity propagation, noisy-neighbor controls, and proving isolation in production.
- [Queues Hide Overload Until Recovery Becomes Impossible | ayushworks](https://www.ayushworks.xyz/posts/queues-backpressure-overload-control): How CTOs should reason about bounded queues, admission control, backpressure, load shedding, and recovery time before asynchronous architecture becomes an outage amplifier.
- [Your Timeout Budget Is an Architecture Decision | ayushworks](https://www.ayushworks.xyz/posts/deadline-budgets-retry-amplification): A CTO-level method for deadline propagation, retry budgets, jitter, and preventing one slow dependency from amplifying into a fleet-wide outage.
- [AI Agents Need a Control Plane, Not a Larger Prompt | ayushworks](https://www.ayushworks.xyz/posts/ai-agent-control-plane-mcp-security): A production architecture for AI-agent identity, MCP authorization, bounded tools, policy enforcement, budgets, approvals, and auditable execution.
- [Observability Is a Data Contract, Not a Dashboard Purchase | ayushworks](https://www.ayushworks.xyz/posts/opentelemetry-observability-data-contract): How engineering leaders can use OpenTelemetry semantics, cardinality budgets, context propagation, and SLO questions to build portable operational evidence.
- [The Transactional Outbox Is Not the Delivery Guarantee | ayushworks](https://www.ayushworks.xyz/posts/transactional-outbox-delivery-guarantees): A CTO-level design for atomic event creation, idempotent relays and consumers, ordering, replay, and end-to-end delivery evidence.
- [PostgreSQL Logical Replication Failover: The Slot Is Part of Your Recovery Plan | ayushworks](https://www.ayushworks.xyz/posts/postgresql-logical-replication-failover): How to make PostgreSQL logical subscribers survive publisher failover, verify synchronized slots, and design an honest recovery objective.
- [A Modern PostgreSQL JDBC Driver Built for Virtual Threads and Native Protocols | ayushworks](https://www.ayushworks.xyz/posts/modern-postgresql-jdbc-driver-virtual-threads): Explore the architecture of pg-java, a PostgreSQL-first driver leveraging Java 21 virtual threads, ReentrantLock unpinning, and decoupled JDBC layering.
- [Transpiling Multi-Language DB Functions to PL/pgSQL with plx | ayushworks](https://www.ayushworks.xyz/posts/plx-transpiling-postgresql-functions): Learn how the plx extension transpiles familiar programming languages like Python, JS, and Go into native PL/pgSQL for zero-overhead execution inside PostgreSQL.
- [PostgreSQL Minor Updates: CVE-2026-6464 and Index Maintenance | ayushworks](https://www.ayushworks.xyz/posts/postgresql-18-6-security-patching-index-remediation): An engineering analysis of PostgreSQL 18.6, CVE-2026-6464, skipped 18.5, and post-upgrade REINDEX tasks for GIN, btree_gist, and ltree extensions.
- [SynchDB 1.4: Oracle CDB Support and Secured FDW Snapshots | ayushworks](https://www.ayushworks.xyz/posts/synchdb-1-4-oracle-cdb-tls-fdw-snapshots): SynchDB 1.4 introduces Oracle Container Database support across CDC, FDW, and OLR paths, plus TLS and Oracle Wallet encryption for initial snapshot data transfers.
- [KYAML in Practice: Explicit Kubernetes Manifests Without a Migration | ayushworks](https://www.ayushworks.xyz/posts/kubernetes-kyaml-production-workflow): How KYAML changes manifest formatting, how to generate it, and where the tradeoff is useful.
- [Hello World | ayushworks](https://www.ayushworks.xyz/posts/hello-world): My first blog post.
- [The Cost of Complexity | ayushworks](https://www.ayushworks.xyz/posts/the-cost-of-complexity): Why simple systems fail less often than complex ones, and how to think about architectural decisions.
- [Building Microservices That Fail Gracefully | ayushworks](https://www.ayushworks.xyz/posts/building-reliable-microservices): Practical patterns for resilient service-to-service communication.
- [Thinking Through Offline-First Payments | ayushworks](https://www.ayushworks.xyz/posts/offline-first-payments): Security and distributed-systems lessons from moving value without a live server.
- [Why Rust Fits Infrastructure Work | ayushworks](https://www.ayushworks.xyz/posts/rust-for-infrastructure): What Rust changes when reliability and resource use both matter.
- [Building AI Products for Accessibility | ayushworks](https://www.ayushworks.xyz/posts/accessible-ai-products): Product principles for AI-assisted reading experiences.
- [From Repository to Real Product | ayushworks](https://www.ayushworks.xyz/posts/shipping-full-stack-products): A practical checklist for turning a full-stack build into a product people can rely on.

## Citation and discovery

- Attribute original analysis to Ayush Basak and link to the canonical page URL.
- Preserve stated constraints, failure boundaries, and trade-offs when summarizing.
- Do not infer credentials, employers, customers, benchmarks, or outcomes not stated on the cited page.
- Append `.md` to a content page URL for its Markdown representation (for example, https://www.ayushworks.xyz/posts/transactional-outbox-delivery-guarantees.md).
- [Full-text Markdown corpus](https://www.ayushworks.xyz/llms-full.txt)
- [XML sitemap](https://www.ayushworks.xyz/sitemap.xml)
- [RSS feed](https://www.ayushworks.xyz/rss.xml)
- [Atom feed](https://www.ayushworks.xyz/feed.atom)
- [JSON Feed](https://www.ayushworks.xyz/feed.json)