Software Architecture Books Summary And Highlights -- Part 10 Scaling

-

 

Scaling

Highlights

Ways to scale up business model integration:

  • Open host service

    When a subsystem has to be integrated with many others , customizing a translator for each can bog down the team.

    • Define a shared protocol with shared a shared domain language
    • Use a one-off translator to augment the protocol for that special case so that the shared protocol can stay simple and coherent.

  • Published Language

    • Use a well-documented shared language that can express the necessary domain information as a common medium of communication, translating as necessary into and out of that language.

DDD ch 14 Maintaining Model Integrity


Large scale domain model

  • evolving order
    • Too complicated and restrictive architecture based on up-front design assumption could prohibit developers from switching to better architecture based on better domain model.
    • Don’t overconstrain the detailed design and model decisions that must be made with detailed knowledge.
    • Let this conceptual large- scale structure evolve with the application, possibly changing to a completely different type of structure along the way.
  • System Metaphor
    • Use analogy to help develops and users understand the domain model
    • Organize the design around this metaphor and absorb it into the UBIQUITOUS LANGUAGE.
  • responsibility layer: Divide the domain model into multiple conceptual layers. Example


  • knowledge level
    • a meta rule level which describes and constrain the structure and behavior of the basic model.
    • like reflection pattern in ood
  • Pluggable Component Framework
    • Distill an ABSTRACT CORE of interfaces and interactions and create a framework that allows diverse implementations of those interfaces to be freely substituted.
  • How Restrictive Should a Structure Be?
    • The more restrictive, the less flexible.
    • Each structural rule should make development easier.

DDD ch 16 Large-Scale Structure


MicroService Scaling:

Goal: reduce failures and improve performance

approach:

  1. vertical scaling
  2. splitting workload: split critical service with low priority service so that critical service can have more resources
  3. splitting risk
    1. deploy your services to different hardwares and data centers . don’t put all services on same server
    2. because cloud providers give you an SLA guarantee, they will tend to limit their liability!
  4. load balancer
    1. some offers ssl termination which transforms https to http
    2. prefer software load balancer over hardware load balancer because it is easy to automate
  5. worker based system
    1. a collection of instances all work on some shared backlog of work. e.g. hadoop
  6. starting again
    1. redesign your service for large load
    2. design for ~10× growth, but plan to rewrite before ~100×

MSV Ch 11 Microservices at Scale


Service mesh:

common microservice communication infra containing observability, security, and reliability features so that it is easy to improve performance.

MSV Ch 11 Microservices at Scale


Caching

  1. Client caching: e.g. CDN
    1. pros: drastically reduce network traffic to server
    2. cons: hard to invalidate and update cache
  2. Proxy caching: a cache layer between server and client
    1. pros: handle multiple services, generic cache,
    2. cons: one more layer of network hops though not big impact
  3. Server caching:
    1. pros: easier to control and invalidate

Usually a mix of the 3 caches

Caching can be very powerful indeed, but you need to understand the full path of data that is cached from source to destination to really appreciate its complexities and what can go wrong.

MSV Ch 11 Microservices at Scale

A key lesson for Google production infrastructure has been to provision the cache to meet your latency goals, but provision the core application for the total load. This has allowed us to avoid outages when the cache layer was lost because the noncached path was provisioned to handle the total load (although with higher latency).

SWG Ch 25 compute as a service


Related Chapters

DDD ch 14 Maintaining Model Integrity

DDD ch 16 Large-Scale Structure

SAP Ch 9 performance

MSV Ch 11 Microservices at Scale

SWG Ch 25 compute as a service

Popular posts from this blog

Does Free Consciousness exist ？

-
Image
I see a study:  Discovery of quantum vibrations in ‘microtubules’ inside brain neurons supports controversial theory of consciousness  shared on social media. Some one comments that this study indicates that human have free consciouness and the freedom comes from quantum process. I disagree with this comments. To oppose this comment clearly, I will raise and answer two questions. First, what does ‘microtubules’ do inside neurons ? Second what is free consciousness ? What does ‘microtubules’ do inside neurons ? The above picture is from Wikipedia. It shows the structure of a neuron and what ‘microtubules’ is in neuron. The way how neuron works is: A neuron collect chemical signals from many other neurons and generate a signal in the left side of the above picture and send the signal to the right side the above picture through the ‘microtubules’ and finally convert that signal to chemical material and emit them. So ‘microtubules’ is more like a cable to transmit signals. And i
Read more

Software Architecture Books Summary And Highlights -- Part 1 Goal, Introduction And Index

-
  Goal And Target Audience This is a summary and highlights of 6 software engineering and architecture related books I recently read. All the 6 books are very heavy and interesting. Reading real contents of them is always recommended. The target audience is experienced software engineers who want to learn more in larger system design and architecture. The goal of this article is to provide summaries of the 6 books as well as brief highlights of interesting or important contents from the 6 books so that the target audience could learn the 6 books’ important ideas quickly and read only important chapters and save time. The highlights and summaries will be divided into several general categories. Each category contains a highlight section and a related chapters section. The related chapters section contains all chapter references which are related to the category’s topic. The highlight section contains a brief summary of interesting or important or enlightening contents from the relat
Read more

拉美500年，荆棘丛生的自由繁荣之路

-
  缘起 最近对拉美的政治经济历史感兴趣，所以读了一些相关书籍，看了一些相关视频，感觉拉美还是一个很有趣的地区：资源丰富，悠久的被殖民的历史，灾难性的通货膨胀，贫民窟，贫富差距大etc。 所以把阅读的笔记和思考重新整理如下。 注 ：下面的很多内容都是来自读书笔记，如有雷同，那是真的在抄书 lol 参考材料： 從「已開發」倒退回「發展中水準」的國家，經濟學家眼中最離奇的案例 （视频） 阿根廷国家崩溃报告 （视频） 《掉队的拉美》 [智]塞巴斯蒂安.爱德华兹 （书）  《拉丁美洲被切开的血管》 [乌拉圭] 爱德华多·加莱亚诺 （书） 正文 拉美的问题 相比其他国家，拉美有很多优势，比如资源丰富，有丰富的矿产资源，气候也很适合农业发展；比如比亚洲和非洲国家更早实现独立和民主制度；比如没有直接卷入一战和二战，二战期间由于欧州陷入战乱无暇输出工业品，拉美的民族工业从而获得了更多市场，并得到了长足发展。但是二战之后拉美的发展速度却远远落后于一片废墟的欧洲，还被东亚诸国后发超车。 《掉队的拉美》中把经济的增长转型分为三个阶段： 第一个阶段 ，产量增加和收入提高主要是由生产率增长驱动的。简单来说，第一个阶段的经济增长不是由于使用了更多机器或雇用了更多工人，而是由于做事的效率提高了。 第二个阶段 ，效率的提高和生产率的增长仍然强劲，整体经济持续快速发展。与第一个阶段不同的是，第二个阶段对机器、建筑物、公路和港口的投资成为增长的另一重要来源。 第三个阶段 ，包括实物资本和人力资本在内的资本积累成为增长最主要的来源，有助于维持相对较快的经济扩张。有时第三个阶段会引起新的结构或技术变革，使生产率有新的跃升，于是上述过程进入一个层次更高的新周期。 作者认为绝大多数拉美国家并没有跨越增长转型的第一个阶段。从各项经济、社会指标上，拉美的各个国家也很落后。比如拉美的贫困人口多。1970年，在实施进口替代发展战略整整30年之后，所有拉美家庭中仍有40%生活在贫困线以下，农村地区的贫困发生率达到令人震惊的62%。还比如拉美的人均收入低。1975年拉美平均人均收入相当于美国的24%，至2006年，这一数值跌至19%。再比如拉美的贫富差距很大，受教育程度普遍偏低，失业率高企，通胀失控等等。 根据经济学研究，一个国家的自由繁荣主要取决于以下几个因素： 首先，在解释长期增
Read more