Architecting the self-service portal
Architecting the data mesh portal is like architecting any web portal. You need to treat your employees as customers of the portal and build a responsive, user-friendly portal that will become an important tool for making their work easier.
From a high-level architecture perspective, a simple N-tier architecture will be sufficient to take care of the scale required for the data mesh portal.
Let’s walk through some of the core components of the N-tier architecture and possible options to build on the Azure cloud.
Active Directory and Domain Name System (DNS)
As a standard practice, all access to the portal needs to be integrated with Active Directory and a DNS to resolve the URL to a specific app gateway IP address. You also need to decide on the URL for the service. Depending on how the company intranet is designed, you can have the data mesh as a subdomain (https://learn.microsoft.com/en-us/azure/dns/delegate-subdomain), for...
