AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Then you would look into the technical solutions and subsequently the tools and applications needed to implement them. After all, the industry your organisation is active in, determines in a way what technology you need and which opportunities could present themselves. You could of course argue that you first set out to identify a business strategy, upon which you build your technology stack and enterprise architecture. They aren’t independent pillars, they collaborate to uphold your foundation Technical Architecture would be placed on the bottom right – low strategy, deep technical know-how.Īnd it’s this view that is incomplete. Solution Architecture would be placed in the center – acting as a bridge between EA and TA. And the x-axis – from left to right – would read Broad Technical Know-How to Deep Technical Know-How.Įnterprise Architecture would be placed on the top left – highly strategic, broad technical know-how. If you would display these three on a matrix, the y-axis – from down to up – would read Low Strategy to Highly Strategic. And Technical Architecture deals with the implementation of those solutions. Solution Architecture then identifies what the solutions for these challenges may look like. Where Enterprise Architecture deals with which challenges are focused on. Oftentimes these three approaches to your overall technology stack are seen as separate from one another. And the technical know-how for its implementation (TA).Well-thought-out roadmaps working towards the above identified direction (SA).Holistic strategies both in technical choices and direction of business (EA).Setting up your technology stack requires a combination of three pillars: The misconception of Enterprise Architecture (EA) vs Solution Architecture vs Technical Architecture This blog aims to provide a slightly more complete view on the definitions of Enterprise and Solution Architecture and how they actually merge and compliment each other. The waterfall or pyramid analogy doesn’t hold up when we zoom in a real business environment. Though there is some truth to it, this hierarchical view is incomplete. A simple Google search of ‘Enterprise Architecture vs Solution Architecture’ brings up thousands of posts with a similar conclusion: “Enterprise Architecture sits above Solution Architecture, which sits above Technical Architecture”.
0 Comments
Read More
Leave a Reply. |