TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Why it's time to retire CRUD

9 点作者 TheFreim7 个月前

2 条评论

rawgabbit7 个月前
Hmm. Accounting solved this issue several hundred years ago. I wish vendors would catch up to what monks did in the Middle Ages.<p>First, entries are made in an append only journal. When a new month begins, you archived the old one and start a new one.<p>Second, you can have several journals. For example one for each subsidiary.<p>Third, you collect each day’s worth of entries into a consolidated journal.<p>Fourth, from the consolidated journal, you make adjustments to your running totals&#x2F;running balance. However, this ledger is not the source of truth. If there is any dispute, you go back to the journals.<p>What this means is the source of truth is immutable append only (transaction journal). For speedy retrievals of data, you cache the running totals (data ledger) by upserts.<p>To make any corrections, you create a new journal entry that negates the bad one.
评论 #41968257 未加载
评论 #41983668 未加载
评论 #41983836 未加载
mooktakim7 个月前
CRUD doesn&#x27;t mean CRUD all the things. If your use case requires it, you can build a create-only environment where you never delete anything.