How handshakesbydc/carpark-info-assignment works
Project type and purpose
• This is a backend‐only service whose responsibilities are:
a. Daily ingestion of a “delta” CSV file of HDB carpark data.
b. Transactional ETL (batch job with rollback on error).
c. Exposing REST APIs (with Swagger docs) for clients to filter carparks, manage favorites.
• There is no front-end code in the repo; clients (e.g. a future web or mobile UI) will call your APIs.
(minimal) file structure
• Top level:
• README.md – spec and tech choices (Spring Boot/Batch, .NET Core, or Node.js)
• hdb-carpark-information-<timestamp>.csv – the daily delta input file
/src
/batch ← Spring Batch jobs or .NET Core background service or Node cron
/api ← REST controllers / route handlers
/service ← business logic (filtering, favorites)
/model ← entity / ORM mappings
/config ← DB, transaction, Swagger
/test ← unit/integration tests
README for additional insights
• Must code a batch job that wraps processing in a single transaction (full-file rollback on error).
• Must expose filter & “add favorite” APIs, with Swagger/OpenAPI annotations.
• Must design for extensibility (e.g. swap CSV→JSON, change DB, injection of new batch steps).
Essential details
• Call out extension points (e.g. replace CSV with JSON feed, swap DB, add authentication).
• Where Swagger UI sits (e.g. a sub‐component of the API module).