west0n

but when the VPS fails, you lost all your data

If you want to run a database on VPS with ssd disk, you'll need at least two replicas for data redundancy, which would cost about $10.

I'm curious about how rqlite's performance compares to other distributed databases developed in Go, such as CockroachDB, Vitess, and TiDB.

If we didn't have abstractions like POSIX, applications would need to write an adaptor for every supported file system.

We have developed a control plane software that can run&manage multiple databases on K8s. I believe that in the public cloud, this business is already "Hair on Fire", as every cloud provider offers their own managed services for databases like MySQL, PostgreSQL, etc. However, in on-premise environments, this is "Hard Fact", because convincing users/customers requires acceptance of two facts:

- The future trend is to run databases on K8s. - Using a unified control plane software for all kinds of databases you use, rather than different control planes for each type of database, which would lead to a high learning curve to the Ops/SRE.

It's encouraging that we have already found some on-premise users who buy in our concept, and we hope to convince more people.

As the founder and CEO of a two-year-old startup, seeking certainty in the direction amidst uncertainty (determining which products can bring customers and profits) should become my instinct.

Interesting, another project implemented in Go that is compatible with MySQL server, alongside others like Vitess and TiDB.

See some development frameworks for local-first apps support both SQLite and PostgreSQL. The advantage of using PostgreSQL is that when you add a cloud option to your local-first app, the migration becomes much easier.

I bet that all message queues and log databases will support S3, as these types of data generally have a large volume and aren't as economically valuable (don't get me wrong, what I mean is that these databases won't be frequently read and processed).

Here is our approach: From Markdown to a Docusaurus Website via GitHub, gh Actions, and gh pages

https://baky0905.github.io/personal-website/blog/2021/04/02/...

Looks like microVM.

Why not use containers, they even shares the kernel.

Adding support for LLM Agent scheduling, context switching, and storage management within the operating system kernel.

I think the codebase of Redis is too small, which makes the cost of maintaining a Redis fork relatively low. Moreover, Redis was forked too late. This puts Redis Inc. at a disadvantage in the battle against cloud vendors.

so I leaved Rails, lol

this is so called "Materialized View"

In our production environment, we use XFS to run various databases, including MySQL, PostgreSQL, MongoDB, etc. It delivers performance that is either superior to or on par with ext4.

I'm interested to see if there're some ZFS users.

lesson: DONOT join more than 3 tables in MySQL, lol