Background Information

Architecture

Fuse is not built using a traditional layered Web architecture. Rather, it is built using a new architecture that supports better control over data for owners. 

This architecture uses persistent compute objects, or picos, as it's fundamental building block and supports an unhosted or personal cloud application architecture (PCAA). As with anything different, there are opportunities and challenges. 

The following articles provide some background on picos and PCAAs. 

• Fundamental Features of Persistent Compute Objects

• Pico APIs: Events and Queries

• Introducing Forever and Personal Cloud Application Architectures

• Fargo and Personal Cloud Application Architectures

Events and Queries

Fuse uses an event-query API rather than a strictly RESTful API. The documentation will present events like so:

<event domain>:<event type>

where the event domain and type are separated by a colon. Most event also use event attributes which will be presented as name-value pairs. 

Events are raised to Fuse by encoding them in HTTP. The Sky Event API describes how this encoding is done. The JavaScript SDK includes a function, CloudOS.raiseEvent(), and support structure for encoding the event with its attributes and performing an HTTP POST.

Queries will be presented like so:

<query domain>:<query name>(<param0>, <param1>,...,<paramn>)

Queries are raised to Fuse by encoding them as HTTP. The Sky Query API describes how this encoding is done. The JavaScript SDK includes a function, CloudOS.skyCloud(), that encodes a query with its parameters and performs an HTTP GET. 

This table provides the query domains for the primary service modules that make up the overall Fuse system. There is a development and a production domain.