Michael Keeling and I recorded a discussion about architectural styles (like pipe and filter, client server) compared to architectural patterns. Not to spoil the surprise, but we ended up mostly agreeing that it's good to think of the style as providing the vocabulary of elements (clients, servers, ...) and the patterns as providing conventional arrangements (ie patterns) of those elements. We recorded this last year and I just discovered that we never posted it!
This really helped put into context why I have been feeling like so many things in my software architecture course seem like the same thing but with a different definition. I am quite a black-and-white thinker which has not served me well in learning these concepts, but your conversation managed to explain it in a way that made sense. Thank you for posting!
Pretty good, thanks for the explanation it is very useful. I was searching for several websites and finally this video explained it very well. Thanks again!
Oh boy, Representational State Transfer (REST) is something that everyone can disagree about. I can't think of a simple answer to your question. I would recommend reading Roy Fielding's thesis on REST to learn more. www.ics.uci.edu/~fielding/pubs/dissertation/top.htm
