Webpack has dominated for years. But Vite (powered by esbuild) is 100x faster. Why Vite is Fast Webpack bundles your entire application before serving it. Vite serves source files over native ESM (ES Modules). The browser does the importing. On a large React project, our startup time went from 45 seconds (Webpack) to 300ms (Vite). […]
Read more →Container Security: Running as Non-Root
By default, Docker containers run as `root`. If an attacker compromises the app, they have root access to the container (and potentially the host). Running as a non-root user is a critical security best practice, mandated by policies like Azure Policy for Kubernetes. The Dockerfile Fix Key Takeaways You cannot bind to ports < 1024 […]
Read more →Visual Studio 2022 Preview 1: 64-Bit is Real
It happened. Visual Studio is finally 64-bit. Use more than 4GB of RAM. Open massive solutions containing 1,600 projects. First Impressions It feels snappier. Finding files in huge repos is instant. The UI has a slight refresh/modernization. And IntelliCode (AI-assisted coding) can now complete whole lines of code. This is the most significant architecture change […]
Read more →.NET 6 Minimal APIs: First Look
.NET 6 introduces “Minimal APIs”, a stripped-down approach to building HTTP APIs without the ceremony of Controllers, Filters, or `Startup.cs`. Four Lines of Code Parameter Binding It infers binding from route, query, or body automatically. Key Takeaways Minimal APIs are **faster** than Controllers (less reflection overhead). You can still use DI, Auth, and Validation. Great […]
Read more →MassTransit: The Enterprise Service Bus for .NET
Don’t implement `RabbitMQ.Client` directly. It’s complex and error-prone. **MassTransit** abstracts the message broker (RabbitMQ, Azure Service Bus, SQS), providing a unified API for consumers, sagas, and fault tolerance. Defining a Consumer Configuration Key Takeaways MassTransit handles **Connection Recovery** and **Retry Policies** out of the box. Use **Sagas** for long-running stateful workflows.
Read more →Bicep Modules: Enterprise Infrastructure Scale
Copy-pasting Bicep code defeats the purpose of Infrastructure as Code. **Modules** allow you to strictly define inputs and outputs for reusable components (like a standardized VNET or Storage Account), enforcing compliance across the enterprise. Creating a Module Consuming the Module Key Takeaways Publish modules to a **Private Bicep Registry** (ACR) for cross-team sharing. Use `br:myregistry.azurecr.io/bicep/storage:v1` […]
Read more →