Tino Tereshko, the founder of MotherDuck helped our to point the mistake in this article i.e. "Duck DB is a distributed SQL database designed to be highly available and able to scale up to millions of transactions per second. It is built on a distributed architecture that allows it to spread data across multiple nodes, making it resilient to hardware failures and ensuring high availability. Duck DB is also designed to be horizontally scalable, meaning that it can easily scale up to handle more transactions as needed. This scalability allows Duck DB to handle large volumes of concurrent transactions, making it well-suited for applications that require high performance."

I would like to thank him for pointing this out.

Here is the link to his post: https://www.linkedin.com/feed/update/urn:li:activity:7105975011491938304/

1. DuckDB is not currently designed to scale up to millions of transactions per second. However, the developers are working on improving the stability of DuckDB in future.

2. DuckDB is not a fully distributed database. it is a hybrid database that used a combination of centralised and distributed storage.