HN user
Typically a separate archive database is not desired choice. You need to specify the rule how old the data is move from production database to archive database. Also the archive database is read only and slow, you can not achieve transaction between production database and archive database.
There is a discussion on Reddit for a 5TB data volume but very low throughput, I think Object Storage based document database would help in this case. https://www.reddit.com/r/mongodb/comments/1o41dta/is_there_a...
Is DuckLake compatible with Iceberg? I remember they create a new catalog.
Yes, we found it to be very useful for things that require durability and transactions. Previously we use JuiceFS community edition with Redis as metadata backend. The main issues are 1) potential metadata loss and 2) Memory capacity limit. We tried EloqKV and it seems to work really well. Anybody use EloqKV in production yet?
Poorest workers are hit hardest by pretty much anything related to money.
All existing programming languages are designed for human beings. Is it the right time to design something that is specifically for vibe coding? For example, ease of read/understanding is probably much more important than all the syntactic sugars to reduce typing. Creating ten ways to accomplish the same task is not useful for LLMs.
In the age of LLM powered coding copilots and agents, do programming skills still matter? Shall we focus more on design and algorithmic thinking instead? Computer science != programming, now more true than ever.