sighansen

I have no use case where I store a TB of data in a sqlite let alone few GB. Currently this checks out and restore is few seconds.

I use the same stack to run my apps! sqlite as Database backen on ephemeral pods. On initialisation, the pod restores the current litestream backup from object storage. No persistent volumes needed. No issues so far.

I wonder if stuff like this will also be created when token costs explode.

The only ISP I have access to is Deutsche Telekom and I often have problems with websites loading slowly. A few more years before other ISPs can provide internet in my new development area. I can't understand, why they are allowed to have a monopoly in some areas.

Looks interesting. I'm interested in the T-Deck Tulip CC and would love to use it for coding whilst im traveling. Any experience with using such a device for light programming?

Really interesting. I wonder if something good will come out of it. It feels like twitch plays pomemon.

Really love litestream. Easy to use and never crashes on me. I still recommend using it as a systemd unit service. I'm not only using it as a backup tool but also to mirror databases. Looking forward to their read-replica feature.

As long as iceberg and delta lake won't support v2, adoption will be really hard. I'm working aot with parquet and wasn't even aware that there is a version 2.0.

I don't understand why you wouldn't just use plain s3. There is no comparison in the readme and I would love to understand what the benefits are. Also I would have expected a comparison to maybe Apache Iceberg, but this might be more specialized for relational data lake data?

That is just plain untrue. They deport criminal migrants or migrants that are not under international asylum law. And we are talking about few thousands per year.

This looks really helpful! I'm working a lot on graph databases and am wondering, if there are similar projects working with say neo4j. I guess because you don't have a schema, the complexity goes up.

The commit messages are terrible. In my opinion, conventional commit messages [0] should be used for a clean commit history.

[0] https://www.conventionalcommits.org/en/v1.0.0/

Are your transformations written in SQL?

We just ditched slack in favour of teams at our company, because slack wasn't "secure" enough. I feel like I see a headline like this twice a month. I can't ever remember seeing a similar headline for slack.