89
edits
Metropolis Microservices/RidgeRun Microservices Demo/Demo Description: Difference between revisions
Metropolis Microservices/RidgeRun Microservices Demo/Demo Description (view source)
Revision as of 20:25, 26 June 2024
, 26 Juneno edit summary
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
#'''Video Storage Toolkit (VST):''' VST NVIDIA microservice auto-discovers ONVIF-S compliant IP cameras, and allows use of custom IP stream as video source. It then allows for video to be stored, played back at various speeds, or paused at any frame | #'''Video Storage Toolkit (VST):''' VST NVIDIA microservice auto-discovers ONVIF-S compliant IP cameras, and allows use of custom IP stream as video source. It then allows for video to be stored, played back at various speeds, or paused at any frame | ||
#'''REDIS: ''' Redis is a message broker that contains all device metadata. VST depends on Redis streams to publish device status change events. DeepStream depends on Redis streams to publish metadata and receive VST camera status events. | #'''REDIS: ''' Redis is a message broker that contains all device metadata. VST depends on Redis streams to publish device status change events. DeepStream depends on Redis streams to publish metadata and receive VST camera status events. | ||
#'''INGRESS: ''' | #'''INGRESS: '''Ingress is the API Gateway to all Metropolis Microservices APIs. It acts as a reverse proxy, where are incoming API requests pass through it, which it then forwards to the appropriate microservice based on path prefix. | ||
{{Review|Add links to the respective MS nvida website|mortigoza}} | {{Review|Add links to the respective MS nvida website|mortigoza}} | ||