Application perspectives

You can tailor your view of an application by using application perspectives. You can capture the type of semantics and information that you need to optimize the applications and services.

An application perspective represents a set of services and endpoints that are defined by a shared context and is declared by using tags.

For example, a team that runs a multi-tenant offering likely wants to capture their tenants (tenant:one, tenant:two) as applications. Another team that runs an e-commerce site might want to capture their US (zone:us) and German (zone:eu) stores as two separate applications. While another team wants to capture their different environments (k8s.env:prod, k8s.env:dev) as applications. Finally, one customer might want to group a set of services that work together functionally into an application. Each of these applications comes with their own semantics and varying use cases.

An application perspective can overlay entire services, or just a subset of calls to those services. Application perspectives can completely overlap each other, partially overlap, or might not overlap at all. Services and endpoints can be included within the definition of more than one application, or none at all.