Is this hyperbole, or are you seriously claiming that the Jewish men who run Breitbart, or Jewish founders like Ben Shapiro or Andrew Breitbart, are neo-Nazis?
The issues that I have with Redis are not at all its API (which is elegant and brilliant) or even its serialized, single-core, single-threaded design, but its operational hazards.
As a cache or ephemeral store like a throttling/rate limiting, lookup tables, or perhaps even sessions store, it's great; but it's impossible to rely on the persistence options (RDB, AOF) for production data stores.
You usually only see this tendency with junior devs, though. It might be a case where "when all you have is a hammer, all you see are nails", or when someone discovers Redis (or during the MongoDB hype cycle ten years ago), which seems like it's in perfect alignment with their language datatypes, but perhaps this is mostly because junior devs don't have as many production-ready databases (from SQL like Postgresql, CockroachDB, Yugabyte to New/NoSQL like ScyllaDB, YDB, Aerospike) to fall back on.
Redis shines as a cache for small data values (probably switch to memcache for larger values, which is simpler key-value but generally 3 to 10 times faster for that more narrow use case, although keep an eye on memory fragmentation and slab allocation)
Just think carefully before storing long-term data in it. Maybe don't store your billing database in it :)
> It seems like the thing getting backed up shouldn’t have the privilege of deleting backups in case it gets compromised.
(agreed)
> For backups, I added a nightly cron job which > exports my SQLite db to a write-only S3 bucket.
Why not only do this and use an s3 sync instead? You can safely backup SQLite databases while they're being written to, so no need to export (dump) them; just copy the files themselves.
This might mean that your entire backup/restore strategy is just to copy some files. If so, that's ideal.
(Of course, s3 sync does require reading as well as writing, so perhaps just increase your cron job to run more often so it fits within your RPO)
OLAP questions are usually out-of-band and preferably by a tool designed for it (like Clickhouse). Scanning all DB's is something that can be done in the background for most of these use cases.
What's wrong with that? Of course it will work fine; SQLite, with or without WAL, has a ton of protections against corruption from writes-in-progress, which is what makes hot backups work.
Both sides agree that America has provided at least $100 billion and possibly up to a half-trillion in aid and other consideration to Ukraine. That's a fair bit of money!
And, if Zelenskyy is to be believed, it was a "grant", or a gift, which makes Zelenskyy's disrespectful attitude and hubris in the White House even more outrageous.
Technically, Zelenskyy instituted martial law and cancelled Ukrainian elections, so although he is the undisputed leader in power in Ukraine, he's not an elected president.
Do actual presidents show up in sweatshirts and insult their benefactors?
It doesn't take more than engineers to maintain an open-source browser, though. Why does it have to be a company at all? Remember Firefox? Firefox was literally just an act-of-love fork from some engineers from a dead acquisition by a dying dot-com era behemoth.
Put another way, does the Linux kernel or the Python language need to be run by a company, or will foundations does these jobs ok?
There are plenty of open source projects that are enormously successful without a single lawyer or project manager in sight.
Complete legal arguments as well. If I was an attorney, I'd love to have a sophisticated LLM write my crib notes for anything I might do or say in the court room, or even the complete direction that I'd take my case. For some cases, that'd be worth almost any price.
Yeah, that's an interesting question, because it sounds like a ton of data vs not enough compute, but, aside from this all being in a SAN or large storage array:
The larger Supermicro or Quanta storage servers can easily handle 36 HDD's each, or even more.
So with just 16 of those with 36x24TB disks, that meets the ~14PB capacity mark, leaving 44 remaining nodes for other compute task, load balancing, NVME clusters, etc.