When it comes to organizing and utilizing data, Unqork provides users with a native, fully integrated document-based database: MongoDB. This offers enhanced flexibility through the use of JSON-like documents. The document-based approach allows developers to build applications that are more scalable, resilient, and adaptable than those built around traditional tabular, relational databases.
Whenever a change is made to a traditional database, it can cause cascading effects throughout the application that need to be addressed. This inhibits the ability of organizations to efficiently adapt software in response to new challenges, which places them at a competitive disadvantage. Unqork’s schema-free model eliminates these constraints, so developers can spend their time addressing business challenges rather than technical ones.
This more-fluid approach to development, however, can open the door to complexity, particularly within the confines of a highly collaborative platform like Unqork. For example, one Creator (the name we use to refer to users from any team) might label a field “address,” while another unknowingly may use “street address” for the same information. Unqork’s inherently open nature provides many benefits, but it can also lead to complications and data conflicts down the road, particularly as applications expand and develop over time.
Unqork’s Data Model function addresses these challenges while still maintaining all the freedom and flexibility of a document-based approach.
Flexible and Functional
Unqork’s Data Model provides Creators with an intuitive visualization of how data is being used throughout the application, including pertinent information such as Property ID, user permissions by role (e.g., write, edit, view, or hide), data type (object, text, number, etc), and persistence status.
Even better, the system also automatically marks any Personally Identifiable Information (PII) flowing through the system with a half-shield icon so Creators know to take particular care with that data (and to help administrators ensure the correct permissions are applied).
Anytime you click on a component in Data Model, the right-hand rail will populate with information on every module where that data component is used. This rail also allows users to identify the path of a specific field with a click.
With Data Model, Creators are able to tap into the power of a data document-based approach, while avoiding complexity, so they can continue to build enterprise-ready applications quickly, efficiently, and collaboratively.
You Might Also Be Interested in
