User71929859 posted
architecture pattern
Hi,
Architecture is not a pattern. It's a part of the development process.
1. Which technology to use?
2. How data will be stored.
3. What are different layers in the system?
4. What are different tiers in the system?
Architecturing means taking decisions about your application. It can vary through all stacks, front-end to back-end. Architecture can be on solution level, network level or application level. Depend on what you architect, the tasks involved will be different.
Since you posted your question in asp.net forums, I believe you are talking about web application architecturing. In that case it usually involved (in a simple application) analysing the requirements and deciding things like which programming model to use,
what libraries should be used, what versions of the frameworks should be used, what tools should be used etc.
And Design pattern is
How a functionality is implemented to make a loosely coupled and reuseable.
Is my understanding correct.
Not really. Design pattern is a reusable solution for a common problem. AFAIK it does not necessarily have to be loosely coupled. Design patterns does not tell you how to write codes (most of the time).
