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. Building Data First
- System Layer
- Data, Core Systems
- Process Layer
- Composition, Aggregation, Process
- Experience Layer
- Consumer based: Mobile, Web, IoT
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. 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. Practice: Center of Excellence
- Integration team focused on solutions
- Not as scalable
- Can become bottleneck
- Technology over practice, governance
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. 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