Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
harisund1990
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
Meko: The Data Infrastructure for Agents That Work and Learn Together
(yugabyte.com)
15 points
by
harisund1990
4mo ago
|
6 comments
2.
▲
by
harisund1990
4mo ago
Meko is the agent-native unified data infrastructure that enables multi-agent systems to learn together, building collective memory, shared knowledge, Conversations and Decision Traces that compounds across the entire system.
3.
▲
Powering AI at Scale: Benchmarking 1B Vectors in YugabyteDB
(yugabyte.com)
1 points
by
harisund1990
11mo ago
|
0 comments
4.
▲
by
harisund1990
11mo ago
This is cool to see! Looks like a compete against pg_mooncake which Databricks acquired. But how is this different from pg_duckdb?
5.
▲
The Index Is the Database
(medium.com)
2 points
by
harisund1990
1y ago
|
0 comments
6.
▲
The Rise and Sprawl of PostgreSQL
(computerweekly.com)
2 points
by
harisund1990
1y ago
|
0 comments
7.
▲
by
harisund1990
1y ago
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 worst, it performs just as well as the 32 core one. If the
8.
▲
by
harisund1990
1y ago
Seems like a perfect use case for a distributed database like YugabyteDB. Have you looked into it?
9.
▲
by
harisund1990
1y ago
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 election. Just add more nodes and you get to increase both r
10.
▲
YugabyteDB now supports MongoDB API
(yugabyte.com)
7 points
by
harisund1990
1y ago
|
1 comments
11.
▲
by
harisund1990
1y ago
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 DocumentDB teams.
12.
▲
Goodbye to Painful PostgreSQL Upgrades: YugabyteDB does it live
(yugabyte.com)
2 points
by
harisund1990
1y ago
|
2 comments
13.
▲
by
harisund1990
1y ago
Anyone who has had to do a Postgres major upgrade can relate to this
14.
▲
Ask HN: Do enterprises now consider the use of C/C++ based databases as bad?
2 points
by
harisund1990
1y ago
|
0 comments
15.
▲
Enhanced Cron Job Resilience with Pg_cron in YugabyteDB
(yugabyte.com)
3 points
by
harisund1990
2y ago
|
0 comments
16.
▲
by
harisund1990
2y ago
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 like YugabyteDB and Aurora DSQL for ditributed, pg_duckdb and
17.
▲
by
harisund1990
2y ago
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.
18.
▲
A look at Aurora DSQL's architecture
(medium.com)
1 points
by
harisund1990
2y ago
|
0 comments
19.
▲
by
harisund1990
2y ago
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 query stat components. At which point it ends up being a
20.
▲
by
harisund1990
2y ago
> 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 versions. The first upgrade is the hardest, but after that
21.
▲
Two approaches to make a cloud database highly available
(medium.com)
1 points
by
harisund1990
2y ago
|
0 comments
22.
▲
by
harisund1990
2y ago
Yugabyte does automatic sharding
23.
▲
by
harisund1990
2y ago
It's easier to manage 1 database instead of 1000s
24.
▲
by
harisund1990
2y ago
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 to get inventive and build with what you have. Th
25.
▲
by
harisund1990
2y ago
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 on... That takes exponentially more number of people and tim
26.
▲
by
harisund1990
3y ago
1% of Visa maybe?
27.
▲
by
harisund1990
3y ago
No one needs 10,000 machines. They likely have scale issues and cannot scale their database quick enough so they planned for the worst spike possible which is likely for a hour on cyber Monday.