Before reading this page, you should understand some Ocean-specific terminology.
See also: Run a Keeper
There are several clients for integrating the Parity Secret Store into Ocean:
🔑 Parity Secret Store Python Client
🔑 Parity Secret Store Java Client
Marketplaces run Aquarius to store and manage metadata about the assets available in their marketplace. It provides an HTTP API for interacting with an off-chain database (sometimes called “OceanDB”).
Aquarius supports several options for the off-chain database (OceanDB), including Elasticsearch and MongoDB. One can add support for another off-chain database by creating a new driver similar to the existing OceanDB drivers.
There is also a BigchainDB driver but it hasn’t been maintained.
You can create your own OceanDB drivers by extending on the
Publishers run Brizo to manage interactions with marketplaces and consumers. It interacts with the publisher’s cloud and/or on-premise infrastructure.
Brizo communicates with the Events Handler to deal with Keeper Contracts events.
The Events Handler monitors Service Execution Agreement (SEA) events and acts as a provider agent to grant access and release rewards for the publisher/provider. This is a critical part in the process of consuming data sets in the Ocean Protocol network.
Every provider in the network must run some sort of an events handler to be able to fulfill the access condition of an
Access service in a Service Execution Agreement.
Brizo supports several options for file storage, including Azure Storage, Amazon S3 and on-premise storage. One can add support for another file storage option by creating a new driver similar to one of the existing Osmosis drivers.
💧Osmosis Azure Driver Implementation 💧Osmosis AWS Driver Implementation 💧Osmosis IPFS Driver Implementation 💧Osmosis On-Premise Driver Implementation
💧Osmosis Azure Driver Implementation
💧Osmosis AWS Driver Implementation
💧Osmosis IPFS Driver Implementation
💧Osmosis On-Premise Driver Implementation
You can create your own Osmosis drivers by extending on the
Client libraries used by applications (such as Pleuston or Jupyter notebooks) to interact with Ocean components, including Keepers, Aquarius nodes, Brizo nodes, etc.
For more information, see the blog post about Commons Marketplace.
The Commons Marketplace is also the default frontend when running a full Ocean network locally with Barge.