This image shows a simplified data flow for the Red5 Pro web party and broadcast connection process.

1. Data flow for authenticated watch party users:
   1. Authenticated users register for events and optionally create a watch party web stream on the watch party servers and invite friends to join them in a watch party.
   2. User account information and event details are stored in a conference database in a fully managed Oracle MySQL Database Service cluster.
2. Data flow for broadcasters:
   1. Broadcasters create a watch party live stream for the event on the watch party servers which is then managed by a stream manager server.

      Broadcasters send their event feed to a transcoder, which transforms the feed into different variants (Adaptive Bit Rate streams of various resolutions) or directly to the origin servers if transcoding is not needed.

   2. Watch party stream data is stored in a stream database in a fully managed Oracle MySQL Database Service cluster.
   3. Stream managers direct broadcaster traffic to origin servers and subscriber traffic to edge servers. The stream managers manage autoscaling of origin servers and edge servers to support the changes in load.
   4. The web stream is delivered to watch party users.
   5. The live stream is delivered to edge servers.