We had a look at some pattern books during this lecture, this was just to get an idea of the number of patterns available or rather documented. I had no idea that therewere just a vast amount, too much to through individually during the lecture.
Our lecturer decided we should go through as many books as possible and looking up patterns or information stands out to us. I went through about 3 books at detail and discovered the following abouyt them.
The Pattern Almanac 2000 by Linda Rising
This book can be considered a s a reference to all widely published patterns and patter collections. It includes a comprensive index of patterns, pattern collections, authors and citations.
Enterprise Solution Patterns using Microsoft .NET
I found this book more interesting, this was probably due to the fact that I had no idea that they were patterns for deployment of any application, imagine my surprise to learn that there was were patterns for deployment on an Enterprise scale. This book had collection of patterns for web presentation, deployment, distributed systems, services, performance and reliability. The pattern i focused on were the deployment patterns.
I reading up the Layered Application pattern I discovered how to structure an application to support operational requirements such as scalability and reusability. This gave me an idea on how I could apply this in m y final year dissertation.
Pattern Hatching by John Vlissides
This book suggested discusses what is a pattern and why people get confused when labelling a pattern. A pattern must be recurrence (making solution relevant outside the immediate one), teaching (understanding to tailor the solution to a variant of the problem) and named. According to Vlissides, a popular misconception is that patterns are rules (programming tricks) that could be applied mindlessly. This is should not the case at all.
No comments:
Post a Comment