Architecture

In this page we will discuss the Turbo360 architecture when the application is deployed in a private hosting model.

Turbo360 Core Architecture

The below diagram shows what the architecture will look like for the core part of the application.

This architecture will cover the following modules within the product:

• Cost Analyzer

• Business Applications

• Azure Documenter

• BAM in the “Pull model” where you are only using the Log Analytics and App Insights data sources.

Note that for BAM there are some additional components if you are using the push model which is discussed later.

What are the components used for

How do the resources authenticate between each other?

When you perform the application installation you can choose the connection string or managed identity option.  We would recommend using the user assigned managed identity which is then associated with the resources and configured for authentication.

For example the user assigned managed identity will be used by the web app when accessing the database and when accessing the storage account.

How can my users authenticate to the application?

Users can authenticate to Turbo360 via one of two available authentication schemes:

1. SSO with Entra ID

2. Username and Password

We would expect most customers would want to use SSO with Entra ID so that it is inline with their other applications using Microsoft based authentication.

Turbo360 BAM Architecture [Optional]

If you have the Turbo360 Business Activity Monitoring (BAM) module and you are using it in the push model where your components like Logic Apps, Power Automate or other integration components are telling Turbo360 where in your business processes they are up to, then there is an additional part of the architecture that you will need.

Note there are 2 data processing models for BAM:

• Push = You send events to Turbo360 and this needs the additional architecture components described here

• Pull = Turbo360 queries your existing Log sources such as app insights where you do not need the additional architecture components described here

Below is the addition to the architecture.  You can see an example of a Logic App calling to Turbo360 BAM via an API that is exposed.  You can consume the API via API Management or a Custom Connector.  Behind the scenes the API is implemented with Azure Functions where we receive the message, drop it on a queue for processing and then its processed in the background.  In the data section you can see where the custom business data related to your process is stored.

In BAM you still use the same user interface as for the other modules but you need the data processing element of BAM.