Skip to main content

Domain model

Domain model is the essential blueprint for the data in an application. It represents the core foundation of any system, defining the structure, relationships, and rules that govern all the information the application will manage. The data modeling process ensures that data is well-organised and reflecting real-world business concepts. A well-designed domain model enhances application performance, improves maintenance, and ensures scalability for future development.

Physical data model​

The Physical data model is the technical specification of how data is actually stored and retrieved from a database. It represents the storage format of information.

  • Structure: This model includes the detailed definition of tables, their columns, and the technical data types (e.g., VARCHAR, SERIAL, INTEGER).

  • Integrity: It enforces data integrity by defining constraints like Primary Keys, Foreign Keys, and Nullable fields to prevent data corruption.

  • Automation: In KAIZEN, this model is used to automatically generate Data Access Objects (DAOs), which are the classes that handle all database interactions (Create, Read, Update, Delete), and automatically write boilerplate code.

Logical data model​

The Logical data model defines how data is structured and presented as it moves within the application, especially when sent or received through APIs. It is the application's view of the data, which can differ from its storage format.

  • API Structure: This model uses definable structures, often called Value Objects (VOs), to package related data into a single, cohesive unit for API requests and responses.

  • Reusability: By defining a logical data type, you can create a reusable structure to be used across multiple API endpoints, which simplifies handling complex data and makes the code cleaner.

  • Consistency: It ensures a clear and consistent data representation between the frontend and backend services.

In KAIZEN, data modeling is a visual process through two primary features:

  1. Database Designer manages the physical data structure.

  2. Service Designer handles data types for the logical data structure.

Last updated on 20 May 2026