Quick recap from PART-1 Before we explore how to use for document store based interface, have you read the PART 1 of this series yet? Here's the link to in case you want to catch up! IPLD PART 1 In PART 1, we explored the basic concepts of IPLD, how it is used in . We also scratched the surface by building a key-value based database interface on IPFS using IPLD. TLDR: IPFS What We Will Learn from PART-2? 🤔 In PART 2 of the series, we will directly dive into the coding and see how to enhance the functionality to build a document storage (similar to MongoDB and other document databases). If you get stuck in any part or have any queries/doubts, then feel free to reach us out on our discord channel . Here is final shown down 😎 Changing the Data Structures 🛠 In contrast to PART 1, our data structure will be a structure which will be further mapped by a type key. Each document entry we store is of the following format. This is very similar to how you develop : string schemas // SampleStruct defines the benchmark payload
type SampleStruct struct {
	ID     string `json: `
	Name   string `json: `
	Salary string `json: `
} "ID" "Name" "Salary" As shown above, we have defined , which defines three fields representing an employee's data record. This means, we can contain each employee's , and corresponding amount in the structure's instances. SampleStruct ID Name Salary Changing the Way We Track Entries 🧐 Further, we need to manage this relationship in a mapping by its own to facilitate Read or Lookup operations for each employee record. Hence, we update the current mapping as follows: ID scanner := bufio.NewScanner(os.Stdin)

fmt.Println( )
scanner.Scan()
inputID := scanner.Text()

fmt.Println( )
scanner.Scan()
inputName := scanner.Text()

fmt.Println( )
scanner.Scan()
inputSalary := scanner.Text() employeeObject := SampleStruct{ID: inputID, Name: inputName, Salary: inputSalary} "Enter the ID of the employee: " "Enter the name of the employee: " "Enter the salary of the employee: " // Create a struct instance and assign the input values to the corresponding fields Taking User Input 👨‍💻👩‍💻 Now, we can ask users to enter the values for all the three fields as defined in the SampleStruct. Once we have the value for all the three fields (namely ID, Name and Salary), we can initiate an object/instance based on the definition and assign the received values as follows: DocStoreMap[inputID] = employeeObject entryJSON, err := json.Marshal(DocStoreMap) err != {
    fmt.Println(err)
} jsonStr := (entryJSON)
fmt.Println( )
fmt.Println(jsonStr)

start := time.Now() cid, err := sh.DagPut(entryJSON, , )
elapsed := time.Since(start) err != {
    fmt.Fprintf(os.Stderr, , err)
    os.Exit( )
} // Map the struct instance to the mapping // Converting the map into JSON object if nil // Display the marshaled JSON object before sending it to IPFS string "The JSON object of your document entry is:" // Dag PUT operation which will return the CID for futher access or pinning etc. "json" "cbor" if nil "error: %s" 1 The Document-Storage Magic 🔮✨ Once the object is created and the captured values are assigned, we can map the same object in the mapping by its own value. Once the mapping is updated, we can now write it to the Merkle DAG as follows: ID DocStoreMap[inputID] = employeeObject entryJSON, err := json.Marshal(DocStoreMap) err != {
    fmt.Println(err)
} jsonStr := (entryJSON)
fmt.Println( )
fmt.Println(jsonStr)

start := time.Now() cid, err := sh.DagPut(entryJSON, , )
elapsed := time.Since(start) err != {
    fmt.Fprintf(os.Stderr, , err)
    os.Exit( )
} // Map the struct instance to the mapping // Converting the map into JSON object if nil // Display the marshaled JSON object before sending it to IPFS string "The JSON object of your document entry is:" // Dag PUT operation which will return the CID for futher access or pinning etc. "json" "cbor" if nil "error: %s" 1 If you are scratching your heading thinking what does a means & what does function do, then we recommend going through the . DAG DagPut PART 1 of the series We have now successfully written the mapping to the IPLD DAG and a CID may be returned. Yay🎉🎉 A Change in Reading DAGs for Entries Now, we must update our code to read the document from the mapping. In contrast to , the read operation will not be returning a mere single-value. It will be returning the whole JSON document as defined in the schema. Hence, we update the getter function by changing the return type as follows: PART 1 {
	err = sh.DagGet(ref+ +key, &out) } // GetDocument handles READ operations of a DAG entry by CID, returning the corresponding document func GetDocument (ref, key ) string (out SampleStruct, err error) "/" return Now, let us call this getter/read function in as follows: main.go fmt.Printf( , inputID)
start = time.Now()
document, err := GetDocument(cid, inputID)
elapsed = time.Since(start) err != {
    fmt.Println(err)
}

fmt.Printf( , (inputID), (document.Salary)) // Fetch the details by reading the DAG for key "inputKey" "READ: Reading the document details of employee by ID: \"%s\"\n" if nil "READ: Salary of employee ID %s is %s\n" string string As shown above, the is passed with the value which was earlier entered by the user. Based on the ID value, the corresponding document is returned from the mapping. GetDocument ID Once the document is returned, we can parse it as required and print the Salary of the inquired employee. Conclusion We hope you had fun learning how to enhance the code to support document storage. Go crazy and build your own decentralized document database ! 🤪 And here is the link to the full implementation of the code on GitHub. If you get stuck in any part or have any queries/doubts, then feel free to reach us out on our discord channel . About the Authors Ganesh Prasad Kumble Ganesh is an expert in emerging technologies and business strategy. He has co-founded, bootstrapped, mentored several start-ups and initiatives across SaaS, eCommerce, IoT, Blockchain & AI. He is a contributor to several open-source projects including Ethereum and IPFS. He is also a moderator at the Ethereum Research forum. Ganesh is currently leading Platform Innovation efforts at & , building a general purpose business protocol featuring identity management, third party services, distributed compute and immutable storage. Aicumen Technologies Inc. KIP Foundation He is also the author of the book. Hands-on Artificial Intelligence for Blockchain Vaibhav Saini Vaibhav Saini is Co-founder of , & . You can know more about him TowardsBlockchain Dappkit SimpleAsWater here . This article was first published on our open-source platform, SimpleAsWater.com . If you are interested in IPFS, Libp2p, Ethereum, Zero-knowledge Proofs, DeFi, CryptoEconomics, IPLD, Multiformats, and other Web 3.0 projects, concepts and interactive tutorials, then be sure to check out SimpleAsWater .

Fetch

How to Build a Twitter Bot with IPFS Cluster

Hands-on IPLD Tutorial in Golang

Hands-on IPLD Tutorial in Golang: Part 2

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

10+ Resources Every IPFS Developer Should Know About

Designing Fair and Efficient Blockchain Games: Background

Blockchain Scalability Solutions [An Overview]

Cypherpunks: The Activists Behind Decentralized Money

$DAG Will Do To Big Data What Bitcoin Did To Money

10+ Resources Every IPFS Developer Should Know About

Designing Fair and Efficient Blockchain Games: Background

Blockchain Scalability Solutions [An Overview]

Cypherpunks: The Activists Behind Decentralized Money

$DAG Will Do To Big Data What Bitcoin Did To Money

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps