Ad serving system architecture – AWS reference

Key user journeys of ad serving systems.

  1. Serving ad.
  2. Click through.
  3. Publisher registration.
  4. Ad booking.
  5. Targeting
  6. Reporting (often, real time)

The below reference architecture focuses on the first 2.

  • For achieving (3), we may need a dynamo db and another
read the rest. “Ad serving system architecture – AWS reference”
Ad serving system architecture – AWS reference

Designing system topology (Physical Architecture)

Steps in coming up physical architecture.

  1. Identify key subsystems of the solution.
  2. Segregate the subsystems physically depending on the resource requirements.
  3. Using baseline size the hardware per node.
  4. Decide on the # of nodes (Factor in scale & HA).
  5. Decide
read the rest. “Designing system topology (Physical Architecture)”
Designing system topology (Physical Architecture)