Use Cases for Multi-Master PostgreSQL in the Open-source Era
Session Description
Database availability is calculated in terms of Uptime as currency and vendor lock-in is a risk, Open-source databases are powering a quiet revolution. At the heart of it lies PostgreSQL, and it's not just standing its ground, it's going multi-master.
This session dives into how distributed PostgreSQL, with true multi-master capabilities, is being deployed across industries to solve high availability, global distribution, and regulatory challenges. all while staying free and open.
We’ll explore the technical underpinnings of multi-master PostgreSQL, why organizations are choosing FOSS over proprietary options, and what happens when Open-source meets mission-critical scale. Expect real use cases, architectural patterns, and lessons learned from deployments in edge environments.
If you're passionate about PostgreSQL, distributed systems, or building future-ready infrastructure, this talk is for you.
Key Takeaways
Getting started: Practical tips and tools to explore multi-master PostgreSQL in your own stack.
Why FOSS matters: The strategic advantages of open-source database infrastructure in distributed environments.
When to go multi-master: Use cases across Fintech, SaaS, and global-scale applications.
Architectural patterns: Common design choices for conflict resolution, write scaling, and region-based sharding.
Deployment lessons: Real-world challenges in consistency, failover, and operational overhead — and how teams solved them.
Session Categories
Which track are you applying for?
Speakers
Hari Kiran
Reviews
(i) Not focused on core internals of distributed postgres or special design review, rather workings, issues and architecture around distributed dabases.
(ii) The pgedge project seems to have its own community license and not an OSI approved license. I am not sure if this is a constraint but wanted to highlight
It seems like you shoehorned FOSS into your talk. Postgres multi-master would be good to talk about, mentioning your project would be permissible. But Based on this talk proposal it doesn't seem like you will be working from the core concepts out it seems more like a sales pitch for postgres --> pgedge.
Most in your audience will already be sold on why FOSS solutions are better than proprietary ones they would really just want to know about this and other new, cool features of PSQL
This talk would be more interesting if it were about the architecture
Doesn't completely fall under FOSS, doesn't seem like a right fit here
The proposal read more like a pitch for a specific product, "pgEdge," rather than a talk focused on core concepts, architecture, or contributions to the PostgreSQL community. A significant concern was also raised that the "pgEdge" project uses a non-OSI-approved license, which goes against the core principles of our conference.