I thought that this kind of solution had high latency and bad OLTP
capabilities (low trans/second)? Analytics is not a high priority.
BR
2018-02-01 19:01 GMT+01:00 Dan Wierenga :
>
>
> On Wed, Jan 31, 2018 at 7:48 PM, Steven Lembark
> wrote:
>
>> On Mon, 29 Jan 2018 15
Boussekey :
> Using citusdb enterprise, you can replicate the table shards.
>
> Here is the link to the documentation:
> https://docs.citusdata.com/en/v7.2/reference/user_defined_
> functions.html#replicate-table-shards
>
> Regards,
> Thomas
>
>
> 2018-01-30 12:18 GMT+0
As already said. It's missing 2 level sharding and is restricted with SPOF.
BR
Matej
2018-01-30 12:05 GMT+01:00 Rakesh Kumar :
>
>
>
> >We are looking for multi tenancy but at scale. That's why the sharding
> and partitioning. It depends how you look at the distributed part.
>
> Citusdb.
>
We are looking for multi tenancy but at scale. That's why the sharding and
partitioning. It depends how you look at the distributed part.
BR
Matej
29. jan. 2018 17.50 je oseba "Rakesh Kumar"
napisala:
>
>
> > On Jan 29, 2018, at 09:34 , Matej wrote:
> >
when something
goes wrong. then it's not a black box anymore and you have to study the
details.
For node loss we plan a master -slave setup, and there will not be so many
cross shard queries.
BR
Matej
2018-01-29 16:15 GMT+01:00 Thomas Boussekey :
> Hello,
>
> Facing the same
Hi Everyone.
We are looking at a rather large fin-tech installation. But as scalability
requirements are high we look at sharding of-course.
I have looked at many sources for Postgresql sharding, but we are a little
confused as to shared with schema or databases or both.
So far our understandin
