Specification

Hyperon work with the following technology stack.

You can benefit from the Hyperon full potential if your application is written in any JVM (Java Virtual Machine) language, for instance:

Java 11
Java Corretto from Amazon
Kotlin
Groovy
Scala
others
However you can employ Hyperon in any application via REST API.

Given you’re developing in JVM language, you can code in any JVM frame work, for instance:

Spring
Grails
GWT
Play
others

Choose your favorite build tool, because you can use any build tool, for instance:

Maven
Gradle
Ivy
Grape
others

Host Hyperon in cloud or locally.

Hyperon can be used in the most popular cloud services, such as:

AWS (Amazon Web Services)
Google Cloud
Microsoft Azure

You can also use Docker.

You can also self host Hyperon, using the following databases:

Oracle
MsSQL
PostgreSQL
H2
HSQL

Before we analyze possible ways of integrating Hyperon with your application, let's specify a few concepts. There are 3 groups of users, that will use Hyperon:

‍USER - application business end-user.

‍DEV - application developer. Developer codes the application and Hyperon Functions. The developer is also usually 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.

Let's see how Hyperon can be integrated independently of the business application's stack by using REST API.



Here are short descriptions of components in the diagram:

‍Business Application - Java application that has its business logic, parametrization 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.

‍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 an in-memory index within the Business 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 repository. Data is altered via Hyperon Studio. Hyperon Runtime Library accesses  the schema in fully read-only mode.

‍Hyperon Studio - the complex web-based user interface for setting up parametrization. The tool includes parameters and functions repository, domain definition and configuration, testing, and export-import capabilities.

There is a dedicated JVM module called Hyperon-Runtime that can be used in any JVM-based application.

Hyperon uses the following concepts:

User Interface
Ultimate performance
Publish changes without deployment
Versioning
and many more

Check details on the features page.

To develop Hyperon we use open source libraries. You can find a complete list of libraries and its licenses here.