Skip to content
Owen Rubel edited this page Jul 11, 2017 · 4 revisions

Owen Rubel

Owen Rubel is an original team member of Amazon(95-98) and the creator of API Chaining(tm) and Shared I/O State. He is also a contributor to the Reactive Manifesto and well as the maintainer of the open source BeAPI Framework. He currently works for the High Performance Computing Team at the University of Washington.

Talks

The New API Pattern

  • Level : Intermediate
  • Description : The original API Pattern was design in the 1970's for centralized architectures and enever was designed for distributed architectures where I/O had to be shared across services and networks. As a result, companies all the way up to Amazon and Netflix experience an issue known as an 'architectural cross cutting concern' caused by the binding of the communication and the business logic resulting from the original API pattern. This talk is designed to show you this issue, how it affects you and the new pattern that fixes these issue for IOT and distributed architectures.
  • Background : NA
  • Slides : Here

REAL API Chaining (TM)

  • Level : Intermediate
  • Description : API Chaining(TM) is an open source process that involves abstraction of communication layer from business logic on the backend so you can share you I/O state. By Doing this, you can DYNAMICALLY chain/batch API's using ONE request/response. This differs from others who have illegally used the term 'API Chaining' in that:
  • their is no hardcoding of the relationships between the chains
  • it is not based on Rest URIs/Eager fetching (hence it is relational; not heirarchical)
  • it uses one request/response. Not one per API call!

Clone this wiki locally