Tech Stack: Best Practices (Big and Small)

Posted by Simon Barth on July 12, 2016
Tech Stack: Best Practices (Big and Small)

CIO, CTOs, and IT managers face the challenge to manage hundreds, or in some companies thousands, of technology products: Which data base technology to favor for the next year? What risk do outdated server operating systems bear? How big is the saving potential of sourcing all middleware from one manufacturer? One goal of Enterprise Architecture is to make such complexity manageable.

In order to cluster technology in a meaningful way, we use the Technology Stack at LeanIX. IT Components (Technologies) are assigned to a specific Technology Stack and therefore categorized. This makes analyses easier and allows for prioritization. For example, it is easier to focus on middleware technology for a detailed cost analysis, rather than trying to assess cost savings potentials for hundreds of different IT Components.

Experience shows that companies struggle to find a good structure for their IT Components. A good Technology Stack puts IT Components in useful categories that are neither too broad nor too narrow. Therefore, a good structure is also dependent on the number of IT Components that are to be clustered. We propose three different Tech Stack variations as a starting point – from very lean to very detailed. Reach out to us, in case you would like to directly load one of the Technology Stacks into LeanIX.

Subscribe to the LeanIX Blog and never miss a post again!

Related Posts