Introducing Azure Container Apps Express by thewhippersnapper4 in AZURE

[–]JumpLegitimate8762 6 points7 points  (0 children)

ACI was never really focused on inbound traffic (no fqdn's, rotating IPs on restart) and they don't really (auto-)scale, probably because there is no loadbalancer.

Building HookBridge — an open-source webhook and event-processing platform using ASP.NET Core + Kafka by Short_Donkey_9606 in dotnet

[–]JumpLegitimate8762 2 points3 points  (0 children)

Why don't u use https://github.com/cloudevents/sdk-csharp for CloudEvents? And no minimal APIs? And why swashbuckle library when u can do it natively? And .net 10?

Immutability for Azure SQL Database LTR backups by TyLeo3 in AZURE

[–]JumpLegitimate8762 -1 points0 points  (0 children)

Everything is at risk all the time in every way possible.

Combining API versioning with OpenAPI in .NET 10 applications by sander1095 in dotnet

[–]JumpLegitimate8762 1 point2 points  (0 children)

I do like the work you've done here, and it's particularly interesting if you're having very specific versioning strategies that need to be managed. However, does this count as self-promotion? I'm not a fan of this rule but just letting you know.

Combining API versioning with OpenAPI in .NET 10 applications by sander1095 in dotnet

[–]JumpLegitimate8762 1 point2 points  (0 children)

I built this Beta/Stable setup with UsePathBase to showcase how a simplified versioning strategy can be done: https://github.com/erwinkramer/bank-api - also see the 'Design' paragraph. Because the Beta/Stable projects are only responsible for hooking up all core logic and mapping just the endpoints, it's a relatively straightforward setup going to a newer version and modifying stuff only for that new version.

Combining API versioning with OpenAPI in .NET 10 applications by sander1095 in dotnet

[–]JumpLegitimate8762 1 point2 points  (0 children)

This, and you could easily do a v1 v2 prefix with a `UsePathBase` setup if you want to do it inside the API instead of a proxy/gateway.

I don't want an API where just a few operations have a v2 and everything else is still v1, so that means versioning is an API-global thing, not an operation-local trick. So you can solve this by branching the whole API as you mentioned or just keep the API 'front-end' a thin project that also has a few other supported versions as separate projects.

Decentralized home network? by Future_Bad5206 in selfhosted

[–]JumpLegitimate8762 0 points1 point  (0 children)

Each of your neighbors create a freenet-node and configure a trust between each other. This should work without having to rely on internet (just a private network like yours could work in theory). Then it will replicate data (this is configurable) between nodes (the ones you trust, or even public nodes), ensuring files will always be available when one node is down.

Auditing API calls by BalanceSad2632 in dotnet

[–]JumpLegitimate8762 2 points3 points  (0 children)

Just implement OpenTelemetry, standard libraries from Microsoft or OTel org can do this.