How jesusdelri0/apis-proyecto works
This repository provides a sensor-records API: a client calls the FastAPI gateway, which forwards list or ID lookups to the matching humidity, pressure, sensors, or temperature service. Each service queries its corresponding PostgreSQL table and returns records. The four services are separate domain endpoints, not a demonstrated ingestion pipeline. The service and gateway relationships are visible in the sampled source; database setup files are present in the tree, but their contents were not sampled.
Main entry points: gateway/main.py Gateway Routes · init.sql PostgreSQL Records · humidity/main.py Humidity API · pressure/main.py Pressure API
Components 7
API Gateway
- Gateway Routes
gateway/main.py
Sensor Services
- Humidity API
humidity/main.py - Pressure API
pressure/main.py - Sensors API
sensors/main.py - Temperature API
temperature/main.py
Data Storage
- PostgreSQL Records
db/init.sql
Other components
- API Client
Connections 9
- API Client → Gateway Routes: requests
gateway/main.py - Gateway Routes → Humidity API: forwards humidity
gateway/main.py - Gateway Routes → Pressure API: forwards pressure
gateway/main.py - Gateway Routes → Sensors API: forwards sensors
gateway/main.py - Gateway Routes → Temperature API: forwards temperature
gateway/main.py - Humidity API → PostgreSQL Records: queries humidity
humidity/main.py - Pressure API → PostgreSQL Records: queries pressure
pressure/main.py - Sensors API → PostgreSQL Records: queries sensors
sensors/main.py - Temperature API → PostgreSQL Records: queries temperature
temperature/main.py