A production write-up on rate limiting and resource governance for MCP orchestration servers, where a single tenant's burst can exhaust shared LLM token quota and starve everyone else. It compares the common limiter algorithms and lands on per-tenant token buckets with Redis-backed state and quota-aware refill rates.
Azure SQL Database Hyperscale splits a single-writer SQL engine across separate compute, log, page server and storage tiers, so it is distributed in architecture but not in write capacity. The author explains where that line falls against the usual meaning of distributed SQL, and cites a commissioned benchmark against Aurora PostgreSQL. Useful when you choose a database for a growing workload.
AWS Transform for .NET can convert Azure cloud-native code, such as Azure SDK calls, to equivalent AWS services. The AWS blog walks through moving an Azure Functions queue-triggered function to AWS Lambda with SQS and DynamoDB, then customizes a larger transformation that redirects Cosmos DB to Amazon S3. It is a useful reference for .NET teams planning a cross-cloud migration.
The Azure Cosmos DB Change Feed Processor spreads change processing across several .NET workers using a lease container for ownership and checkpoints. The article walks through the setup in the .NET SDK and explains when adding workers actually helps. It also covers why downstream operations must be idempotent, since changes can be delivered again after a failure.
Amp can now boot a cloud Mac during a thread to build, test and run iOS and macOS apps. The feature, macOS Satellites, is in beta and billed hourly. For developers working on Apple platforms, it changes how an agent verifies its own changes.
Visual Studio Marketplace now offers Trusted Publishing, which lets VS Code and Visual Studio extensions be published from GitHub Actions or Azure Pipelines without a long-lived personal access token. Publishing uses federated identity instead, so there is no secret to store or rotate. Extension authors who automate releases should review the setup and migration steps.
The October 2026 Azure SDK release highlights Azure Core 1.63.0 for .NET, Identity updates for Python and Java, and the first stable Cosmos DB for Rust 1.0.0. The authentication changes affect how DefaultAzureCredential behaves in production. Teams on the Cosmos DB Rust preview also get concrete upgrade steps.
AWS has documented how to connect its AWS Transform MCP server to GitHub Copilot agent mode, so migrations can be driven from the chat box in Visual Studio or VS Code. The walkthrough ports an Azure Functions .NET app to AWS Lambda using the Lambda Annotations Framework. It is worth a read if your team is weighing an Azure-to-AWS move or wants a repeatable agent-driven migration workflow.
The AWS .NET blog shows how to run Blazor Server applications on Amazon ECS with AWS Fargate. The post explains how the persistent WebSocket connection and in-memory circuit shape routing, session stickiness and deployment behavior. It walks through a CDK-based sample stack fronted by CloudFront.
PHP disclosed two critical vulnerabilities on October 21, 2026 that can allow remote code execution. Azure DevOps Services and Server do not use PHP for customer requests, so the exposure sits in the PHP runtimes your pipelines, agents, containers and deployed apps use. The post explains which PHP installs Microsoft patches and which ones you must patch.
Avalonia reported that unauthorised access during the 22-23 October 2026 attack was limited to its marketing website CMS. The entry point was an administrator token accidentally embedded in browser-delivered JavaScript. All 39 attempts to publish to its NuGet feeds were rejected, and customers need not reset passwords or replace licence keys.
The Azure Cosmos DB blog shows how to test a database-backed feature against the Azure Cosmos DB Emulator running in Docker, then run the same tests in GitHub Actions. The example is a Python demo app, but the pattern applies to any .NET service that talks to Cosmos DB. Each pull request update runs against a fresh emulator, so you can check that a write reached storage and changed the answer, not just that the HTTP call returned 200.