https://github.com/bradygaster/aspnetcorewithyarponazurecontainerapps

https://github.com/bradygaster/aspnetcorewithyarponazurecontainerapps

Last synced: 2 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/bradygaster/aspnetcorewithyarponazurecontainerapps
• Owner: bradygaster
• Created: 2022-01-04T17:09:33.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2022-11-02T15:15:39.000Z (about 2 years ago)
• Last Synced: 2023-03-06T14:48:52.516Z (almost 2 years ago)
• Language: C#
• Size: 1020 KB
• Stars: 10
• Watchers: 1
• Forks: 4
• Open Issues: 1
• Metadata Files:
  • Readme: readme.md

Awesome Lists containing this project

README

        
# .NET with YARP on Azure Container Apps

This repository contains a simple scenario built to demonstrate how ASP.NET Core 6.0 can be used to build a cloud-native application hosted in Azure Container Apps. The repository consists of the following projects and folders:

* Catalog API - this is an ASP.NET minimal API project with one endpoint. 

* Orders API - this is an ASP.NET minimal API project with one endpoint. 

* UI - an ASP.NET Blazor Server app that calls out to both the Catalog and Orders API and renders their status.

* Proxy - a YARP proxy project that proxies to the UI app.

* ```deploy``` folder - this folder contains a series of [Azure Bicep](http://aka.ms/bicep) templates that can be used to create the application and deploy it.

* ```setup.ps1``` - this file is a one-stop way for you to deploy the app to your own Azure subscription so you can try the scenario. 

## Prerequisites

* .NET 6.0

* The Azure CLI

* An Azure subscription

* Docker

* PowerShell *(GitHub Actions will replace this prerequisite soon)*

## Setup

1. Clone this repository.

2. Sign in to your Azure subscription using the `az login` command.

3. If you have more than 1 Azure subscription, make sure you're targeting the *right* Azure subscription by using the `az account show` and `az account set -s ` commands.

4. From the root of this repository, run `./setup.ps1`. 

## Topology diagram

The resultant application is an Azure Container Environment-hosted set of containers - the `catalog` API, the `orders` API, the `ui` Blazor Server front-end, and the `yarp` reverse proxy app.

![Topology diagram](static/topology.png)

Internet traffic should not be able to directly access either of the back-end APIs, or the Blazor Server interface, as each of these containers is marked as "internal ingress only" during the deployment phase. Internet traffic hitting the `yarp...azurecontainerapps.io` URL should be proxied to the `ui` container, which in turn makes outbound calls to both the `catalog` and `orders` APIs within the Azure Container Apps Environment. The `yarp` Azure Container App should be the only app in the environment marked with "external ingress," as it should proxy to the UI and thus, shield the back-end from internet traffic.