Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

Table of Contents
stylenone

 

...

 

 

The Maestrano platform is composed of the following components:

...

While Maestrano publicly provides Impac-Angular as a convenient way to display data provided by Impac!™ engine, one could easily choose to implement their own frontend using any technology/framework that they may see fit.

6 - Internal - Nex!™ Applications

The Nex!™ web applications are all packaged using Docker. Docker allows one to define an OS image containing everything that is needed to run a particular web application such as vTiger, Dolibarr, WordPress and Joomla. So far, all applications hosted by Nex!™ are open source. Examples of these applications can be found on Github under Maestrano's account (e.g.: 

...

https://github.com/maestrano/vtiger6). Actual Docker packages can be found on Docker Hub under Maestrano's account (e.g.: https://hub.docker.com/r/maestrano/vtiger6).

These open source applications have been modified by Maestrano to include Maestrano-specific features such as Single Sign-On and Connec!™ Data Sharing. They leverage Maestrano's SDKs - found on Github under Maestrano's account - for this.

Customers can easily point a custom domain name to their applications if required. Each application comes with a default unique url which can be used by customers to point a CNAME.

While most Nex!™ applications are served using HTTPS, some applications - such as Joomla and WordPress - require to be served under HTTP. At first, this may be considered as a potential security issue but most of these applications require a custom domain and a custom SSL certificate in any case. Therefore this "HTTP vulnerability" is only a temporary situation that any customer would resolve anyway after purchasing a custom domain and certificate.

7 - External - Cloud Applications

Cloud applications are online services that have used Maestrano's SDK to integrate with the platform and enable features such as Single Sign-On, Single Billing and Data Sharing. They reside outside of the Maestrano infrastructure but are still considered part of the ecosystem.

Because they integrate with the platform, customers do not need to signup separately to these services. Using Single Sign-On customers can automatically get setup on these kind of services.

Cloud applications are expected to communicate with two components of the platform: MnoHub and Connec!™. MnoHub is used by cloud applications to retrieve information about their customers as well as submit bills related to customer subscriptions. Connec!™ is used for Data Sharing, meaning that cloud applications are expected to send data updates to Connec!™ when records are updated on their side as well as receive updates whenever things get updated on the Connec!™ side (= data pushed by another application).

8 - External - Connector Applications

Connector applications are online services that exchange data with Connec!™. These applications did not integrate using one of Maestrano's SDKs. Instead Maestrano connected them to Connec!™ using their public APIs.

These applications do not feature any Single Sign-On or Single Billing capability. Customers are required to have an account on these services before connecting them to the platform.

9 - Overview Diagram

The diagram below show how all components interact together.

...