583
edits
DeepStream Reference Designs/Project Architecture/High Level Design: Difference between revisions
DeepStream Reference Designs/Project Architecture/High Level Design (view source)
Revision as of 17:47, 17 May 2022
, 17 May 2022→Custom Action
| Line 75: | Line 75: | ||
=== Custom Action === | === Custom Action === | ||
This type of module represents the actions that will be executed once the business rules established by the policies are activated. As with the previous component, the user has complete freedom on what type of actions he wants to implement and what tools he will use for its development. | |||
It is important to mention that different policies will trigger different actions. In a parking lot example, you can have several policy-action relationships like: | |||
* If a car enters the parking lot a picture is taken | |||
* If a car is detected in any zone, the event is logged to a database | |||
* If a car is detected in any zone, the event is displayed in a dashboard to the user | |||
* If a car is flagged as suspicious, a video recording will be triggered | |||
Most of them can be recycled for other applications. Again, being decoupled in independent modules and protected by the action interface allows very custom actions without interfering with the overall architecture. | |||
=== Custom Config=== | === Custom Config=== | ||