Technical architecture: What IT does for a living (cio.com)

Technical architecture: What IT does for a living

Building effective IT 101: Technical architecture is what separates a hard-to-navigate pile of tech from accelerating IT’s ability to get things done.

Technical architecture is the sum and substance of what IT deploys to support the enterprise. As such, its management is a key IT practice. We talked about how to go about it in a previous article in this series.

Which leads to the question, What constitutes good technical architecture? Or more foundationally, What constitutes technical architecture, whether good, bad, or indifferent?

[ Learn the 10 old-school IT principles that still rule and the 12 ‘best practices’ IT should avoid at all costs. | Get the latest insights by signing up for our CIO newsletter. ]

In case you’re a purist, we’re talking about technical architecture, not enterprise architecture. The latter includes the business architecture as well as the technical architecture. Not that it’s possible to evaluate the technical architecture without understanding how well it supports the business architecture. It’s just that managing the health of the business architecture is Someone Else’s Problem.

Why technical architecture matters

IT always has a technical architecture. In some organizations it’s deliberate, the result of processes and practices that matter most to CIOs.

But far too often, technical architecture is accidental — a pile of stuff that’s accumulated over time without any overall plan.

As Figure 1 shows, during initial IT implementations, managed architecture costs more than just ignoring the subject and hoping for the best, but pays for itself over time as the advantages of a well-managed architecture — reduced maintenance and support costs, easier and less-fragile integration, and overall improved flexibility in addressing new business challenges — dwarf the initial investment.

What constitutes technical architecture

Before we get started, no, what you’re about to see isn’t the well-known TOGAF architecture framework. It isn’t inconsistent, but I’ve found what follows to be more concrete and an easier fit to real-world IT portfolios. But whatever framework you use, its purpose is to sort the bits and pieces of stuff IT manages into portfolios of parallel components for ongoing analysis and planning.

Figure 2 shows the components of technical architecture. It includes the external factors that influence it, its building blocks, and the standards it generates. One at a time:

External factors

These include business drivers, architecture principles, and technology trends:

  • Business drivers: These are the broad IT capabilities the company will need, as inferred from its strategic goals. These aren’t requirements in the app dev sense. They’re broader than that. Examples might be machine learning, automated language translation, and facial recognition. Business drivers have a direct impact on the architecture; they also affect it indirectly by helping guide formulation of the architecture principles.
  • Architecture principles: As explained in the last installment of this series, these are broad principles that define what constitutes “good” architecture in your business. They combine an overall knowledge of what constitutes good engineering with the company’s business drivers.
  • Technology trends: No, you don’t have to be trendy. But you do need to recognize when a trend in the external technology marketplace will invalidate some components of your technical architecture or could create an opportunity to do something differently and better.

Technical architecture’s building blocks

IT architecture is layered and segmented. It’s comprised of applications, data, and technology. Drilling down, it consists of:

Applications: The portfolio of software programs business users make use of to do their jobs. The application layer is divided into three sublayers:

  • Systems of record: The applications and application suites that serve as the authoritative source of information and business logic.
  • Integration and synchronization: The inter-application interfaces that make sure applications whose data and business logic overlap agree with each other.
  • Satellite apps and Integration APIs: By themselves, systems of record can be unwieldy ways to address all the fine-grained automation opportunities various business constituencies need addressed. Sometimes it’s better to implement specialty apps that connect to the systems of record, either directly through the integration sublayer or through APIs exposed by the integration layer that provide an integrated, idealized view of the underlying data and business logic.

Data: IT provides capabilities for managing two types of information: structured, aka data comfortably represented in tables and forms; and unstructured, aka content and documents more free-form in nature. Business users don’t, by the way, ever interact directly with data of any kind. They interact with applications that interact with data repositories, ingesting it, managing it, and representing it.

The data layer encompasses just the data themselves, not the DBMSes, content management systems (CMS), and document management systems (DMS) that contain them.

Technology: This consists of two sublayers:

  • Infrastructure and facilities, which encompass: the data center itself (even if you’ve gone full cloud there’s a data center lurking around somewhere); networks; servers, whether physical or virtual; storage, whether SAN, NAS, or direct-attached; plus systems monitoring, management, and administration tools — stuff like that.
  • Platforms: The software on which everything in the higher layers is built and run, including server operating systems, development languages and environments, DBMSes, CMSes, and DMSes, and enterprise service buses (ESBs) and equivalent integration systems.

Standards

As a result of evaluating the information technology deployed in the application, data, and technology portfolios, IT establishes standards — guidelines the portfolios must conform to. Standards fall into two categories:

  • Product standards: The specific products approved for use for delivering each IT capability. MS Word, for example, is the word processing standard for most businesses today. Applications, data repositories, and technologies that are in use but aren’t approved for use violate an architectural product standard.
  • Engineering standards: In addition to specific products, the technical architecture also consists of approved ways to structure its various components. As an example, most IT shops consider normalization to be their standard way of organizing structured data; many are in the process of establishing microservices as their standard way of organizing application logic.

Moving from primer to practicality

So far we’ve covered how to classify the bits and pieces of information technology you have into portfolios. That’s everything except what matters. The next articles in this series will cover using the results to evaluate the architecture you have and plan how to morph from it to the architecture you need.

技术架构:IT生存之道的更多相关文章

  1. 软件架构设计学习总结(3):QQ空间技术架构之详解

    QQ空间作为腾讯海量互联网服务产品,经过近七年的发展,实现了从十万级到亿级同时在线的飞跃.在这个过程中,QQ空间团队遇到了哪些技术挑战?其站点前后台架构随着业务规模的变化又进行了怎样的演进与变迁?成长 ...

  2. [置顶] QQ空间技术架构之深刻揭密

    QQ空间作为腾讯海量互联网服务产品,经过近七年的发展,实现了从十万级到亿级同时在线的飞跃.在这个过程中,QQ空间团队遇到了哪些技术挑战?其站点前后台架构随着业务规模的变化又进行了怎样的演进与变迁?成长 ...

  3. QQ空间技术架构之深刻揭秘

    QQ空间技术架构之深刻揭秘 来源: 腾讯大讲堂  发布时间: 2012-05-17 17:24  阅读: 7822 次  推荐: 4   [收藏]   QQ 空间作为腾讯海量互联网服务产品,经过近七年 ...

  4. 一个美国小券商的生存之道Tradestation

    转自:证券时报记者 张欣然 桂衍民 中国互联网金融的口号喊了十几年,众多证券公司仍然苦于找不到新的蓝海,研究大西洋彼岸的美国TradeStation公司的业务模式,也许对国内的证券公司会有一些启迪. ...

  5. Hive技术架构

    一.Hive概念 Facebook为了解决海量日志数据的分析而开发了Hive,Hive是一种用SQL语句来读写.管理存储在分布式存储设备上的大数据集的数据仓库框架. 1. 数据是存储在HDFS上的,H ...

  6. Web高级征程:《大型网站技术架构》读书笔记系列

    一.此书到底何方神圣? <大型网站技术架构:核心原理与案例分析>通过梳理大型网站技术发展历程,剖析大型网站技术架构模式,深入讲述大型互联网架构设计的核心原理,并通过一组典型网站技术架构设计 ...

  7. Worktile 技术架构概要

    其实早就该写这篇博客了,一直说忙于工作没有时间,其实时间挤挤总会有的,可能就是因为懒吧!从2013年11月一直拖到现在,今天就简单谈谈 Worktile 的技术架构吧 . Worktile 自上线到现 ...

  8. 聚光灯下的熊猫TV技术架构演进

    2015年开始的百播大战,熊猫TV是其中比较特别的一员. 说熊猫TV是含着金钥匙出生的公子哥不为过.还未上线,就频频曝光,科技号,微博稿,站上风口浪尖.内测期间更是有不少淘宝店高价倒卖邀请码,光内测时 ...

  9. eaby技术架构变迁

    如果你对项目管理.系统架构有兴趣,请加微信订阅号"softjg",加入这个PM.架构师的大家庭 最近在infoq上面看到 ebay介绍其系统架构变迁以及系统设计分享方面的讲座,其中 ...

  10. 大型网站技术架构介绍--squid

    一.大型网站技术架构介绍 1.pv高  ip高 并发量 2.大型网站架构重点    1. 高性能:响应时间,TPS,系统性能计数器.缓存,消息队列等.     高可用性High Availabilit ...

随机推荐

  1. python 中的迭代器和生成器简单介绍

    可迭代对象和迭代器 迭代(iterate)意味着重复,就像 for 循环迭代序列和字典那样,但实际上也可使用 for 循环迭代其他对象:实现了方法 __iter__ 的对象(迭代器协议的基础). __ ...

  2. QT:Qt Creator使用CTRL+C后变成了光标覆盖,插入模式

    菜单栏→工具→选项→FakeVim→取消勾选"使用FakeVim"

  3. VS常用的快捷键

    整理代码          Ctrl+k+f 注释                 Ctrl+k+c 取消注释          Ctrl+k+u 帮助文档          F1 无调试启动     ...

  4. 函数式组件中实现Antd打开Modal后其Input框自动聚焦(focus)到文字的最后

    目前React使用函数式组件已经成为趋势, 如何把React函数式组件用好, 提高性能, 从而实现业务需求也成为了一种能力的体现......咳咳咳, 进入正题: 现实场景需求 我想实现这一个需求, 父 ...

  5. dvwa-暴力破解(low-high)

    靶场环境 phpstudy8.1.1.3 Apache2.4.39 FTP0.9.60 MySQL5.7.26 Burpsuite v2.1 LOW 首先看一下源码: 这里没有任何限制,可以使用万能破 ...

  6. 【SQL】数据库运维实习工作经验

    1.导入表格的时候回出现类型不对应的问题,T-SQL代码如下: USE zzzj2017 ALTER TABLE CJ ALTER COLUMN 付款时间 datetime    2.删除 USE s ...

  7. 浅浅的聊一下 WebSocket

    第一次看到 ws:// 和 wss:// 时候,感觉好高级啊,还有这种协议. Websocket 历史 WebSocket是在2008年6月诞生的1.经由IEFT标准化后,2009年chrome 4第 ...

  8. 关于 Linux Polkit 权限提升漏洞(CVE-2021-4034)的修复方法

    镜像下载.域名解析.时间同步请点击阿里云开源镜像站 近日,国外安全团队披露了 Polkit 中的 pkexec 组件存在的本地权限提升漏洞(CVE-2021-4034),Polkit 默认安装在各个主 ...

  9. _u32定义

    驱动开发的原则: 能用__u32就最好用它,或者用u_int32_t之类的也可以,但不要直接用unsigned int等默认的数据类型.目的是让别人明白,你这个变量占多大内存. 原因: 1.你不能确定 ...

  10. AVRmega16 LED 例程

                                                                                      AVRmega16 LED 例程   ...