Skip to content

Latest commit

 

History

History
16 lines (9 loc) · 1.34 KB

ArchitecturalModel.md

File metadata and controls

16 lines (9 loc) · 1.34 KB

PART 2 – UNDERSTANDING THE FR8 ARCHITECTURAL MODEL

Go to Contents

Hubs and Terminals: Where Work Gets Done

Fr8 Plans are assembled out of individual Activities. The Web Services that host and process Fr8 Plans are called Fr8 Hubs. The Fr8 Company operates a major Hub at www.fr8.co, but anyone can run their own Hub by creating a web service that supports the Fr8 Hub Specification.

When a Hub is ready for the next Activity in the Plan to be executed, it makes a call to the Activity’s Fr8 Terminal. Terminals carry out Activity processing. Many Terminals focus on a single web service. For example, in the Plan above, the Activity “Get Google Sheet Data” will be executed by the Fr8 Google Terminal, the Activity “Send DocuSign Envelope” will be executed by the Fr8 DocuSign Terminal, and the Activity “Loop” will be execute by the Fr8 Core Terminal.

Fr8 Workflow

Main Flow

Part 3 – The Fr8 Data Model

Go to Contents