You will learn how to create the web site so that the site (or you) will not fall apart when
functionality is extended or updates are made. Because this is a programming book, instead of
focusing on how to design the user interface or on marketing techniques, we??™ll pay close attention
to designing the code that makes them work.
The phrase ???designing the code??? can have different meanings; for example, we??™ll need to
have a short talk about naming conventions. Yet, the most important aspect that we need to take
a look at is the application architecture. The architecture refers to the way you split the code into
smaller components (for example, the product search feature) for a simple piece of functionality.
Although it might be easier to implement that functionality as quickly and as simply as possible
in a single component, you gain great long-term advantages by creating smaller, more simple
components that work together to achieve the desired result.
Before talking about the architecture itself, you must determine what you want from this
architecture.
Meeting Long-Term Requirements with Minimal Effort
Apart from the fact that you want a fast web site, each of the phases of development we talked
about in Chapter 1 brings new requirements that must be met.
Every time you proceed to a new stage, you want to be able to reuse most of the already
existing solution.
Pages:
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68