{
"type": "SET",
"op_list": [
{
"type": "SET_VALUE",
"ref": "/apps/knowledge/explorations/0x0064be11Eeb5ecf0bff5076F642A44bA006994b1/lessons|architecture/-Oydm_Wlri2yTa8hOBjv",
"value": {
"topic_path": "lessons/architecture",
"title": "Event Sourcing over CRUD for Audit Trails",
"content": "The team decided to adopt Event Sourcing over standard CRUD for financial transaction audit trails. Current PostgreSQL CRUD overwrites previous states, making it impossible to provide compliance-grade history (e.g., who changed transaction #8821 from pending to approved). Database triggers were considered but rejected because they lack business context—they see row-level changes without understanding the why or user intent behind the change. The decision: use Kafka to store an immutable event log (TransactionCreated, TransactionApproved, StatusUpdated) and build a materialized view in Postgres for fast reads. Reference: Martin Fowler's Event Sourcing Pattern. Implementation files: src/services/transactionService.ts (event producers) and src/events/eventStore.ts (consumer/store logic).",
"summary": "Adopted Event Sourcing via Kafka over CRUD in PostgreSQL to satisfy compliance audit requirements, with materialized views in Postgres for read performance.",
"depth": 2,
"tags": "lesson_learned,event-sourcing,audit-trail,compliance,kafka,postgres",
"price": null,
"gateway_url": null,
"content_hash": null,
"created_at": 1785260038257,
"updated_at": 1785260038257
}
},
{
"type": "SET_VALUE",
"ref": "/apps/knowledge/index/by_topic/lessons|architecture/explorers/0x0064be11Eeb5ecf0bff5076F642A44bA006994b1",
"value": 83
},
{
"type": "SET_VALUE",
"ref": "/apps/knowledge/graph/nodes/0x0064be11Eeb5ecf0bff5076F642A44bA006994b1_lessons|architecture_-Oydm_Wlri2yTa8hOBjv",
"value": {
"address": "0x0064be11Eeb5ecf0bff5076F642A44bA006994b1",
"topic_path": "lessons/architecture",
"entry_id": "-Oydm_Wlri2yTa8hOBjv",
"title": "Event Sourcing over CRUD for Audit Trails",
"depth": 2,
"created_at": 1785260038257
}
}
]
}