Skip to content
Kedgeworks
← All workPublic sectorTeam · Scale

Heading up web development across live bus arrivals, traffic cameras and tfgm.com.

We headed up the web development team across Transport for Greater Manchester's public services and sites.

Transport for Greater Manchester, in public figures
43.7 million
Passenger journeys made on Manchester Metrolink, annually
Department for Transport, accredited official statistics, table LRT0101
Nearly 400 miles
Length of the Key Route Network of Greater Manchester's busiest roads that TfGM manages
Transport for Greater Manchester

These describe the client and the system, not our contribution. What we did is in the sections below.

The situation

Transport for Greater Manchester runs the region's public transport network. Several busy websites and services sit around that, and we headed up the web development team working on them.

The list included live bus arrival times, live traffic camera feeds, the main tfgm.com site, and a number of smaller marketing campaigns around clean air and legislation changes. All of it was based on Node with Angular or React.

The constraint

These services take high loads with extreme peaks, and they have to stay available through them. A large amount of the work went into AWS and Azure for that reason.

They also lean on systems belonging to other people, and one of the things asked of us was that the estate should hold up better when a third party goes down.

What we did

We ran the team across the sites and services, with the availability and load work spread over AWS and Azure.

One project was ours alone from start to finish: redesigning a service and implementing it against the Contentful headless CMS, with new features built on a Redis cache to bring response times down and to make the thing more tolerant of third-party systems failing.

What we are not claiming

The services, the role and the technology are what we can evidence, on loads that are high with extreme peaks. We hold no number for any of it, so neither does this page.

The redesigned service was built to improve response times and resilience. That was the aim rather than a measured result, and we hold no before or after figure, so none is quoted here.

The record also does not say how large the team was, and this page does not guess.

Stack
  • AngularJS
  • React
  • Node.js
  • Handlebars
  • C#
  • AWS Lambda
  • AWS
  • Azure
  • S3
  • Redis
  • Contentful
  • Jenkins
  • Git
Related

Working on something similar?