1 / 7

Campus Drivers

Embrace marginalization and evolve building blocks for innovation in response to user needs and regulations. Explore the importance of resiliency and telemetry in detecting and preventing abuses. Learn how to navigate dependencies for successful innovation.

julioa
Download Presentation

Campus Drivers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Campus Drivers Jon Moore Ron Hutchins Kevin Miller Mark Poepping

  2. Drivers? Not us • We’re Responders – sometimes “first” • Responding to: • User ‘needs’ – each application interaction is an overlay network from the app/user PoV • Vendors – metamorphosing building blocks • Regulations – left field and buzzword • By expediency or soapbox? • Operationally: answering the phone

  3. Lesson1: Marginalization is inevitable… • Good general building-block models enable innovation in areas unexpected. Often leads to a few… • high-value ideas that people *really* start to like (willing to pay for), leading to… • specialization that makes that cool thing really efficient, leading to… • marginalization where the general model is no longer a value for a majority, meaning.. • violation of generality is the expedient thing, making innovation increasingly problematic

  4. Lesson2: Need to appreciate and keep working both ends • If we don’t embrace marginalization, we become irrelevant • If we don’t rework our building blocks, we lose ability to change • Oh by the way, we don’t own all the building blocks (personal lambdas, cellular, overlays - see above)

  5. More Lessons: • Resiliency masks fixable problems • Allows us to be lazy • If it can be abused, someone will • If you can’t prevent all abuse you need to be able to detect it. • If you have to detect anyway, then you can optimize prevention and detection, maybe you don’t need so much prevention • We have very little by way of telemetry to support detection in today’s ‘interactions’

  6. Telemetry? Data to help with… • “Please just tell me” • What’s my machine doing? • Weather Report or “Eyewitness Account” • Performance of the next packet, or the last packet? • So what the heck *really* happened • Who says what happened • Digital forensics

  7. Other Telemetry • Dearth of useful diagnostic (mgmt) data • Data useful in application stovepipes, but.. • Interdependent infrastructures need to share too • Among layers/peers in technology • Among layers/peers of organizations • “Dependency in seemingly unrelated events” • Sharing is hard, unpredictable, changing, and ultimately Essential

More Related