From: | "MauMau" <maumau307(at)gmail(dot)com> |
---|---|
To: | <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Merlin Moncure" <mmoncure(at)gmail(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com> |
Subject: | Re: I'd like to discuss scaleout at PGCon |
Date: | 2020-09-15 04:40:36 |
Message-ID: | 95E9141724C94B7897E97FA3DA105349@tunaPC |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello all,
# I'm resending because some error occurred
I've overhauled the scaleout design wiki I presented at PGCon 2018
developer unconference and assembled the research of other DBMSs'
scale-out features.
Scaleout Design
https://wiki.postgresql.org/wiki/Scaleout_Design
I intentionally have put little conclusion on our specification and
design. I'd like you to look at recent distributed databases, and
then think about and discuss what we want to aim for together. I feel
it's better to separate a thread per topic or group of topics.
I'm sorry, but I'm not confident about the readability at all, because
I cannot draw figures due to my visual impairment, and the page is
full of text only.
What workload do you think we should focus on first, OLTP or
analytics? I think OLTP, because open source Postgres probably has
been so far getting popular with OLTP. Also, I don't expect many
people will use existing popular SaaS for data warehousing like Amazon
Redshift, Azure Synapse, Google BigQuery and Snowflake, rather than
build their analytics databases on public IaaS or on-premises.
Regards
MauMau
From | Date | Subject | |
---|---|---|---|
Next Message | Bharath Rupireddy | 2020-09-15 04:41:00 | Re: Parallelize stream replication process |
Previous Message | MauMau | 2020-09-15 04:37:32 | Re: I'd like to discuss scaleout at PGCon |