Prepare to Pick Two
来源:互联网 发布:日语跟读软件 编辑:程序博客网 时间:2024/05/21 06:33

Prepare to Pick Two
Bill de hÓra
SoMETiMES ACCEpTing A ConSTRAinT or giving up on a property can lead to a better architecture, one that is easier and less expensive to build and run. Like buses, desirable properties tend to come in threes, and trying to define and build a system that supports all three can result in a system that does noth- ing especially well.
A famous example is Brewer’s conjecture, also known as Consistency, Avail- ability, and Partitioning (CAP), which states that there are three properties that are commonly desired in a distributed system—consistency, availability, and partition tolerance—and that it is impossible to achieve all three. Trying to have all three will drastically increase the engineering costs and typically increase complexity without actually achieving the desired effect or business goal. If your data must be available and distributed, achieving consistency becomes increasingly expensive and eventually impossible. Likewise, if the system must be distributed and consistent, ensuring consistency will lead at first to latency and performance problems and eventually to unavailability since the system cannot be exposed as it tries to reaches agreement.
It’s often the case that one or more properties are considered inviolate: data cannot be duplicated, all writes must be transactional, the system must be

100% available, calls must be asynchronous, there must be no single point of failure, everything must be extensible, and so on. Apart from being naïve, treating properties as religious artifacts will stop you from thinking about the problem at hand. We start to talk about architectural deviation instead of prin- cipled design and we confuse dogmatism with good governance. Instead we should ask, why must these properties hold? What benefit is to be had by doing so? When are these properties desirable? How can we break up the system to achieve a better result? Be ever the skeptic, because architectural dogma tends to undermine delivery. The inevitability of such tradeoffs is one of the most difficult things to accept in software development, not just as architects, but also as developers and stakeholders. But we should cherish them; it’s far better than having limitless choice, and accepting tradeoffs often induces a creative and inventive result.
Bill de hÓra is chief architect with NewBay Software, where he works on large scale web and mobile systems. He is co-editor of the Atom Publishing Protocol and previously served on the W3C RDF Working Group. He is a recognized expert on REST style and message-passing architectures and protocol design.
- Prepare to Pick Two
- veste barbour homme the mother Chen Fengju two cronies to pick up one by one
- How to prepare tech interview
- How to pick up English..
- prepare
- prepare
- prepare
- How to Prepare Storage for ASM
- How to prepare for CSQA Exam ?
- 安装Ubuntu Prepare to Install Ubuntu 解决
- How to prepare the Good Presenation
- How to Prepare Storage for ASM
- How to prepare for an interview
- 关于解决 Failed to prepare partial IU:
- Prepare to deploy SharePoint add-in
- How to Quickly Pick up a Project
- gerrit cherry pick to merge code
- To have a bone to pick 抱怨有理
- sql计算时间差执行存储过程
- 计算机视觉CV 之 CMT跟踪算法分析四
- Hibernate检索方式浅记
- 笔记
- Android 6.0 (marshmallow)中新的新技术
- Prepare to Pick Two
- vagrant 使用
- Android批量上传文件
- 原子量
- 原型模式
- Uboot笔记档案【0】:mkconfig分析
- [Bluetooth Core V4.2 ] VOL2, PartB, 2 PHYSICAL CHANNELS
- 黑马程序员——java基础——Java中创建线程的两种方式
- Entityframework 连接 Mysql 出现闪退的问题