Introducing the Holon platform Property model

One of the Holon platform foundation concepts is the Property model, which can be used to represent a generic data model, abstracting away from data structure and persistence implementation details. The property model architecture is designed for maximum flexibility and versatility, so as not to limit its use to backend or data management application levels, but to make it a cross-cutting asset, to be seamlessy used in a multitude of situations and application or communication layers.

The Property interface, as PathProperty or VirtualProperty implementation in particular, along with the PropertySet and PropertyBox structures, allow you to obtain the main following benefits:

• Collect all the relevant features and configuration data in a single point, represented by a Property, to avoid duplications and inconsistency between application layers;
• Abstract away the property definition from the concrete data representation and persistence model, to favor loose coupling and independence from underlying data structures, extensibility and versatibility;
• Provide common operations and functionalities, such as value converters and validators, in a consistent and well defined way;
• Enable the use of a standard API to manage the data model, relying on the Property architecture abstractions, for example to query the data model or to transport data in the form of property values.

Read the reference documentation to get all the information about the Property model and to explore the Holon Platform APIs which allow you to define and use it to the maximum of its potential.

Or just start coding, following the property model tutorial and exploring the examples available on GitHub.