{"id":3177,"date":"2020-04-12T16:24:51","date_gmt":"2020-04-12T15:24:51","guid":{"rendered":"https:\/\/www.itersdesktop.com\/?p=3177"},"modified":"2020-05-10T10:01:26","modified_gmt":"2020-05-10T09:01:26","slug":"how-to-build-and-render-data-in-json-format-with-grails","status":"publish","type":"post","link":"https:\/\/www.itersdesktop.com\/vi\/2020\/04\/12\/how-to-build-and-render-data-in-json-format-with-grails\/","title":{"rendered":"How to build and render data in JSON format with Grails"},"content":{"rendered":"\n

Nowadays, an awful lot of web based applications are using JSON<\/a> as a principal data to load and render information rapidly. While some applications store data into persistence volume as JSON string, the others still use relational databases as the primary storages. Loading data from these relational databases from backend, then building JSON objects and sending them to frontend are all things a web developer often does on a daily basis.<\/p>\n\n\n\n

In this post, I will show you how to build JSON objects and pass them to client, such as JavaScript where you have to use the data for displaying or reprocessing.<\/p>\n\n\n\n

To ease reading and absorbing the knowledge I am writing here, let’s play with a simple project. The project aims to retrieve organisms and the number of models classified in each organism from BioModels<\/a>, then make a a bubble chart using D3js<\/a> library. Thus, you can conceive the idea from getting data from the backend and plotting data to the frontend.<\/p>\n\n\n\n

\"\"
The graphical representation of the illustrated application<\/em><\/figcaption><\/figure>\n\n\n\n

Obviously, the query to fetch all organisms will give you a result in JSON or XML format, so then you can use that format data directly into the view (i.e. frontend) without converting it again. In reality, we often re-process data returned external API before embedding them to internal services. Also, it is very often to obtain data from multiple calls and combine the results before using them in a different place. Moreover, I create a class named Organism to capture the properties such as name, label, taxonomy accession and the number of models for the specific purpose in this post.<\/p>\n\n\n\n

Note<\/strong>: This project was built in grails 2.5.6<\/a>, therefore, it would be valuable if you have experienced and familiarised with it before making your hands dirty.<\/p>\n\n\n\n

\n

Table of Contents<\/p>\n