Json

Management of JSON data for NO SQL projects

JSON Files

Make your Information System compatible with "No SQL" formats

JSON has become an essential exchange format. Most web APIs use this format to exchange data with third party applications..

Because of its principle of "universal mapping" Stambia allows any type of data structure to be easily manipulated.

Thus, the management of JSON files in Stambia is surprisingly easy and is very appreciated by users. Stambia can reverse this type of file, directly from the file or through a web service definition.

 

 

Writing JSON Data

Stambia can manage JSON files as sources or targets of a mapping, in a way that is performant and easy to design.

In one single mapping, Stambia can load complex JSON files regardless of the deepness or the number of hierarchies.

 

Reading JSON data

In the same way, through the multiple-target approach of the mapping, Stambia can read complex JSON files and load them into multiple targets.

Each file will be only read once, and thus it provides the maximum performance.

 

JSON Files replication

Coupled to the Stambia replication component, the connector allows you to replicate a hierarchical JSON model into a standard relational database.

This component allows you to browse a directory and massively integrate JSON files into a relational database. In this case, there is no mapping, thus no development. The replicator is able to create a relational structure from the hierarchical structure of the file and to fill the database with the files that have been found in the folder.

Thus the reading or writing of a JSON file is automated and requires no complex development.

 

JSON and web services

JSON can also be the input or the output part of a web service. The way to manage the JSON format will be the same as for a mapping using an XML exchange format.

Stambia can directly reverse the web service description including the JSON definition.

If the web service definition doesn't provide the JSON input or output definition, it's possible to associate a JSON file definition to the web service definition in order to complete the metadata.

In that case, the mappings are very simple to implement.