...
Collections of picos are used to create models of interacting entities in the Internet of Things. Picos communicate by sending events to or making requests of each other in anActoran actor-like manner. These communications are point-to-point and every pico can have a unique address, shared by no one else, to any other pico to which it communicates. Collections of picos were used in architecting the Fuse connected-car system with significant advantage.
...
The event-query API is a name I gave the style of interaction that picos support. Picos don't implement RESTful APIs. They aren't meant to. As I explain in Pico APIs: Events and Queries, picos are primarily event-driven but also support a query API for getting values from the pico. Each pico has an internal event-bus. So while picos interact with each other and the world in a point-to-point Actor modelactor model, internally, they distribute events with a publish and subscribe mechanism. More
...
The pico engine is a host or container engine for picos. A given instance of the pico engine can host any number of picos. The pico engine makes picos work. Pico Engine is an open source project, hosted on GithubGitHub.
KRL rulesets are usually hosted online. Developers register the URL with a pico engine to create a ruleset ID or RID. A given ruleset can be installed in any number of picos. When the pico runs, the engine gets the ruleset source, parses it, optimizes it, and executes it.
...