Website:
xirevoa.com
Job details:
Hey, I wanted a serious technical review of my software architecture from a scalability and systems-design perspective.
Current infra:
* Dedicated VPS
* 6 vCPU
* 12 GB RAM
* 200 GB SSD
* Ubuntu 22.04
* ASP.NET Core APIs + MySQL + OpenLiteSpeed
* WPF desktop manager + Android client
* Current architecture document attached
The system currently handles:
* Multi-million vehicle records
* Indexed suffix search (RC/chassis)
* Bulk compressed uploads
* Mobile offline sync
* GPS tracking
* Real-time audit logging
* In-memory caching
* Live users/maps
* Desktop + mobile APIs
What I really want to understand is:
If this system grows to hundreds of millions or even billions of records, what are the biggest architectural problems or bottlenecks we’ll hit first?
Please review things like:
* MySQL limitations at extreme scale
* Whether current indexing strategy will eventually collapse
* RAM pressure from indexes/caching
* Disk IO bottlenecks
* API concurrency limits
* Table growth issues
* Risks with single-server deployment
* Bulk upload design risks
* Whether suffix-search tables are enough long term
* Sync architecture scalability
* Cache invalidation strategy
* Query patterns that may become dangerous
* Logging/audit table explosion
* Any hidden design flaws/security risks/devops concerns
I especially want honest feedback on severe issues that could realistically break the system under massive scale or high concurrency.
For example:
* What happens when rc_info/chassis_info become billions of rows?
* Will JOIN-based searches still survive?
* Would partitioning be enough or would we eventually need sharding/search engines?
* Would Redis/ElasticSearch become mandatory?
* Could uploads lock tables or kill read performance?
* Is MySQL even the correct choice long-term for this workload?
* Is the current VPS architecture fundamentally insufficient?
Please be brutally honest and treat this like a production-scale system review, not a beginner project review.
Click on Apply to know more.