The Next Generation
“The Grand Challenge of Conviva:
Device Dominance”
– Hui, CEO
-
Too Many Devices
-
Too Many Platforms on Each Device
-
High Effort to Add a New Device Support
-
High Effort to Maintain an Existing Device
Today’s Architecture
Monitor
1. Observe selected APIs
2. Listen to selected events
Proxy
Convert properties and events
to
Conviva Data Model
Insights Client Lib/SDK
Backend
Conviva
Computation
Layer
CWS
Proxy - Too Complex
Monitor
1. Observe selected APIs
2. Listen to selected events
Proxy
Convert properties and events
to
Conviva Data Model
Insights Client Lib/SDK
Backend
Conviva
Computation
Layer
CWS
Move Proxy to Backend
Monitor
1. Observe selected APIs
2. Listen to selected events
Proxy
Convert properties and events
to
Conviva Data Model
Insights Client Lib/SDK
Backend
Conviva
Computation
Layer
Raw
Info
Monitor Logic is Hardcoded
Monitor
1. Observe selected APIs
2. Listen to selected events
Proxy
Insights Client Lib/SDK
Backend
Conviva
Computation
Layer
Raw
Info
Make Monitor Configurable
Monitor
Monitor purely based on config
Proxy
Insights Client Lib/SDK
Backend
Conviva
Computation
Layer
Monitor Configuration Engine
What/How to Monitor
Raw
Info
TNG Architecture
Monitor
Monitor purely based on config
Proxy
Insights Client Lib/SDK
Backend
Conviva
Computation
Layer
Monitor Configuration Engine
What/How to Monitor
Raw
Info
Client-side Feasibility
| Platform | Library | Notes |
|---|---|---|
| Javascript | Ramda | Will Demo! |
| iOS | Ramda | |
| Android | Reflection, Lambda Expression | |
| Silverlight - C# | Rx |
- Configuration only contains a set of strings, therefore, there is no security concerns.
Impacts and Achievements
- Reduce client complexity
- Shorter initial development cycle.
- Simplify integration by removing Conviva data model from client.
- Surprise: it’s a pleasant one, Device Engineers will actually code mostly in the backend!
- Configurable clients
- Easy to adjust client behavior when platform upgrades
- Easy to adjust client behavior to add new features
