How A Ground Transit Provider Uses Serverless To Inform Passengers In Real-Time

Tell Us About Your Project

The Challenge

The Company transports 1.5 billion passengers per year in 470 cities across the globe, including Washington D.C., Charlotte, and Waco.

  • They lacked an efficient tool to notify passengers when incidents changed traffic patterns, leading to mistaken communications.
  • They needed a reliable system to manage alerts in real-time and improve customer experience.
  • They didn’t want to increase the team size.

The Solution

Serverless architecture was an obvious choice, for two reasons.

  • It allowed their tech team to remain focused on developing features and not on managing the infrastructure.
  • It offered the flexibility to scale according to the number of users connected.

We developed a tool to help broadcast alerts among various channels and in order to maximize user satisfaction, we understood that they needed to be notified immediately.

However, those communication channels can vary. So, we unified them under one interface to have the ability to publish across all of these channels in real-time.

"When we have a transport service interruption, we must have the power to send the alert, in real-time for it to happen quickly, and a solution that can scale according to demand. Serverless architecture makes it possible to have a worldwide solution, operational with a minimum of interventions and at a lower cost."

VP of IT Marketing

Project Takeaways

The team focused on writing code specific to the business application rather than coding standard features like authentication or message dispatch.

SaaS platforms manage the sending of hundreds of thousands of emails, text messages, and notifications, all triggered by events managed by the serverless architecture.

We built this system leveraging AWS services, but Microsoft Azure and Google Cloud Platform offer similar services.

Serverless Architecture For Real-Time Notifications

The diagram above represents a complete architecture similar to the one created for the client:
  • Each dashed box represents serverless functionalities grouped by domain (e.g., user and authentication, file upload, etc.).
  • Each service is serverless by default and allows for auto-scaling (up and down), hence with no internal dev-ops costs.

Read this Medium article to learn more!

Technologies Used for the Project:

API Gateway

Final Product

No items found.

Get in touch with us.

We're excited to hear about your project.

Contact Us

Discover Our Other Case Studies

Build a Digital Factory
Learn More →
FinTech Chatbot
Learn More →
Accelerate Your Delivery
Learn More →