Uber like App on AWS Serverless Cloud Architecture

Author

Govardhana M K
November 06, 2025

In partnership with

TechOps Examples

Hey — It's Govardhana MK 👋

Welcome to another technical edition.

Every Tuesday – You’ll receive a free edition with a byte-size use case, remote job opportunities, top news, tools, and articles.

Every Thursday and Saturday – You’ll receive a special edition with a deep dive use case, remote job opportunities, and articles.

👋 👋 A big thank you to today's sponsor THE DEEP VIEW

Become An AI Expert In Just 5 Minutes

If you’re a decision maker at your company, you need to be on the bleeding edge of, well, everything. But before you go signing up for seminars, conferences, lunch ‘n learns, and all that jazz, just know there’s a far better (and simpler) way: Subscribing to The Deep View.

This daily newsletter condenses everything you need to know about the latest and greatest AI developments into a 5-minute read. Squeeze it into your morning coffee break and before you know it, you’ll be an expert too.

Subscribe right here. It’s totally free, wildly informative, and trusted by 600,000+ readers at Google, Meta, Microsoft, and beyond.

👀 Remote Jobs

📚️ Resources

Looking to promote your company, product, service, or event to 56,000+ Cloud Native Professionals? Let's work together. Advertise With Us

🧠 DEEP DIVE USE CASE

Uber like App on AWS Serverless Cloud Architecture

Apps like Uber, Lyft, or Ola have made real-time ride matching feel effortless. You tap a button and within seconds you're paired with a nearby driver, watching them move toward you on the map.

But behind that smooth experience is a system handling real-time location updates, distributed coordination, payments, state transitions, and user communication, all under unpredictable traffic.

In this edition, I’ll break down how I designed a fully serverless backend for a ride-hailing platform, focusing on scale, reliability, and real-time responsiveness.

Here, I’ve created the design document covering the components and the end-to-end flow.

Download a copy of this image here for future reference.

Architecture Diagram:

Here is the complete architecture designed purely with AWS serverless services and integrators. Let's dig into the most crucial core of this.

1. User Auth

This part seems straightforward but has serious implications on user security, API protection, and long term flexibility.

  • Cognito offloads user management and token handling, keeping your Lambdas stateless and focused.

  • API Gateway uses Cognito Authorizers to validate the JWT before invoking the Lambda.

  • Decoupling auth this way gives flexibility to change auth logic without impacting core business flows.

Blind Spots to Watch

  • API Gateway endpoints without authorizers can be exposed unintentionally. Always audit.

  • Misconfigured user pools can allow weak passwords or open sign-ups if defaults are not overridden.

  • Mobile apps must refresh and handle token expiry correctly to avoid authentication drift.

  • Logging anything related to user identity without masking tokens can become a liability.

🔴 Get my DevOps & Kubernetes ebooks! (free for Premium Club and Personal Tier newsletter subscribers)

Upgrade to Paid to read the rest.

Become a paying subscriber to get access to this post and other subscriber-only content.

Already a paying subscriber? Sign In.

Paid subscriptions get you:

  • • Access to archive of 200+ use cases
  • • Deep Dive use case editions (Thursdays and Saturdays)
  • • Access to Private Discord Community
  • • Invitations to monthly Zoom calls for use case discussions and industry leaders meetups
  • • Quarterly 1:1 'Ask Me Anything' power session