Difference between 3 tier architecture and MVC pattern
Hi All, I was trying to understand the concepts of fusebox and came across MVC design pattern, Can anyone please help me in understanding the difference between MVC and 3 tier architecture. I am confused as both are concerened with separation of layers? Thanks. ~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:329765 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
Re: Difference between 3 tier architecture and MVC pattern
MVC is a pattern for structuring your UI-layer code, while a three tier architecture is about how your hardware is laid out. MVC is about separating the request processing code from the state (model) code and from the display (view) code. The three all worth together to deal with a user interaction, but the pieces have distinct roles and are typically best served to be segregated based on those roles. Three tier architecture is about physically separating your presentation code (typically an MVC application) from your business logic (typically a set of business objects) and your persistence layer (a database) onto different hardware. The advantages are that the three layers can then scale independently and that they can have different network security policies wrapped around them. Fusebox is concerned with MVC, since it is a UI-layer code framework. cheers, barneyb On Mon, Jan 18, 2010 at 11:34 AM, funand learning funandlrnn...@gmail.com wrote: Hi All, I was trying to understand the concepts of fusebox and came across MVC design pattern, Can anyone please help me in understanding the difference between MVC and 3 tier architecture. I am confused as both are concerened with separation of layers? Thanks. -- Barney Boisvert bboisv...@gmail.com http://www.barneyb.com/ ~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:329767 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Re: Difference between 3 tier architecture and MVC pattern
On Mon, Jan 18, 2010 at 11:56 AM, Barney Boisvert bboisv...@gmail.com wrote: Three tier architecture is about physically separating your presentation code (typically an MVC application) from your business logic (typically a set of business objects) and your persistence layer (a database) onto different hardware. In the web world, it can often mean having separate web servers, application servers and database servers. The advantages are that the three layers can then scale independently and that they can have different network security policies wrapped around them. Yup, what Barney said (even about web, app and DB servers). Fusebox is concerned with MVC, since it is a UI-layer code framework. ...and it lives on the application server. -- Sean A Corfield -- (904) 302-SEAN Railo Technologies US -- http://getrailo.com/ An Architect's View -- http://corfield.org/ If you're not annoying somebody, you're not really alive. -- Margaret Atwoo ~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:329775 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4