Tag Archives: software

Timing Minimal APIs vs Controllers

ASP.NET Core developers can choose between Minimal APIs and traditional MVC controllers, each offering unique structure and performance implications. This analysis highlights the request lifecycle differences and performance benchmarks. Generally, Minimal APIs are slightly faster, though real-world conditions often diminish the timing significance. Code organization also varies, with MVC providing inherent structure.

How the ASP.NET Runtime Works – part 2

This content outlines the request pipeline in an ASP.NET Core application, detailing its construction from the initial application builder through to the execution of requests. The process includes building and configuring middleware, managing endpoints, and handling requests with various delegate types. The final transition to live execution occurs upon calling Run, finalizing the pipeline.

How the ASP.NET Runtime Works – part 1

This article describes the startup process of an ASP.NET Core application, focusing on the WebApplication.CreateBuilder method that initializes the web host, configuration, dependency injection, and logging. It highlights server options like Kestrel and HTTP.sys, and the role of reverse proxies such as IIS, Nginx, and Apache in managing HTTP requests.

Model Binding in Minimal API

Model binding in web development is the process of mapping HTTP request data to programming objects. ASP.NET Core Minimal APIs automate this, handling types and validation seamlessly. It prioritizes binding methods: custom BindAsync, TryParse for simples, and property matching for complex types. Dependency injection is also streamlined, ensuring efficient handling of services.

Debunking ASP.NET Core Routing  

Routing in ASP.NET Core is essential for request processing, evolving from traditional MVC patterns to Minimal APIs. The UseRouting middleware matches HTTP requests to defined endpoints, while UseEndpoints executes corresponding handlers. The system is unified and endpoint-driven, providing capabilities like model binding and automatic validation across different routing models.

The Next Frontier of Conversational Application Programming

Conversational programming involves building software applications that understand and respond to natural language queries in various languages. Unlike traditional chatbots, it leverages Large Language Models (LLMs) to interpret user intent and interact with APIs for specific tasks. This enables seamless integration with backend functionalities and simplifies user interactions, as demonstrated in a backoffice task tracking scenario.

When Coding, Think Like a Lawyer

Software engineering shares many traits with traditional engineering including systematic approaches, design, planning, problem-solving, and quality assurance. However, ‘Big Upfront Design,’ now viewed as ineffective, sets software development apart. The role of a software architect in providing technical leadership, strategy, and risk mitigation, coupled with software engineers’ coding and problem-solving skills, underpin successful software creation. An analogy is made to law, where software engineers need deep domain knowledge, as lawyers do, to deliver more effective end products. However, thinking like a lawyer when coding can provide distinguishing benefits.