kyhsa93 / nestjs-rest-cqrs-example Goto Github PK

I noticed a lot of repetition (maybe this is just a cqrs thing), and I can understand that some is justified, but for example closedAt is defined 14 times across different objects/types https://github.com/kyhsa93/nestjs-rest-cqrs-example/search?q=closedAt

So my question is this, can you think of any way to dry up your CQRS pattern?

Thanks

Hi,
Thanks for your work, I achieved to launch it quickly.
However I don't understand how it works :

• the both databases (redis and mysql) have the same data stored in them.
• I don't see any event store where each event is stored to be able to come back in the past

@kyhsa93 could you help me to understand your work please?

Hello,

I'm sorry, I am studying about DDD and CQRS.

I have to ask you: Why are you persisting database after send event?

https://github.com/kyhsa93/nestjs-rest-cqrs-example/blob/master/src/account/application/command/handlers/open.account.ts

Will the event get dispatched if the database save fails?

Should we call the "await this.accountRepository.save(account);" before calling the "account.commit();"?

Thank you!

i was trying to deploy this to kubernetes but the yaml files are missing?

Can not install and run
Then install follow your Guild it's not run. Table is not exist.
I think need have automation create Schema.
Thank you!