Gregor Hohpe; The Architect Elevator – Visiting the Upper Floors; In Martin Fowler’s Blog; 2017-05-24.
tl;dr → an architect must be able to speak argot to a wide range of cultures; the architect travels to meet the client & the service workers, they do not travel to meet him. The elevator is a metaphor for SES in the workplace.
is an IT architect who’s been building systems in a start-up, consultancy, internet giant, and corporate IT environment. He likes to untangle complex topics to make them approachable without dumbing them down, while spicing things up with pointed metaphors. He likes to tinker with Raspberry Pi’s and IT organizations. His Internet home is EnterpriseIntegrationPatterns.com
Choose design over architecture; Kane Baccigalupi; In 18F; 2015011-17.
tl;dr → just do it; use craftsmanship, use devops, always be launching; planning is old school and bad, but perhaps necessary
- Robert C Morris; Design Principles and Design Patterns; 2000; 34 pages.
- Object-Oriented Design Principles
- Open-Closed Principle (OCP)
- Liskov Substitution Principle (LSP)
- Dependency Inversion Principle (DIP)
- Interface Segregation Principle (ISP)
- Rlease Reuse Equivalency Principle (RREP)
- Common Closuer Principle (CCP)
- Acyclic Dependencies Principle (ADP)
- In Jimi Wales’ Wiki
Neal Ford (ThoughtWorks); Building Microservice Architectures; In Some Venue; 2014; 80 slides.
tl;dr → Enterprise Service Bus (ESB) rides again, but with Agile, Conway, Java, JSON, HTTP, REST, CI/CD & DevOps!
Sam Newman; Building Microservices: Designing Fine-Grained Systems; O’Reilly Media; preview edition; WHEN?; 102 pages; free sample (final edition); 25 pages; Amazon: kindle: $31, paper: $42+SHT; O’Reilly: pdf: $43, paper: $50+SHT.
<quote>actual development becomes a vanishingly small part of a developer’s job.</quote>