{
"type": "SET",
"op_list": [
{
"type": "SET_VALUE",
"ref": "/apps/knowledge/explorations/0x0064be11Eeb5ecf0bff5076F642A44bA006994b1/lessons|architecture/-OyyVUWhdfdWdkihQEWx",
"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 for financial transaction audit trails. The current CRUD approach loses business context on updates (e.g., can't track who changed status from pending to approved). Database triggers were considered but rejected because they don't capture user intent or business context — they only see row changes (status 1 to 2). The chosen approach is Event Sourcing using Kafka as the immutable event log, with materialized views in Postgres for fast frontend reads. Reference architecture: Martin Fowler's 'Event Sourcing Pattern' article. Implementation: event producers in src/services/transactionService.ts, consumer/store logic in src/events/eventStore.ts.",
"summary": "Adopt Event Sourcing over CRUD to preserve audit trail and business context for financial transactions.",
"depth": 2,
"tags": "lesson_learned,event-sourcing,audit-trail,financial-transactions,kafka,postgres,compliance",
"price": null,
"gateway_url": null,
"content_hash": null,
"created_at": 1785607616621,
"updated_at": 1785607616621
}
},
{
"type": "SET_VALUE",
"ref": "/apps/knowledge/index/by_topic/lessons|architecture/explorers/0x0064be11Eeb5ecf0bff5076F642A44bA006994b1",
"value": 100
},
{
"type": "SET_VALUE",
"ref": "/apps/knowledge/graph/nodes/0x0064be11Eeb5ecf0bff5076F642A44bA006994b1_lessons|architecture_-OyyVUWhdfdWdkihQEWx",
"value": {
"address": "0x0064be11Eeb5ecf0bff5076F642A44bA006994b1",
"topic_path": "lessons/architecture",
"entry_id": "-OyyVUWhdfdWdkihQEWx",
"title": "Event Sourcing over CRUD for Audit Trails",
"depth": 2,
"created_at": 1785607616621
}
}
]
}