Application Architecture
The application estate as a designed portfolio rather than an accumulation.
4 to work through
-
intermediate
You inherit an estate of 300 applications. What do you record about each and what decision does it support?
2 min answer -
advanced
A global employment platform must handle country-specific rules that differ in every dimension. How should the architecture accommodate that variation?
2 min answer -
advanced Multiple choice
An enterprise platform serving many countries keeps hitting jurisdiction-specific rules - different approval chains, retention periods, mandatory fields and tax treatments - that vary independently of each other. Which accommodation holds up as the number of jurisdictions grows?
2 min answer -
advanced Multiple choice
An enterprise platform's application architecture must serve tenants ranging from small businesses to very large enterprises. Should one architecture serve all of them?
2 min answer
3 terms in this topic
Application Architecture
The set of applications, what each is responsible for, and how they relate — the view that reveals duplication and orphaned ownership.
conceptApplication Landscape
The inventory of systems in an organisation with their ownership, capabilities supported, integrations and lifecycle status.
patternMetadata-Driven Multi-Tenancy
Holding each tenant's custom structures as metadata rows over one shared physical schema, so that customisation needs no DDL and one upgrade reaches …
Neighbouring topics
Enterprise Architecture
General material on architecture at portfolio and estate scale.
EA Domains
Business, application, data and technology architecture as viewpoints.
Technology Architecture
Platforms, runtimes and infrastructure standards across the estate.
Capability Maps in EA
The stable frame for hanging investment, ownership and health off.
Application Portfolio Management
Inventory, ownership, cost and health for every application.
Application Rationalisation
Retire, consolidate, replatform — and why retirement is under-applied.
Technology Standards
Guidance that teams follow because it helps, not because it is mandated.
Technology Radar
Adopt, trial, assess and hold — with movement, dates and owners.
Reference Architectures
Pre-approved templates for recurring solution shapes.
Architecture Governance
Preventive, automated controls rather than review meetings.
Architecture Review Boards
Thresholds, early engagement and a real route to accept deviation.
Enterprise Integration
Estate-wide integration strategy, standards and shared infrastructure.
TOGAF
The ADM as a checklist, tailored rather than followed literally.
EA Frameworks
Zachman, FEAF and others — vocabulary rather than method.
Architecture Roadmaps
Sequencing change across an estate with dependencies and funding.
Paved Roads
Making the supported path the easiest path, with a way to leave it.
Platform Teams
Reducing other teams' cognitive load, measured by adoption.
InnerSource
Open-source collaboration practices applied inside an organisation.
EA Metrics
Measuring whether architecture work changed anything.