Yes, the code first configuration in .NET attracted my interest. Also it's testability. I don't understand why they push their JSON configuration so much. If you want config files, take nginx, HAproxy, Traefik, ...
LettuceEncrypt is more or less currently unmaintained. Way too risky to use, no idea how to fix that, if something breaks.
YARP got me interested, because I thought I could write some complex caching rules in C#. But you can’t, so every other proxy that doesn’t cache is as good as YARP ;)
Uh, not sure I understand. Do you mean you didn't want to write the logic? That issue you point to just means the component doesn't exist out of the box. Is that what you meant?
I wanted to implement some very specific caching rules, based on some POST parameters inside a JSON.
This seems to be possible with nginx and Lua, you extract a unique cache key from your request, and then nginx caching takes care of the rest. But in my case not out of the box or without the paid version.
So I hoped to fix that problem with YARP, but I would’ve needed to implement my own caching as a completely new middleware.
In the end I implemented the caching in the database.
- Writing code in a .net based language is one of the strengths.
- let’s encrypt isn’t built in but can be added by using https://github.com/natemcmaster/LettuceEncrypt
- Not sure about the caching one. Do you have more details?