What Does an Exec Need to About Architecture and Why

What Does an Exec Need toAbout Architecture and Why

1 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281

Chapter 1

What Does an Exec Need toAbout Architecture and

Why2 / 16Copyright © 2016 Smoking Hand LLC. All rights Reserved. Version: d8c4c281

Why Change?Latest Technology TrendsManaging Change

What Does an Exec Need to About Architecture and Why


You're here at this conference with yourteam

Are you worried about the new ideas andtechnologies the technical team learnedabout?

Is this another engineers love to reinventthe wheel?

Or does this really solve a real businessproblem?

Conferences and New Technology


You go back to work on Monday and startdiscussing your technology

Every answer is Hadoop and Spark

But are those the right answers?

Or did they get sucked in thereinforcement loop vortex of a Big Dataconference?

Hammers Named Hadoop and Spark





Let's look at the latest technology trendsthrough a different lens

Not as the next big thing

We should look at technology trends as ameans to solve a real business problem

Business View of Technology Trends


If you're trying to work with data butCan't due to a technical limitation.Can’t add new features because the database will fall over anddieCan’t do you a report because it would take too long or processtoo much dataCan’t run a SQL statement because that kill the of yourproduction databaseCan’t do the most intensive queries because they take too muchtime and resources to run

This is what Big Data technologies likeSpark and Hadoop change

http://tiny.jesse-anderson.com/bigdata

When You Can't


http://tiny.jesse-anderson.com/bigdata

Some teams spend 80-90% of their timeon complexity issues

The system is complex any change will be break other systemsThe team spends most of their time testing and analyzing a fixrather than implementing

This is what microservices technologieschange how difficult it is to integratesystems

Technologies like Kafka, Kubernetes, and Docker

When Everything Is Too Complex


Some teams spend too much time andeffort thinking about the hardware theyhave to run on

They are too tied to the number of cores oramount of RAM

This is what Lambdas services do to makeit easier to deploy code

Technologies like AWS Lamdba and Googe Cloud Functions

When It's Too Difficult to Deploy


Some operations teams can't keep up withthe speed of a development team

This is especially prevalent in largeenterprises

The team can't wait 6 months while newhardware is requisitioned

This is what cloud service providerschange

Providers like Amazon Web Services, Microsoft Azure, andGoogle Cloud

When It Takes Too Long to Get Resources





Should you add technology X?

Is the risk/reward worth it?

Will it really increase productivity?

Will it really decrease developer andoperational overhead?

Is This the Right Direction?


This encapsulates themessage I couldn't

articulate well!

Your Developer

Why Can't They Articulate or Explain Well?


Is the engineer known for quixoticadventures?

Quixotic - extremely idealistic; unrealistic and impractical

Do you trust their ability to honestlyevaluate the needs?

Get some neutral outside help to evaluate

How to decide?


Current: Instructor, Thought Leader, Monkey Tamer

Previously:Curriculum Developer and Instructor @ ClouderaSenior 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@jessetandersonhttp://tiny.bdi.io/linkedinhttp://tiny.bdi.io/youtube

About Me


http://www.jesse-anderson.com/

https://twitter.com/jessetanderson

http://tiny.bdi.io/linkedin

http://tiny.bdi.io/youtube