Skip to content

Quarks Providers

Dan Debrunner edited this page Feb 27, 2016 · 1 revision

Quarks Providers

Overview

A provider provides the capability to execute Quarks applications by providing implementations of various Quarks APIs. Currently two providers are implemented:

  • DirectProvider - a minimal provider that provides the topology api direct execution using the etiao runtime. This is the provider expected to executed on devices.
  • DevelopmentProvider - a development provider that is aimed at application developers, typically developing the core of an application on a laptop or workstation. It extends DirectProvider to add:
  • a development console that visualizes running applications
  • control service that registers control MBeans in the platform JMX server
  • automatic addition of metrics to submitted applications.

Additional providers may be added in the future to address common requirements.

Clone this wiki locally