To design our modules, classes and functions in a way that when a new functionality is needed, we should not modify our existing code but rather write new code that will be used by existing code.
http://net.tutsplus.com/tutorials/php/solid-part-2-the-openclosed-principle
http://net.tutsplus.com/tutorials/php/solid-part-1-the-single-responsibility-principle/
Class and module design is highly affected by The Single Responsibility Principle and leads to a low coupled design with less and lighter dependencies. But as any coin, it has two faces. Excessive SRP consideration can easily lead to premature optimization and instead of a better design, it may lead to a scattered one where the clear responsibilities of classes or modules may be hard to understand
Class and module design is highly affected by The Single Responsibility Principle and leads to a low coupled design with less and lighter dependencies. But as any coin, it has two faces. Excessive SRP consideration can easily lead to premature optimization and instead of a better design, it may lead to a scattered one where the clear responsibilities of classes or modules may be hard to understand
Category : architecture
http://www.codeproject.com/Articles/555855/Introduction-to-CQRS
CQRS (Command Query Responsibility Segregation, http://martinfowler.com/bliki/CQRS.html) is a technique that separates data creation and modification from data querying. In a pure CQRS model a stored procedure would not both insert/update data and then retrieve data. Those are two distinct operations, and therefore separated.
Ok, I’ll do want to acknowledge that CQRS can complicate your application infrastructure, and that it does not make sense to use this pattern in any and every application you ever build. This is a pattern you would use when you have requirements for Resilience or massive scale.
http://www.sswug.org/editorials/readed.aspx?id=3004
CQRS (Command Query Responsibility Segregation, http://martinfowler.com/bliki/CQRS.html) is a technique that separates data creation and modification from data querying. In a pure CQRS model a stored procedure would not both insert/update data and then retrieve data. Those are two distinct operations, and therefore separated.
Ok, I’ll do want to acknowledge that CQRS can complicate your application infrastructure, and that it does not make sense to use this pattern in any and every application you ever build. This is a pattern you would use when you have requirements for Resilience or massive scale.
http://www.sswug.org/editorials/readed.aspx?id=3004
Subscribe to:
Posts (Atom)