Popular posts from this blog
Securing a Web API using Azure AD and Consuming it with Swagger - Step by Step Guide
Introduction: we will walk you through the process of securing a Web API using Azure AD (Azure Active Directory) and generating tokens through Swagger to call this protected API. Securing your APIs is crucial to protect sensitive data and ensure only authorized applications can access them. We'll break down the process into easy-to-follow steps. Prerequisites: Before we begin, make sure you have the following prerequisites in place: An Azure account with the necessary permissions. Visual Studio or a similar code editor. Basic knowledge of .NET Core and Swagger. Github Repository: Secure the Web API using Azure AD Steps to Secure the Web API using Azure AD: Step 1: Create Two App Registrations We need to create two Azure AD App Registrations, one for the Web API and the other for the Swagger client application. Create a new App Registration named "EmployeeWebApi." Leave the Redirect URI empty. Create a new App Registration named "EmployeeClientApp." Click ...
Durable Functions
Durable function components: How durable functions works: Step 1: Orchestrator starts Step 2: It will call await method (Task schedule) --> it's long running task Step 3: Then Orchestration sleeps Steps 4: Task schedule job it will finish the job and notify the orchestration job is done like that Step 5: Orchestrator starts --> check with execution history like did call the await method or not --> it will return yes. --> then return the output Execution history plays important role to maintain the state Orchestrator always starts the task and go for sleep --> once the task completed it will update to history table and notify the orchestrator --> then orchestrator will wakeup and do the rest of work. --> when orchestrator starts again it will start from first and check with history table and based on that it will continue the job. Orchestrator Constraints: Fan out/Fan in
Comments
Post a Comment