Microservices are a service-oriented architecture composed of loosely coupled elements that have bounded contexts. Each microservice can be updated independently without risking other services. Considerations for microservices include the complexity of building distributed systems, increased number of components to manage, steps needed to maintain data consistency across services, and increased network latency and API traffic. Iron.io advocates for empowering developers by providing abstraction, self-service tools, and focusing on code.

1. MICROSERVICES
www.iron.io
Architecture and Practice

2. About Iron.io
Infrastructure
Runtime Apps Async Workloads
APIs
>50% of the modern workload processing
happens in the background asynchronously.
IronMQ IronScheduler
IronWorker

3. Microservices

4. Microservices Search Trend

5. A service-oriented architecture composed of
loosely coupled elements that have bounded contexts.
Microservices
Every service can be updated
independently and without risk
Model where you don’t need to
know internals of peer services.
Adrian Cockcroft, Battery Ventures
(previously lead cloud architect for Netflix)

6. Monolith vs Microservices
All functions, single process Single function per process
scale by replicating monolith across nodes scale by distributing services across nodes

7. Considerations
➔ Building and maintaining highly available
distributed systems is complex
➔ More moving parts means more components to
keep track of and configure properly
➔ Loosely coupled services means steps must be
taken to keep data consistent
➔ Distributed asynchronous processes create
network latency and more API traffic
➔ Testing and monitoring individual services is
challenging

8. What We’ve Learned at Iron.io

9. Empowering Developers
⬢ Innovation depends on developers
⬢ Developers want abstraction
⬢ Developers want self-service
⬢ Developers want tools to get out of the
way
⬢ Developers want to write code!

10. Code API
URL HTTP Verb Purpose
/projects/{Project ID}/codes GET List Code Packages
/projects/{Project ID}/codes POST Upload or Update a Code Package
/projects/{Project ID}/codes/{Code ID} GET Get Info About a Code Package
/projects/{Project ID}/codes/{Code ID} DELETE Delete a Code Package
/projects/{Project ID}/codes/{Code ID}/download GET Download a Code Package
/projects/{Project ID}/codes/{Code ID}/revisions GET List Code Package Revisions
IronWorker makes it easy to write, package, and upload code to our system

11. Task API
URL HTTP Verb Purpose
/projects/{Project ID}/tasks GET List Tasks
/projects/{Project ID}/tasks POST Queue a Task
/projects/{Project ID}/tasks/webhook POST Queue a Task From a Webhook
/projects/{Project ID}/tasks/{Task ID} GET Get Info About a Task
/projects/{Project ID}/tasks/{Task ID}/log GET Get a Task's Log
/projects/{Project ID}/tasks/{Task ID}/cancel POST Cancel a Task
/projects/{Project ID}/tasks/{Task ID}/progress POST Set a Task's Progress
/projects/{Project ID}/tasks/{Task ID}/retry POST Retry a Task

12. ● Before: Monolithic PHP app
● After: Services - Social, Geo, Image, Recommendation
Result: 500K check-ins/night, 500ms response, 1 engineer
Case Study

13. Small Loosely Coupled Teams

14. Stateless by Design
You name them and when
they get sick you nurse them
back to health.
You number them and when
they get sick, you shoot them.

15. Stateless by Design

16. Stateless using Webhooks
● Job can be kicked off using a webhook
URL and HTTP Post
● Create powerful workflow between
workers, services, and other endpoints

17. Case Study
● Before: A single process that handles the entire ETL pipeline
● After: A set of stateless services that only understand their single
purpose functions. Each scale independently.
Result: Dozens of sources syncing 24x7 with NO infrastructure
Cloud ETL

18. Queue all the Things
➔ Decouples
➔ Buffers
➔ Delivery/Order properties
➔ Async Communication

19. Services: Collection, Process, Send
● Intelligent speed bumps that activate only when needed
● Road modules collect speed, vehicle type, and other data
● Ops gains intelligence for traffic management and flow
Result: Faster and simpler data collection
and processing
Case Study
IoT Data Collection and Processing

20. Containerize Everything
⬢ Can be any but Docker is winning
⬢ Stateless and horizontal scaling
⬢ Deploy anywhere
⬢ Enables full developer workflow and CI/CD

21. Monitor, Alert, Analyze
Runtime Monitoring
Audit trails
Logging
Error Handling
Alerting
Performance Testing

22. Worker/Service List

23. Tracking Activity

24. Polyglot Persistence
Key/Value
Rapid access for reads/writes
SQL
Transactional data
NoSQL
High volume reads
File
Distributed file system

25. Share Nothing, Denormalize
Service A Service B
MDM

26. Iron.io
325 9th St
San Francisco, CA 94103
1-888-939-4623
www.iron.io
sales@iron.io
THANK YOU
QUESTIONS?