Тёмный
No video :(

Must Have API Controllers! 

ScriptBytes
Подписаться 2,2 тыс.
Просмотров 182
50% 1

Every time I create a new API, I always end up adding these two controllers.
One is a /status controller, which does health checks on various parts of my API and responds if everything is ok. I then call these endpoints from a monitoring tool to check on the status of my API.
The other is an /errors controller, which will respond with a given error code whenever an endpoint is called. I use this from my user interfaces to ensure that the users have a good experience when something goes wrong on the backend.
I show how I implement these in a .Net 7 API.
Follow me on social media!
Twitter: / scriptbytesio
Instagram: / scriptbytes
Threads: www.threads.ne...
Check out my blog!
scriptbytes.io/

Опубликовано:

 

27 авг 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 2   
@AZisk
@AZisk 11 месяцев назад
hey. 🎉
@scriptbytes
@scriptbytes 11 месяцев назад
🥳
Далее
Basic Authentication in Dotnet API
13:15
Просмотров 4,3 тыс.
Entity Framework Web API Tutorial .Net 8
36:47
Просмотров 3,7 тыс.
拉了好大一坨#斗罗大陆#唐三小舞#小丑
00:11
Fix Your Controllers By Refactoring To Minimal APIs
14:56
Blazor 8 Docker  | Build a Blog - Ep 04.5
13:16
Просмотров 1,6 тыс.
How to Run MongoDB in Docker
11:44
Просмотров 17 тыс.
I Never Want To Build Authentication Any Other Way
2:03:20
Task WhenAll vs Parallel ForEach
6:04
Просмотров 545
Memory Cache in Dotnet API
8:28
Просмотров 282