From be7963591a6d8cec352de9664b05f2b766db97ef Mon Sep 17 00:00:00 2001 From: Jamie Hewitt Date: Mon, 17 Jun 2024 13:15:13 +0000 Subject: [PATCH] GITBOOK-2: No subject --- developers/old-infrastructure/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/developers/old-infrastructure/README.md b/developers/old-infrastructure/README.md index 861ebbf1..74c884b1 100644 --- a/developers/old-infrastructure/README.md +++ b/developers/old-infrastructure/README.md @@ -2,6 +2,6 @@ Ocean Protocol is now using Ocean Node for all backend infrastructure. Previously we used these three components: -* [Aquarius](aquarius/) -* [Provider](provider/) -* [Subgraph](subgraph/) +1. [Aquarius](aquarius/): Aquarius is a metadata cache used to enhance search efficiency by caching on-chain data into Elasticsearch. By accelerating metadata retrieval, Aquarius enables faster and more efficient data discovery. +2. [Provider](provider/): The Provider component was used to facilitate various operations within the ecosystem. It assists in asset downloading, handles [DDO](../ddo-specification.md) (Decentralized Data Object) encryption, and establishes communication with the operator-service for Compute-to-Data jobs. This ensures secure and streamlined interactions between different participants. +3. [Subgraph](subgraph/): The Subgraph is an off-chain service that utilizes GraphQL to offer efficient access to information related to datatokens, users, and balances. By leveraging the subgraph, data retrieval becomes faster compared to an on-chain query. This enhances the overall performance and responsiveness of applications that rely on accessing this information.