Introduction
Imagine that you work for a small to medium-sized company with a public-facing web application deployed on-premises. Your servers are aging and running at near-capacity. Rather than invest more heavily in hardware, you're going to migrate to Azure. You want the benefits of hosting in the cloud, while minimizing downtime and using the existing skills of your team. Further, the application is layered and deployed on an N-tier architecture. You want to ensure that you're able to scale, manage, and secure your application now and in the future.
In this module, you learn what N-tier (or multitier) architecture is, when to use it, and what the benefits and drawbacks of this architectural style are.
By understanding what makes up an N-tier architecture and how to optimize it, you can make the right decisions when selecting an architecture for new applications. You can also improve deployments of existing applications.
Learning objectives
In this module you will:
- Identify the features, limitations, and considerations of the N-tier architecture style
- Identify use cases for when an N-tier architecture is appropriate
- Deploy a sample N-tier architecture
- Identify methods and resources to improve your N-tier architecture