From 871c35a3b8a10e49c576e49845fbea6011b3468a Mon Sep 17 00:00:00 2001
From: Mohammed Arshad Ansari <423442+arshadansari27@users.noreply.github.com>
Date: Tue, 1 Sep 2026 13:49:38 +0530
Subject: [PATCH] Add DuckDB in Production blog post (#334)

---
 README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/README.md b/README.md
index 573eb86..acff827 100644
--- a/README.md
+++ b/README.md
@@ -460,6 +460,7 @@ Community-contributed DuckDB extensions, which can be installed via `INSTALL ⟨
 - [SwanLake](https://www.wangfenjin.com/posts/swanlake-en/) - An Arrow Flight SQL Datalake Service Built on DuckDB + DuckLake
 - [DuckDB-Wasm on a Plain Static Host — Without Breaking AdSense](https://csvtodashboard.com/duckdb-wasm-static-host) - Why a static site ships the single-threaded build: SharedArrayBuffer, COOP/COEP, and the cross-origin isolation tradeoff.
 - [Building duckdb-pst](https://intellekt.fyi/2026/02/03/the-data-warehouse-in-your-email-archive-teaching-duckdb-to-speak-outlook/) - How to go from 0 to a production-ready DuckDB extension for Outlook PSTs, including table functions, MAPI schema serialization, projection/statistics pushdown, concurrent planning, and late materialization.
+- [DuckDB in Production: What It's Actually Good At (and What It Isn't)](https://hikmahtechnologies.com/blog/duckdb-in-production-what-its-good-at/) - Where DuckDB fits in production and where it does not: three deployment patterns (in-process in a service, containerised batch job, Parquet lake with read-only readers), plus its limitations around single-process writes, governance and memory spill.
 
 ### Books