K. Tsang wrote:
Ludwin Barbin wrote:
The design principles are explained in a concise manner with visuals, analogies, real-world examples to help strengthen the concept.
About the visuals, is there a separate PDF or file similar to SOA principles/patterns here
K. Tsang wrote:Thanks Ludwin.
About the e-book it's 50 pages yet on Amazon it says estimated 72 pages. Not sure if it's refer to the Kindle edition.
K. Tsang wrote:Welcome to the Ranch Ludwin.
Your book looks like a great reference for any architect and developer. I want to know if the book mentions examples when to use (or more importantly not to use) each design principle.
Also will applying one principle affect or break the outcome of another principle? Such interrelationship or dependency should be invaluable.
Thanks.
E Armitage wrote:Design principles are the desirable goals that one aims to achieve. Design patterns are tools one can use to realize those goals.
It's therefore better to learn design principles first because then you can easily understand what (and why) a pattern is trying to achieve.
Campbell Ritchie wrote:Would the book be suitable for an introduction, for experienced students, etc?
Campbell Ritchie wrote:By lower‑level, do you mean that design patterns have a finer granularity than principles?