I wonder why the author views CQRS negatively and then later gives this classic CQRS advice:

      >What this means in practice is having one service that knows about the state - i.e. it talks to a database - and other services that do stateless things. Avoid having five different services all write to the same table. Instead, have four of them send API requests (or emit events) to the first service, and keep the writing logic in that one service.

Because you dont need CQRS to achieve that.

i also found the cqrs shade to be peculiar