У нас вы можете посмотреть бесплатно Microservices Explained with .NET | Build Your First Library API (In-Memory) | Episode 1 или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
In this episode, we build our first microservice from scratch using ASP.NET Core. We create a Library API that manages video metadata and focus on the core fundamentals of microservices: Clear service boundaries Ownership of business logic and data Clean architecture decisions Simple, intentional design 👉 What we cover in this episode: What a microservice really is (no buzzwords) Why ownership matters more than size Building a Library API using ASP.NET Core Controllers In-memory storage (no database yet) Clean CRUD endpoints Repository pattern (kept simple) First GitHub commit (professional habit) 🚫 What we intentionally do NOT include (yet): Database Docker Authentication / Authorization This is done on purpose — to keep the focus on fundamentals before scale. ⏱️ TIMELINE / CHAPTERS 00:00 - Introduction & Series Overview 01:05 - Episode 1 Goal 01:37 - What is a Microservice? 02:28 - Admin is a Role, Not a Service 02:58 - Architecture Before Code 05:01 - Project Setup 07:33 - Video Domain Model 09:13 - In-Memory Repository 13:53 - Interface Extraction 15:30 - Controllers & CRUD APIs 18:12 - HTTP & REST Concepts 26:01 - Dependency Injection 29:59 - Running the Application 31:02 - API Documentation (Scalar) 35:22 - Testing CRUD Operations 38:52 - GitHub Commit 39:32 - Recap & Next Episode 👉 Use the timeline above to jump to any section. 💻 GITHUB REPOSITORY All the code from this episode is available here: 🔗 https://github.com/catchsubu/dotnet-m... This repository will be extended in future episodes — no resets. 🔜 Next Episode: We’ll Dockerize this service so it runs the same way everywhere — without changing the code or breaking service boundaries.