Reactive APIs for Microservices Using Reactive Streams
•Download as ODP, PDF•
1 like•205 views
The document discusses reactive APIs and microservices architectures. It introduces the concept of reactive systems as being responsive, resilient, elastic, and message-driven. It then discusses some issues with using RPC-style APIs between microservices, such as fragility and data silos. As an alternative, it presents the concept of reactive technologies like message-based communication using protocols like the Muon reactive streams protocol. It also discusses using event logs and streaming data between services using this approach. Finally, it gives examples of implementing domain-driven design patterns on top of a reactive event log API using the Newton library.
Recommended
Recommended
More Related Content
Similar to Reactive APIs for Microservices Using Reactive Streams
Similar to Reactive APIs for Microservices Using Reactive Streams (20)
More from David Dawson
More from David Dawson (8)
Recently uploaded
Recently uploaded (20)
Reactive APIs for Microservices Using Reactive Streams
- 1. Reactive APIsReactive APIs usingusing LJC – 2017-10-16
- 2. David Dawson me@daviddawson.me Microservices | JVM | IoT consultant Organiser, London Microservices User Group, Founder, Muon Project – http://muoncore.io http://daviddawson.me
- 5. Isolation
- 6. Aspiration
- 22. Orders
- 29. Orders Product Users Auth Fulfillment Order X Default Product Name: £12 Default Product Name: £99 Default Product Name: £77 Shipping Date: No idea.
- 30. Orders Product Users Auth Fulfillment This Service is broken by its dependencies breaking
- 31. Orders Product Users Auth Fulfillment 99.999% uptime for each service 5 services in a web ~25 mins/ year downtime. Guaranteed
- 33. FragileFragile
- 35. FragileFragile Higher LatencyHigher Latency Data is Relational...Data is Relational...
- 36. FragileFragile Higher LatencyHigher Latency Data is Relational...Data is Relational... .... Inner Join over HTTP.... Inner Join over HTTP
- 37. RPC APIs + MicroservicesRPC APIs + Microservices == Data SilosData Silos
- 38. :-(:-(
- 39. Reactive
- 45. Reactive System
- 47. Designing Reactive Systems With Great Power.... ....comes great responsibility
- 48. Using Data Your data is here
- 49. Using Data Your data is here You need it here.
- 50. Using Data RPC Fragile, etc ...
- 51. Using Data Materialise View Eventually consistent Resilient Best performance
- 53. Using Data SEDA – Staged Event Driven Architecture
- 56. Reactive Tech Selection Message Based Manage State
- 57. Reactive Technologies Actors – Akka/ Logam SEDA Events – Lambda, Vertx etc Data Flow/ CSP – Spring Data Flow Event Logs – Kafka, EventStore.io
- 58. What have you lost? Reactive Systems
- 59. APIs
- 60. APIs == HTTP
- 61. APIs == HTTP Discovery Docs (swagger et al) Well defined Technical Interaction model monitoring testing tech autonomy
- 62. HTTP: Technical Interaction Model HTTP API "GET me X please" "Here is X"
- 63. APIs Docs (swagger et al) Discovery Well defined Technical Interaction model monitoring testing== HTTP tech autonomy
- 64. APIs == HTTP Docs (swagger et al) Discovery Well defined Technical Interaction model monitoring testing tech autonomy
- 65. APIs == HTTP Docs (swagger et al) Discovery Well defined Technical Interaction model monitoring testing
- 66. :-(:-(
- 67. Reactive tech as an API surrogate
- 68. Building a Reactive System becomes a Strategic Choice
- 69. APIs == HTTP
- 70. APIs == HTTP
- 72. APIs Reactive
- 73. APIs Message
- 74. Reactive: Technical Interaction Models?
- 75. Reactive: Technical Interaction Models? Reactive API
- 76. Reactive: Technical Interaction Models? Reactive API "I want to trade X for Y"
- 77. Reactive: Technical Interaction Models? Reactive API "I want to trade X for Y" "I offer 10*Y in 2 minutes, or Z now"
- 78. Reactive: Technical Interaction Models? Reactive API "I want to trade X for Y" "I offer 10*Y in 2 minutes, or Z now" "I'll take 10Y"
- 79. Reactive: Technical Interaction Models? Reactive API "I want to trade X for Y" "I offer 10*Y in 2 minutes, or Z now" "I'll take 10Y" "Here is Y"
- 80. Reactive: Technical Interaction Models? Reactive API "I want to trade X for Y" "I offer 10*Y in 2 minutes, or Z now" "I'll take 10Y" "Here is Y" "Here is Y" "Here is Y"
- 81. Reactive: Technical Interaction Models? Reactive API "I want to trade X for Y" "I offer 10*Y in 2 minutes, or Z now" "I'll take 10Y" "Here is Y" "Here is Y" "Here is Y" "Slow down"
- 82. Reactive: Technical Interaction Models? Reactive API "I want to trade X for Y" "I offer 10*Y in 2 minutes, or Z now" "I'll take 10Y" "Here is Y" "Here is Y" "Here is Y" "Slow down" .....
- 83. Reactive: Technical Interaction Models? Technical Messages and Domain Messages [often events]
- 84. Reactive: Technical Interaction Models? Technical Messages and Domain Messages [often events]
- 85. Reactive: Technical Interaction Models? = reusable Communication protocol Technical Messages
- 86. Reactive: Technical Interaction Models? Reactive API "I want to trade X for Y" "I offer 10*Y in 2 minutes, or Z now" "I'll take 10Y" "Here is Y" "Here is Y" "Here is Y" "Slow down" .....
- 87. Reactive: Technical Interaction Models? Reactive API Two Party Negotiation Client Managed Streaming
- 88. APIs Reactive
- 91. Example: Rx from DB to browser
- 93. MongoDB
- 98. Websockets?
- 99. Back pressure?
- 100. Ugh :-(
- 104. The Muon Model
- 105. The Muon Model Discovery Transport Network …. Protocol Client channel N channel channel channel Service X Service 2 Service 1 API App Code …. 1) Your code uses an API 2) The API creates a Protocol 3) The Protocol communicates using messages 4) A transport routes them over the network
- 106. The Muon Model Discovery Transport Network …. Protocol Client channel N channel channel channel Service X Service 2 Service 1 API App Code …. 1) Your code uses an API 2) The API creates a Protocol 3) The Protocol communicates using messages 4) A transport routes them over the network
- 107. The Muon Model Discovery Transport Network …. Protocol Client channel N channel channel channel Service X Service 2 Service 1 API App Code …. 1) Your code uses an API 2) The API creates a Protocol 3) The Protocol communicates using messages 4) A transport routes them over the network
- 108. The Muon Model Discovery Transport Network …. Protocol Client channel N channel channel channel Service X Service 2 Service 1 API App Code …. 1) Your code uses an API 2) The API creates a Protocol 3) The Protocol communicates using messages 4) A transport routes them over the network
- 109. Solution Using Muon
- 110. Muon Reactive Streams A Message based API using http://reactivestreams.org http://github.com/muoncore/stack-reactive-streams
- 111. Muon Reactive Streams Stream Client Stream Server Transport Failure SubscriptionRequested SubAck SubNack Data Complete Error Cancel Request
- 112. Java Server Muon muon = ... ReactiveStreamServer rx = new ReactiveStreamServer(muon); Publisher<Data> pub = doMongoQuery(…); muon.publishSource("/my-big-data", COLD, pub); Muon Reactive Streams
- 113. Node Client muon.subscribe("stream://myservice/my-big-data", {}, (data) => { console.log(“I got data “ + data) }, (error) => {}, () => { // complete}); Muon Reactive Streams
- 119. MongoDB TODO Chrome Microservice? Microservice? MongoDB Muon Gateway 1 websocket, multiplexing Internal comms AMQP | TCP | Kafka ... Browser
- 120. Browser Muon?
- 121. var Muon = require("muonjs") var muon = Muon.client({port:9898}) Browser Muon?
- 122. var Muon = require("muonjs") var muon = Muon.client({port:9898}) muon.subscribe("stream://myservice/my-big-data", {}, (data) => { console.log(“I got data “ + data) }, (error) => {}, () => { // complete}); Browser Muon?
- 124. A brief intro to Event Logs
- 125. Events ? Events ?
- 128. Order Placed Payment Taken Email Sent EventsEvents
- 131. Order Stream Notification Stream Payment Stream EventsEvents
- 132. Order Stream Events
- 136. Reactive tech as an API surrogate?
- 137. The Muon Model Discovery Transport Network …. Protocol Client channel N channel channel channel Service X Service 2 Service 1 API App Code …. 1) Your code uses an API 2) The API creates a Protocol 3) The Protocol communicates using messages 4) A transport routes them over the network
- 138. Muon Event Log API A Message based API http://github.com/muoncore/stack-events
- 139. Java Client Muon muon = getMuon(); EventClient client = new DefaultEventClient(muon); Order order = ... client.event( ClientEvent.ofType("OrderPlaced") .payload(order) .stream("/orders").build()) Muon Event Log API
- 140. Java Client Muon muon = getMuon(); EventClient client = new DefaultEventClient(muon); Subscriber<Event> s = … (RxJava, Reactor etc) client.replay("/requests", REPLAY_ONLY, s); Muon Event Log API
- 141. Building on the Event API Newton http://github.com/muoncore/newton
- 142. DDD patterns onDDD patterns on Muon Event APIMuon Event API JVM onlyJVM only Currently,Currently, Spring Boot FocusedSpring Boot Focused
- 143. compile "io.muoncore:muon-core:7.4.1" compile 'io.muoncore.newton:newton-core:0.0.13' compile 'io.muoncore.newton:newton-spring-starter:0.0.13' …. @SpringBootApplication @Configuration @EnableNewton class MyApplication { static void main(args) { SpringApplication.run(MyApplication, args) } } Setup
- 144. Aggregate RootsAggregate Roots Part of the C in CQRS Transactional Components A Web of Objects, loaded as a Unit Machines to turn Commands into Events
- 145. User: 1 Aggregate RootsAggregate Roots Events UserCreated UserNameUpdated UserActivated Stream contains events for a single User/ entity
- 146. Aggregate RootsAggregate Roots class User extends AggregateRoot<String> { private String email; private boolean active; private String id; User(String email) { raiseEvent(new UserCreated(email)); } public void activateAccount() { raiseEvent(new UserRegistrationConfirmed(id)); } public void delete() { raiseEvent(new UserDeleted(id)); } @EventHandler public void on(UserCreated ev) { id = ev.getId(); Email = ev.getEmail(); } @EventHandler public void on(UserRegistrationConfirmed ev) { active = true } }
- 147. Aggregate RootsAggregate Roots class User extends AggregateRoot<String> { private String email; private boolean active; private String id; User(String email) { raiseEvent(new UserCreated(email)); } public void activateAccount() { raiseEvent(new UserRegistrationConfirmed(id)); } public void delete() { raiseEvent(new UserDeleted(id)); } @EventHandler public void on(UserCreated ev) { id = ev.getId(); Email = ev.getEmail(); } @EventHandler public void on(UserRegistrationConfirmed ev) { active = true } }
- 148. Aggregate RootsAggregate Roots class User extends AggregateRoot<String> { private String email; private boolean active; private String id; User(String email) { raiseEvent(new UserCreated(email)); } public void activateAccount() { raiseEvent(new UserRegistrationConfirmed(id)); } public void delete() { raiseEvent(new UserDeleted(id)); } @EventHandler public void on(UserCreated ev) { id = ev.getId(); Email = ev.getEmail(); } @EventHandler public void on(UserRegistrationConfirmed ev) { active = true } }
- 149. Aggregate RootsAggregate Roots @Autowired EventSourceRepository<User> repo; … repo.newInstance(()-> new User(“someone@hello.com”)); User user = repo.load(id); user.activateAccount(); repo.save(user); ← Events emitted here
- 150. Event ViewsEvent Views The Q in CQRS Materialise a data structure from event streams Provide Queries on it
- 152. Event ViewsEvent Views @Component public class UserInfoView extends SharedDatastoreView { private MongoTemplate mongoTemplate; // constructor & others ommitted public protected String[] eventStreams() { return new String[] { “/user” } } public UserInfo findById(String id) { return mongoTemplate.findById(id, UserInfo.class); } public List<TaskView> listAll() { return mongoTemplate.findAll(UserInfo.class); } @EventHandler public void handle(UserCreatedEvent event) { mongoTemplate.save(new UserInfo(event.getId(), event.getEmail())); }
- 153. Process ManagersProcess Managers Manage event based distributed workflows Machine to turn Events into Commands
- 154. Process ManagersProcess Managers @Scope("prototype") @Component @SagaStreamConfig(aggregateRoots = {User.class}) public class UserRegistrationProcess extends StatefulSaga { @StartSagaWith public void start(UserCreatedEvent event) { notifyOn(TaskDescriptionChangedEvent.class, "id", event.getId().toString()); raiseCommand(CommandIntent.builder(EmailUserInfo.class.getName()) .id(event.getId()) .build() ); } @EventHandler public void handle(UserRegistrationConfirmed event) { raiseCommand(CommandIntent.builder(EmailConfirmation.class.getName()) .id(event.getId()) .build() ); end(); } }
- 155. Thoughts
- 156. Thoughts Uses Muon Event Log API.
- 157. Thoughts Uses Muon Event Log API. All Muon implementations can contribute/ consume data (jvm, node, browser etc)
- 158. Thoughts Uses Muon Event Log API. All Muon implementations can contribute/ consume data (jvm, node, browser etc) Runs on any event store that implements the Muon Event Log API
- 159. Event Log API == Less Strategic Decisions
- 161. There's more... More types of API available ... me@daviddawson.me http://muoncore.io
- 162. There's more... More types of API available ... Multiple transports available me@daviddawson.me http://muoncore.io
- 163. There's more... More types of API available ... Multiple transports available Any infrastructure you like! me@daviddawson.me http://muoncore.io
- 164. There's more... More types of API available ... Multiple transports available Any infrastructure you like! Want to extend/ contribute? Join us at me@daviddawson.me http://muoncore.io
- 165. Hire me? Freelance, remote preferred! JVM, Node, IoT, Microservices. me@daviddawson.me me@daviddawson.me http://muoncore.io
Editor's Notes
- Isolation! Aspiration Evolution Ability to change
- Dan North Bounded/ Centred Community
- Not the solution! An approach to solving the problem. Tools to engage the world Sounds familiar.
- h
- Ask the audience. One big one.
- Some say XXX This is what we are going to discuss! Understand a man by walking in his shoes
- Some say XXX This is what we are going to discuss! Understand a man by walking in his shoes
- Some say XXX This is what we are going to discuss! Understand a man by walking in his shoes
- Some say XXX This is what we are going to discuss! Understand a man by walking in his shoes
- Some say XXX This is what we are going to discuss! Understand a man by walking in his shoes
- Some say XXX This is what we are going to discuss! Understand a man by walking in his shoes
- Some say XXX This is what we are going to discuss! Understand a man by walking in his shoes
- Some say XXX This is what we are going to discuss! Understand a man by walking in his shoes
- Some say XXX This is what we are going to discuss! Understand a man by walking in his shoes
- Some say XXX This is what we are going to discuss! Understand a man by walking in his shoes
- Some say XXX This is what we are going to discuss! Understand a man by walking in his shoes
- Some say XXX This is what we are going to discuss! Understand a man by walking in his shoes
- Ask the audience. One big one.
- Ask the audience. One big one.
- Ask the audience. One big one.
- Ask the audience. One big one.
- Ask the audience. One big one.
- Ask the audience. One big one.
- Ask the audience. One big one.
- Ask the audience. One big one.
- Ask the audience. One big one.
- Ask the audience. One big one.
- Ask the audience. One big one.
- Ask the audience. One big one.
- Ask the audience. One big one.