oceanprotocol/docs
1
0
Fork 0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-07-01 06:02:10 +02:00
Code Releases Activity

Finished v1 of the setup/marketplace/ page

Browse Source
This commit is contained in:
Troy McConaghy 2018-11-15 16:38:42 +01:00
parent 15420c225b
commit a978a33220
1 changed files with 33 additions and 41 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

74
content/setup/marketplace.md
View File

@ -1,68 +1,60 @@
---
title: Set Up a Marketplace
description: Build and run a data marketplace in the Ocean network.
description: Set up and run a data marketplace in the Ocean network.
---
If you want to set up and run a marketplace in the Ocean network, then at a technical level, you must:
- Build your marketplace application
- Run:
- Your marketplace application
- Aquarius
- A database for Aquarius
- Parity Ethereum
- Maybe Brizo, unless you are working with others (publishers) running Brizo
- Maybe more?
1. Develop a marketplace application (app).
2. Run your marketplace app in production.
We expand on all of that below.
**Note: In the early days of the Ocean network, there won't be many marketplaces or publishers, so marketplaces will often also act as publishers.**
## Building A Marketplace Application
## Develop a Marketplace App
An Ocean marketplace application (app) is one of the primary ways that end users use the Ocean network. For example, a data scientist could use a marketplace app to see what data sets and data services a marketplace has on offer. They can use the marketplace app to buy access to data sets or services.
An Ocean marketplace app is one of the primary ways that end users use the Ocean network. For example, a data scientist could use a marketplace app to see what data sets and data services (data assets) a marketplace has on offer. They can use the marketplace app to buy access to assets. Publishers make those data assets available.
To build an Ocean marketplace application, you will probably want to use one of the Squid software libraries because they simplify working with the Ocean network.
Currently there are Squid libraries for JavaScript, Python and Java.
As an analogy, squid-py is to Ocean like boto3 is to AWS.
### Easiest Option: Fork Pleuston
Dev example 1: Fork Pleuston (serverless). Use the Docker Compose workflow that Pleuston devs use.
[Pleuston](https://github.com/oceanprotocol/pleuston) is a reference marketplace app written in JavaScript, using React and squid-js (which is like a JavaScript SDK for Ocean).
Pleuston has an Apache v2 license, so you can fork it to make your own Ocean marketplace.
Dev example 2: Build a marketplace with a Python server-side (using squid-py) and a web frontend. Use one of the Squid libraries.
This option is straightforward because you can follow the dev process used by the Pleuston devs. They already have a Docker Compose setup that runs all the other Ocean components needed for testing a marketplace, e.g. Aquarius, a database for Aquarius, a local Parity Ethereum node, and Brizo.
<hr>
Note that Pleuston is a "serverless" app: it runs entirely in the browser and has no server-side component.
Note that you can probably use Docker Compose or similar to run all the other stuff, for now.
<repo name="pleuston"></repo>
Old content to scavenge:
### Other Options for Developing a Marketplace App
## Pleuston
There are many ways to create an ocean marketplace app. For example, you could use one of the existing e-commerce platforms and frameworks (e.g. WooCommerce, Magento, Shopify). Or you could use a lower-level framework like Django or Vue.js. The main consideration is that you should probably use a programming language with an existing Squid library.
Pleuston is an example Ocean marketplace written in JavaScript using React and Redux.
It uses the squid-js library to interact with Ocean network services, such as Keepers, Brizo nodes, Secret Stores, and your own Aquarius node.
<repo name="squid-js"></repo>
<repo name="squid-py"></repo>
<repo name="squid-java"></repo>
Pleuston runs entirely in the browser, i.e. Pleuston has no server-side part. It communicates directly with Keepers etc.
Note: There are examples of how to use squid-py in the [Tutorials](/tutorials/introduction/). squid-py is to Ocean like boto3 is to AWS.
You _could_ build an Ocean marketplace with a browser-side frontend and a server-side part.
For example, the server-side part could be written in Python and it could use the squid-py library.
Of course, you could always write your own Squid library in the language of your choice. A squid-java library is in development.
Currently, there is no explicit example of how to do that, but there are examples of how to use squid-py, e.g. from IPython running in a Jupyter notebook.
See the Tutorials section.
## Run Your Marketplace App in Production
You could even write an entirely server-side marketplace with a command-line interface, but let's not get carried away.
Before running your marketplace app in production on the Ocean Mainnet, you may want to test it on the Ocean Testnet.
The Ocean Testnet is similar to the Ocean Mainnet.
The main difference is that there is less risk on the Ocean Testnet.
Note: There's also a squid-java library but it's currently not as full-featured as squid-js and squid-py.
**Note: At the time of writing, the Ocean Mainnet hadn't gone live yet, but the Trilobite Testnet was about to go live.**
## Aquarius
Some technical differences between local testing and connecting to a live external test/mainnet are:
Aquarius is an application used by Marketplaces to store, update, read and delete metadata about assets. The Squid libraries all know how to talk to Aquarius, so you don't need to think about it or its API too much. You just need to make sure you have Aquarius running on a server somewhere.
- Local Keeper nodes (Parity user nodes) must connect to the live network of Keepers.
- Your Aquarius and Brizo instances must connect to the live Ocean Secret Store network.
TODO: Add instructions here.
Of course, there are many other things that must be handled for live production apps:
## Database for Aquarius
- Security of the infrastructure where the software is running
- Monitoring
- Log aggregation, storage and search
- Handling crashes or other faults
At the time of writing, Aquarius worked with three databases:
- MongoDB
- Elasticsearch
- BigchainDB
TODO: Outline the pros and cons of each database.
Each of those is a big topic beyond the scope of these docs.