كلكم سمعتوا عن المسألة الر��اضية اللي حلها ChatGPT لكن اكثركم ما فهمتوها
قسم بالله انجاز عظيم ومرعب !
تخيلوا Open AI سووا جيش 10 الاف عالم رياضيات AI وسولفوا بين بعض 130 مليار كلمة خلال 88 ساعة لين حلوها
صورت الان فيديو شرحت المسألة واوعدك تفهمها لو ما معك الا سادس
Here's how I implement CQRS in my applications.
The CQRS pattern is actually simple.
I organize my application around use cases.
Use cases represent a feature (functionality) in your application:
- Get the current user's details
- Add an item to the shopping cart
- Refund the payment for an order
So you can think of a use case as a business capability.
I structure my code around a single use case (feature).
There are two types of use cases:
- Commands → business logic, database write, trigger side effects
- Queries → return the required data representation for the UI
If you think it should be more complex than this, you're overengineering it.
What do you think about applying CQRS?
P.S. No - you don't need event sourcing or a separate database.