Component Features
Why Do We Use the CRUD Framework?
-
Reduce Development Effort
Without a CRUD framework, every table typically requires:
- Controller
- Service
- Repository
- DTOs
- Query handling
This results in repetitive boilerplate code. The CRUD framework eliminates this redundancy by providing reusable generic APIs.
-
Faster Development
New modules or tables can be onboarded quickly by:
- Adding configurations
- Defining metadata
- Creating mappings
Instead of building complete APIs from scratch, teams configure the metadata and mappings and the framework provides the runtime behavior, significantly reducing implementation time.
-
Multi-Environment Support
The CRUD framework supports multiple datasource environments such as:
- DEV
- QA
- PROD
- Customer-specific schemas
Example environments from configuration:
itm
itm_qa
wf_dev_hana
wf_qa_hana
ipm_dev
This allows the same application to connect dynamically to different databases based on environment or customer-specific schema.