O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

API Driven Development 2016-10-27

A brief walkthrough of some ideas on API Driven Development.

  • Entre para ver os comentários

  • Seja a primeira pessoa a gostar disto

API Driven Development 2016-10-27

  1. 1. API Driven Development October 27, 2016
  2. 2. About Me R.J. Salicco Twitter @rjsalicco LinkedIn /in/rjsalicco GitHub /rjsalicco www.rjsalicco.com www.axiomaticit.com rj.salicco@axiomaticit.com
  3. 3. Application Programming Interface - Allows external systems to interact with a system - Exposes functionality - Exposes data
  4. 4. Modular Code - Easier to test and debug - Easier to maintain - Plug and play technology* - Easier to learn - Logical separation
  5. 5. Wait, I Know This, Don't I? - Interface - Abstraction - Encapsulation - Discrete functions - Enforcing logical boundaries
  6. 6. What's Changed? - Use HTTP in a RESTful manner - Modern products are API enabled - JSON (or XML) - Design is (more) open - Implementation - Java, .NET, Ruby, Groovy - You choose?*
  7. 7. Building Data First - System Layer - Data, Core Systems - Process Layer - Composition, Aggregation, Process - Experience Layer - Consumer based: Mobile, Web, IoT
  8. 8. Avoid "Build it and they will come!" - You (should) know what you are building before you build it - Many of us already work this way - No more cowboy coding* - Write code with purpose
  9. 9. The Life Cycle of an API - Pick your poison - Analysis, Development, Operations, Retirement - Proposed, Accepted, Designed, Approved, Released, Deprecated, Retired - Requirements, Modeling, Specification, Implementation - Etc., etc. - What kind of governance do you need? - How do you work?
  10. 10. Practice: Center of Excellence - Integration team focused on solutions - Not as scalable - Can become bottleneck - Technology over practice, governance
  11. 11. Practice: Center of Enablement - Integration team focused on platform - Integration team focused on framework(s) - Integration team focused on solutions that enable - Requires governance - More scalable (horizontal vs. vertical)
  12. 12. Design Tools - RAML - yaml like - http://raml.org - Swagger - json or yaml like - http://swagger.io - Human readable format - Extend API design resources - Be familiar with both
  13. 13. Questions?

×