Tidy up - Unused Project and Nuget package reference using Visual Studio 2019

If you are a Developer/Architect using Visual Studio as IDE for your development activities, this blog post will be of your interest. During the Ignite 2021 conference, Microsoft released Visual Studio 2019 v16.9 and v16.10 Preview 1. As part of version 16.10 Preview 1, one of the cool features they introduced is to "Remove Unused References..." for any Projects and Nuget packages that are not in use. At the time of writing this blog post, we have Visual Studio Version 16.10.0 (official release) which includes this new feature.  As part of development, we generally get carried away and introduce new Nuget package references to your project and add new references to your Projects. By the end of development, you will not be 100% sure which are not being referenced and unused which means you will leave those unused project references in your application. Now you might be wondering what's the big deal in it since it doesn't harm. The advantage of removing unused project r

Azure Front Door vs Azure Traffic Manager?

 In my previous blog post, we looked in detail Azure Front Door (AFD). In this blog post, let's compare Azure Front Door (AFD) with another popular Azure service named Azure Traffic Manager (ATM). Prior to AFD most of the applications made use of ATM in their architecture now with AFD being available it's good to understand in which scenarios these individual services are ideal.

Azure Front Door (AFD)

Azure Front Door Service (AFD) a scalable and secure entry point for the fast delivery of your global applications. Azure Front Door allows you to transform your global (multi-region) applications into robust, high-performance applications, APIs, and content.

Azure Traffic Manager (ATM)

Azure Traffic Manager is a DNS-based traffic load balancer for geographically distributed Datacenters. Traffic Manager uses DNS to direct traffic to endpoint based on the traffic routing method and health of the endpoints.

Similarities between AFD and ATM

Both Azure Services support
  • Multi-geo redundancy - If the application goes down in one region traffic routes to the closest region without any intervention (automatic failover routing)
  • Closest region routing - Traffic is automatically routed to the closest region which improves application performance.

Differences between AFD and ATM

Few differences are shown below by classifying at the feature level.

Features

 Azure Front Door

Azure Traffic Manager

TLS termination

SSL offload by AFD

No SSL offload

Protocol

HTTP(s)

Supports any protocol like HTTP, TCP, UDP, etc.

Network Routing

Uses Reverse proxy

Uses DNS lookup

Cache

Caches static content

No caching available

WAF Integration

AFD provides WAF integration

Not available

URL Rewrite

AFD supports URL rewriting

Not available


The below flowchart helps you to decide on choosing a load balancing service like AFD vs ATM vs others.
Decision tree for load balancing in Azure

References

Comments

Popular posts from this blog

Tidy up - Unused Project and Nuget package reference using Visual Studio 2019

Swagger UI for Azure Function v2 & v3 APIs

Authenticate Azure Functions - API Keys