name

The service URL returned after creating our Principal Service

password

The password returned after creating our Principal Service

tenant

The tenant ID returned after creating our Principal Service

organization

project

webUrl

Building Event Driven and Microservices Architecture in Azure.png

AzureDatastudio.tar.gz

run pwsh

run code

run code-cli

run code-cli-copy

Building a cloud infrastructure can be a challenging task. There are a lot of dependencies in your software and services like database, storage, and connections to log analytics that make it difficult.

In this course, you will learn how to easily design and build complex solutions based on the Event-Driven Architecture in the Azure Cloud. You will cover how to design, manage and monitor infrastructure. You will also learn how to select and combine resources like virtual machines and run books, databases, and application servers.

By the time you finish this course, you will be able to design and build complex architectures for enterprise-ready solutions based on Azure Cloud.

For the course, basic knowledge of Azure cloud or another cloud provider is needed.

Building Event Driven and Microservices Architecture in Azure

## Creating a Queue Storage Account 
Our event storage will be based on a Queue Storage Account. First, we will create a storage account. We will then add this storage account to the `middleware-eg-rg` resource as discussed in the previous lesson.

### CLI
We will create the `middleware-eg-rg` resource group with the command we discussed in the previous lesson. If you have already created this resource group, you may skip this step.

This is our command to create a resource group:
```text
New-AzResourceGroup -Name middleware-eg-rg -Location westeurope
```

Next, to create a storage account, we will use the `New-AzStorageAccount` command with the following parameters:
- `[-ResourceGroupName] <String>`: The resource group we want to create our storage account in.
- `[-Name] <String>`: The name of the storage account.
- `[-Location] <String>`: This is the server location.
- `[-SkuName] <String>`: The type of replication we want.
- `[-Kind] <String>`: The tier of storage we want.

This is our command to create the storage account:

```text
New-AzStorageAccount -ResourceGroupName middleware-eg-rg -Name devvmegrid1 -Location westeurope -SkuName Standard_RAGRS -Kind StorageV2
```


Hit the **RUN** button to access the terminal. You can run the script with the following command:
```
pwsh ./usercode/runCode.ps1
```


# Creating a Queue Storage Account 
Our event storage will be based on a Queue Storage Account. First, we will create a storage account. We will then add this storage account to the `middleware-eg-rg` resource as discussed in the previous lesson.

## CLI
We will create the `middleware-eg-rg` resource group with the command we discussed in the previous lesson. If you have already created this resource group, you may skip this step.

This is our command to create a resource group:
```text
New-AzResourceGroup -Name middleware-eg-rg -Location westeurope
```

Next, to create a storage account, we will use the `New-AzStorageAccount` command with the following parameters:
- `[-ResourceGroupName] <String>`: The resource group we want to create our storage account in.
- `[-Name] <String>`: The name of the storage account.
- `[-Location] <String>`: This is the server location.
- `[-SkuName] <String>`: The type of replication we want.
- `[-Kind] <String>`: The tier of storage we want.

This is our command to create the storage account:

```text
New-AzStorageAccount -ResourceGroupName middleware-eg-rg -Name devvmegrid1 -Location westeurope -SkuName Standard_RAGRS -Kind StorageV2
```


Hit the **RUN** button to access the terminal. You can run the script with the following command:
```
pwsh ./usercode/runCode.ps1
```


Let's create a storage account for our main event storage.  

Introduction

Architecture

Building CI/CD

Conclusion

Building an Event Storage

Creating a Queue Storage Account

CLI