// scroll down - nav condenses to the bracket mark · hover it to expand

// case study · higher education - Texas A&M Muster · software engineering + cloud development

One Day. Tens of Thousands of
Simultaneous Users. No Margin for Error.

// the challenge

Muster is not a typical college event.

Muster is a 100-year-old Texas A&M tradition - a solemn Roll Call ceremony where the names of Aggies who died in the past year are read aloud at simultaneous events worldwide. Tens of thousands of people attend in person. Tens of thousands more watch online, simultaneously, on the same day.

The digital platform supporting Muster needed to be ready for that spike. Not approximately ready - actually ready. The kind of ready where you don't refresh the monitoring dashboard every two minutes hoping nothing breaks. The previous experience hadn't always held up. This time needed to be different.

image / video - 4:3

// built for the day that mattered

One Shot A Year. No Room For Almost.

Chat With Us to Learn More →

// in their words

Feedback from executives, public, everyone has been overwhelmingly positive.

Scot W. · Texas A&M Muster

// the approach

High-availability isn't a checkbox - it's a decision at every layer.

ASP.NET Web Application

Server-side rendering for reliability and fast initial loads - critical when tens of thousands of people hit the site at the same time. Not a moment for single-page app cleverness that might fail under traffic.

Azure Functions, Event-Driven

Serverless architecture handles traffic spikes without pre-provisioning for worst-case load. When 200,000 people arrive on the same day, Azure Functions scales to meet them rather than falling over.

Load Testing Before the Deadline

We ran the platform through simulated peak traffic before go-live. This is the part where you find out what your architecture actually does under pressure, not what you hoped it would do.

Built for the Moment

Muster happens once a year. There is no 'we'll fix it in the next release' - the next release is twelve months away. We built with that reality in mind.

// the through-line

A Tradition That Doesn't Get A Second Try.

// the outcome

70k+

simultaneous users on the day that mattered

A platform that held up on the day that mattered.

Tens of thousands of simultaneous users, a serverless-backed high-availability architecture that held through peak load - and a client response that was overwhelmingly positive across executives and public.

HeldThrough peak load

ServerlessHigh-availability stack

PositiveExec + public response

// technologies used