Title_Documentation

Documentation

Contact Us

Visualizzazione Knowledge Base

HyperIoT Framework

HyperIoT OSGi Framework was born as a solution for implementing µSerivces in OSGi.

The goal behind the creation of this framework is very simple: to enable µServices-based applications to be written in a short time by trying to provide a ready-to-use framework that tries to simplify development with a number of out-of-the-box features, offering integrations and patterns for microservices-oriented development.

The framework is based on a paradigm we have coined: “Convention over coding”. It means that the structure of applications follows certain mechanisms and dynamics that allows them to have truly simple code management (from development to build and deployment) and interface remoting. “Convention over coding” is not just a “development to a standard” but a set of techniques, tools and code conventions that ,if followed, drastically cut down development time and especially code maintenance.

This framework has solid basis and used in a lot application. Our roadmap provides to insert are µServices related patterns in the future such as: Api Gateway, Service Mesh, Support for SAGA pattern, Certificate Management and rotation, and µServices configuration management. Everything available in one place, written in a modular way so that the final user can customize it for his purpose. Another interesting field of research would be to implement a generic cluster deployer module for Kubernetes in order to ship and balance microservices automatically based on the current resource consumption updating the service registry automatically.

Imagine having to write a micro-service that performs the CRUD of an entity: the developer will have at his disposal a generator that will create at zero time the infrastructure underlying the micro-service in terms of: persistence layer with its transactions, entity validation layer, class layer for business logic and finally the rest services. The developer’s task will only be to define the entity in terms of fields and related annotations for validation and finally to define the access permissions. Once this is done, the work will already be finished and the deployment of the micro-service can be done directly in the container.

The Container used for development is Apache Karaf precisely because of the possibility of creating features that directly install all the necessary dependencies, it is possible, in any case, to use any OSGi container.

Since HyperIoT Framework is based on a model rather than a tecnology we are planning to evolve this model for other frameworks like Spring or Quarkus.

Articoli figli (6)

  • Convention Over Coding

    The way it is described, our solution sounds very similar to the classic “Convention over configuration.” In reality, it is not. The so-called “Convention over configuration” reduces the...

  • Framework Overview

    HyperIoT Framework consists of a number of development tools that increase the speed of writing and scaffolding projects and actually accomplish what we call “Convention over coding”. Below is the...

  • Deploy Unit is Micro!

    The framework encourages the development of individual self-consistent modules that constitute a deployment unit in themselves. With this approach, deployments are also “micro” by always involving...

  • Application Basic Structure

    The first concept to be introduced is the difference between project and module. A project is a self-consistent entity that has a specific purpose, for example: CRUD of the User entity. In order to...

  • Basic Concepts

    The layers defined within each project (considering also al part of persistence that we said is optional) are: Persistence Service Layer System Api Service Api Rest Websocket The persistence layer...

  • Ecosystem Overview

    EcoSystem Overview HyperIoT Framework is focused on increasing developer productivity. Basically it defines a structure model for projects. Developers who follows this model will inherit a lot of...