BigchainDB transactions

The first thing to understand about Resdb is how we structure our data. Traditional SQL databases structure data in tables. NoSQL databases use other formats to structure data such as JSON and key-values, as well as tables. At Resdb, we structure data as assets. We believe anything can be represented as an asset. An asset can characterize any physical or digital object that you can think of like a car, a data set or an intellectual property right.

These assets can be registered on Resdb in two ways.

1. By users in CREATE transactions.
2. Transferred (or updated) to other users in TRANSFER transactions.

Traditionally, people design applications focusing on business processes (e.g. apps for booking & processing client orders, apps for tracking delivery of products etc). At Resdb, we don’t focus on processes rather on assets (e.g. a client order can be an asset that is then tracked across its entire lifecycle). This switch in perspective from a process-centric towards an asset-centric view influences much of how we build applications.

BigchainBD License

• Apache License 2.0

Making client requests Asyncronous

Comparison between different ways to send send request

asyncio - an introduction

more asyncio

aiohttp

Remaining tasks

1. test the sdk
2. Implement verify transaction on resdb client
3. A solution for storing secrets
4. Build the APIs for NFT marketplce

~ 3 weeks