bubbletea VS tidb

I recommend looking at the charm libraries. Lip gloss https://github.com/charmbracelet/lipgloss can provide the styling and bubble tea can handle the screen updates and framework https://github.com/charmbracelet/bubbletea there is a premade progress bar component in bubbles library. https://github.com/charmbracelet/bubbles

I built a TUI app to find anime scenes by image to learn the TUI framework [Bubbletea](https://github.com/charmbracelet/bubbletea)

TUI’s are awesome; I’ve used this library to build them in the past: https://github.com/charmbracelet/bubbletea

For a sufficiently-complex system, a CLI client just isn’t as powerful as a live “console”. A TUI can play the part and you don’t have to venture into the web SPA world.

If you want to build terminal app, I highly recommend the bubbletea library: https://github.com/charmbracelet/bubbletea

You can view your snippets in a human-friendly web UI that syntax-highlights the code and even renders markdown. In addition to the Web UI, the TUI (powered by bubbletea) has a file browser, code viewer and attribute editor.

A sibling comment points at https://github.com/charmbracelet/bubbletea as a Go alternative with a similar architecture

The closest thing in Go I know about is bubbletea:

https://github.com/charmbracelet/bubbletea

tidb has been around for a while, it is distributed, written in Go and Rust, and MySQL compatible. https://github.com/pingcap/tidb

Somewhat relatedly, StarRocks is also MySQL compatible, written in Java and C++, but it's tackling OLAP use-cases. https://github.com/StarRocks/starrocks

It's MySQL-Compatible database for scale and real-time analytics https://github.com/pingcap/tidb

PingCAP | https://www.pingcap.com | Database Engineer, Product Manager, Developer Advocate and more | Remote in California | Full-time

We work on a MySQL compatible distributed database called TiDB https://github.com/pingcap/tidb/ and key-value store called TiKV.

TiDB is written in Go and TiKV is written in Rust.

More roles and locations are available on https://www.pingcap.com/careers/

Pesquise por CockroachDB ou TiDB

OLTP usually comes with high throughput of transactions, which means usually write(e.g., IUD - insert, update, delete) to read (e.g., select) ratio is above 4 or 5 or even higher. There are some good benchmarks to test OLTP workload like TPC-C (https://www.tpc.org/tpcc/), and some benchmarks to test OLAP workload like TPC-H (https://www.tpc.org/tpch/). For mixed or hybrid OLTP and OLAP (it's called HTAP, see this blog for some background https://en.pingcap.com/blog/the-beauty-of-htap-tidb-and-allo...), TPC-H was originally designed for this, however, it actually doesn't reveal the real world workload with several drawbacks. A newer research work from UC Berkeley proposed a HTAP benchmark called TAOBench (https://www.vldb.org/pvldb/vol15/p1965-cheng.pdf) which is pretty interesting and worthy to check.

For the HTAP systems, as mentioned in the above blog, there are quite a few industrial products, like Google just announced AlloyDB (https://cloud.google.com/alloydb), Snowflake's UniStore (https://www.snowflake.com/workloads/unistore/), and one of the most popular open source projects TiDB (https://github.com/pingcap/tidb) which have been deployed by many business applications.

Hopefully these may help a little bit :-)