Ares

Figure 2: Ares interacting with Demeter and Nemesis

Ares - the God of War - is responsible for capturing the data feed from the camera and sending it to an off-site storage and face recognition component (Demeter and Nemesis respectively) (see Fig: 2). Since the system is dynamic, it has to be capable of finding the required components dynamically. To do so, it locates Hermes - the load balancer - and queries for the desired component. Upon receiving the addresses, it registers itself with these two components and starts sending its camera feed (see Fig: 3). On a side note it's worth noting that the camera feed is first processed through motion detection plug-in to save on bandwidth and time-stamped with data and location. Also the camera feed is stored locally, for redundancy reasons.

Figure 3: Ares frames passing through the motion detection engine, handled off by media protocol to be distributed to Nemesis (for face recognition) and Demeter (for storage).

And that is the extent of the Ares functionality. It's rather a dull component, more like an eye in a human - the eye by itself cannot do any processing, but the brain does it.

The transportation mechanism implemented in the work to transfer the camera feed was RTP multicast. More information about RTP is found in the ``RFC 1889''.

It is also modular - if one of the systems from this pool fails, there are many other ones that can take the job over, thought they might not be in the same physical place.