How bitmovin/pwx-package-template works
Core Framework Layer (Bottom Layer)
a. Structured Concurrency Implementation (left)
b. Effect System (center)
c. Package System (right)
• Context object as a connecting element between these components
Player Building Blocks Layer (Middle Layer)
• Two main effects above the core framework:
a. State Management Effect
b. Network Effect
Player Packages Layer (Top Layer)
• Following packages in a logical group:
• Core Package
• Data Package
• HLS Package
• Network Package
• Presentation Package
• Source Package
• Sources API Package
State Management (Side Panel)
• Atoms:
• SourceStateAtom
• StreamAtom
• Their relationships to the packages
Execution Flow
Special Elements to Include:
Task Execution
• Fork points where tasks can spawn child tasks
Effect System Integration
• How effects connect to external systems
• Browser API integration points
Package Dependencies
• Use a different line style for package dependencies
• How packages can be composed
• Core Framework: Blue
• Effects: Green
• Packages: Orange
• State Management: Purple
• External Systems: Gray
• Double lines: Package boundaries
How error handling and cancelation propagate through the system
Level of Detail:
• Keep the core framework layer detailed but abstract
• Package interactions at a high level
• Specific implementation details only for critical components
• Reactive nature of the system