Microservices 2015 Vienna

1. AGILE WEB DEVELOPMENT
MicroServices

2. MONOLITH
• dependencies
• locks
• hard to deploy
• side effects

3. AGILE
• independent
• productive
• sustained
• scale
• continuously

4. PERSPECTIVES
• agile architecture
• development
• delivery & operation
• in practice

5. LOOSE COUPLING
• self contained
systems
• location transparency
• async communication

6. BOUNDED CONTEXT

7. DECOMPOSITION
Sales DistributionAccountingMarketing
Recommendation
Campaign
Coupon
…
Catalog
Price
Calculations
…
Payment
Invoices
…
Availability
Shipping
…

8. COMPOSITION
on Service Level

9. MICROSERVICE
The
Unix
Way
Each APP only does one thing
Small enough to fit your head
Small enough to throw away

10. SELF-CONTAINED
• lightweight communication
• independent development
• independent deployment (container, package
manager)
• strict contracts & versions
• one process
• UI & (temporary) store included

11. 12-FACTOR APP
• log to stdout
• bundle config via ENV-Var
• explicit port bindings
• scale via processes
• share nothing
• prefer stateless / temporary
states
• start fast / graceful shutdown
• decouple admin process

12. SYSTEM OF SYSTEMS
• distributed
• integration
• dependencies
• state & consistency
guarantees
• fast releases
• parallel
development
• scale vertical &
horizontal
• resilient

13. RELEASE IT!
DEV OPS
Architecture
Infrastructure

14. FEATURE TEAMS

15. CROSS CUTTING
• OAuth(2)
• Tracking
• Testing
• Configuration

16. CHOOSE

17. NOT A FREE LUNCH
• what? learn & improve
• discuss & agreement
• explicit failure
strategies
• documentation

18. PRACTICE
• functional prototype
• ui, services & integration
• delivery & operations infrastructure
• resilient & scale
• monitoring & SLAs

19. PROTOTYPE
Web-App Back-Office

20. INTEGRATION

21. HANDS ON

22. DECOUPLE
COMMUNICATION
• async
• timeouts & retry
• circuit breaker
• fallback

23. INTEGRATION
• Links, Frames, Redirects
• AJAX
• SDK

24. INTEGRATION
• Data Replication
• WebHooks
• Request/Response
• Dedicated App-DB
• Message Broker

25. MANAGE STATE
• trade off - explicit state
• relaxed consistency
• avoid persistent data
• prefer in-memory + expiry
• prefer replication

26. RESILIENT & SCALE
• failure compensation (retry, fallback, cache, etc.)
• data correlation
• CQRS / ES / LOGS
• client side load balance
• algorithm for traffic distribution (e.g. shards)
• scoring per read and write operations

27. SERVICE TEMPLATE
• rapid application development
• experimental & feasibility development
• batteries includes (UI, Storage, Streams,
Tasks, etc.)
• simple to extend
• simple to deploy

28. DELIVERY & OPERATIONS
SOURCEGIT PUBLISH
DELIVER
MONITOR
DISCOVER

29. DELIVERY
cURL

30. SERVICE DISCOVERY

31. HEALTH CHECK

32. LOG COLLECTOR

33. MONITORING
Notifications

34. AUTO REGISTER
• Services
• Health-Checks
• Log-Collection

35. SLA
• 99,9% availability
• 90% < 500ms click
performance
• 80% < 1s data
processing performance
• 60% integration test
errors

36. THANK YOU
Questions?