Transactional outbox pattern with Azure Cosmos DB

In a distributed system we might typically involve publishing events/messages via a message broker to other services, where we might face challenges in the reliability and guaranteed delivery of those events. In this session we will learn how to overcome it using Transactional Outbox pattern with Azure Cosmos DB

From Data to Insights : Azure Cosmos DB in IoT workloads

In the session we will see how to use Raspberry Pi with PM sensor and GPS sensor to measure air quality.

Takeaways
- How to setup Azure Cosmos DB as a custom routing endpoint
- When to use Synthetic Partition Key
- Integration of Synapse analytic + Azure Cosmos Db
- Visualizing data in Power BI

Microservices: Saga orchestration using outbox pattern

This session aims at displaying what a practical implementation of an Event-Driven Architecture (using Event Streaming) would look like in the context of a Microservice system that uses the Saga-Choreography pattern for communication.
We would also be touching upon the associated design concepts including Async APIs for Events and implementation of observability in such a system that relies on events for communication between the components (traces/spans and dependency graphs )

Build Serverless Web Pub Sub using Azure Functions

In the Demo we will see how to develop real time speech translator Web Pub Sub using Functions App

Demo is based on a tool that allows you to host a session and listen to it, in any preferred languages .

Speech are transcribed and translated using Azure cognitive services . It is then pushed to Web Pub sub with the help of Azure Functions , by which all the listeners who are subscribed to this session can see the translations with their preferences.

What happens when PubSub meets Azure Static Web App ?

In the Demo we will see how to develop real time speech translator Web Pub Sub using Functions App
Demo is based on a tool that allows you to host a session and listen
to it, in any preferred language .
Speech is transcribed and translated using Azure cognitive services .It is then pushed to Web Pub sub with the help of Azure Functions , by which all the listeners who are subscribed to this session can see the translations with their preferences

Build integrated workflows with Event Grid and Logic Apps

In the Demo

- We will discuss on the use case that we are trying to solve.
- Create Custom CloudEvent v1.0 event types.
- Challenges that we face in Logic Apps for the CloudEvent support.
- Workaround for implementing it , to support CloudEvent.
- Will trigger approval-based automations based on the model.

Build Serverless Web Pub Sub using Azure Functions

In the Demo we will see how to develop real time speech translator Web Pub Sub using Functions App

Demo is based on a tool that allows you to host a session and listen to it, in any preferred languages .

Speech are transcribed and translated using Azure cognitive services . It is then pushed to Web Pub sub with the help of Azure Functions , by which all the listeners who are subscribed to this session can see the translations with their preferences.

Continuous Performance testing

We will learn about how to implement continuous performance testing using Azure Load testing and GitHub Actions.

Middleware pattern for Azure Functions

We all are aware that from .NET 5 release we have two modes in which we can run Azure Functions
- Out-Of-Process
- In-Process
Out-of-process or Isolated mode have ability to define middleware as on out-of-box feature. But we will see how to achieve the same in the traditional Azure Functions using my open-source library AzureFunctions.Extensions.Middleware

Introduction to Azure Load Testing for developers

we will cover everything that you need to kickstart your performance testing with Azure Load Test service

Real-time cosmic chat

In the demo we will cover how to built a Cosmic chat application in real time using Azure cosmos Db + Azure Functions + Azure Web PubSub

Secretless in Serverless

In this workshop we will learn about how to manage secrets built on .NET 6 function app.

Real-world Event sourcing with Redis as Read model and Azure SQL as Write model

As part of this demo , I will be providing a brief introduction on Event sourcing in distributed systems and how to chose the right model for your application.

We will develop an application with an use case to cover all below points

- CQRS
- Azure Function to build REST API
- Azure Service Bus
- Azure Redis
- Design patterns

Build everything on Serverless !

In the Demo

* We will see how to develop Angular SPA and host it on Azure Static Web app and will use integrated API ( Azure Function ) to develop our translator modules , authentication .

* We will see how to use workflows using Azure Logic Apps to trigger invite mail once a user login to our application

* Finally we will also cover Serverless Cosmos DB which is used as our persistence layer.

Serverless Middleware in Azure Functions

When it comes to microservice architecture , sometimes all you wanted is to perform cross cutting concerns ( logging, authentication , caching, CORS, Routing, load balancing , exception handling , tracing, resiliency etc..) and also there might be a scenario where you wanted to perform certain manipulations on your request payload before hitting into your actual handler. And this should not be a repetitive code in each of the services , so all you might need is a single place to orchestrate all these concerns and that is where Middleware comes into the picture. In the demo I will be covering how to orchestrate these cross cutting concerns by using Azure functions as a Serverless model both in current runtime and as well in out-of-process model which is still in preview stage

https://ccdays.konfhub.com/

Serverless Middleware in Azure Functions

When it comes to microservice architecture , sometimes all you wanted is to perform cross cutting concerns ( logging, authentication , caching, CORS, Routing, load balancing , exception handling , tracing, resiliency etc..) and also there might be a scenario where you wanted to perform certain manipulations on your request payload before hitting into your actual handler. And this should not be a repetitive code in each of the services , so all you might need is a single place to orchestrate all these concerns and that is where Middleware comes into the picture. In the demo I will be covering how to orchestrate these cross cutting concerns by using Azure functions as a Serverless model.