ITU
Back to Blog
Platform Modernization · [2026-10-08] · 2 min read

Architectural decisions behind a high-traffic platform

Constraints that show up after a few hundred thousand monthly visits, and the ones that do not.


// Article
476
Words
2
Tags
2 min
Read Time

// Content

Traffic is not a personality. It is a set of constraints that show up when a page is no longer a private demo.

I do not treat 300,000 monthly visits as a trophy. I treat it as a reason to be boring: caching that is explicit, assets that do not surprise the browser, data access that you can explain, and logs you can use when a release is bad.

The AvenFort UI modernization sits on that traffic. Crowbar’s quote and tracking portal is smaller, but the same questions apply the moment sales starts living in the app.

Decisions that compound

Rendering and assets. The first visit is a budget. A modernization that pulls a new framework for every page will look fine in staging and heavy in the field. I want a default page that is cacheable, a small set of entry points, and no “just one more” client-side fetch on the critical path unless the data is actually personal.

Data access. List endpoints that return the world will work until they do not. Pagination, indexes, and a cap on what a page may request are architecture, not polish. If the UI needs five round trips to draw a dashboard, the API is the product — fix that before you restyle the chart.

Caching. Cache what is public and versioned. Do not cache what is tenant-specific unless you can name the key and the invalidation. A CDN in front of a personalized app is not a strategy. It is a way to leak.

Observability. High traffic without traces is a rumor mill. I want deploy id, route, and latency on the hot paths, and a way to turn a user report into a request, not into a guess.

Decisions that do not

Rewriting the database because the design system changed. Moving hosts because the new CSS framework prefers a different region. Adding a second CMS “for marketing” that serves the same URL with a different title tag.

Those feel like architecture meetings. They are usually taste. Taste is allowed on a marketing page. It is not a reason to dual-write orders.

I also do not chase a number I cannot defend. If I cannot show the visit count from analytics, I do not put it on a slide. The 300,000 figure on this site is the one I will stand behind. Everything else is a constraint, not a metric.

What this asks of a lead

You sequence the work so the team can still ship. You refuse PRs that make the hot path worse in exchange for a cleaner folder. You keep one URL, one canonical, one intent — which is also SEO, and which is another note.

The platform is the set of decisions that still hold when you are not in the room. If they only hold because you remember them, write them down.

// Work With Me

Need a lead who has lived with real traffic?

I am modernizing a UI on a site with more than 300,000 monthly visits. Recruiter conversations welcome.

Contact

// Share

Share this article with your network


Ecosystem