arambazamba / az-native

Designing & Implementing Cloud Native Applications using Microsoft Azure

Ask me about:

• Cloud Native Apps, Azure Container Apps & Dapr
• Azure DevOps & Infrastructure as Code
• Angular & Micro-Frontends
• Azure AI Studio, OpenAI, Semantic Kernel
• Microsoft Graph & Identity Platform
• Microsoft 365, Teams & SharePoint Development

az-native's Issues

realtime - migrate to container app

undefined

events - event domain & filters

https://learn.microsoft.com/en-us/azure/event-grid/event-domains?tabs=event-grid-event-schema

payment - move to repsitory

az-native/labs/lab-07/solution/payment-service/Controllers/PaymentController.cs

Lines 28 to 66 in 350dd63

	// http://localhost:PORT/payment/create
	[HttpPost()]
	[Route("create")]
	[Dapr.Topic("food-pubsub", "payment-requests-topic")]
	public async Task AddPayment(OrderEvent evt)
	{
	Console.WriteLine($"Received payment request for order: {evt.OrderId}", evt);
	PaymentRequest paymentRequest = Newtonsoft.Json.JsonConvert.DeserializeObject<PaymentRequest>(evt.Data.ToString());
	if (paymentRequest != null)
	{
	// When using transactional Outbox pattern, we need to add the payment to the database
	// We then could use Cosmos Change feed to execute the payment against our dapr bank service
	// PaymentTransaction payment = new PaymentTransaction()
	// {
	// Id = Guid.NewGuid().ToString(),
	// CustomerId = evt.CustomerId,
	// OrderId = paymentRequest.OrderId,
	// PaymentInfo = paymentRequest.PaymentInfo,
	// Amount = paymentRequest.Amount,
	// Status = "Pending"
	// };
	// await this.payment.AddPaymentAsync(payment);
	// To keep things simple we will just execute the payment against our dapr bank service
	// Make sure to created the bank account with the same account number in advance
	// You will find a sample in the bank client of the starter
	var usersBank = ActorProxy.Create<IBankActor>(new ActorId(paymentRequest.PaymentInfo.AccountNumber), "BankActor");
	var withdrawResp = await usersBank.Withdraw(new WithdrawRequest() { Amount = paymentRequest.Amount });
	// Now we could issue a payment response just like we did in
	PaymentResponse paymentResponse = new PaymentResponse()
	{
	OrderId = paymentRequest.OrderId,
	Status = withdrawResp.Status,
	Data = withdrawResp.Message
	};
	await daprClient.PublishEventAsync("food-pubsub", "payment-response-topic", paymentResponse);
	}
	}

ddd - create bounded context diagram

az-native/labs/lab-05/solution/readme.md

Line 19 in 239056b

## Task: Designing the Data Model

events - lab

durable funct - upgrade to .net isolated

az-native/demos/04-functions/05-durable-entity/readme.md

Lines 1 to 6 in 62e59ab

	# Azure Durable Entities: Aggregation & Actors
	A Durable Entity can be used:
	- As an actor like object to manage state and perform operations on the object, like a bank account.
	- To implement the Aggregator pattern to aggregate data from multiple sources like IOT devices

cosmos - data api builder

https://learn.microsoft.com/en-us/azure/data-api-builder/get-started/get-started-azure-cosmos-db