Week 8, year 2019

When to validate commands in CQRS? - There’s a question that I didn’t cover in the course and that was raised at least twice since then: when to validate commands in CQRS? [Enterprise Craftsmanship]

Permalink | From 18 February 2019 to 24 February 2019 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT

Week 6, year 2019

We are switching to a new login provider - We will soon switch to a new login provider hosted on Amazon AWS/Frankfurt [Serialized development blog]

Permalink | From 04 February 2019 to 10 February 2019 | Last updated on: Mon, 7 Jun 2021 09:09:29 GMT

Are CQRS commands part of the domain model? - I published an online course about CQRS a couple months ago, and since then I realized that there are some topics I didn’t put enough emphasize on in that course, or didn’t cover at all. In the next several blog posts, I’m going to fill this gap. [Enterprise Craftsmanship]

Permalink | From 28 January 2019 to 03 February 2019 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT

CQRS replay performance tuning - Command Query Responsibility Separation (CQRS) has become a popular pattern to avoid complex, and therefore slow, database queries in applications. With CQRS, queries are served from dedicated read models that are optimized for the query’s specific needs. This ensures that queries are as simple as possible, and therefore as fast as possible. The read models need to be initialized and kept up to date with the primary storage (the command side). This is done most easily if the primary storage is event-based: the Event Sourcing (ES) concept. Axon offers a mature and popular implementation of the CQRS/ES concepts on the JVM, but several other implementations exist. [Axon Framework and related blogs via Aggregater Linklog]

Permalink | From 07 January 2019 to 13 January 2019 | Last updated on: Thu, 22 Jul 2021 06:56:20 GMT

Hierarchy of value objects - This article is a response to a reader’s question. The question posed an interesting problem that I think will be interesting to a wider audience. [Enterprise Craftsmanship]

Permalink | From 24 December 2018 to 30 December 2018 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT

DDD Weekly: Issue #57 - ThoughtWorks Technology Radar: Event Storming [blog] ThoughtWorks. When organizations move toward microservices, one of the main drivers is the hope for faster time to market. However, this aspiration only tends to be realized when services (and their supporting teams) are cleanly sliced along long-lived business domain boundaries. Otherwise meaningful features will naturally require tight coordination between multiple teams and services, introducing natural friction in competing roadmap prioritization. The solution to this problem is good domain modeling, and event storming has rapidly become one of our favorite methods for rapidly identifying the key concepts in a problem space and aligning a variety of stakeholders in the best way to slice potential solutions. [DDD Weekly]

Permalink | From 17 December 2018 to 23 December 2018 | Last updated on: Mon, 7 Jun 2021 09:10:49 GMT

Datomic: Event Sourcing without the hassle - In this article, we'll describe briefly what Event Sourcing is, how it's conventionally implemented, analyze the limitations of that, and contrast that with how Datomic enables you to achieve the same benefits. We'll see that, for most use cases, Datomic enables us to implement Event Sourcing with much less effort, and (more importantly) with more agility. [Val on Programming via Aggregater Linklog]

Permalink | From 12 November 2018 to 18 November 2018 | Last updated on: Fri, 28 Apr 2023 17:40:48 GMT