The following diagram shows basic components of a Hyperon integrated applications and interactions between them.
Application - Java application that has its business logic, parametrization or tariffication externalized to Hyperon. The application is e.g. sales portal, product management system, policy life system. The parametrization is accessed via embedded Hyperon Runtime Library.
Application Database schema - storage for application own entities, e.g. clients, accounts, proposals, policies, printouts, user data.
Hyperon Runtime Library - provides robust API for parameter/function/domain access for its host Application. The library is responsible for retrieving data from Hyperon Database schema and caching it as in-memory index within the Application. At fixed intervals the library checks for schema alterations and updates itself asynchronously. Therefore no network traffic is necessary while Application calls API as configuration data is already cached. That approach significantly expedites parametrization calls.
Hyperon Database schema - storage for Hyperon externalized parametrization, function repository. Data is altered via Hyperon Studio. Hyperon Runtime Library accesses the schema in fully read-only mode.
Hyperon Studio - complex web-based user interface for setting up parametrization. The tool includes parameters repo, functions repo, domain definition, testing and export-import capabilities.
USER - application business end user.
DEV - application developer. Developer codes the application and Hyperon Functions. The developer is commonly also responsible for designing parameters and inputting test parameter values.
BA - business analyst. Initially BAs input final parameters values. Experienced BAs can perform highly sophisticated parameter redesigns without the necessity of application code change.