Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
n-tier is an architecture that helps you to develop distributed applications, the main advantage of using that is scalability.
The MVC is a design pattern, it helps you implement n-tier architecture in a way that insures that tiers are not tightly coupled.
What MVC says is that only your controller (Business Logic) should access the Model (generally DB) while the view access data using the Controller API without being aware to the source of the data. That implies that a change in the database will affect the Controller but not the View (GUI) since the interface between the Controller and the View should not change.
So, those terms a complete each other and are not contradictory.