Hub is a collection of web applications, viewed as a single web site, and owned by multiple development teams. The applications are all displayed within the Hub Shell.
Hub allows users to manage a business's core functions and many of their products. Providing various back-office operations, Hub is tailored based on the iQmetrix products the clients use and is a center for configuration.
All Hub apps are hosted in Azure on a single app server. Most Hub apps have their build and deploy through Azure Pipelines, with a small portion still using TeamCity.
Hub and the apps are deployed across three environments: Integration, Release Candidate, and Production. You can view Hub in each environment with the following links. Sign in with your iQmetrix Active Directory credentials or a company user's test credentials.
- INT: This is the
integrationenvironment. Your CI/CD will automatically deploy any commits to the main repository branch to
- RC: This is the
release candidateenvironment. RC is used to test applications before production and for client demos. You will need to manually trigger deploying to RC and have a Change Management ticket before doing so.
- PROD: This is the
productionenvironment. Prod is the client-facing instance of Hub. You will need to manually trigger deploying to Prod and have a Change Management ticket before doing so.
Hub v2 is deprecated and should not be used for any new project. Hub v2 uses Aurelia and the ducks pattern (using a Redux and RxJS implementation) to develop applications. Only a few apps use Hub v2, including the Hub Shell. These applications will be migrated to React in the future.
Hub applications are frontends for many services. It is recommended to use the Backend for Frontend (BFF) pattern between your core feature service and Hub application.
For best practices related to developing services, refer to product-excellence.