How I write back ends

Re:How I write back ends by _tkzm on Wednesday January 22, 2020 @04:24AM (#22115946)

next time try cockroachdb instead of postgres.

[ Parent | on HN ]

Re:How I write back ends by stevewodil on Wednesday January 22, 2020 @05:26AM (#22116224)

Perhaps you could elaborate further on this to add to the discussion

[ Parent | on HN ]

Re:How I write back ends by _tkzm on Thursday January 23, 2020 @03:31AM (#22125864)

when you hit scaling issues with standard postgres. cdb has the same wire format so no code change would be needed. for mysql alternative, there is tidb but that one is not a single binary so i never used it.

[ Parent | on HN ]

Re:How I write back ends by zahrc on Wednesday January 22, 2020 @07:36AM (#22116971)

I’ve never heard of cockroachdb, what are the advantages of it and why is it preferable to Postgres?

[ Parent | on HN ]

Re:How I write back ends by vvern on Wednesday January 22, 2020 @08:12AM (#22117210)

A primary advantage is horizontal scalability. If you need more capacity, just add more nodes.

Additionally it offers better fault tolerance and zero-downtime online upgrades. For more advanced use cases it can be deployed in a geo-replicated topology and configured with partitioning for low latency transactions when confined to a single region while proving strong consistency and a single logical database globally.

Disclaimer: I work on cockroach.

[ Parent | on HN ]

Re:How I write back ends by williamdclt on Wednesday January 22, 2020 @06:00AM (#22116396)

An explanation of why would be nice

[ Parent | on HN ]