MIME-Version: 1.0
References: <Z_1Cq7JvabsFYjQo@ark>
 <CAJ7c6TOfQhE51Gf-=FeRgBTcUgznAcAA3Sa4mexi5MUg3ODj2Q@mail.gmail.com>
 <0e01fb4d-f8ea-4ca9-8c9b-79264ce11993@postgrespro.ru>
In-Reply-To: <0e01fb4d-f8ea-4ca9-8c9b-79264ce11993@postgrespro.ru>
From: Aleksander Alekseev <aleksander@timescale.com>
Date: Tue, 15 Apr 2025 14:15:36 +0300
Message-ID: 
 <CAJ7c6TOXPTaE6Bb33B1fEiOb7ifjmE7rWs9rp8Crc6r808zP6A@mail.gmail.com>
Subject: Re: Built-in Raft replication
To: pgsql-hackers@lists.postgresql.org
Cc: Yura Sokolov <y.sokolov@postgrespro.ru>,
 Konstantin Osipov <kostja.osipov@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAJ7c6TOXPTaE6Bb33B1fEiOb7ifjmE7rWs9rp8Crc6r808zP6A%40mail.gmail.com>
Precedence: bulk

Hi Yura,

> I've been working in a company which uses MongoDB (3.6 and up) as their
> primary storage. And it seemed to me as "God Send". Everything just worked.
> Replication was as reliable as one could imagine. It outlives several
> hardware incidents without manual intervention. It allowed cluster
> maintenance (software and hardware upgrades) without application downtime.
> I really dream PostgreSQL will be as reliable as MongoDB without need of
> external services.

I completely understand. I had exactly the same experience with
Stolon. Everything just worked. And the setup took like 5 minutes.

It's a pity this project doesn't seem to get as much attention as
Patroni. Probably because attention requires traveling and presenting
the project at conferences which costs money. Or perhaps people are
just happy with Patroni. I'm not sure in which state Stolon is today.

-- 
Best regards,
Aleksander Alekseev