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 23:32, 9 May 2022
, 9 May 2022→Decoupling Interfaces
| Line 18: | Line 18: | ||
== Decoupling Interfaces == | == Decoupling Interfaces == | ||
Interface modules are responsible for establishing the connection between framework components and custom application modules. Thanks to these blocks, any type of design dependency on custom | Interface modules are responsible for establishing the connection between framework components and custom application modules. Thanks to these blocks, any type of design dependency on custom applications is eliminated. In addition, this agnostic design allows the project to decouple and rearrange components, without affecting its functionality. | ||
== Custom Application Specific == | == Custom Application Specific == | ||
As seen in the diagram, custom application blocks represent any type of implementation or specific technology that can be included in the system design. The diagram presents some examples, however, the DeepStream Reference Designs project is not limited to those particular modules. The possibility of extending the design and incorporating specific business rules for each application is what gives this project a high degree of flexibility. | As seen in the diagram, custom application blocks represent any type of implementation or specific technology that can be included in the system design. The diagram presents some examples, however, the DeepStream Reference Designs project is not limited to those particular modules. The possibility of extending the design and incorporating specific business rules for each application is what gives this project a high degree of flexibility. | ||