Modeling an Application
When modeling an application in Txture, it is crucial to accurately reflect its deployment environments and relationships. Follow these guidelines for a correct and effective application model.
Agenda
Key Concepts
-
Application Instance
Represents a single installation of an application instance
corresponding to a specific deployment environment, such as
Testing, Production, or
Staging. Each environment is modeled as a separate
application instance asset. Each application instance (deployment
environment) has a unique deployment stack, encompassing its
infrastructure, dependencies, and configurations.
- Business Application Serves as a grouping asset for multiple deployment environments of the same application. It aggregates shared properties and facilitates a consolidated view.
Property Management
-
Business Application Populate properties that are consistent across all deployment environments.
-
Application Instance (Deployment Environment) Maintain properties specific to the individual deployment environment.
Assessments and Target Architecture
The Assessment and computation of Target Architecture recommendations are performed at the level of the individual application (deployment environment), ensuring environment-specific results.
Best Practices
-
Environment Granularity Always model each deployment environment as a separate application instance asset for clarity and precision.
-
Parent-Child Relationship Link all deployment environments (applications) to their corresponding business application for a structured hierarchy.
-
Consistent Naming Use environment identifiers in application instance names (e.g.,
AppName - Production,AppName - Testing) to avoid ambiguity.
Example
The below example shows the Business Application "Inventory Control" that consists of two deployment environments, a production and a testing environment. Each deployment environment is represented by a dedicated Application instance asset. Each Application instance has its own deployment stack with Database, Technical Component and Virtual Server assets. The use of an asset such as a database from multiple environments is possible, but not shown in this example.
