Skip to content

Latest commit

 

History

History
27 lines (18 loc) · 1.84 KB

01.project-structure.md

File metadata and controls

27 lines (18 loc) · 1.84 KB

Project Structure

Kcrud is organized into a multi-project setup, where each component (subproject) serves a distinct role within the overall server architecture:

  1. kcrud-server is the primary project component, responsible for server initialization, and integration of all server components. It manages the server's lifecycle from startup to shut-down and serves as the backbone of the application's operations.

  2. kcrud-core provides shared infrastructure and services, such as utility functions, server configurations, and database connection facilities. Designed to support operational needs of domain-specific components, promoting code reuse to shared concerns.

  3. kcrud-access provides security and access control services, including authentication, authorization, and actors management. It leverages the kcrud-core for shared functionalities.

  4. kcrud-employee is a specialized domain component dedicated to managing employee records, encompassing all CRUD operations. It leverages the kcrud-core component for shared functionalities, and kcrud-access for security and access control.

  5. kcrud-employment manages employment related data and logic, relying on kcrud-employee for accessing specific employee details, kcrud-core for shared services, and kcrud-access for security and access control.

server

A note about startup times.

Kcrud server startup time can be optimized by disabling unnecessary features. Turn off documentation API schema generation. Conduct database migrations in a controlled setting, not in production. Manage these settings via hconf configuration files.