Content Management & Microservices - Drupal Business Days · 2017-05-28 · Microservices A...
Transcript of Content Management & Microservices - Drupal Business Days · 2017-05-28 · Microservices A...
Content Management & Microservices
A Unifying Strategy for the Distributed Enterprise
Zach ChandlerDirector, Research IT & InnovationOffice of the Vice Provost and Dean of ResearchStanford University
Wait, who are you? … (and why should I care?)Zach Chandler
Research IT & Innovation
Stanford University
● API Strategy 2012 - present
● Web Strategist, Stanford Web Services (SWS) 2011-2015
● Drupal since 2006
Stanford & Silicon Valley (in 90 seconds)
Silicon Valley & Stanford
Fred Terman (1900-1982)● Dean of Engineering (14 years)
● Provost (10 years)
● Mentor, visionary, strategist
Fast Forward to the present
Inherent tension: innovation vs. stability
APIs open the door to innovation
APIs are disruptive
APIs are hard to do right, at scale, in production
We are trying to be intentional about creating “production ready” microservices
API Strategy at Stanford● Pragmatic REST
● OAuth 2.0
● JSON
● API Catalog
● Concurrent client release
● Community of Practice
DX = Developer Experience
Get Help! (we asked Apigee: RAD workshop, circa 2012)
Profiles: our first REST API
Simultaneous Release: API + Client
Drupal: how the CMS ties it all together● 1000+ Drupal sites at Stanford (yes, really)
Many of which on a common distribution
● API client modules included in distro out of the box,
making all of them API-ready
● No special skills required to connect, simple config:
That is the difference between adoption and failure.
Benefits of Drupal as primary client● Incredibly flexible
● Shift server load from API
● Reduces requests for added functionality (for API)
● End users can configure as needed
● Persistence of content
The Future: A Microservices Ecosystem
API Gateway