#hacksummit 2016 - event-driven microservices – Events on the outside, on the inside and at the...
-
Upload
chris-richardson -
Category
Software
-
view
5.973 -
download
2
Transcript of #hacksummit 2016 - event-driven microservices – Events on the outside, on the inside and at the...
@crichardson
Events on the outside, on the inside and at the coreChris Richardson
Founder of Eventuate.io Founder of the original CloudFoundry.com Author of POJOs in Action
@crichardson [email protected] http://microservices.io http://eventuate.io http://plainoldobjects.com
@crichardson
Presentation goal
Events play a key role in applications
Event sourcing enables the event-driven enterprise
@crichardson
About Chris
@crichardson
About Chris
Consultant and trainer focusing on
microservices (public class: April 28th, Oakland, CA)
http://www.chrisrichardson.net/
@crichardson
About Chris
Founder of a startup that is creating
a platform that makes it easy for application developers to write
microservices
http://eventuate.io
@crichardson
For more information
http://bit.ly/eventsfeb24
@crichardson
Agenda
Events on the outside
Events on the inside
Events at the core with event sourcing
Designing event-centric domain model
@crichardson
Events on the outside
Application A
Application B
Application C
Event X
Event YEvent Z
@crichardson
What’s an event?
http://www.merriam-webster.com/dictionary/event
@crichardson
Examples of events
@crichardson
Instacart: event-driven grocery shopping
@crichardson
An event is produced when…
Creation or update of a business object
Attempt to violate a business rule
@crichardson
How to reliably generate events?
More on that later…
@crichardson
Who consumes an event?
Order Application
HumanNotification Service
Dashboard/ Monitoring
Shipping Application
OrderCreated
Email SMS …
@crichardson
How to deliver events?
@crichardson
Inside the firewall
@crichardson
Enterprise integration patterns
http://www.enterpriseintegrationpatterns.com/patterns/messaging/
@crichardson
messaging system
Messaging-based IPC
Sender RecipientChannelmessage
@crichardson
Example messaging systems
@crichardson
Outside the firewall
@crichardson
Polling for events
HTTP
Periodically poll for events
Atom Publishing Protocol (AtomPub)
Based on HTTP
Head is constantly changing
Tail is immutable and can be efficiently cached
High-latency, inefficient
@crichardson
Using WebSockets
Browser
Web Socket
STOMP
Client application
Service
Web Socket
STOMP
ApplicationSUBSCRIBE
MESSAGEMESSAGE
Low latency, more efficient, but what about past events?
@crichardson
Webhooks = user-defined HTTP callback
Client Service
register(events, callbackUrl)
POST callbackUrl
POST callbackUrl
…
https://en.wikipedia.org/wiki/WebhookLow latency, more efficient, but what
about past events?
@crichardson
WebHooks =
web friendly publish/subscribe
@crichardson
Github webhookshttps://developer.github.com/webhooks/
Installed on an organization or repository
e.g. POST /repos/:owner/:repo/hooks
Available events:
push - push to a repository
fork - repository is forked
pull_request - assigned, unassigned, …
push - push to a repository
…
@crichardson
Twilio - Telephony and SMS as a service
Twilio Your Application
TwiML doc
HTTP GET/POST
REST API
Manage resourcesSend SMS
Initiate voice calls
Webhooks handle incoming SMS and voice calls
VoiceSMS
Phone number ⇒ SMS URL + VOICE URL
@crichardson
Integration hubs - Zapier, IFTTTApplication abstraction:
Triggers - events published by application: polling or Webhooks
Action - operation supported by application, e.g. REST API end points
@crichardson
The event-driven enterprise
App A App BApp X
App Y
Firewall
Message Broker
webhooks
WebSockets
AtomPub
App Z App C
MsgBrokerClient Msg
BrokerClient
MsgBrokerClient
App D
MsgBrokerClient
Inside the firewallOutside the firewall
@crichardson
Agenda
Events on the outside
Events on the inside
Events at the core with event sourcing
Designing event-centric domain model
@crichardson
Events on the insideApplication
Service A
Service B
Service C
Event X
Event YEvent Z
Event X
Event Y
@crichardson
Traditional monolithic architecture
Simple to develop
test deploy scale
Shopping Cart
CustomersOrders
Mobile client RESTAPI
Browser WebUI
MessageBroker
Adapter
MySQLAdapter
RDBMS
…
Message Broker
@crichardson
But that leads* to monolithic hell
For large and/or complex applications…
@crichardson
Today: use a microservice, polyglot architecture
Orders
Customers
…Shopping UI
Mobile Client
Browser
API Gateway
Order management
RESTAPI
CustomerManagement
RESTAPI
….
RESTAPI
OrderDatabase
(MongoDB)MongoDBAdapter
CustomerDatabase(Sharded MySQL)
MySQLAdapter
@crichardson
But now we have distributed data management
problems
@crichardson
Example: placing an order
Order Service Customer Service
Order Database
Customer Database
Order #1 Customer #1
No 2PC
No ACID
NoSQL SQL
@crichardson
Customer management
How to maintain invariants?
Order management
Order Service
placeOrder()
Customer Service
updateCreditLimit()
Customer
creditLimit ...
has ordersbelongs toOrder
total
Invariant: sum(open order.total) <= customer.creditLimit
?
@crichardson
Use an event-driven architecture
Services publish events when something important happens, e.g. state changes
Services subscribe to events and update their state
Maintain eventual consistency across multiple aggregates (in multiple datastores)
Synchronize replicated data
@crichardson
Event-driven application architectureApplication
Service A Service B
Message Broker
Service C
MsgBrokerClient
MsgBrokerClient
MsgBrokerClient
Service D
MsgBrokerClient
@crichardson
Order ManagementOrder
id : 4567 total: 343 state = CREATED
Customer Management
Customer creditLimit : 12000 creditReservations: {}
Customer creditLimit : 12000 creditReservations: { 4567 -> 343}
Order id : 4567 total: 343 state = OPEN
Eventually consistent credit checking
Message Bus
createOrder()
Publishes:Subscribes to:
Subscribes to:
publishes:
OrderCreatedEvent
CreditReservedEvent
OrderCreatedEvent CreditReservedEvent
@crichardson
Now there are two problems to solve….
@crichardson
Problem #1: How to design eventually consistent business logic?
More on that later….
@crichardson
Problem #2: How to atomically update database and publish an event
Order Service
Order Database
Message Broker
insert Order
publish OrderCreatedEvent
dual write problem
?
@crichardson
Failure = inconsistent system
Order Service
Order Database
Message Broker
insert Order
publish OrderCreatedEvent
X
@crichardson
Two-phase commitX
@crichardson
Agenda
Events on the outside
Events on the inside
Events at the core with event sourcing
Designing event-centric domain model
@crichardson
Just publish events
Application
Database
Message Broker
update
publish
X
@crichardson
Event sourcingFor each aggregate (business entity):
Identify (state-changing) domain events
Define Event classes
For example,
ShoppingCart: ItemAddedEvent, ItemRemovedEvent, OrderPlacedEvent
Order: OrderCreated, OrderCancelled, OrderApproved, OrderRejected, OrderShipped
@crichardson
Persists events NOT current state
Order
status ….
101 ACCEPTED
Order tableX
@crichardson
Persists events NOT current state
Event table
Entity type Event id
Entity id
Event data
Order 902101 …OrderApproved
Order 903101 …OrderShipped
Event type
Order 901101 …OrderCreated
@crichardson
Replay events to recreate state
Order
state
OrderCreated(…) OrderAccepted(…) OrderShipped(…)
Events
Periodically snapshot to avoid loading all events
@crichardson
The present is a fold over history
currentState = foldl(applyEvent, initialState, events)
@crichardson
Events at the core
Aggregate A
Aggregate B
Aggregate C
Event X
Event YEvent ZEvent Z
Event Y
Service
@crichardson
Domain logic = event-driven aggregates
CustomerAggregateOrder
Aggregate
Order CreatedEvent Check Credit
Command
Credit ReservedEvent
Approve OrderCommand
Create OrderCommand
External request
Emits events Event ⇒ Command
@crichardson
Request handling in an event sourced application
HTTP Handler
Event Store
pastEvents = findEvents(entityId)
Order
new()
applyEvents(pastEvents)
newEvents = processCmd(SomeCmd)
saveEvents(newEvents) (optimistic locking)
Order Service
apply(newEvents)
@crichardson
Event Store publishes events consumed by other services
Event Store
Event Subscriber
subscribe(EventTypes)
publish(event)
publish(event)
Customer
update()
Customer Service
@crichardson
Event Store publishes events consumed by other services
Event Store
Event Subscriber
subscribe(EventTypes)
publish(event)
publish(event)
CQRS View
update()
Service Xyz
send notifications
…
Event store = database + message broker
Hybrid database and message broker
Implementations:
Home-grown/DIY
geteventstore.com by Greg Young
http://eventuate.io (mine)
Event Store
Save aggregate
events
Get aggregate
events
Subscribe to events
@crichardson
Benefits of event sourcingSolves data consistency issues in a Microservice/NoSQL based architecture
Reliable event publishing: publishes events needed by predictive analytics etc, user notifications,…
Eliminates O/R mapping problem (mostly)
Reifies state changes:
Built in, reliable audit log,
temporal queries
Preserved history ⇒ More easily implement future requirements
@crichardson
Drawbacks of event sourcing…
Requires application rewrite
Weird and unfamiliar style of programming
Events = a historical record of your bad design decisions
Must detect and ignore duplicate events
Idempotent event handlers
Track most recent event and ignore older ones
…
@crichardson
… Drawbacks of event sourcing
Querying the event store can be challenging
Some queries might be complex/inefficient, e.g. accounts with a balance > X
Event store might only support lookup of events by entity id
Must use Command Query Responsibility Segregation (CQRS) to handle queries ⇒ application must handle eventually consistent data
@crichardson
Agenda
Events on the outside
Events on the inside
Events at the core with event sourcing
Designing event-centric domain model
@crichardson
Use the familiar building blocks of DDD
Entity
Value object
Services
Repositories
Aggregates ⟸ essential
About AggregatesGraph consisting of a root entity and one or more other entities and value objects
Each core business entity = Aggregate: e.g. customer, Account, Order, Product, ….
Reference other aggregate roots via primary key
Often contains partial copy of other aggregates’ data
Order
OrderLine Item
quantity productId productName productPrice
customerId
Address
street city …
@crichardson
Domain model = collection of loosely connected aggregates
Order
OrderLine Item
quantity
…
Addressstreet city …
Customer
Productname price
@crichardson
Product service
Customer serviceOrder service
Easily partition into microservices
Order
OrderLine Item
quantity
…
Addressstreet city …
Customer
Productname price
@crichardson
Transaction = processing one command by one aggregate
No opportunity to update multiple aggregates within a transaction ⇒ event driven eventual consistency between aggregates
If an update must be atomic (i.e. no compensating transaction) then it must be handled by a single aggregate
Therefore, aggregate granularity is important
@crichardson
Product service
Customer serviceOrder service
Transaction scope = service
Order
OrderLine Item
quantity
…
Addressstreet city …
Customer
Productname price
@crichardson
Aggregate granularity
Consistency Scalability/ User experience
Customer
Order
Product
Customer
Order
Product
Customer
Order
Product
Designing domain eventsRecord state changes for an aggregate
Part of the public API of the domain model ProductAddedToCart
id : TimeUUID senderId: UUID productId productName productPrice …
Required by aggregate
Enrichment: Useful for
consumers
Event metadata
@crichardson
Example event
@crichardson
Designing commandsCreated by a service from incoming request
Processed by an aggregate
Immutable
Contains value objects for
Validating request
Creating event
Auditing user activity
@crichardson
Example command
@crichardson
Various programming models
“Traditional Java” mutable object-oriented domain objects
https://github.com/cer/event-sourcing-examples/tree/master/java-spring
Functional Scala with immutable domain objects
https://github.com/cer/event-sourcing-using-scala-typeclasses
Hybrid OO/Functional Scala with immutable domain objects
https://github.com/cer/event-sourcing-examples/tree/master/scala-spring
@crichardson
OO = State + Behavior
creditLimit creditReservations : Map<OrderId, Money>
Customer
List<Event> process(CreateCustomerCommand cmd) { … } List<Event> process(ReserveCreditCommand cmd) { … } … void apply(CustomerCreatedEvent anEvent) { … } void apply(CreditServedEvent anEvent) { … } …
State
Behavior
@crichardson
Familiar concepts restructured
class Customer {
public void reserveCredit( orderId : String, amount : Money) {
// verify
// update state this.xyz = … }
public List<Event> process( ReserveCreditCommand cmd) { // verify … return … new CreditReservedCredit(); }
public void apply( CreditReservedCredit event) { // update state this.xyz = event.xyz }
@crichardson
Real-time, collaborative Kanban Board
@crichardson
Kanban domain model
Board
title createdBy …
Task
title state …
@crichardson
ArchitectureCreate/update boards
and tasks
Change notifications Materialized views
Event Store
@crichardson
Request and event flow
Eventuate event store
Kanban Server
AngularJS application POST
/tasks/xyz/start
Task xyz
POST /entity/….
Task StartedAngularJS
applicationWebSocket Message
STOMP Message
@crichardson
Demo
@crichardson
Summary
Events are a central to modern applications
Events integrate applications
Events maintain data consistency in a microservices architecture
⇒
Build events into the core of your application using event sourcing
@crichardson
For more information
http://bit.ly/eventsfeb24