Have been watching this site for a while. Even more interesting is natural language to search and get answer right away! Check it out here. https://twitter.com/OSSInsight/status/1601253589615271938?s=...

What exactly is the scoring behind?

I think the author meant a bit different with Apps, that can process complex transaction with high availability only it a match database is chosen.

Found this really cool tool! https://ossinsight.io/collections/static-site-generator/tren...

I think the major point of this article is for engineers to focus on innovation for business, rather than optimizing infra to support app new trial. Then a scalable and agile stack is critical for choice.

If you're always focused on just building new shit instead of maintaining the stuff you build, then you will always be building nothing but shit.

Try doing nothing but building new toilets without ever understanding how they work in the real world, and without learning any lessons about how they work at scale.

There has got to be a good balance. Without that, you are lost, as is everyone else that is involved in that project.

We do a lot of Rust compilation exploration during the development of TiKV(github.com/tikv/tikv), a lot of interesting learnings ... https://en.pingcap.com/blog/rust-huge-compilation-units/

thanks for maintaining jemalloc :)

A relational database scalable for the billing data volume, should be a best answer, in term of realtime process and analysis，say complex query. Suggest an article of a big logistics company case here, not only billing, but also order, messaging, transshipment: https://en.pingcap.com/blog/how-to-reduce-cost-per-order-wit...

Another comparison maybe interesting too Comparing ARM based K8s to x86 based for TiDB (a distributed database) https://en.pingcap.com/blog/tidb-on-arm-based-k8s-cluster-ac...