|
|
New Data Structure
The same data is stored differently in the database than that in the running applications. For example, Oracle databases store data in files and the logical storage structures in the databases are data blocks, extents, segments and table spaces. The same data is stored in Java programs in linear data structures (arrays and list), trees (binary trees) and Data Access Objects. The same data will pass through a number of conversions from its starting point in the database until it reaches clients views in the browser or mobile.
In the human cardiovascular system, the blood circulates and transports nutrients and oxygen to nourish the body without any conversions. We are applying the same principle where data should be only stored in IDAO structure regardless where it is located in the running system.
The main objective of our new data structures is to speed the creation and storage of IDAO data in and out of the databases. IDAO will perform the data services as a Visitor Pattern object requested by any software components in any tier within the running system. The data structure should simplify all the CRM, BI, Analytics and customization-personalization processes. It also includes developing IDAO Factors-Adapters and lookup matrixes. We would be developing the following components:
• IDAO Factories-Adapters
• CRM Lookup Objects
• Dynamic Business Rules Properties Files
• Performance (Audit Trial and Tracking) Objects
• Batch Processes
IDAO Factories-Adapters:
The role of Factories and Adapters is the creation and the storing of IDAO and our IDAO is self-contained Java object which is composed of the following objects:
• DAO - to store data
• Questionnaire Object
• Decision-Maker Object
• Options-Answers Object
Check our Online-Banking-IDAO Security example in Design-Architect pages with Java code to illustrate the actual implementation of IDAO.
CRM Lookup Objects:
These are running objects with the parallel arrays of bits, indexes and hashing lookup processes using logarithms. The creation and storing of these objects are covered in the Design-Architect pages.
Dynamic Business Rules Properties Files:
The dynamic business rules are stored in System Properties files as text (Tokens) for easy editing by system admin for changing these rules. Using Properties files give the system admin the ability to dynamic change the rules without any code changes or modifications.
Performance (Audit Trial and Tracking) Objects:
Using Threaded objects (the same approach as Logging) to track all the running objects and create all reports and statistic which make our CRM Metadata intelligent and self-correcting.
Batch Processes:
The batch processes do the updating, cleaning and synchronization of all the lookup matrixes objects and databases.
|
|
