Building CityScale 🏙️ — Engineering a City-Scale Logistics System

What started as an idea to simulate urban parcel distribution turned into CityScale — a full-stack logistics platform for modelling deliveries, locations, routes, and distribution workflows.
🏗️ Architecture
The current stack includes:
Java + Spring Boot — backend & REST APIs
PostgreSQL — persistent data storage
JPA/Hibernate — ORM and entity management
Frontend + Maps — visualizing locations and logistics data
The system follows a layered backend structure:
Controller → Service → Repository → Database
This separation keeps API handling, business logic, and persistence independent.
🧠 The interesting part
The core challenge is translating a real-world logistics problem into software.
Given multiple parcels, locations, and routes, the system needs to model relationships between them and eventually support efficient distribution and route decisions.
That means thinking beyond:
request → database → response
and instead considering:
Data modelling → Business rules → Algorithms → APIs → Visualization
I've also had to deal with the less glamorous side of engineering — database configuration, API integration, debugging, and discovering that a perfectly reasonable-looking configuration can completely destroy your evening. 💀
CityScale is still under development, but I'm using it to explore how DSA concepts and backend engineering come together in a real system.
More technical deep-dives coming soon.
Build → Break → Debug → Optimize. 🚀
