Remove non-working links #11844
Remove non-working links #11844
Conversation
There was no replacement links after contacting the blog author. Closes #11705
|
There are two other topics linking to that site: https://github.com/dotnet/docs/search?utf8=%E2%9C%93&q=codebetter&type= Do you wanna tackle them on the same PR? |
|
Done @mairaw! |
| CQS is a simple concept—it is about methods within the same object being either queries or commands. Each method either returns state or mutates state, but not both. Even a single repository pattern object can comply with CQS. CQS can be considered a foundational principle for CQRS. | ||
|
|
||
| [Command and Query Responsibility Segregation (CQRS)](https://martinfowler.com/bliki/CQRS.html) was introduced by Greg Young and strongly promoted by Udi Dahan and others. It is based on the CQS principle, although it is more detailed. It can be considered a pattern based on commands and events plus optionally on asynchronous messages. In many cases, CQRS is related to more advanced scenarios, like having a different physical database for reads (queries) than for writes (updates). Moreover, a more evolved CQRS system might implement [Event-Sourcing (ES)](http://codebetter.com/gregyoung/2010/02/20/why-use-event-sourcing/) for your updates database, so you would only store events in the domain model instead of storing the current-state data. However, this is not the approach used in this guide; we are using the simplest CQRS approach, which consists of just separating the queries from the commands. | ||
| [Command and Query Responsibility Segregation (CQRS)](https://martinfowler.com/bliki/CQRS.html) was introduced by Greg Young and strongly promoted by Udi Dahan and others. It is based on the CQS principle, although it is more detailed. It can be considered a pattern based on commands and events plus optionally on asynchronous messages. In many cases, CQRS is related to more advanced scenarios, like having a different physical database for reads (queries) than for writes (updates). Moreover, a more evolved CQRS system might implement [Event-Sourcing (ES) (page 25)](https://cqrs.files.wordpress.com/2010/11/cqrs_documents.pdf#page=25) for your updates database, so you would only store events in the domain model instead of storing the current-state data. However, this is not the approach used in this guide; we are using the simplest CQRS approach, which consists of just separating the queries from the commands. |
There was a problem hiding this comment.
This link doesn't seem very applicable. Isn't there something more approachable we can link to?
Perhaps https://martinfowler.com/eaaDev/EventSourcing.html?
There was a problem hiding this comment.
Yep, will update as per your suggestion.
|
|
||
| ## Additional resources | ||
|
|
||
| - **Greg Young. Versioning in an Event Sourced System** (Free online e-book) \ |
There was a problem hiding this comment.
I see a minimum price of $5? I don't think we should be linking to paid resources,
There was a problem hiding this comment.
The book is free to read online, anyway I checked with @CESARDELATORRE first.
Perhaps changing it to "Free to read online e-book"?
There was a problem hiding this comment.
It's easy to miss that. How about you keep the Free online e-book but link to https://leanpub.com/esversioning/read instead?
There was a problem hiding this comment.
Yep, certainly much better 😊
|
No worries 😊 |
Summary
There was no replacement links after contacting the blog author.
Closes #11705