Kairos

This is a monorepo for Kairos back-end services. This repo contains (or will contain) the following modules:

• Gateway: a mediator that redirects the incoming requests to the other modules
• Account: responsible for authentication, authorization, account preferences and personal data
• Trade: manages the lifetime of orders
• Portfolio: materializes the stock positions accordingly to the settled orders
• Banking: responsible for money deposits and withdrawals
• MarketData: provides market data for other modules
• Exchange: act as a clearing that matches orders in the order book

More details on the underlying architecture can be seen in this figma file.

• Kairos Broker app: Link
• Kairos RabbitMQ: Link
• Kairos Seq: Link

How to run it locally

To run the app outside of a docker container, log in to Azure, in order to get access to the Azure KV secrets in a passwordless manner:

az login

Then run only the required infra as containers, while the app is ran normally via kestrel server:

docker --env-file ./.env compose up --build -d seq.kairos rabbitmq.kairos

cd src/Gateway && dotnet run --lp Local

If you need to run the app inside of a container, through docker-compose.yml for example, it's required to define the Service Principal credentials in a .env file, instead of simply doing az login, as mentioned earlier:

AZURE_CLIENT_ID=
AZURE_CLIENT_SECRET=

After setting the correct values you can simply execute docker compose up -d

Infra

After manually creating some basic resources such as RG, KV and ACR, the following instructions might come in handy for automatically creating more complex infra, such as vnet, subnet, storage account, file share, ACA environment, the ACAs themselves, etc.

Container App Env

The Azure Container App (ACA) Environment must be created with a subnet, because it's required to allow the container apps expose multiple ports. In this case, some containers, like RabbitMQ's and Seq's, will need to expose one HTTP port for the management UI and at least one TCP port, which will be used by the Kairos API to integrate with this infra.

RG_NAME="kairos"
LOCATION="eastus2"
VNET_NAME="vnet-kairos"
SUBNET_NAME="cae-subnet"

az network vnet create \
  --resource-group $RG_NAME \
  --name $VNET_NAME \
  --location $LOCATION \
  --address-prefix 10.0.0.0/16

az network vnet subnet create \
  --resource-group $RG_NAME \
  --vnet-name $VNET_NAME \
  --name $SUBNET_NAME \
  --address-prefix 10.0.1.0/27 \
  --delegations "Microsoft.App/environments"

SUBNET_ID=$(az network vnet subnet show --resource-group $RG_NAME --vnet-name $VNET_NAME --name $SUBNET_NAME --query id -o tsv)

az containerapp env create \
  --name cae-kairos \
  --resource-group $RG_NAME \
  --location $LOCATION \
  --infrastructure-subnet-resource-id $SUBNET_ID

Storage Account

Create a storage account that'll be used by the stateful containers (e.g., Seq and RabbitMQ):

STORAGE_ACCOUNT="kairostoraging"

# Create a Storage Account
az storage account create \
  --name $STORAGE_ACCOUNT \
  --resource-group kairos \
  --location eastus2 \
  --enable-large-file-share \
  --sku Standard_LRS \
  --query provisioningState

# Get the Storage Account Key
STORAGE_KEY=$(az storage account keys list -g kairos -n $STORAGE_ACCOUNT --query "[0].value" -o tsv)

RabbitMQ

Before creating the RabbitMQ container app, it's required to create an Azure File Share that'll be used for mounting the volume, in order to persist the Rabbit data.

# Create the File Share
FILE_SHARE="fs-kairos-rabbitmq"

az storage share-rm create \
  --resource-group kairos \
  --name $FILE_SHARE \
  --storage-account $STORAGE_ACCOUNT \
  --output table

# Link ACA env to the storage
az containerapp env storage set \
  --name cae-kairos \
  --resource-group kairos \
  --storage-name $FILE_SHARE \
  --azure-file-account-name $STORAGE_ACCOUNT \
  --azure-file-account-key $STORAGE_KEY \
  --azure-file-share-name $FILE_SHARE \
  --access-mode ReadWrite \
  --output table

Now the ACA can be created:

az containerapp create \
  --name capp-kairos-rabbitmq \
  --resource-group kairos \
  --environment cae-kairos \
  --yaml .github/capp-kairos-rabbitmq.yml \
  --output table

Seq

Assuming that the storage account was already created because of RabbitMQ, then the seq infra creation would be the following:

# Create the File Share
FILE_SHARE="fs-kairos-seq"

az storage share-rm create \
  --resource-group kairos \
  --name $FILE_SHARE \
  --storage-account $STORAGE_ACCOUNT \
  --output table

# Link ACA env to the storage
az containerapp env storage set \
  --name cae-kairos \
  --resource-group kairos \
  --storage-name $FILE_SHARE \
  --azure-file-account-name $STORAGE_ACCOUNT \
  --azure-file-account-key $STORAGE_KEY \
  --azure-file-share-name $FILE_SHARE \
  --access-mode ReadWrite \
  --output table

Now the ACA can be created:

az containerapp create \
  --name capp-kairos-seq \
  --resource-group kairos \
  --environment cae-kairos \
  --yaml .github/capp-kairos-seq.yml \
  --output table

Kairos Broker

Before creating the app itself, a user assigned managed identity should be created, because it'll be granted a ACR Pull permission, which will be used by the capp-kairos-broker creation YAML.

az identity create -n kairos-service -g kairos

PRINCIPAL_ID=$(az identity show \
  --name kairos-service \
  --resource-group kairos \
  --query principalId \
  --output tsv)

az keyvault set-policy \
  --name kv-kairos \
  --resource-group kairos \
  --object-id $PRINCIPAL_ID \
  --secret-permissions get list

ACR_ID=$(az acr show \
  --name kairosfinance \
  --resource-group kairos \
  --query id \
  --output tsv)

az role assignment create \
  --assignee $PRINCIPAL_ID \
  --scope $ACR_ID \
  --role "AcrPull"

Now the app can be created:

docker build --no-cache \
  -t kairosfinance.azurecr.io/kairos/broker . \
  -f ./src/Gateway/Dockerfile

docker push kairosfinance.azurecr.io/kairos/broker

az containerapp create \
  --name capp-kairos-broker \
  --resource-group kairos \
  --environment cae-kairos \
  --yaml .github/capp-kairos-broker.yml

Database Migrations

Generate the migration:

dotnet ef migrations add MigrationName -p src/SpecificModule -s src/Gateway -o Infra/Migrations --context SpecificModuleContext

Apply the migrations:

dotnet ef database update -p src/SpecificModule -s src/Gateway --context SpecificModuleContext