What Does an Exec Need to About Architecture and Why
0 likes•138 views
The document discusses the importance of understanding technology trends for executives, emphasizing that these trends should be viewed as solutions to real business problems rather than just innovations. It outlines specific challenges that organizations face, such as complexity, deployment difficulties, and resource limitations, and how modern technologies like big data solutions, microservices, and cloud services can address these issues. It encourages executives to assess the risk and reward of adopting new technologies and seek independent evaluations to make informed decisions.
What Does an Exec Need to About Architecture and Why
- 1. What Does an Exec Need to About Architecture and Why 1 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 2. Chapter 1 What Does an Exec Need to About Architecture and Why 2 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 3. Why Change? Latest Technology Trends Managing Change What Does an Exec Need to About Architecture and Why 3 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 4. You're here at this conference with your team Are you worried about the new ideas and technologies the technical team learned about? Is this another engineers love to reinvent the wheel? Or does this really solve a real business problem? Conferences and New Technology 4 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 5. You go back to work on Monday and start discussing your technology Every answer is Hadoop and Spark But are those the right answers? Or did they get sucked in the reinforcement loop vortex of a Big Data conference? Hammers Named Hadoop and Spark 5 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 6. Why Change? Latest Technology Trends Managing Change What Does an Exec Need to About Architecture and Why 6 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 7. Let's look at the latest technology trends through a different lens Not as the next big thing We should look at technology trends as a means to solve a real business problem Business View of Technology Trends 7 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 8. If you're trying to work with data but Can't due to a technical limitation. Can’t add new features because the database will fall over and die Can’t do you a report because it would take too long or process too much data Can’t run a SQL statement because that kill the of your production database Can’t do the most intensive queries because they take too much time and resources to run This is what Big Data technologies like Spark and Hadoop change http://tiny.jesse-anderson.com/bigdata When You Can't 8 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 9. Some teams spend 80-90% of their time on complexity issues The system is complex any change will be break other systems The team spends most of their time testing and analyzing a fix rather than implementing This is what microservices technologies change how difficult it is to integrate systems Technologies like Kafka, Kubernetes, and Docker When Everything Is Too Complex 9 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 10. Some teams spend too much time and effort thinking about the hardware they have to run on They are too tied to the number of cores or amount of RAM This is what Lambdas services do to make it easier to deploy code Technologies like AWS Lamdba and Googe Cloud Functions When It's Too Difficult to Deploy 10 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 11. Some operations teams can't keep up with the speed of a development team This is especially prevalent in large enterprises The team can't wait 6 months while new hardware is requisitioned This is what cloud service providers change Providers like Amazon Web Services, Microsoft Azure, and Google Cloud When It Takes Too Long to Get Resources 11 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 12. Why Change? Latest Technology Trends Managing Change What Does an Exec Need to About Architecture and Why 12 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 13. Should you add technology X? Is the risk/reward worth it? Will it really increase productivity? Will it really decrease developer and operational overhead? Is This the Right Direction? 13 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 14. This encapsulates the message I couldn't articulate well! Your Developer Why Can't They Articulate or Explain Well? 14 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 15. Is the engineer known for quixotic adventures? Quixotic - extremely idealistic; unrealistic and impractical Do you trust their ability to honestly evaluate the needs? Get some neutral outside help to evaluate How to decide? 15 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281
- 16. Current: Instructor, Thought Leader, Monkey Tamer Previously: Curriculum Developer and Instructor @ Cloudera Senior Software Engineer @ Intuit Covered, Conferences and Published In: GigaOM, ArsTecnica, Pragmatic Programmers, Strata, OSCON, Wall Street Journal, CNN, BBC, NPR See Me On: http://www.jesse-anderson.com @jessetanderson http://tiny.bdi.io/linkedin http://tiny.bdi.io/youtube About Me 16 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281