CASE STUDY / ASSET MANAGEMENT API
PatrimonioGest API
REST API development for modernizing municipal asset management with maintainable backend services and domain-specific depreciation logic.
System flow
02
Project Snapshot
Responsibilities, stack and scope for the REST API layer of a municipal asset platform.
- Developed REST API modules with Node.js, Express and TypeScript.
- Implemented authentication, validation, documentation and file handling.
- Supported PostgreSQL workflows and annual asset depreciation rules.
03
The challenge behind the project
The client managed municipal assets through a legacy platform used to register and administer public property such as land, buildings, vehicles and other assets.
The existing system had become difficult to maintain and extend, limiting future functionality and technical evolution. The API work helped establish a more stable backend foundation.
- Municipal asset categories required accurate domain understanding.
- Annual depreciation rules influenced backend behavior.
- Future integrations needed a clearer API foundation.
04
Translating municipal rules into backend behavior
The approach gathered formulas and criteria from domain experts, translated them into business rules and validated the API behavior against expected results.
System flow
05
Architecture & Technical Decisions
Layered REST API built with Node.js, TypeScript, Express and TypeORM over PostgreSQL.
Frontend Scope
No documented frontend ownership; Wilhen’s contribution focused on the REST API layer.
REST API Layer
Node.js, Express and TypeScript endpoints with JWT authentication.
PostgreSQL Data
TypeORM entities and persistence for municipal asset workflows.
Docs & Integration Readiness
Swagger documentation, validation, file handling and Cloudinary integration.
06
Key Challenges
The key documented challenge was translating annual depreciation criteria into reliable backend rules.
- 01 — Understand which municipal assets were subject to depreciation.
- 02 — Translate client formulas into application behavior.
- 03 — Validate depreciation logic against expected criteria.
07
My Contribution & Solution Highlights
Wilhen’s contribution centered on API implementation and domain-rule support, not frontend ownership.
- Built REST API modules using Node.js, Express, TypeScript and TypeORM.
- Implemented JWT authentication, input validation and Swagger documentation.
- Integrated PostgreSQL, document/image handling and Cloudinary support.
- Supported annual asset depreciation logic based on client criteria.
System flow
08
Business Impact
Documented impact is qualitative: maintainability, workflow standardization and continuity, with no verified numeric metric.
- Improved maintainability
- Standardized municipal asset workflows
- Supported future integrations
- Maintained operational continuity
09
Lessons learned
This project reinforced the importance of understanding domain-specific rules before encoding them into software.
- Municipal administrations manage diverse asset categories with different rules.
- Annual depreciation can directly shape software behavior.
- Administrative and financial criteria must guide technical decisions.
10
Next Evolution
Continue supporting new functionality, maintainability and future integrations as asset-management needs evolve.
LET’S TALK