In REST, we use HTTP Status Codes (404, 500). In gRPC, we must use `RpcException` and `Status` objects to communicate errors rich in metadata across service boundaries. Standard Status Codes StatusCode.NotFound -> Entity missing. StatusCode.InvalidArgument -> Validation failed. StatusCode.FailedPrecondition -> ETag mismatch / Conflict. Interceptor for Global Error Handling Key Takeaways Never expose internal stack […]
Read more →Visual Studio 2022 64-bit: First Impressions
For the first time, Visual Studio is 64-bit (devenv.exe). This removes the 4GB memory limit that has plagued developers of large enterprise solutions. We successfully loaded a solution with 1,600 projects. Performance Specs **Memory Usage**: Can now exceed 4GB (we saw 8GB usage on giant solutions). **Find in Files**: 3x faster using the new indexing […]
Read more →Dapr v1.0: Building Microservices for Any Cloud
Dapr v1.0 is production-ready. It solves the hardest parts of distributed systems: State management, Service Invocation, and Event-driven messaging. This guide implements the “Virtual Actor” pattern using Dapr actors. Virtual Actors Actors are single-threaded units of state and logic. Dapr handles their lifetime (activating them when a message arrives, deactivating them after timeout). Output Bindings […]
Read more →Dependency Injection in .NET: Service Lifetimes
Using the wrong DI lifetime is the #1 cause of concurrency bugs in ASP.NET Core. We revisit Singleton, Scoped, and Transient with a focus on thread safety. The Three Lifetimes Lifetime Created… Thread Safety Transient Every time requested Safe (Instance per usage) Scoped Once per HTTP Request Safe (Single thread per request) Singleton Once per […]
Read more →Azure Static Web Apps: Now Generally Available
Azure Static Web Apps (SWA) has hit GA. It’s the best way to host Blazor WASM, React, or Vue apps on Azure. Features Global Hosting: Content serves from edge locations. Integrated API: Deploy Azure Functions alongside your frontend in the same repo. Auth: Built-in auth for Azure AD, GitHub, etc. Staging Environments: Every Pull Request […]
Read more →Azure SQL Hyperscale: 100TB Databases
Traditional Azure SQL Database is limited by the disk size of the underlying VM (4TB max usually). **Hyperscale** decouples compute from storage, allowing databases to grow up to 100TB with rapid scaling. Architecture Why use it? **Instant Backups**: Backups are file-snapshots, taking zero IOPS from the compute. **Fast Restore**: Restoring a 50TB database takes minutes, […]
Read more →