High-traffic SSR marketplace
A production marketplace where pages failed intermittently and memory kept growing. This is the part I worked on, as the frontend developer in the team.
- Engagement
- Since 2024, ongoing
- Role
- Frontend developer in the team
- Scale
- High-traffic production marketplace
The problem
Pages failed intermittently in production, and server memory kept growing until the servers had to be restarted. The issues did not show up locally.
The problems showed up in the frontend first, but the causes were not only there. I worked on it together with the rest of the team: backend and DevOps engineers and the CTO.
What I did
My part of the work:
Added logging to see what was happening
Added logs for requests and memory usage, in the frontend code and on the server, to get a clear picture of what was happening on the live platform.
Found and fixed a memory leak
Used that data to track down a memory leak and fix it, and fixed server-side rendering errors so that a failing page does not affect the rest of the app.
Frontend side of a backend migration
Moved the frontend to a new backend architecture while the site kept serving users, with no downtime.
Ongoing frontend work
I still work on the product, building new features and keeping the existing ones stable.
The outcome
What changed:
- The memory leak was fixed and the intermittent page failures stopped.
- The migration to the new backend went through with no downtime.
Stack
React with server-side rendering, and Node.js. The problems showed up in the frontend, but finding them meant looking at the whole platform, not just one layer.
Does this sound like your app?
If your app has a similar problem, an audit is a low-risk way to start: read-only access, a written report and a prioritized list of fixes.