Benefits of Eclipse Che When Developing Microservices Apps
summary
Eclipse Che runs on Kubernetes/OpenShift and can create a workspace from K8s YAML that reproduces a production microservices runtime; demo uses a four-component ToDo app, language servers (Theia), separate build containers identical to CI, and exposes ports/routes. A real bug is found—an endpoint renamed from /users to /user—fixed, rebuilt in a build container, and restarted in the runtime pod so the app returns 200. CI trigger to push images fails due to Jenkins network issues, but local fix and debug inside runtime containers succeed.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:17Eclipse Che
- 2:55Typical Problems
- 4:07Microservices vs Monolithic Apps
- 5:01The Problem with Containers
- 7:13How it Works
- 8:28Workspace
- 9:42IDE
- 10:46Language Servers
- 12:24Built Containers
- 14:37Demo
- 15:12Application overview
- 16:41Factory
- 23:26Authentication API
- 24:56User API
- 26:06Fixing User API
- 28:36Build Containers
- 30:41Factories
related talks
47mEclipse Che and Development of Microservices Apps
24mEclipse Che & the future of Cloud Development Tool
45mEclipse Che
25mIntroduction to Eclipse Che
39mSwapping your IDE in Eclipse Che
45mDevelopment environment as code
06mLeveraging Eclipse Che for developers
05mLightning Talk: Code Kubernetes While You Are Using It
