Top Banner
@windley The University API Phillip J. Windley, Ph.D. Brigham Young University http://www.windley.com
59

A University API

Apr 15, 2017

Download

Education

Phil Windley
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: A University API

@windley

The University API

Phillip J. Windley, Ph.D.Brigham Young Universityhttp://www.windley.com

Page 2: A University API

@windley

Page 3: A University API

@windley

Page 4: A University API

@windley 4

Software is Eating the World!More and more major businesses and industries are being run on software and delivered as online services—from movies to agriculture to national defense. Many of the winners are Silicon Valley-style entrepreneurial technology companies that are invading and overturning established industry structures. Over the next 10 years, I expect many more industries to be disrupted by software, with new world-beating Silicon Valley companies doing the disruption in more cases than not.

- Marc Andreessen

Page 5: A University API

@windley

Page 6: A University API

@windley

Page 7: A University API

@windley

{“answer”: “University API”}

Page 8: A University API

@windley

Page 9: A University API

@windley

Page 10: A University API

@windley

API

Page 11: A University API

@windley

APIAPI

Page 12: A University API

@windley

Page 13: A University API

@windley

Page 14: A University API

@windley

Page 15: A University API

@windley

Page 16: A University API

@windley 16

Bake your business model into your API

- John Musser Founder, Programmable Web

“”

Principle #1: Design Business-Oriented APIs

Page 17: A University API

@windley

Page 18: A University API

@windley

/students/instructors/courses/classes/locations/programs/colleges/departments

Page 19: A University API

@windley

Page 20: A University API

@windley

Principle #2: Ensure interfaces are open, extensible, and published

Page 21: A University API

@windley

GET /studentsGET /students?major=CS

GET /students/:idGET /students/:id?fieldset=transcripts

Page 22: A University API

@windley

POST /students

{id: ... first_name: ... last_name: ... ...

}

Page 23: A University API

@windley

Page 24: A University API

@windley

Principle #3: Support student and faculty choice.

Page 25: A University API

@windley

Page 26: A University API

@windley

Page 27: A University API

@windley

Principle #4: Access Control Happens at the API

Page 28: A University API

@windley

Page 29: A University API

@windley

Page 30: A University API

@windley

Page 31: A University API

@windley

Page 32: A University API

@windley

Page 33: A University API

@windley

Principle #5: Keep workflow below the API

Page 34: A University API

@windley

Page 35: A University API

@windley

Page 36: A University API

@windley

HATEOASHypertext as the Engine of

Application State

Page 37: A University API

@windley

An ever expanding range of computing platforms are needed to reach students

Page 38: A University API

@windleySource: Morgan Stanley Mobile Internet Report (12/09)

Page 39: A University API

@windley

Hundreds, even thousands of developerswho don’t work for youmust be convinced to adapt your product to the dynamic environment of various apps

Page 40: A University API

@windley

Principle #6: Developers are Your Customer

Page 41: A University API

@windley

Page 42: A University API

@windley

Principle #7: Cloud First

Page 43: A University API

@windley

Page 44: A University API

@windley

Principle #8: Security is Too Important to Not Outsource

Page 45: A University API

@windley

Page 46: A University API

@windley

Page 47: A University API

@windley

Principle #9: Focus on What’s Core

Page 48: A University API

@windley

Page 49: A University API

@windley

Principle #10: APIs First

Page 50: A University API

@windley

Page 51: A University API

@windley

Page 52: A University API

@windley

Principle #11: Start Where You Are

Page 53: A University API

@windley

Page 54: A University API

@windley

Principles for Starting an API Initiative1. Design business-oriented APIs2. Ensure interfaces are open, extensible, and published3. Support student and faculty choice.4. Control access at the API5. Keep workflow below the API6. Make developers the customer7. Be cloud first8. Security is too important to not outsource9. Focus on what’s core10. Buy and build API first11. Start where you are

Page 55: A University API

@windley

Resources• Mashup Corporations’• The Phoenix Project• Implementing Domain Driven Design• Kin Lane on University APIs• windley.com

Page 56: A University API

@windley

Join us on this journey

• @UniversityAPI• University API Workshops• Utah, Feb 28-Mar 1, 2017 (http://bit.ly/UAPI2017)• Chicago Summer 2017

Page 57: A University API

@windley

The University API

Phillip J. Windley, Ph.D.Brigham Young Universityhttp://www.windley.com

Page 58: A University API

@windley

Page 59: A University API

@windley

Other issues• Other university APIs: services like lockers, vending machines, health,

payments, HR, calendars, assets, library, collections