Architecture, what does it even mean?
•17 likes•4,564 views
Report
Share
Download to read offline
Everyone seems to have an intuitive understanding of ‘architecture’ as the process and product of planning, designing, and constructing. The problem is most people don’t have the same understanding which leads to disagreements about what the process and product entails. The transition from software shipped on physical media to software delivered as services further complicated the conversation as operating services introduces other factors that must be considered on an ongoing basis. These misunderstandings have only been exacerbated as greater speed and scale create new problems necessitating novel emergent solutions. This presentation will attempt to highlight the need for new language with dense semantics about the emerging architectures (because just saying ‘microservices’ is causing more problems than it solves) while also pointing out that many of the struggles people have delivering software are rooted in architecture.
More Related Content
What's hot
What's hot(20)
Viewers also liked
Viewers also liked(20)
![The New Perspective On Paul[1]](https://cdn.slidesharecdn.com/ss_thumbnails/thenewperspectiveonpaul1-1223565460161162-8-thumbnail.jpg?width=768&fit=bounds)
Similar to Architecture, what does it even mean?
Similar to Architecture, what does it even mean?(20)
More from Andrew Shafer
More from Andrew Shafer(20)
Recently uploaded
Recently uploaded(20)
Architecture, what does it even mean?
- 1. Architecture I do not think it means what you think it means Andrew Clay Shafer @littleidea
- 2. Microservices you keep using that word @littleidea
- 3. You are going to need it the last responsible moment was 12 months ago @littleidea
- 4. Sympathy for the Machine pleased to meet you, hope you guessed my name @littleidea
- 5. We are missing language we have no timeless way of building @littleidea
- 6. Story Time With Uncle Andrew this is fine @littleidea
- 7. @littleidea tl;dr there is a new thing better than the old thing local rationality rules everything we have not yet developed the words
- 8. @littleidea Agenda • Introduction • Influences • Assertions • Meandering • Bikeshedding • Conflate Things • More Meandering • Call to Action
- 11. @littleidea
- 16. Principles > Practices >Tools
- 18. These things are all one…
- 20. @littleidea everyone wants to continuously devops microservices buzzword compliance™
- 21. faster and safer OODA LOOPSMALL BATCHES
- 23. A Quantum of Delivery
- 25. @littleidea if the per service cost of deployment and management of each service is not negligible… gl;hf the best way to drive down the cost of deployment… architecture
- 26. @littleidea improved architecture >> ad hoc automation
- 27. @littleidea more problems are architectural than people seem to realize most problems don’t manifest in slides
- 28. @littleidea deployment problems operational problems scaling problems resilience problems
- 29. @littleidea non-functional requirements requirements, which if not met, will make a system non-functional
- 34. @littleidea prelude: relate to coarse patterns declaration: a statement of value narrative: prose about the pattern continuity: relate to fine grain patterns A Pattern Language
- 35. @littleidea If I had an hour to solve a problem I'd spend 55 minutes thinking about the problem and 5 minutes thinking about solutions. — Albert Einstein
- 36. @littleidea What is the problem?
- 41. @littleidea So Obvious? So What?
- 48. @littleidea what even is an architect?
- 49. @littleidea • Software Architecture? • System Architecture? • Service Architecture?
- 52. Differentiated Value Line Someone Else’s Problem Someone Else’s Problem Someone Else’s Problem Someone Else’s Problem Someone Else’s Problem Someone Else’s Problem
- 53. @littleidea I’d rather be able to fix a bug in the kernel and not need to, than need to fix a bug in the kernel and not be able to
- 54. @littleidea What do you need to deliver a service?
- 55. @littleidea When you draw a hexagon connected to a database what did you actually decide?
- 56. @littleidea What can actually be implemented?
- 57. @littleidea prelude: relate to big picture declaration: a statement of value narrative: prose about the pattern continuity: relate to details A Pattern Language
- 59. @littleidea What promises does the architecture help you make and keep?
- 60. @littleidea How does it relate to the people?
- 61. @littleidea Inside and Outside the ‘Software’? System? Service?
- 62. How do people gain confidence about their work? What do they enjoy? What do they dread? How do people perceive the difficulty of their work? What do they learn through conversation alone? How do engineers learn “on-the-job”? Bonus Allspaw Slide
- 63. “Well”-adapted work occurs with a facility that belies the difficulty of the demands resolved and the dilemmas balanced. Joint Cognitive Systems, Patterns in Cognitive Systems Engineering. Woods, Hollnagel, 2006 Law of Fluency Bonus Allspaw Slide
- 64. @littleidea we need shared metaphors
- 65. @littleidea we need a sociolect
- 68. @littleidea In Summary • This cloud thing is really going to be changing everything • We develop pop cultures as practitioners • Architecture is generally poorly understood • Qualitative and quantitative understanding would benefit everyone
- 69. @littleidea Call To Action • Continuously Expand Your Understanding • Share Your Understanding With The Global Community of Practice • Develop Shared Metaphors and Sociolects • Please Someone Write This Book For Me (So I don’t have to)
- 71. Differentiated Value Line Someone Else’s Problem Someone Else’s Problem Someone Else’s Problem Someone Else’s Problem Someone Else’s Problem Someone Else’s Problem