Book: Building Evolutionary Architectures

Had this book for some time, just took a while to write up my notes 🙂

  • Page 7, Fitness Functions – objective function used to summarise how close a prospective design solution is to achieving the set aims
  • Page 12, structure of teams around service boundaries.
  • Page 35, QA in Production.  I’ve used this over the last n years, to great effect 🙂
  • Page 36, Chaos Monkey, Simian Army, and Conformity Monkey.  Design with Chaos Monkey in mind to ensure architectures have resilience built in from day 1 🙂  Conformity Monkey checks services to ensure they follow architect-defined best practices.
  • Hypothesis driven UX design
  • Page 48, Domain-Driven Design.  Forget the unified class across all services concept.  Allow each service to define their own, and reconcile differences at integration points (bounded context)
  • Page 96, Use Deployment Pipelines to Automate Fitness Functions.  Cycle Time is the measure of engineering efficiency.
  • Page 98, the biggest single common impediment to building evolutionary architecture is intractable operations.
  • Page 128, Anti-pattern – Code Reuse Abuse
  • Page 131, Pitfall – Resume-Driven Development.  We’ll all seen this one
  • Page 133, Forced Decoupling
  • Page 133, Goldilocks Governance model – pick three technology stacks for standardisation: Simple, intermediate and complex.
  • Page 144, Product over project 🙂  Like this concept a lot 🙂
  • Page 154, Testing.  Obvious, but constantly needs to be re-iterated 😦

Great book.  Sensible length.  Easy to consume 🙂

~ by mdavey on May 28, 2018.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: