Bárbara M. Peres · Full-Stack Developer & AI Engineer, Portugal
The interactive version of this page did not load. Reloading usually fixes it. Otherwise the links below still reach me.
Full-Stack Platform + HA Infra · 2023–2024
Lost & Found platform load-tested to 10,000 concurrent users
A full-stack Lost & Found platform with auctions, built by a team of six; my part was the front end, the database layer and a share of the REST endpoints. It was deployed at returnity.info on a fault-tolerant Google Cloud architecture. Laravel 10 REST API with 81 endpoints, ~65 Bootstrap HTML pages, four roles (owner, police, administrator, bidder), and a full object lifecycle: report → search/compare → claim → delivery, or auction → bid → payment → transfer. Network side: 2 Nginx load balancers (Keepalived/VRRP, floating IP, active-passive), 2 Nginx web servers (active-active), 2 MySQL VMs in Master-Master with API-side middleware failover, auto-scaling via gcloud snapshots, TLS via Let's Encrypt, Google OAuth 2.0 sign-in. Load-tested in Locust up to 10k concurrent users.
Laravel 10 · PHP 8.1 · MySQL · Bootstrap · Nginx · Keepalived/VRRP · GCP · OAuth 2.0 · Let's Encrypt · iptables · Locust · OWASP ZAP · GitHub Actions · Master-Master Replication · REST API
Build a production-grade Lost & Found platform (owners report missing objects, police register objects physically handed in at police stations, an administrator manages auctions of unclaimed items, and bidders compete for them) on a real domain and a network architecture that survives load-balancer and database failures.
Application (PTI): Laravel 10 REST API (PHP 8.1), 81 endpoint operations across 69 paths covering users, police stations, police accounts, lost/found items, categories, comparison, auctions, bids, payments and notifications, documented in OpenAPI/Swagger (ReturnityApi.yaml). ~65 static HTML pages on Bootstrap + FontAwesome for the four role-specific frontends (owner, police, admin, bidder). Google OAuth 2.0 + People API for sign-in, Google Maps JavaScript API + Geocoding API for object/user location.
Infrastructure (PTR): Deployed on GCP at returnity.info via Cloud Domains + Cloud DNS. 2 Nginx LB VMs in active-passive Keepalived + VRRP with a floating IP and a takeover.sh script (Least-Connections algorithm), 2 Nginx web-server VMs (Debian 12, e2-standard-2, us-central1) in active-active Keepalived, 2 MySQL VMs in Master-Master replication with an API .env-driven middleware that fails over automatically (database-1 → database-2). Bash auto-scaling scripts spawn a snapshot-based VM when CPU or RAM > 80% and tear it down on recovery. iptables firewall isolates the DB to the API IP and blocks known malicious IPs. TLS via Let's Encrypt + Certbot.
Validated with Postman + Swagger acceptance tests, OWASP ZAP scan (17 alert categories), GitHub Actions api-test.yaml CI, and Locust load tests.
Three parts of it were mine: the front end, the database layer and a share of the 81 REST endpoints. The front end is the four role-specific interfaces, for owners, police, administrators and bidders, in about 65 Bootstrap pages.
The front end held 10,000 concurrent users on the fault-tolerant GCP setup (Nginx load balancers in Keepalived failover, the web tier behind them, Master-Master MySQL) at a flat error rate, though not at speed: the 95th percentile passed 80 seconds. The API tier did not hold: at the same load it starts shedding requests. Both cap out at a fixed throughput rather than degrading gently, and past that ceiling extra users only queue, so the API's 95th percentile goes from 6.6 seconds at 2,500 users to over a minute at 10,000. Finding that ceiling was the point of running the tests.