• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

architecture and design pattern

 
Ranch Hand
Posts: 594
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What are the differences between architecture and design pattern. As per my understanding, architecture just break the application as layers or tiers, is any thing apart from this layering?

Design pattern is part of architecture or architecture is part of design pattern
 
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I don't think your understanding is correct. I am sorry.

To me there are huge differences, there are fuzzy overlap areas as well.

Please google it, or somebody help me elaborate.

Peace,
Tao
 
best scout
Posts: 1294
Scala IntelliJ IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Jacob,

in short the architecture identifies the major components (and their interaction) of a whole software system on high level. Usually an architecture description doesn't care about details in the code. In your example for a 3-tiered application the three layers could be identified as architecture components at the highest level. Additionally you could break up each layer into more components for a fine-grained view on the software.

A design pattern in contrast is something completely different. Design patterns are some sort of recipe to solve common software problems. Design pattern are developed for similar coding problems which repeatedly occur in software systems. So design pattern come into play at a very low level of an application.

Of course this description is very oversimplified but you'll find lots of information on this in the internet or books on these topics.

Marco
 
Ranch Hand
Posts: 254
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If you don't really understand what software architecture is I'd recommend reading 'Software Architecture in Practice (SEI Series in Software Engineering)' by Len Bass, Paul Clements, and Rick Kazman
 
Ranch Hand
Posts: 1936
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In short.
Software architecture is structures, relationships, and interactions of most important components of software.

Design patterns are good practices about software design that occur again and again.
 
The happiness of your life depends upon the quality of your thoughts -Marcus Aurelius ... think about this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic