Overview
Last updated
Inforiver Writeback Matrix On-Prem
Last updated
Inforiver has been developed with Cloud first architectural pattern and it has been designed with cloud native components itself. Below is an ideal architecture diagram.
Please note that all the components shown here won't be deployed. Only the required components will be deployed and others are optional or external.
Only the following components will get created and configured in your Resource Group when you are deploying by using the marketplace app.
This is the API Server / Backend server for the Inforiver application. This service handles all the APIs triggered from the visual or Add-on App. This contains all the business logic and acts as a back-end service and route handler to serve static files like HTML, JS, CSS, and all images for the Inforiver Add-On.
It's a fully managed database-as-a-service from Azure which acts as an application database. Inforiver stores its data in its database. The data like users, logs, permissions, visual and report information are some of the data that gets stored inside this database. It is recommended not to touch this database or repurpose it for any other use.
It serves as both caching server for our application and queue for our background worker jobs.
It stores the static files which are uploaded or created from the Inforiver application. It will also acts as a temporary storage while writing the data to the writeback destinations or scheduler destinations.
It runs multiple containers which acts as a background task worker to handle heavy or slow jobs. Jobs like sending emails, writing data to final destinations, generating the reports for a schedule and data cleanups would be handled by this containers.
All the Inforiver components will be enclosed into different subnets in the same virtual network. For the management and complete isolation, four subnets has been designed.
Private endpoint is a network interface that uses a private IP address from a virtual network. This network interface connects privately and securely to a service that's powered by Azure Private Link. By using this private endpoints, Inforiver app service can access database, storage and other resources securely.
Private DNS zones are linked with private endpoints and app service would be able to exchange the private IP address for the provided private endpoints names.
Azure Container Registry (External): All application code would be compiled and stored in this centralized registry from where each component will pull its code.
Licensing Service (External): This service will help Inforiver to identify your license information and the features available to you. This will exchange only your license information.
Power BI Service (External): Power BI Service in which the Inforiver visual would be running.
Azure Active Directory Service (External): This service would help us to fetch information from your O365.
SMTP Service (External): This service will help us to send email from Inforiver.
Application Gateway (Optional): Application Gateway connects web applications to the cloud. It provides a web interface so that users can monitor traffic usage and block the unwanted traffic with the help of firewall policies.
Log Analytics Service (Optional): Log analytics will help you to collect log and provide the insights about the connected services.
Azure Key Vault (Optional): It helps teams to securely store and manage sensitive information such as keys, passwords, and certificates in centralized storage with industry-standard algorithms, it even has fine granular control for permissions over sensitive data.
You can read more about configuring these additional components from the How-To Guides.
