Modules and Hosting¶

HortiView supports various options to extend its functionality. Independent software vendors (ISVs) are able to create so-called Modules that are built on top of HortiView and provide added value for farmers.

The HortiView platform distinguishes between different module types and hosting types.

Module Types¶

Depending on the use case ISVs can publish various modules to HortiView.

Solutions are self-contained extensions that provide business logic and a user interfaces for farmers to interact with
Models published in HortiView can be used by other ISVs to build solutions on top of them, such as predictions or recommendations
Datasets published in HortiView can be consumed by solutions as well as models to provide added value to farmers
Connections are experimental module types that, in the future, will allow for chaining models and datasets to build sophisticated solutions for HortiView

HortiView currently only supports Solutions

As the platform progresses we will support Models, Datasets and even Connections to be published. If you plan to extend the HortiView platform, a solution is your best option at the moment.

Hosting Types¶

ISVs have multiple options of extending the platform. In HortiView we support two approaches to bringing modules into the platform.

Use Your Own Backend (UYOB)¶

Standard Hosting is the simplest hosting strategy that requires ISVs to publish a package providing a self-contained frontend which may be connected to an external backend if necessary. The idea behind this hosting type is to allow ISVs to leverage existing infrastructures they have built over time. All that is needed is a frontend that connects to the existing backend hosted by the ISV. This is what we call "Use your own backend".

The data and asset services are not fully functional, yet

The platform is under constant development. Although included in the diagram, the data service will provide more and more functionality as we make progress. The asset service is being designed and won't be available until the end of Q2.

To get started developing your first module for HortiView using the Standard Hosting approach, please refer to the "Module Development with React" guide.

Bring Your Own Backend (BYOB)¶

This is a strategy where ISVs can upload container definitions (either Docker files or Docker Compose files) and use them as their backend. As with Standard Hosting, vendors still need to provide a self-contained frontend package to interface with the container and to provide a UI for farmers. The idea behind Container-based Hosting is that ISVs can bring their own tech stack that might already exist. This hosting type addresses ISVs that do not want to maintain a backend in their own infrastructure. This is what we call "Bring your own backend".

Container Hosting — Container hosting supports the use of a container to serve as a backend for executing business logic. Solutions based on this approach are encouraged to use HortiView's data and asset services from within the container to ensure consistent data access and exchange across the platform.

The data and asset services are not fully functional, yet

The platform is under constant development. Although included in the diagram, the data service will provide more and more functionality as we make progress. The asset service is being designed and won't be available until the end of Q2.