Hi,
I have a few open queries in my mind on architectural styles.
I have just put them as questions below. Can someone advise
1. What is an Architectural Style and What purpose does it solve
2. When do we use architectural styles (i.e at what phase of a project)
3. What are the different architecture style
Some of them that I am aware of are Layered, OO, Client Server, RPC, Structured.
4. How can one add a style Is style a pattern
5. How do we select a style during architectural design
6. Can more than one style be mixed and if yes are there suitable partners for a style
Thanks,
Prasanth
Architectural Styles
Hot Topic
- What about making domain specific "Enterprise Library" ?
- Contract first - what tools do you recommend?
- Version Checking & upgrading in XP
- WCF and WinFS
- windows scheduler - who gets the CPU?
- the best orm for .net?
- Software Development Processs Question
- SOA and supporting products
- Deleting Hotmail Contacts
- General business object requirements
Architecture
- OO design question.
- Database Design based on Service Oriented Architecture.
- Layered Architecture across Boundaries
- finding design patterns from Model or P.E file
- Architecting a System is a Thought Process or Practice or Combination of both of these or others too
- Guidance Needed on User Interface Process Application Block (UIPAB) - Starting a Open Navigation Task
- Prerequisite Knowledge - to be an Architect
- Software architecture... I'm stuck!
- Restrictive Development- Propagating Architectural Patterns
- Architecting a System is a Thought Process or Practice or Combination of both of these or others too
Architectural Styles
Dietmar Gleu
An Architecture style can be thought of as a family of related architectures or a pattern at the architecture level
An Architectural style is basically a set of
If a style is documented it will probably have additional ingredients (like variations, examples, pros, cons etc.).
Architecture styles are used in a similar fashion to design patterns both as a common vocabulary and as design elements
To answer question 6 - yes styles can be mixed for example REST (Representational State Transfer) is a derived style mixing styles like Client-server and layered you've mentioned with constraints like use of uniform interface and stateless server.
There are many architecture styles - few notable ones (in addition to the ones you've mentioned) include pipes and filters, blackboard, hub and spoke, interpreter, MVC, Master-Slave and many many others.
Regarding question 5 - you would choose a style the same way you do any other architectural decision by weighing benefits and costs and evaluating tradeoffs - you can read a few post I've recently wrote on architecture evaluation:SAF - Architecture Evaluation (Introduction) , SAF - Architecture Evaluation - Evaluation in Code and SAF - Evaluation part II - the "Formal Methods" Also here's a link to an older post I made on Modeling - Architectural Styles
HTH,
Arnon