What is IT Architecture & Types of Architectures | ITARCH.INFO

What is IT Architecture & Types of Architectures

What is IT Architecture

We talk a lot about IT architectures, but a lot of times people are confused how to interpret what exactly an IT architecture is. According to Wikipedia "Architecture is the art or practice of designing and constructing buildings". IT market analyst Gartner defines IT architecture as "a series of principles, guidelines or rules used by an enterprise to direct the process of acquiring, building, modifying and interfacing IT resources throughout the enterprise.”

And both are right. In one way IT architecture is the process of designing and constructing IT solutions guided by principles and guidelines. But still the definition lacks what should exactly include a well defined architecture deliverable.

IT architecture should cover and facilitate the following:

  • Is a high-level diagram of the IT components in an application, covering the software and hardware design,
  • Shows the fundamentals of how custom-built solution(s) or vendors´ product(s) are designed and built to integrate with existing systems and meet specific requirements,
  • Is integrated in the software development methodology to understand and design IT software and hardware specifications and models in line with standards, guidelines and specifications,
  • Leverages Best Practices to encourage the use of (for example "open") technology standards, global technology interoperability and existing IT platforms (integration, data etc),
  • Provides a consistent, coherent and universal way to show and discuss the design and delivery of solution´s IT capabilities.

Types of IT Architectures

The other thing that confuses people is there are different types of IT architectures. The fact is that like when talking about designing a building as a parallel example, there are different levels of architecture such as the overall architecture of the building, floor plans for each floor, and the interior designs. Same applies to IT architecture and we can distinguish three types of IT Architectures:

  • Enterprise Architecture (EA)
  • Solution Architecture (SA)
  • Technology Architecture (also referred generally to as IT Architecture)

We will explain each of these types here below:

Enterprise Architecture

Enterprise architecture (EA) is the blueprint of the whole company and defines the architecture of the complete company. It includes all applications and IT systems that are used within the company and by different companies' departments including all applications (core and satellite), integration platforms (e.g. Enterprise Service Bus, API mgt), web, portal and mobile apps, data analytical tooling, data warehouse and data lake, operational and development toolings (e.g. DevOps tooling, monitoring, backup, archiving etc.), security, and collaborative applications (e.g. email, chat, file systems) etc. The EA blueprint shows all IT system in a logical map.

The objective of an enterprise architecture is to focus on making IT work for the whole company and business and fit the companies' and business' goals. It looks at the business strategy and find IT solutions to make it work including innovation and digital enablement. Therefore, an enterprise architect needs to be able to understand both IT and business at a high level.

The intent of EA blueprint is to improve transversal consistency, coherence and efficiency across the whole company while meeting its current and future business and IT objectives.

Enterprise architecture is important to clarify how business and IT align and how they support, enable and facilitate each other. In this article about Enterprise architecture, we discuss more about this specific IT Business alignment.

In a company there is one overall corporate enterprise architecture view that all applications are embedded in. However, each and every application has its own solution and technology architecture. So, each application uses enterprise architecture standards and technologies, but designs and builds its own solution and technology architecture to serve its application purpose. The following diagram depicts that situation how companies have their architectures structured:

In the following sections we explain the concepts of solution, technology and IT architectures in more detail.

Solution Architecture

Solution Architecture describes what functionalities a specific system needs to perform. It is a detailed description of the functionalities needed to meet business objectives, the logic that governs them, and the information associated with them. It is also described as the functional architecture of an application or system.

A Solution Architecture typically applies to a single project or project release and facilitates the translation of requirements into a solution vision, high-level business and/or IT system specifications. This blueprint receives direction from the Enterprise Architecture team in terms of corporate business, information and technical guidance. Difference between a solution and enterprise architecture and is that its context is to a specific solution as opposed to an entire company or enterprise.

Technology Architecture

Technology Architecture is the detailed description of the various technology components needed to meet business objectives, the logic that governs them, and the data associated with them. In summary, IT architecture shows the software and hardware architecture and is less relevant to overall business and company strategy, but more focused on how the specific solution can be served by this platform.

Technology architects focus on how components are designed and built to help you find robust and cost-effective software and hardware solutions. They act as the gateway between the software development team and the business to make sure that business needs are met.

IT Architecture = Solution + Technical Architecture

So, IT Architecture is the combination of a high level functional solution architecture together with the alignment of the Technology Architecture.

It contains the main functional components, but also the channels, architectural components, databases and infrastructure. It is the view that aligns business and technology as it shows the overall solution blueprint. Once you want to put a double click on each of the architectures, you get a more detailed solution or technical architecture.

This post does not go all in depth in all architecture layers, and you can read in more depth the following articles about enterprise architecture and IT framework, but here I show you a diagram that shows the full spectrum of all architectures:

Is Digital Architecture an application or enterprise architecture?

A question I am asked often is whether digital architecture is an application or enterprise architecture topic. The truth is that digital architecture is an enabling platform that integrates multiple applications (back-ends, web portal, mobile, analytics etc.) and optimizes its interaction. Therefore, digital architecture is an enterprise architecture pattern and not an application architecture per se. We explain more about digital architecture in the post "what is digital architecture and how to design".

But that does not yet respond to who is responsible for designing a digital architecture. In most companies, digital transformation is a project or even a department on its own. Its responsibility is to define digital strategy, roadmap and enable a digital platform. Therefore, design of digital architecture is typically led by digital transformation as such, in collaboration with enterprise architecture to ensure it is aligned to the corporate IT standards and vision.

I am Michael Widjaja, retired Partner after 25+ years consultancy with Accenture. I was leading Technology Architecture Practice within Europe till 2010 and then for Latin America. Worked with 100+ companies across the world, advising them on IT, Technology & Enterprise Architectures. Always want to make complex things look simple and therefore this Guide to Practical and Pragmatic IT Architecture Design to design IT architectures for simple as well as complex applications. Now spending time with family and co-founded InAdvance Consulting Group, and as its managing director, I am sitting in number of IT advisory committees and steering groups to help large companies with IT guidance. Material is free to use, but as a courtesy, please do refer ITarch.info.

IT架构和架构类型的更多相关文章

  1. 微信架构 & 支付架构(下)

    微信架构 & 支付架构(下) 3. 管理网络请求 首先看看原来 iOS 处理支付网络请求的缺陷: 原来支付的请求,都是通过一个单例网络中心去发起请求,然后收到回包后,通过抛通知,或者调用闭包的 ...

  2. 微信架构 & 支付架构(上)

    微信架构 & 支付架构(上) 一. 微信和支付宝对比 这两者现在已经占领了移动支付的90%市场,支付形式也都大抵相同,只是在实现细节上略微不同.这里之所以要专门对比,是因为有些接口的不同在后边 ...

  3. 单KEY业务,数据库水平切分架构实践 | 架构师之路

    https://mp.weixin.qq.com/s/8aI9jS0SXJl5NdcM3TPYuQ 单KEY业务,数据库水平切分架构实践 | 架构师之路 原创: 58沈剑 架构师之路 2017-06- ...

  4. 【大数据】大数据处理-Lambda架构-Kappa架构

    大数据处理-Lambda架构-Kappa架构 elasticsearch-head Elasticsearch-sql client NLPchina/elasticsearch-sql: Use S ...

  5. 看阿里P9架构师如何向你定义架构及架构师

    架构的定义 先来看看软件架构的普遍定义吧. 一个程序和计算系统软件体系结构是指系统的一个或多个结构.结构中包括软件的构建,构建的外部可见属性以及它们之间的相互关系. 体系结构并非可运行软件.确切的说, ...

  6. Java之架构(0) - 架构之路

    软件架构作为一个概念,体现在技术和业务两个方面. 从技术角度来说:软件架构随着技术的革新不断地更新其内容,软件架构建立于当前技术和一些基本原则的基础之上. 先说一些基本原则: 分层原则:分层是为了降低 ...

  7. Atitit.vod 视频播放系统 影吧系统的架构图 架构体系 解决方案

    Atitit.vod 视频播放系统 影吧系统的架构图 架构体系 解决方案 1. 运行平台:跨平台 android ios pc mobile 1.1. -------------前端 界面------ ...

  8. 大型网站技术架构(四)--核心架构要素 开启mac上印象笔记的代码块 大型网站技术架构(三)--架构模式 JDK8 stream toMap() java.lang.IllegalStateException: Duplicate key异常解决(key重复)

    大型网站技术架构(四)--核心架构要素   作者:13GitHub:https://github.com/ZHENFENG13版权声明:本文为原创文章,未经允许不得转载.此篇已收录至<大型网站技 ...

  9. 大数据分析的下一代架构--IOTA架构设计实践[下]

    大数据分析的下一代架构--IOTA架构设计实践[下] 原创置顶 代立冬 发布于2018-12-31 20:59:53 阅读数 2151  收藏 展开 IOTA架构提出背景 大数据3.0时代以前,Lam ...

  10. PHP. 01. C/S架构、B/S架构、服务器类型、服务器软件、HTTP协议/服务器、数据库、服务器web开发、PHP简介/常见语法、PHPheader()、 PHP_POST/GET数据获取和错误处理

    C/S架构 Client/Server 指客户端,服务器 架构的意思 优点:性能性高:可将一部分的计算工作放在客户端上,服务器只需处理出局即可   洁面炫酷,可使用更多系统提供的效果 缺点:更新软件需 ...

随机推荐

  1. 微信小程序token失效 自动请求后端,适用于自动登录

    app.js // app.js App({ onLaunch() { let token = wx.getStorageSync('token') if (!token) { wx.login({ ...

  2. 【故障公告】没有龙卷风,k8s集群翻船3次,投用双集群恢复

    今天没有龙卷风(异常的高并发请求),故障却依然出现,问题非常奇怪. 某种异常情况会造成短时间内, k8s 集群中大量 pod (超过60%)因健康检查失败而处于 CrashLoopBackOff 状态 ...

  3. 全量、增量数据在HBase迁移的多种技巧实践

    作者经历了多次基于HBase实现全量与增量数据的迁移测试,总结了在使用HBase进行数据迁移的多种实践,本文针对全量与增量数据迁移的场景不同,提供了1+2的技巧分享. HBase全量与增量数据迁移的方 ...

  4. LGP5493题解

    卡完常后来造福一下人类 如何从4.80s卡到920ms.jpg 本题解的复杂度为 \(O(\frac {n^{3/4}} {\log n})\),然而标算是 \(O(\frac {n^{2/3}} { ...

  5. django主要文件介绍及django请求生命流程图

    -mysite文件夹 --mysite文件夹 --setting.py 配置文件 --urls.py 路由和视图函数对应关系(路由层) --wsgi.py wsgiref模块 --manage.py ...

  6. C# 静态成员和方法的学习小结

    C# 静态成员和方法的学习小结 数据成员:数据成员可以分静态变量.实例变量两种.静态成员:静态成员变量是和类相关联的,可以作为类中"共"有的变量(是一个共性的表现),他不依赖特定对 ...

  7. RepLKNet:不是大卷积不好,而是卷积不够大,31x31卷积了解一下 | CVPR 2022

    论文提出引入少数超大卷积核层来有效地扩大有效感受域,拉近了CNN网络与ViT网络之间的差距,特别是下游任务中的性能.整篇论文阐述十分详细,而且也优化了实际运行的表现,值得读一读.试一试   来源:晓飞 ...

  8. 前端经典面试题vue面试题

    1.什么是MVVM? MVVM是一种设计思想. Model 层代表数据模型,也可以在Model中定义数据修改和操作的业务逻辑: View 代表UI 组件,它负责将数据模型转化成UI 展现出来,View ...

  9. Paypal标准支付对接

    提醒一下,题主是在快速标准支付做到一半的时候换成了标准支付,所以该文档的快速支付大家做个参考就可以了. 一.两种支付方式 标准支付 优点:纯前端对接,简单方便,适用于非技术开发人员.个人即可用,不用花 ...

  10. snort规则

    一.Snort规则分为两个部分 二.规则头的基本格式 动作: 动作描述一个数据包的"谁,在何处,什么"的问题,并指明规则被激发后,在事件中应当做什么.在编写规则时,你可以从下面的关 ...