Simplify Microservices development with Tye
summary
Project Tye claims to cut the microservice setup bottleneck by detecting .NET solutions, creates Dockerfiles on the fly, and runs services in-process so apps are debuggable without first building containers. It exposes service addresses as SERVICE_URI environment variables, can generate Kubernetes YAML with tie generate, and deploys images to minikube via tie deploy. Demos show a front-end/back-end pair, adding Zipkin and Seq with three lines in tye.yaml, and successful local kubernetes deployment and tracing.
AI-written summary · about
chapters (18)
- 0:00Start
- 2:08Containers
- 6:59New Problems That Come with Moving from a Monolith to a Microservice
- 8:03Declarative Yaml Files
- 15:26Demos
- 24:09Debugging
- 24:48Attach To Process
- 27:51Mini Cube
- 32:21Service Discovery
- 33:17Azure Functions
- 33:32Azure Functions Recipe
- 33:57Deploying with Github Actions
- 35:13Extensions
- 37:56Zipkin
- 38:33Logs
- 40:56Readiness Checks
- 42:48Visual Studio Code Extension
- 44:55Frequently Asked Questions
related talks
42mProject Tye to Tie .NET Microservices
46mProject Tye — Building Microservices in .NET Core
20mProject Tye: Building Developer Focused Tooling for Kubernetes and .NET
01h 05mBuilding Cloud Native .NET Applications with Project Tye
01h 07mNavigating microservices with .NET Core
49mDeveloping microservices applications on the Kubernetes platform
54mAppify your service mess(h)
46mSimplifying Microservices: The art of effortless development