Architecture Overview

This page describes the typical architecture scenarios we have identified when working with customers on implementing Domec Tools platform.

The first set, called Application Configurations, describes the typical application implementation patterns.

The second set, called Business Scenarios, describes the architecture depending on the type of businesses, whether that be B2C (Business to Consumer applications), B2B (Business to Business applications), B2E (Enterprise applications), or a combination of B2B and B2E. Click on any scenario to get more information.

Application configuration

These scenarios describe the different type of technology architectures you application may use, and how Domec Tools can help for each of those

  • Single Page Application + API. Single Page Web Application “Client” which talks to an API (“Resource Server”). The application will use OpenID Connect with the Implicit Grant Flow to authenticate users with Domec Tools.
  • Mobile Application + API. Mobile Application “Client” which talks to an API (“Resource Server”). The application will use OpenID Connect with the Authorization Grant Flow (with the PKCE extension) to authenticate users.
  • Server to Server as a Client + API. Server to server communication where a server “Client” needs to make secure calls to an API (“Resource Server”), but on behalf of the client vs. a user.
  • Regular Web App (using OIDC). Traditional web application which needs to authenticate users using OpenID Connect.