How does Nodlin manage the propagation of change?
Nodlin manages the propagation of change across one large connected graph. This presents challenges that need to be managed.
- Events have no payloads
- Loops are expected
- Parallel execution
- Identify ‘hot’ nodes
Is nodlin the right tool for the job?
Where you can use nodlin and when you should not.
- Eventual consistency is OK
- User based workflows
- Where standard data entry forms are OK
Golang API
An API to build your own external agents
- Build your own external agents
- Access internal business systems
- Extend your own applications