{"id":6745,"date":"2026-06-29T18:45:50","date_gmt":"2026-06-29T15:45:50","guid":{"rendered":"https:\/\/publish.kpi.ua\/?p=6745"},"modified":"2026-06-12T00:31:33","modified_gmt":"2026-06-11T21:31:33","slug":"engineering-of-software-systems-based-on-snapshot-centric-cqrs-with-event-sourcing-architecture","status":"publish","type":"post","link":"https:\/\/publish.kpi.ua\/en\/engineering-of-software-systems-based-on-snapshot-centric-cqrs-with-event-sourcing-architecture\/","title":{"rendered":"Engineering of software systems based on snapshot-centric CQRS with event sourcing architecture"},"content":{"rendered":"

This article introduces “mCQRS,” an optimized variation of the Command Query Responsibility Segregation (CQRS) with Event Sourcing architecture. The proposed approach significantly reduces development and maintenance complexity by utilizing aggregate state snapshots in a relational database as the single source of truth.<\/span><\/p>\n

Command Query Responsibility Segregation (CQRS) combined with Event Sourcing (ES) is a widely adopted standard for designing highly scalable and performant information systems. However, implementing the classical variation of this architecture presents a significant challenge: it is notoriously associated with high development and maintenance complexity. Managing these intricate components requires an advanced level of developer expertise and drives up operational costs. Therefore, finding an alternative that balances architectural benefits with manageable complexity is highly relevant for modern software engineering teams.<\/span><\/p>\n

To address this issue, the researchers conducted a thorough analysis of the classical CQRS architecture to identify the specific components that inflate system complexity. Based on these findings, they proposed an alternative variation\u2014dubbed “mCQRS”\u2014which utilizes a simplified component set. The core innovation of this method relies on using a relational database where aggregate state snapshots are treated as the absolute source of truth. This strategic design choice fundamentally reduces implementation hurdles and facilitates smoother future migrations to other architectural patterns.<\/span><\/p>\n

The researchers validated their approach by developing representative test projects for both architectural variations. The results revealed that mCQRS achieved a remarkable 31.67% decrease in cyclomatic complexity for typical command workflows (dropping from a score of 120 to 82). While server query response times remained identical at 44 ms for both models, the end-to-end consistency time for commands experienced a 22.76% degradation in mCQRS (347 ms compared to 268 ms). Despite this slight drop in write performance, the overall throughput remains robust and fully aligns with established industry standards.<\/span><\/p>\n

In conclusion, the proposed mCQRS architecture successfully enhances development and maintenance efficiency while significantly lowering the required threshold for developer expertise. This optimized variation serves as an excellent, cost-effective solution for scalable systems where absolute write-operation performance is not the ultimate critical priority.\u00a0<\/span><\/p>\n

https:\/\/scinews.kpi.ua\/article\/view\/350992<\/span><\/a><\/p>\n

https:\/\/scinews.kpi.ua\/article\/view\/350992\/341782<\/span><\/a><\/p>\n

DOI: https:\/\/doi.org\/10.20535\/kpisn.2026.1.350992 <\/a><\/span><\/p>","protected":false},"excerpt":{"rendered":"

This article introduces “mCQRS,” an optimized variation of the Command Query Responsibility Segregation (CQRS) with Event Sourcing architecture. The proposed approach significantly reduces development and maintenance complexity by utilizing aggregate…<\/p>","protected":false},"author":7,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[130,123,120,124,141,139,160,131,140,155,156,157,158,165,132,143,122],"tags":[206,207,205,204],"class_list":["post-6745","post","type-post","status-publish","format-standard","category-spetsialnist-113","category-spetsialnist-121","category-spetsialnist-122","category-spetsialnist-123","category-spetsialnist-124","category-spetsialnist-131","category-spetsialnist-132","category-spetsialnist-133","category-spetsialnist-134","category-spetsialnist-141","category-spetsialnist-142","category-spetsialnist-143","category-spetsialnist-144","category-151-avtomatyzatsiya-ta-kompyuterno-intehrovani-tekhnolohiyi","category-spetsialnist-161","category-spetsialnist-171","category-spetsialnist-172","tag-cqrs","tag-event-sourcing-comparative-analysis","tag-optimisation-models","tag-software-architecture"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t