Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
magden
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
Postgres for analytics: these are the ways
(justpostgres.tech)
3 points
by
magden
7mo ago
|
0 comments
2.
▲
Just Use Postgres the Book
(manning.com)
3 points
by
magden
2y ago
|
1 comments
3.
▲
by
magden
2y ago
I’ve always thought that "Just Use Postgres" would make an excellent title and topic for a book. And we’ve partnered with Manning to bring it to life. Looking forward to your feedback on the TOC and chapters that have already been
4.
▲
by
magden
2y ago
Cool, works with my YugabyteDB deployment using the provided scripts for Postgres.
5.
▲
by
magden
2y ago
1. Nope, I don't think that CRDB is generally faster than Yugabyte. Vendors can't say otherwise in their own benchmarks :) 3. That code must be the tooling around the db and various smart drivers (that extend default drivers of Po
6.
▲
What Is the Open Source Alternative to CockroachDB?
(medium.com)
10 points
by
magden
2y ago
|
6 comments
7.
▲
Postgres to YugabyteDB in 100 Apps: The Postgres App Century Challenge
(yugabyte.com)
1 points
by
magden
2y ago
|
0 comments
8.
▲
Does Open Source Work as a Long-Term Business Model?
(yugabyte.com)
24 points
by
magden
2y ago
|
3 comments
9.
▲
[2019] We Changed YugabyteDB Licensing to 100% Open Source
(yugabyte.com)
2 points
by
magden
2y ago
|
1 comments
10.
▲
by
magden
2y ago
In light of the recent license changes by CockroachDB, their competitor (YugabyteDB) took another approach that seems to work well.
11.
▲
When to use distributed Postgres for gen AI apps?
(yugabyte.com)
1 points
by
magden
2y ago
|
0 comments
12.
▲
YugabyteDB Moves Beyond PostgreSQL 11
(yugabyte.com)
2 points
by
magden
2y ago
|
0 comments
13.
▲
Will Postgres use my index or not?
(medium.com)
1 points
by
magden
2y ago
|
0 comments
14.
▲
Why Has Figma Reinvented the Wheel with PostgreSQL?
(medium.com)
169 points
by
magden
2y ago
|
91 comments
15.
▲
What we learned in 6 months of working on an AI Developer
(blog.pythagora.ai)
63 points
by
magden
3y ago
|
49 comments
16.
▲
by
magden
3y ago
Here is a detailed article covering various design patterns for multi-region deployments: https://www.yugabyte.com/blog/multi-region-database-deployme...
17.
▲
by
magden
3y ago
(I'm the author of the article) There are several design patterns depending on whether you need to optimize the latency for reads, writes, or both. If it's all abour reads, then you can use follower reads (as shown in the article)
18.
▲
Live Streaming the Super Bowl: The Art of Scaling Across Multiple Cloud Regions
(yugabyte.com)
32 points
by
magden
3y ago
|
3 comments
19.
▲
Why Postgres RDS didn't work for us
(medium.com)
2 points
by
magden
3y ago
|
1 comments
20.
▲
We switched to Java 21 virtual threads and got a deadlock in TPC-C for Postgres
(blog.ydb.tech)
280 points
by
magden
3y ago
|
243 comments
21.
▲
by
magden
3y ago
CloudnativePg scales vertically. Distributed Postgres assumes you can data and read-write workload both horizontally and vertically.
22.
▲
How to Scale a Single-Server Database: A Guide to Distributed PostgreSQL
(yugabyte.com)
33 points
by
magden
3y ago
|
3 comments
23.
▲
by
magden
3y ago
It was great to see the article about distributed Postgres by the Crunchy Data team trending on HN. Judging by the ongoing discussion, many got interested in the whys and hows of distributed Postgres. I published the following guide to dist
24.
▲
by
magden
3y ago
> You handwaved this away, saying you can just store an entire table on a single node, but that defeats many of the benefits of these sharded SQL databases. I just clarified one-liners listed under the closing "Cons" section. M
25.
▲
by
magden
3y ago
There are good and solid HA options in the Postgres ecosystem that are fully open. You can use Patroni for standard Postgres or YugabyteDB that is fault-tolerant by design. Specifics are here: https://www.yugabyte.com/postgr
26.
▲
by
magden
3y ago
You can achieve RPO=0 with Postgres using synchronous logical replication. You would need to replicate to 2+ standbys because if there is only one standby and it goes down then the primary will stuck. During the failover you would need to h
27.
▲
by
magden
3y ago
Scalability is not the only reason for jumping on a distributed Postgres version. Some apps might do just 1000 ops/second but still run on a distributed database for high availability or data locality reasons. For instance, shared-noth
28.
▲
by
magden
3y ago
First time seeing someone call Spanner, CockroachDB, and YugabyteDB a "distributed key-value store with SQL" :) The cons of the mentioned distributed shared-nothing SQL databases are questionable: - "Key-value store" is
29.
▲
AI Workforce Is Already Coming for Junior Developer Jobs on Wall Street
(medium.com)
22 points
by
magden
3y ago
|
34 comments
30.
▲
Two Things to Keep in Mind Before You Start Building Another Database System
(medium.com)
1 points
by
magden
3y ago
|
0 comments
More ›