but when the VPS fails, you lost all your data
HN user
west0n
A database & K8s engineer
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.
This analysis is very insightful.
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
TLTR:
Understand and optimize relational databases (MySQL, PG) rather than introducing a new type of database (e.g., DynamoDB, Kafka, Redis) whenever issues arise. Common mistakes:
- Lack of indexes
- Using ORM (generating too many SQL queries or inefficient queries that return all columns)
Some suggestions:
- Use relational databases where possible, instead of NoSQL
- Use read-only replicas instead of Redis when applicable
- Keep relational databases clean and data size small
The author's message is: Hey, folks, if you don't have the ability to use relational databases properly, then your usage of Kafka and DynamoDB will certainly be a mess as well.
The Reason Behind "Why Amazon forces its developers to write press releases"
https://www.businessinsider.com/heres-the-surprising-way-ama...
Recently, I learned that PostgreSQL can integrate with many languages through plugins, such as PL/Python, pgrx (Rust), pgzx (Zig), and so on. I wonder if anyone is planning to write one for Java or C#, lol.
It seems that to counter this type of supply chain attack, the best practices for managing software dependencies are to pin the version numbers of dependencies instead of using `latest`, and to use static linking instead of dynamic linking.
According to this paper, GPU4FS is a file system that can run on the GPU and be accessed by applications. Since GPUs cannot make system calls, GPU4FS uses shared video memory (VRAM) and a parallel queue implementation. Applications running on the GPU can utilize GPU4FS after modifying their code, eliminating the need for a CPU-side file system when accessing the file system. The experiments are done on Optane memory.
It would be interesting to know if this approach could optimize the performance of training and inference for large models.
PostgreSQL is a very unique community compared to other database community(MySQL, Redis, MongoDB, ClickHouse et.c). It is INDEED decentralized, which means NO single company control it. This is related to the style of PostgreSQL's primary maintainers and leaders, who have ensured that the project's decisions and direction are determined collectively by the community members, rather than being controlled by a single company. Hopefully, their departure will not change this aspect.
Neal Gompa opened a discussion on the Fedora development list, noting the license change and the need to remove Redis from Fedora.
Gompa also raised the issue on openSUSE's Factory discussion list.
After Docker was phased out, various distributions have adopted the compatible Podman as a replacement for Docker. It seems that a similar story is unfolding with Redis.
You may try kubeblocks(kubeblocks.io), a database control plane that can run almost any database on K8s.
If you see following error logs,
$ pueue Error: Couldn't find a configuration file. Did you start the daemon yet?
Run `pueued -d` first. I think this prompt should be printed on the screen the first time it runs, or automatically executed.
From this blog(https://engineering.mercari.com/en/blog/entry/20240206-3a12b...), it appears that Tortoise provides a feature that I think could be called managed HPV. It offers a way for administrators to configure and manage complex HPV policies while requiring minimal configuration from application developers (i.e., the users of HPV). BTW, I have a pet turtle and really like the pictures in the documentation.
This incident reflects the increasing profit pressure on Redis Inc. Furthermore, Redis' competitive edge in performance is declining, especially with the emergence of alternatives like Dragonfly and Garnet (disscussed here https://news.ycombinator.com/item?id=39752504).
I know that some companies are developing AI-based interview products. In a video conference, the AI asks questions and then evaluates the candidate's answers, giving a score. This can save a lot of time for the interviewer. Such a world is quite scary.