Skip to main content

AWS Microservice Architecture

Refer to this file for our raw drawing: https://drive.google.com/drive/folders/1y3xWsHIW5_S1DNRxCdgnh22Kg-ewCGf-?usp=drive_link

Diagram​

Here we explain the top part of the followeing diagram, which correlates to the main traveloka website.

  1. Incoming requests hit our Cloudfront, which:

    • may block the request depending on our WAF configuration,
    • may respond the request from cache,
    • through webrtr Lambda@Egde service, adds the X-TVLK-Target-Service request header depending on the routing configuration in route.yml (see the Cloudfront "behavior" settings to verify this);

  2. Cloudfront hits our ALB, which:

    • reads the path, header, and/or the X-TVLK-Target-Service header to route to the relevant ECS service;

  3. ALB hits product ECS service, which:

    • may call backend API through VPC peering.

Page Data Dependency Diagram