Enable javascript in your browser for better experience. Need to know to enable it? Go here.
radar blip
radar blip

Pace-layered Application Strategy

Last updated : Nov 10, 2015
Not on the current edition
This blip is not on the current edition of the Radar. If it was on one of the last few editions it is likely that it is still relevant. If the blip is older it might no longer be relevant and our assessment might be different today. Unfortunately, we simply don't have the bandwidth to continuously review blips from previous editions of the Radar Understand more
Nov 2015
暂缓 ? 谨慎行事

Gartner's Pace-layered Application Strategy approach appears to be creating an unhelpful focus on the idea of layers within an architecture. We find thinking about the pace of change within different business capabilities (which can be made up of several architectural layers) to be a more useful concept. The danger in focusing on layers is that many types of change cut across multiple layers. For example, being able to add new class of stock to a website is not just about having an easy-to-change CMS; you also need to update the database, integration points, warehouse systems, etc. The recognition that some parts of an architecture need to be more maneuverable than others is useful. However, a focus on layers is proving unhelpful.

Jan 2015
评估 ? 在了解它将对你的企业产生什么影响的前提下值得探索

Gartner's Pace-layered Application Strategy approach to architecture attempts to articulate the fact that decisions about architecture should not be a one-size fits all approach. Instead, it is important to take a balanced view of your technology portfolio. We have qualms about some of the prescriptive recommendations that come with Pace. In particular, we have found some situations where the layering concept is too simplistic. That said, we believe the core idea that different components and systems within an architecture need to change at different paces is sound.

Jul 2014
评估 ? 在了解它将对你的企业产生什么影响的前提下值得探索
Gartner's Pace-layered Application Strategy approach to architecture attempts to articulate the fact that decisions about architecture shouldn't be a one-size-fits-all approach. Instead, it is important to take a balanced view to your technology portfolio in terms of where to be conservative, and where to take risks. While we have qualms about some of the more prescriptive recommendations that seem to come with Pace, in general we like the concept and many organizations could benefit from adapting similar models.
已发布 : Jul 08, 2014
Radar

下载第25期技术雷达

English | Español | Português | 中文

Radar

获取最新技术洞见

 

立即订阅

查看存档并阅读往期内容