Say that you want to write a minimal API as seen in Can .net compete with NodeJS. How would you structure such an application? You would end up with something like 0-1 layers in your application. Some of my previous coworkers embrace these patterns in order to focus on business value. In this post I’ll try to get into how you could make such a system without going into detail (pointing instead to examples). Embrace SQL One way to write simple API’s is to embrace SQL when you feel that it’s appropriate. [...]

Say that you want to write a minimal API as seen in Can .net compete with NodeJS. How would you structure such an application? You would end up with something like 0-1 layers in your application. Some of my previous coworkers embrace these patterns in order to focus on business value. In this post I’ll try to get into how you could make such a system without going into detail (pointing instead to examples). Embrace SQL One way to write simple API’s is to embrace SQL when you feel that it’s appropriate. [...]

This example is loosely based on how the API looks for aggregates in Axon Framework. We also base some of the code around examples of ValidationBehavior found online. Stackoverflow CodeMaze The reason why I’ve implemented these examples is in order to showcase how you can cut down on some of the ceremony around using a generic mediator interface implementation togheter with fluent validation logic (pipeline behavior in MediatR parlance). Note that I’m not making a value judgement around if you sh[...]

This example is loosely based on how the API looks for aggregates in Axon Framework. We also base some of the code around examples of ValidationBehavior found online. Stackoverflow CodeMaze The reason why I’ve implemented these examples is in order to showcase how you can cut down on some of the ceremony around using a generic mediator interface implementation togheter with fluent validation logic (pipeline behavior in MediatR parlance). Note that I’m not making a value judgement around if you sh[...]

NodeJS applications can be a single file with minimal overhead: const express = require('express') const app = express() app.get('/', (req, res) => { res.send('Hello World!') }) app.listen(3000, () => { }) How does this compare to what we have seen in the .net world? For .net 5 C# HelloWorld.csproj <Project Sdk="Microsoft.NET.Sdk.Web"> <PropertyGroup> <TargetFramework>net5.0</TargetFramework> </PropertyGroup> </Project> Program.cs using Microsoft.AspNetCore.Builder; using Microsoft.Asp[...]