How kubedev/conversao-temperatura works
This is a small Express temperature-conversion app. A client submits a value through the web interface or conversion endpoints; the server calls the conversion functions and returns JSON or renders the result in the page. The server also exposes health/readiness and stress-control routes, and registers request metrics middleware. The README documents port 8080. Source excerpts show these connections; no separate metrics exporter or scrape target is evidenced.
Main entry points: server.js Express server · system-life.js Health and readiness · convert.js Temperature converter · index.ejs Conversion page
Components 8
Web application
- Express server
src/server.js - Temperature converter
src/convert.js - Conversion page
src/views/index.ejs
Operations
- Metrics middleware
src/server.js - Health and readiness
src/config/system-life.js - CPU stress control
src/config/system-life.js - NodeHog
Other components
- Client
Connections 7
- Client → Express server: sends requests
src/server.js - Express server → Temperature converter: calls conversion
src/server.js - Express server → Conversion page: renders page
src/server.js - Express server → Metrics middleware: registers middleware
src/server.js - Express server → Health and readiness: registers routes and middleware
src/server.js - Health and readiness → CPU stress control: routes stress request
src/config/system-life.js - CPU stress control → NodeHog: starts CPU load
src/config/system-life.js