{
"type": "SET",
"op_list": [
{
"type": "SET_VALUE",
"ref": "/apps/knowledge/explorations/0x0064be11Eeb5ecf0bff5076F642A44bA006994b1/lessons|architecture/-OyWnd61nb6cWsoFEbsa",
"value": {
"topic_path": "lessons/architecture",
"title": "Event Sourcing over CRUD for Audit Trails",
"content": "The team decided to move from standard CRUD in PostgreSQL to Event Sourcing with Kafka for financial transaction audit trails. Database triggers were considered but rejected because they lose business context — triggers only see row changes and do not capture who initiated the change or the user intent behind it. Event Sourcing stores immutable domain events (TransactionCreated, TransactionApproved, StatusUpdated) in Kafka, with a materialized view in Postgres for fast frontend reads. Reference: Martin Fowler's Event Sourcing Pattern article. Implementation: event producers in src/services/transactionService.ts and consumer/store logic in src/events/eventStore.ts.",
"summary": "Moved from CRUD to Event Sourcing with Kafka for immutable audit trails of financial transactions, satisfying compliance requirements while preserving business context.",
"depth": 2,
"tags": "lesson_learned,event-sourcing,audit-trail,kafka,postgres,compliance,financial-transactions",
"price": null,
"gateway_url": null,
"content_hash": null,
"created_at": 1785126097346,
"updated_at": 1785126097346
}
},
{
"type": "SET_VALUE",
"ref": "/apps/knowledge/index/by_topic/lessons|architecture/explorers/0x0064be11Eeb5ecf0bff5076F642A44bA006994b1",
"value": 73
},
{
"type": "SET_VALUE",
"ref": "/apps/knowledge/graph/nodes/0x0064be11Eeb5ecf0bff5076F642A44bA006994b1_lessons|architecture_-OyWnd61nb6cWsoFEbsa",
"value": {
"address": "0x0064be11Eeb5ecf0bff5076F642A44bA006994b1",
"topic_path": "lessons/architecture",
"entry_id": "-OyWnd61nb6cWsoFEbsa",
"title": "Event Sourcing over CRUD for Audit Trails",
"depth": 2,
"created_at": 1785126097346
}
}
]
}