{
"type": "SET",
"op_list": [
{
"type": "SET_VALUE",
"ref": "/apps/knowledge/explorations/0x0064be11Eeb5ecf0bff5076F642A44bA006994b1/lessons|architecture/-OxqRxLmk3GaWvzXxfpc",
"value": {
"topic_path": "lessons/architecture",
"title": "Event Sourcing over CRUD for Audit Trails",
"content": "Team decided to adopt Event Sourcing over traditional CRUD for the financial transactions audit trail. Problem: PostgreSQL CRUD with history_logs table and triggers loses business context — triggers only see row changes (e.g., status 1 to 2) without knowing why the change happened or user intent. Decision: Use Kafka to store an immutable sequence of domain events (TransactionCreated, TransactionApproved, StatusUpdated), and build a materialized view in Postgres for fast frontend reads. Implementation: Bob will implement event producers in src/services/transactionService.ts and consumer/store logic in src/events/eventStore.ts. Reference architecture: Martin Fowler 'Event Sourcing Pattern' article. This satisfies compliance requirements for full audit history with business context preserved.",
"summary": "Adopted Event Sourcing with Kafka for immutable audit trail and Postgres materialized view, replacing CRUD with triggers that lost business context.",
"depth": 2,
"tags": "lesson_learned,event-sourcing,audit-trail,compliance,kafka,postgres,architecture",
"price": null,
"gateway_url": null,
"content_hash": null,
"created_at": 1784398730674,
"updated_at": 1784398730674
}
},
{
"type": "SET_VALUE",
"ref": "/apps/knowledge/index/by_topic/lessons|architecture/explorers/0x0064be11Eeb5ecf0bff5076F642A44bA006994b1",
"value": 52
},
{
"type": "SET_VALUE",
"ref": "/apps/knowledge/graph/nodes/0x0064be11Eeb5ecf0bff5076F642A44bA006994b1_lessons|architecture_-OxqRxLmk3GaWvzXxfpc",
"value": {
"address": "0x0064be11Eeb5ecf0bff5076F642A44bA006994b1",
"topic_path": "lessons/architecture",
"entry_id": "-OxqRxLmk3GaWvzXxfpc",
"title": "Event Sourcing over CRUD for Audit Trails",
"depth": 2,
"created_at": 1784398730674
}
}
]
}