Across the 200,000+ APIs we've seen at Apiary, here are 5 simple lessons on what to watch out for when switching to micro services. First presented at SF Microservices meetup on May 19th, 2016.

1. Scaling your
API Design
workflow

2. Jakub Nesetril
@jakubnesetril

3. Apiary

4. API Craft
San Francisco
» February - APIs and IoT
» March - API Design Hackathon
» June - ?
meetup.com/API-Craft-San-Francisco
#apicraftsf

5. (REST) API Design &
Collaboration

6. » 211k APIs
» 180k API Designers
» 2.1M API Developers
» GitHub, CI, prototyping, documentation, design
& governance
» support Swagger, API Blueprint & OpenAPI
Specification

7. Most APIs are not public

8. It's all fun and games when you have a
single API...

9. ...what happens when you have 100's

10. 1,000's?

11. 5 simple rules:

12. #1 Standardize

13. #1
Standardize
» processes (design, Git flow, approval,
deployment)
» protocol (gRPC, hypermedia, restful design)
» semantics (data objects, naming)

14. #2
Automate

15. #2
Automate
» all about speed
» change detection
» compliance, monitoring, deployment

16. #3
Version "less"

17. #3
Version "less"
» API versioning is change management
» if you must, version explicitly (/job/scheduler
+ /job/schedulerAsync)

18. #4
Embrace

19. #4
Embrace
» embrace the consumer, they are your customer
» don't design a service without a usecase
» without a usecase, an API is like a Schrödinger's
cat

20. #5
Decouple

21. #5
Decouple
» resist the urge to couple API automation to
language
» lang independence, refactoring, mocking

22. » Standardize
» Automate
» Version "less"
» Embrace
» Decouple

24. Questions?
jakub@apiary.io
http://apiary.io/