SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
The Bezos Mandate 1. All
teams will expose their data and functionality through service interfaces. https://plus.google.com/112678702228711889851/posts/eVeouesvaVX
The Bezos Mandate 1. All
teams will expose their data and functionality through service interfaces. 2. Teams must communicate with each other through these interfaces. https://plus.google.com/112678702228711889851/posts/eVeouesvaVX
The Bezos Mandate 1. All
teams will expose their data and functionality through service interfaces. 2. Teams must communicate with each other through these interfaces. 3. There will be no other form of interprocess communication allowed: no direct linking, no direct reads of another team's data store, no shared- memory model, no back-doors. https://plus.google.com/112678702228711889851/posts/eVeouesvaVX
The Bezos Mandate 4. It
doesn't matter what technology they use. https://plus.google.com/112678702228711889851/posts/eVeouesvaVX
The Bezos Mandate 4. It
doesn't matter what technology they use. 5. All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions. https://plus.google.com/112678702228711889851/posts/eVeouesvaVX
The Bezos Mandate 4. It
doesn't matter what technology they use. 5. All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions. 6. Anyone who doesn't do this will be fired. https://plus.google.com/112678702228711889851/posts/eVeouesvaVX
Jason Griffey Email: griffey@gmail.com Site:
jasongriffey.net gVoice: 423-443-4770 Twitter: @griffey Other: Perpetual Beta ALA TechSource Head of Library Information Technology http://pinboard.in/u:griffey/ University of Tennessee at Chattanooga
Editor's Notes
I’m not going to make a case for any one service, although I am going to mention one company that I think is doing the best job at what I’m going to describe. \n
\n
from wikipedia\n
An operating system is a platform...it allows for the development of applications that run on top of it, and that rely on the OS to perform some of the heavy lifting by communicating directly with the hardware. \n
What is this? This is maybe what you think of when you think of Amazon, but in 2002 Jeff Bezos changed the direction of the company forever with his Mandate.\n
From around 2002 \nEnd of Part 3: The only communication allowed is via service interface calls over the network.\n
From around 2002 \nEnd of Part 3: The only communication allowed is via service interface calls over the network.\n
From around 2002 \nEnd of Part 3: The only communication allowed is via service interface calls over the network.\n
From around 2002\n
From around 2002\n
From around 2002\n
that’s not what Amazon is...\n
The right platform extends your capabilities. It keeps you from having to worry about low-level infrastructure, and frees you to develop services that directly impact your patrons. \n
At their best, a well-built platform can seem like it makes magic possible. The allow for more development at a lower person-cost for libraries...and in the best of all worlds, they can actually let patrons build their own interfaces as well. Think about the number of different Twitter clients that are available...now imagine if your catalog had that kind of freedom. How could that help your patrons? \n
Doesn’t this look a lot like...\n
....this?\n
\n
\n
\n
Eventually you’ll be able to share your data freely across the web...\n
...and although we’re different libraries, we could have a common data set that could allow our patrons a great deal more power in accessing the info they need. Worldcat is a tiny, tiny example of the sorts of things that could be possible. \n
A connection with our data, and we can let people make connections that we don’t see.\n
We can build and share our resources because we’ll be writing on a common platform.\n