1.
Microservices:
Architecture forthe
Real-time
Organization

2.
Whymicroservices?

3.
heritage
architecture
» Single points of failure
» Impossible to scale out
(shared mutable state, etc)
» Different non-functional
requirements (reads,
writes, compute)
» Optimized for none!
» Long, risky release cycles

4.
Whatare microservices?

5.
Microservices
» Ubiquitous language
» Well defined models &
boundaries
» Single responsibility
» Independantly deployable,
scalable, resilient
» Communicate via async
messaging
» Own their data
» Don't expose a public API

6.
Approach?
Principles
» responsive, resilient,
elastic, message-driven

7.
Approach?
Principles
» responsive, resilient,
elastic, message-driven
Concepts
» bounded contexts (DDD),
event sourcing, CQRS, CAP
(eventual consistency)

8.
Approach?
Principles
» responsive, resilient,
elastic, message-driven
Concepts
» bounded contexts (DDD),
event sourcing, CQRS, CAP
(eventual consistency)
Tools
» Typesafe Reactive Platform
(Play, Akka, Spark)

9.
Conceptsand patterns
We will cover:
» Domain Driven Design (DDD)
» Async messaging
» API management
» Dependency management
» CQRS & event sourcing
» Transactions & ordering

10.
Domain Driven Design

11.
Goingasync

12.
Async Benefits
» Not wasting resources
» Memory, CPU, threads
» Embracing failure
» Not expecting a return
from a remote service
» Designing for all
scenarios

13.
AkkaActors
» Message driven architecture
» Distribution
» Location transparency
» Isolation

14.
API management

15.
API mgmt.
» Messaging patterns
» Pub/sub, point-to-point,
streaming
» API gateway
» Routing, aggregation,
protocol translation
» Discovery
» Service discovery,
registry, versioning

16.
Dependencymanagement

17.
CQRS & eventsourcing

18.
Transactionsand
ordering

19.
Considerations
» ACID doesn't work across location/trust boundaries
» No 2-Phase commits (2PC)
» No holding locks for the duration of work
» In distributed systems we need to compensate for
for failure rather than prevent failure

20.
Whatnext?

21.
Microservices
withTypesafe
» Play for API gateway
» Akka for core microservices
(DDD, CQRS, event sourcing)
» ConductR for cluster
management (service
registry, discovery,
architecture visualization,
security)

22.
Thankyou!
Visit https://www.typesafe.com/products/typesafe-
reactive-platform to get started
Contactinfo
» Twitter: @kvnwbbr
» Email: kevin.webber@typesafe.com