Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

TiDB – cloud-native, distributed SQL database written in Go

github.com

Post reply on HN
Print view View original

61–67 of 67 posts

Re: TiDB – cloud-native, distributed SQL database written in Go

#61

Post by std_reply »

sgarland wrote: post #59
std_reply wrote: post #38

Earlier quoted context omitted.

TiDB is running core banking services too. I think people’s idea of scale and operating at scale is limited to their experience. You can get MySQL to run at any scale, look at Meta and Shopify. Operational complexity at that scale is a different story. Distributed databases reduce a lot of the operational complexity. To take one example: Try a DDL on a 5 TB table in any replicated MySQL topology of choice and compare…

> Distributed databases reduce a lot of the operational complexity That’s a new one to me; never have I ever heard someone claim that making a system distributed reduces complexity. I’ve operated EDB’s Distributed Postgres at a decent scale (< 100 TB of unique data); in no way did it enable reduced complexity. For the devs, maybe – “chuck whatever data you want wherever you want, it’ll show up.” But for Ops? Absolute…

I’m contrasting a single node database with bolted on replication vs a distributed SQL database that gives strong consistency out of the box.

Re: TiDB – cloud-native, distributed SQL database written in Go

#62

Post by std_reply »

sgarland wrote: post #59
std_reply wrote: post #38

Earlier quoted context omitted.

TiDB is running core banking services too. I think people’s idea of scale and operating at scale is limited to their experience. You can get MySQL to run at any scale, look at Meta and Shopify. Operational complexity at that scale is a different story. Distributed databases reduce a lot of the operational complexity. To take one example: Try a DDL on a 5 TB table in any replicated MySQL topology of choice and compare…

> Distributed databases reduce a lot of the operational complexity That’s a new one to me; never have I ever heard someone claim that making a system distributed reduces complexity. I’ve operated EDB’s Distributed Postgres at a decent scale (< 100 TB of unique data); in no way did it enable reduced complexity. For the devs, maybe – “chuck whatever data you want wherever you want, it’ll show up.” But for Ops? Absolute…

EDB Distributed Postgres under the hood is a single node database with bolted on replication.

Re: TiDB – cloud-native, distributed SQL database written in Go

#64

Post by rpaik »

travem wrote: post #19
jitl wrote: post #10

Earlier quoted context omitted.

I hear through the grapevine they’ve got a bunch of companies using it. I think Airbnb migrated to it.

There are quite a few. Pinterest, LinkedIn, Plaid, Mercari, and Rakuten shared their experiences with TiDB at PingCAP's annual event last year (2024) - https://www.pingcap.com/htap-summit/ . In the previous event (2023) there were speakers from Airbnb, Databricks, Flipkart, PayPay, and others sharing their experiences as well - https://www.pingcap.com/htap-summit/sept-2023/ Disclosure: Employee of PingCAP the company…

Not only are these companies using TiDB, they're also contributing to it as you can see in this recent blog post: https://medium.com/@ray.paik/tidb-8-5-is-here-b2ca09e972d5

Re: TiDB – cloud-native, distributed SQL database written in Go

#66

Post by maxloh »

foota wrote: post #60
maxloh wrote: post #53

Earlier quoted context omitted.

Open software licenses are generally non-revokable (unless you violate them). They can only change the license of future versions. I'm afraid that they can always do that with or without a CLA. Apache is quite a permissive license.

I'm not an expert in licenses, but my understanding is that if someone makes a contribution under one license, then any program including that code needs to obey the terms of that license. The CLA allows them to choose any license (well, depending on the specifics of the CLA) they would like to distribute that code under in the future (although they'd likely need to continue to make available past source to meet the…

Apache license doesn't forbid anyone to integrate your code and release the combination under proprietary licenses. The only requirements are to keep the license file and the copyright notice intact, and to state changes if you choose to publish the modified source code.

Therefore, it doesn't make a difference to have a CLA or not. What you trying to avoid is already allowed as per the license.

However, some CLAs require you to declare the originality and ownership of your contributions. Maybe that's why they require a CLA to be signed for contributions.

Re: TiDB – cloud-native, distributed SQL database written in Go

#67

Post by PeterCorless »

sgarland wrote: post #58
PeterCorless wrote: post #48

Earlier quoted context omitted.

If you look at DB-engines.com/ranking and look at all of the collective interest in all of the databases listed, you will see that the aggregate "score" of all databases combined 7105.84. Postgres is indeed popular; but it is only ranked 4th on the list, with its own score of 648.96. MySQL currently is still 50% larger in terms of interest, with a score of 998.15. Which means interest in Postgres (specifically) is on…

While you’re not wrong re: Postgres and MySQL not being necessarily designed for PB-scale, IME many shops with huge datasets are just doing it wrong. Storing numbers as strings, not using lookup tables for low-cardinality data, massive JSON blobs everywhere, etc. I’m not saying it fixes everything, but knowing how a DB works, and applying proper data modeling and normalization could severely reduce the size of many d…

Yes. The chance to do wrong things with data increases with scale.
Post reply on HN