Problem vs Nodlin - The Key Concept
The problem that Nodlin solves
- Companies run many tools
- Nodlin saves manual effort (cut/paste, import/export)
- Nodlin reduces lag between data and insights
Change propagation and design implications
How changes are propagated from one node to another and considerations for node design.
- Companies run many tools
- Nodlin saves manual effort (cut/paste, import/export)
- Nodlin reduces lag between data and insights
Developer Mental Model
Nodlin is for reactive derivation of business state, not iterative simulation.
- Propagation of change follows the full dependency closure
- Recomputation cost is controlled through deduplicated invalidation and hot-node coalescing
- Nodlin is not a simulation engine
The nodlin ‘Agent’
Where the logic is defined in nodlin
- Define your own external agents
- Integrate with internal systems & other datasources
- Connect and utilise to capabilities across agents
The nodlin ‘Node’
What makes up a node?
- Any data points you wish to model
- A form to capture data points
- An image, summary, actions, FYIs
A nodlin ‘perspective’
View a nodlin in different ways
- Choose the appropriate visual to represent your data
- Flexible and customisable
Organisation principles
Folders, tags, nodlins, nodes, actions & FYI’s
- Multiple methods of categorising your data
- Enhance your organisation