SpinalModel Structures

This page explain how data / objects are organized in spinalcore, how to create your own objects, and how to use the standard API to create, modify or remove objects.

Spinalcore do not only help you to synchronize objects between the "organs" of the system. Spialcore defines a programming language based on standard containers (the atomic objects) that map the standard containers of standard programming languages (C++ and Javascript by now) and transform them into "nativelly synchronized" containers. This means that all objects created with the spinalcom framework (objects that extend from Spinalcore Model class) :

• are nativelly collaborative
• will be nativelly synchronized in a spinalcore system
• will be automatically "recomposed" of Spinalcore atomic objects 
• will be automatically stored in the spinalhub object database after each modification by any connected organ
• can be observed by any connected organ (with respect to its authorizations)
• will automatically generate events after each modification on all organs that observe it...

Spinalcore offer you a easy way to build native distributive systems where data/objects/contexts... are automatically synchronized and distributed processes are nativelly managed ! 

The Models pages of this doc are organized this way :

• Spinalcore Atomic objects : description of Spinalcore standard container and their API. The global "Model" class, that you are going to use systematically when developping with Spinalcore, will be describe in this page ! 
• Spinalcore Standard objects : description of the standard objects that are implemented and provided in our connectors (c++ and javascript). This standard objects are used in all our application for user management, file management or graph management
• Spinalcore standard contextual organization : the FileSystem and the Semantic Graph

The Utilities (standard organs that use the standard objects) are described in the "Utility" pages.