|
|
This is only a preview of the paper
Click here to register and get the full text.
Existing members click here to login
|
|
|
... In the endeavour to find such a solution we propose to adopt the A-3 (or N Tier) distributed architecture. ...
A-3 distributed architecture would be the most suitable for the company’s network. According to this model, the client machines are at the first tier, which will be responsible for the presentation of data, receiving user events and controlling the user interface, the application servers will be at the second tier, and the data storage at the third tier.
The A-3 architecture overcomes the weaknesses of the 2-tier and client/server architectures. ... However, the downside is the successful implementation of A-3 architecture requires considerable applied experience.
The advantage of the A-3 architecture is that it offers a clear separation of user-interface-control and data presentation from application-logic. ...
Greater flexibility is also achieved with A-3 design, as it partitions application functionality into three independent layers, enabling easier integration with core business systems and other e-Business applications. ...
The allowance of shared services also simply the development, businesses can extend the benefits of the A-3 architecture even further by establishing standardized hardware and software designs at each tier. ...
The best practice recommendations for the implementation would be to become proficient at designing and deploying A-3 architecture. ... During application development, push session management back to the database layer, to improve scalability at the front-end and middle tier.
Approximate Word count = 1107
Approximate Pages = 4.4
(250 words per page double spaced)
|
|
|
|
|
|