Scribd Logo
Upload

Welcome to Scribd!

  • 215 views

    LeanIX - Poster - Best Practices To Define Technology Stacks

    Uploaded by

    Paul Vintimilla Carrasco
    This document provides best practices for defining technology stacks for a cloud native journey. It recommends: 1) Technology stacks should represent an organization's IT infrastructure without overlapping components. 2) Definitions should focus on breadth over depth, including key components at a high level. 3) Auto-population tools can help map relationships between on-premises, infrastructure as a service (IaaS), and platform as a service (PaaS) components.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    LeanIX - Poster - Best Practices To Define Technology Stacks

    Uploaded by

    Paul Vintimilla Carrasco
    215 views1 page
    This document provides best practices for defining technology stacks for a cloud native journey. It recommends: 1) Technology stacks should represent an organization's IT infrastructure without overlapping components. 2) Definitions should focus on breadth over depth, including key components at a high level. 3) Auto-population tools can help map relationships between on-premises, infrastructure as a service (IaaS), and platform as a service (PaaS) components.

    Original Title

    LeanIX_Poster_Best-practices-to-define-technology-stacks

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides best practices for defining technology stacks for a cloud native journey. It recommends: 1) Technology stacks should represent an organization's IT infrastructure without overlapping components. 2) Definitions should focus on breadth over depth, including key components at a high level. 3) Auto-population tools can help map relationships between on-premises, infrastructure as a service (IaaS), and platform as a service (PaaS) components.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    215 views1 page

    LeanIX - Poster - Best Practices To Define Technology Stacks

    Uploaded by

    Paul Vintimilla Carrasco
    This document provides best practices for defining technology stacks for a cloud native journey. It recommends: 1) Technology stacks should represent an organization's IT infrastructure without overlapping components. 2) Definitions should focus on breadth over depth, including key components at a high level. 3) Auto-population tools can help map relationships between on-premises, infrastructure as a service (IaaS), and platform as a service (PaaS) components.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 1

    BEST PRACTICES TO DEFINE

    Technology Stacks

    Cloud Native Journey

    On-Prem IaaS PaaS SaaS


    Based on TBM Based on TBM Partly Based on TBM

    Auto-populated by Auto-populated by
    LeanIX Cloud Intelligence LeanIX Cloud Intelligence

    Client Operating Compute Data Center Storage Application Business Strategy and
    Hardware Virtualization Network Data Services Operations Support
    Software System Services Services Services Services Services Planning

    Container Compute on Enterprise Data Backup and Foundation Data Analytics Capacity Business Solution Application
    Mobile Software Mainframe HW Mainframe OS Data Network Collaboration
    Virtualization Demand Center Archive Platform and Visualizations Management Consulting Support

    Desktop Other Data Distributed Data Deployment and Enterprise


    Server Software Mobile HW Mobile OS MainFrame Domain Services Streaming Core Business Central Print
    Virtualization Center Storage (CDN) Management Administration Architecture

    Workstation Network Physical File and Object Data Event Innovation and
    Network HW Server OS Internet Productivity IT Training
    Software Virtualization Compute Storage Warehouse Management Ideation

    Server Virtual Compute Networked IT Service IT Vendor


    Server HW Workstation OS Load Balancing Database Service Desk
    Storage Virtualization and Containers Storage Development Management Management
    Solutions
    Storage Virtual Private Distributed Design and Program, Product
    Storage HW Scheduling
    CDN Virtualization Network Cache Development and Project
    Management

    Voice Network System


    File Share Telephony HW
    Integration Technology
    Business
    Management
    Workstation HW Testing

    DevOps Security and Compliance

    Business Cyber Security Governance Identity and Threat and


    Data Privacy Endpoint Security
    Database Framework IDE Languages Monitoring Continuity and and Incident Risk and Access Vulnerability
    and Security Management Awareness
    Disaster Recovery Response Compliance Management Management

    Partly Based on TBM

    Cross Cutting

    BEST PRACTICES
    Technology stacks represent an organization’s IT Don’t overlap Breadth over depth Long-term stability
    capabilities, independent of its structure, processes, Good tech stacks do not overlap; they are mutually exclusive. If you While more levels can help to get a better structure, it comes at the Properly defined tech stacks are fairly stable over time, persisting
    people, or domains. They help to organize IT components are able to assign your level 2 stacks without any ambiguity, you are cost of increased complexity. We recommend keeping the tech stacks throughout any organizational changes. Only major business model
    (e.g., a service, software, or hardware). on the right track. to no more than three levels down. updates should affect them.

    www.leanix.net

    You might also like