Viewing profile — harisund1990

Meko is the agent-native unified data infrastructure that enables multi-agent systems to learn together, building collective memory, shared knowledge, Conversations and Decision Tr…

This is cool to see! Looks like a compete against pg_mooncake which Databricks acquired. But how is this different from pg_duckdb?

That's a very big difference which makes this hard to believe. I would expect them to be within 20% of each other. I think I know the trick they used. The 48 core Aurora is the wor…

Seems like a perfect use case for a distributed database like YugabyteDB. Have you looked into it?

YugabyteDB a distributed postgres database. Think of it as a true drop in replacement for postgres that runs on multiple nodes. It internally does replication, sharding and leader …

This is a fully open source MongoDB alternative that offers high availability and horizontal scalability. It's a joint collaboration between YugabyteDB, FerretDB and the Microsoft …

Anyone who has had to do a Postgres major upgrade can relate to this

"What good is an open source database when it’s written in a mix of memory-unsafe language?" A OLTP high performance Relational Database vendor has this section in their competitiv…

Is Postgres becoming the new SQL standard? You have the ANSI SQL, but it does not cover a lot of stuff, and everyone has their own variances, and extra features. But, all new DBs l…

I love headers but I wish you could split them in two so that private functions and variables can line in the c file. This would help reduce a lot of header bloat as well.

Cutis is an extension. That's the best you can get by being outside the core db. If you want true distributed architecture then you need to change the QO, DDL, transaction, even qu…

> What we see in cases where someone takes Postgres and replaces the guts (Greenplum, Cloudberry, and of course YDB) is that it becomes a huge effort to keep up with new Postgres v…

Yugabyte does automatic sharding

It's easier to manage 1 database instead of 1000s

The article should be titled "Why Figma HAD TO reinvent the wheel with PostgresSQL". When you have a legacy system and not enough time, or will to move off of it the only option is…

Sharding is the easy part. Eventually you need to implement distributed transactions, taking a consistent backup across shards, PITR, resharding, load balancing, and the list goes …