Skip to main content

Posts

.NET developer moving into Azure Functions and Durable Functions

 For a .NET developer moving into Azure Functions, I’d prioritize learning in this order: HTTP Trigger Timer Trigger Queue Trigger Dependency Injection Configuration & app settings Blob Trigger Service Bus Logging + monitoring Durable Functions Deployment to Azure After this, the next major topic is Durable Functions (fan-out/fan-in, chaining, orchestration), which is frequently asked in interviews and used in enterprise projects. This pattern is very common in production systems. Example: E-commerce order processing HTTP Trigger       ↓ Queue Output       ↓ Queue Trigger       ↓ Process order       ↓ Blob Storage       ↓ Send Email https://chatgpt.com/share/6a151bf1-e124-8322-96f5-84b133b2a0b1 Since you're already a .NET developer, the fastest path is: understand what Azure Functions are , create one locally, run/debug it, then deploy it. Here's a practical step-by-step roadmap....
Recent posts

Azure function - sample in visual studio code - Run locally

 Install an older LTS Node version (for example Node 18 or Node 16 rather than the newest release): https://nodejs.org/en/download step 2: node --version npm --version step 3:  npm install -g azure-functions-core-tools@4 --unsafe-perm true step 4:  func --version step 5: dotnet --version step 6: mkdir C:\AzureDemo Step 7: func init MyFunctionApp --worker-runtime dotnet-isolated Step 8: cd MyFunctionApp step 9:create http trigger function func new Step 10: enter the function name hellofunction Step 11: It will create automatically, to check the name hellofunction.cs create new file Step 12: func start Step 13: url - http://localhost:7071/api/HelloFunction

bot hit - server response time and overall page loadtime increase - aws, ec2, google analytic, cloudflare, ms sql cpu usage 100%

 Dear All, I've recently facing website page load time and server response time issue,  troubleshooting -  1. IIS log via - http log browser (tool to identify the bot hit) 2. disallow in robots.txt 3. article found and feature enabled in Cloudflare   Bot Fight Mode Challenge requests matching patterns of known bots before they can access your site. Requests matching Cloudflare-identified, non-legitimate automated traffic patterns will be challenged and/or blocked by Cloudflare. And, JavaScript Detections Use lightweight, invisible JavaScript detections to improve Bot Management products. 4. AWS EC2  Add new security group for Cloudflare ips list Ref:  https://dev.to/johnmccuk/automate-aws-security-group-with-cloudflare-ips-la6 And referred follow articles: https://www.imperva.com/products/advanced-bot-protection-management/ https://blog.apnic.net/2019/11/15/how-to-hide-aws-ec2-instances-from-network-scanning-bots-using-ipv6/ https://pawelurbanek.com/ec...

IPv4 header to requests when a client is using IPv6

  What is Pseudo IPv4? As a stopgap to accelerate the adoption of IPv6, Cloudflare offers Pseudo IPv4 which supports IPv6 addresses in legacy applications expecting IPv4 addresses. The goal is to provide a nearly unique IPv4 address for each IPv6 address, using Class E IPv4 address space, which is designated as experimental and would not normally see traffic. To learn more see  here . Options Add header:  Add additional Cf-Pseudo-IPv4 header only Overwrite headers:  Overwrite the existing Cf-Connecting-IP and X-Forwarded-For headers with a pseudo IPv4 address Cloudflare

Android Pay for Payment Request API

https://developers.google.com/android-pay/mobile-web/tutorial Tutorial With Android Pay for Payment Request API, you may request one of two payment token types: gateway or network. If you are using Braintree, Stripe, or Vantiv as your payment gateway, then you may request a gateway token from Android Pay. Otherwise, you may request an encrypted network token bundle. You may either handle the network token yourself or work with your processor to handle decrypting the token bundle.