Breakout session at the API Strategy conference Nov 20, 2015.

1. The Fork in the API
App-centric vs Job-centric Microservices
Ivan Dwyer | Head of Business Development | Iron.io | @fortyfivan

2. “Loosely coupled service oriented
architecture with bounded contexts”
- Adrian Cockroft
characteristics of a microservice

3. a containerized workflow sets the stage
runshipbuild
Dockerfile Docker Image Docker Container Docker Daemon
?

4. “The intended lifecycle of the workload itself
determines how a microservice should behave”
- Me
but what about its behavior?

5. a further distinction needs to be made
App-centric
Real-time requests
Job-centric
Background processes

6. how does it run?
Synchronous Asynchronous
request 1
response 1
request 2
response 2
waitwait
request 1
response 1
request 2
response 2

7. how is it deployed?
Staged Uploaded
Runtime Image
Repo
push upload

8. how is it invoked?
Request Event
request
Client Event
trigger
response

9. how is it routed?
Load Balancer Queue
Load
Balancer

10. how does it fail?
Reroute Retry
Load
Balancer
retry

11. how does it scale?
Elastic Concurrent
Load
Balancer

12. how does it execute?
Long Running Ephemeral
start stop
process

13. how does it get data?
Connection Payload
DB

14. when to do what?
Stream processing
Real-time analytics
Client requests
Database queries
User facing processes
Scheduled jobs
Batch processing
Transactions
Mobile backends
ETL pipelines

15. event-driven computing for cloud native applications
queue, schedule and execute
job-centric microservices at scale
www.iron.io