mirror of
https://github.com/oceanprotocol/docs.git
synced 2024-11-26 19:49:26 +01:00
Merge branch 'master' into feature/architecture_details
This commit is contained in:
commit
7a7bee1897
@ -7,15 +7,15 @@ Before reading this page, you should understand some [Ocean-specific terminology
|
|||||||
|
|
||||||
## Aquarius
|
## Aquarius
|
||||||
|
|
||||||
Aquarius provides an API to an off-chain database ("OceanDB") to store and manage metadata about data assets: the assets listed in that marketplace. Every marketplace must run an instance of Aquarius.
|
Marketplaces run Aquarius to store and manage metadata about the data assets available in their marketplace. It provides an HTTP API for interacting with an off-chain database ([OceanDB](/concepts/components/#oceandb-drivers)).
|
||||||
|
|
||||||
The off-chain database might be MongoDB, Elasticsearch or BigchainDB.
|
|
||||||
|
|
||||||
<repo name="aquarius"></repo>
|
<repo name="aquarius"></repo>
|
||||||
|
|
||||||
## Brizo
|
## Brizo
|
||||||
|
|
||||||
Publishers run Brizo to manage access control to assets on behalf of asset owners or data service providers.
|
Publishers run Brizo to manage interactions with marketplaces and consumers.
|
||||||
|
It interacts with the publisher's cloud and/or on-premise infrastructure.
|
||||||
|
The most basic scenario for a publisher is to provide access to the assets the publisher owns or manages, but [Brizo can do much more](/concepts/architecture/#brizo).
|
||||||
|
|
||||||
<repo name="brizo"></repo>
|
<repo name="brizo"></repo>
|
||||||
|
|
||||||
@ -29,7 +29,7 @@ where the associated blockchain network is running the Ocean Protocol
|
|||||||
|
|
||||||
<repo name="keeper-contracts"></repo>
|
<repo name="keeper-contracts"></repo>
|
||||||
|
|
||||||
See also: [Set Up a Keeper](/setup/keeper/)
|
See also: [Run a Keeper](/setup/keeper/)
|
||||||
|
|
||||||
## Pleuston
|
## Pleuston
|
||||||
|
|
||||||
@ -63,7 +63,7 @@ These drivers are extended from a high-level module implementing OceanDB functio
|
|||||||
|
|
||||||
A [Parity Secret Store](https://wiki.parity.io/Secret-Store): software for distributed key pair generation, distributed key storage, and threshold retrieval. It's used to store asset access-control keys.
|
A [Parity Secret Store](https://wiki.parity.io/Secret-Store): software for distributed key pair generation, distributed key storage, and threshold retrieval. It's used to store asset access-control keys.
|
||||||
|
|
||||||
We have created multiple clients for integrating the Parity Secret Store into Ocean:
|
There are several clients for integrating the Parity Secret Store into Ocean:
|
||||||
|
|
||||||
<repo name="secret-store-client-js"></repo>
|
<repo name="secret-store-client-js"></repo>
|
||||||
<repo name="secret-store-client-py"></repo>
|
<repo name="secret-store-client-py"></repo>
|
||||||
|
2
external/dev-ocean
vendored
2
external/dev-ocean
vendored
@ -1 +1 @@
|
|||||||
Subproject commit 0aeaf4eeadda2901da629ead14748c89d05c26dc
|
Subproject commit dfaf26f53366130da2973a25e596f0ed6fe7b0c7
|
@ -63,8 +63,6 @@
|
|||||||
background: $brand-white;
|
background: $brand-white;
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
||||||
}
|
}
|
||||||
|
|
||||||
.repositoryCategoryTitle {
|
.repositoryCategoryTitle {
|
||||||
|
Loading…
Reference in New Issue
Block a user