UTEC · .NET workshop
SolarUY
Web platform to monitor solar farms: real-time telemetry, maintenance and AI-powered queries.
- Role
- Team development: panel actions, maintenance and historical queries
- Year
- 2026
- Stack
- C#.NET 10ASP.NET CoreSignalRMySQLNginxDocker
The problem
Programming .NET workshop: build the system of a solar-farm operator, with nodes, inverters and panels, that reads sensor telemetry and shows it instantly. The sensors and their inverters are simulated by a separate service that stands in for the hardware.
What I built
- UI actions to enable or disable a panel and to turn an inverter's grid feed on or off.
- Maintenance task management, linked to a panel or a node, with its history.
- Historical queries over the stored telemetry.
- By the rest of the team: the telemetry collector, real-time notifications with SignalR, Keycloak authentication and natural-language queries through an MCP server.
Technical decisions
Clean Architecture with a dependency-free domain
The domain is plain C# and the application depends on interfaces, such as the sensor client. Swapping the simulator for real hardware doesn't mean touching the rest of the system.
Active/passive high availability
Nginx sends all traffic to one replica and keeps the other as a standby. Since replicas keep no state, no sticky sessions or Redis were needed, and a new version installs without downtime. The limit is documented: a single server.
Work driven by requirements, specs and tasks
Every feature has its requirements document, spec and tasks in the repository, which made it easier to split the work and review deliveries.
What I took away
- Organizing a .NET solution in layers and respecting who may reference whom.
- Designing a deployment with stateless replicas and zero-downtime updates.
- Coordinating a team of five on the same code.