12/25: Technology Stack
The word Technology Stack means different things to different people due to their roles and responsibility. The context of Technology Stack also changes it's contents such as Application Technology Stack versus Server Technology Stack that hosts an Application Component(s). The Application Technology Stack serves the Strategy and Design needs while Server Technology Stack serves the Implementation and Engineering needs as a result the Application Technology Stack drives the Server Technology Stack.
The Technology Stack schema elements are given below:
Application Technology Stack may have multiple Server Platform and Operating System while Server Technology Stack will have only one Server Platform and associated Operating System. Application and Server Technology Stacks both can have multiple Middleware Platforms and Application Products.
The Technology Stack schema elements are given below:
- Server Platform such as x86, Mainframe, Mac, Solaris
- Operating System such as Windows, Linux, Solaris
- Middleware - Web, App and Database Platforms
- Application Products
- Commercial-Off-the-Shelf (COTS)
- Opensource-off-the-shelf (OOTS)
- Hardware and Software Appliances such as Google Search Appliance
Application Technology Stack may have multiple Server Platform and Operating System while Server Technology Stack will have only one Server Platform and associated Operating System. Application and Server Technology Stacks both can have multiple Middleware Platforms and Application Products.
12/25: Applications Metadata
The Applications Metadata is the information about an application that provides high level quick insight into the underlying business architecture, application architecture, system architecture and infrastructure architecture of the application. The Applications Metadata of an enterprise portfolio is a key foundation to develop IT strategy that includes cloud strategy, applications and infrastructures rationalization strategy, data center migration and consolidation strategy, technology refresh strategy, security strategy, and business continuity & disaster recovery strategy for the enterprise.
Sample Schema Elements for Applications Metadata:
Sample Schema Elements for Applications Metadata:
- Core Information
- applicationName
- description
- serviceUrls
- applicationType
- businessFunction
- businessCriticality
- userBase
- userType
- securityAndCompliance
- cloudReadiness
- roadMap
- knownIssues
- comments
- Target SLAs
- Site
- System
- Service
- Implementation Information
- implementationType
- technologyStack
- applicationArchitecture
- applicationDependencies
- System Maintenance
- blackoutPeriod
- maintenanceWindow
- maintenanceTypes
- Sizing Information
- userBaseSize
- transactionVolume
- transactionRate
- operatingSystemsInstances
- webAppServersInstances
- databaseServersInstances
- databaseSize
- filesystemSize
- Software / System Deployment Life Cycle (SDLC)
- type
- lifeCyclePath
- lifeCycleDuration
- testingType
- testingDuration
- state
- Backup and Disaster Recovery
- performanceObjective
- RPO
- RTO
- deploymentState
- Contacts
- business
- development
- testing
- productionSupport
Disclaimer
The views expressed in the blog are those of the author and do not represent necessarily the official policy or position of any other agency, organization, employer, or company. Assumptions made in the study are not reflective of the stand of any entity other than the author. Since we are critically-thinking human beings, these views are always subject to change, revision, and rethinking without notice. While reasonable efforts have been made to obtain accurate information, the author makes no warranty, expressed or implied, as to its accuracy.
The views expressed in the blog are those of the author and do not represent necessarily the official policy or position of any other agency, organization, employer, or company. Assumptions made in the study are not reflective of the stand of any entity other than the author. Since we are critically-thinking human beings, these views are always subject to change, revision, and rethinking without notice. While reasonable efforts have been made to obtain accurate information, the author makes no warranty, expressed or implied, as to its accuracy.