A input triggers a process which may produce implicit or explicit output. In the backdrop of this simplicity MVC framework/architecture manifests itself.
MODEL - Core Process Engine
CONTROLLER - Communication Hub (Receives/Sends Instructions/Data)
VIEW - User Interface
In the trio, Controller forms the basic fabric of the architecture. Its the layer which "cements" as well as provides "independence" to Model and View. Infrastructure which provides PERSISTENCE by modulating/handshaking on both sides i.e. VIEW and MODEL.
As the clients now a days have enough memory and CPU power , VIEW (user-interface) can be intelligent. And that's the space which can contribute to scalability , all the UI needs can be taken care of without the server coming into picture.
Business logic and data binding makes the MODEL. Here flexibility is a big challenge , SOA (Service Oriented Architecture) approach makes this area of architecture most refined process of all. Business Processes identification leading to component build up. Data Layer acts as persistent memory while data schema will reflect business cases (Entity-Relationships).
No comments:
Post a Comment