Get Reactive: Microservices, Programming, and Systems
•
2 j'aime•269 vues
Today there are more monthly, active users of Facebook (>2B) than there were active users of the internet in 2000. Humans create 2.5 quintillion bytes of data every day. Massively scalable systems and massive amounts of data are now part of every developer’s life-even if you don’t work at a Silicon Valley unicorn. Reactive approaches are critical pieces in scaling modern systems--especially microservices architectures. This talk addresses why these approaches are critical pieces in scaling microservices architectures; especially greenfield microservices applications. This talk dives into Reactive Programming with ReactiveX and building reactive systems with Eclipse Vert.x, Akka and Spring Reactor.
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Get Reactive: Microservices, Programming, and Systems
Similaire à Get Reactive: Microservices, Programming, and Systems (20)
Plus de Jeremy Davis
Plus de Jeremy Davis (13)
Dernier
Dernier (20)
Get Reactive: Microservices, Programming, and Systems
- 1. Get Reactive: Microservices, Programming, and Systems Jeremy Davis Principal Solution Architect, App Dev @argntprgrmr
- 2. Why Does Any of This Matter?
- 3. microservicesjourney.com3 46 years, 3 numbers 0.1 1 10 Jakob Nielsen
- 6. 6 there are always tools Also Tools!
- 8. 8 Programming, Systems, Both Observable.range(1, 100) .groupBy(n -> n % 2 == 0) .flatMap(g -> { return g.takeWhile(i -> i < 30).toList(); }).filter(l -> !l.isEmpty()).forEach(System.out::println);
- 10. imicroservicesjourney.com Reactive Programming 10 Event Driven Message Driven Embraces realities of the networkEmbraces realities of data Reactive Systems
- 11. Reactive Systems
- 13. 13 Responsive • dependability • maintained under failure (resilience) • maintained under load (elasticity) because people get bored
- 14. microservicesjourney.com14 things fail The system must be responsive in the face of failure • must be designed for not added in • self-healing, full recovery • replication • isolation and containment • delegation Resilient
- 15. A System must stay responsive under various workloads • scales up and down • no contention points or bottlenecks • replicable/shardable components • provide relevant live performance measures 15 Elastic everything changes
- 16. 16 asynchronous communication • asynchronous, non-blocking • location transparency • failures delegated as messages • back pressure Message Driven
- 18. 18 the basics “The microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. “ — Martin Fowler http://martinfowler.com/articles/microservices.html Why?
- 22. INSERT DESIGNATOR, IF NEEDED (EDIT ON MASTER SLIDE)22 An API for asynchronous programming with observable streams ReactiveX
- 23. INSERT DESIGNATOR, IF NEEDED (EDIT ON MASTER SLIDE)23 as opposed to traditional programming Traditional • Call a method • Store the return value in a variable • Do something useful with the variable RxJava RxJava • Create a method that does something useful with the return values of an asynchronous call • Define the asynchronous call (Observable) • Attach an observer to the Observable by subscribing • Do other stuff until the call returns and the Observable begins to operate on the results
- 24. 24 rx.Observable() Observable.range(1, 100) .groupBy(n -> n % 2 == 0) .flatMap(g -> { return g.toList(); }).forEach(System.out::println);
- 25. microservicesjourney.com25 like the Gang of Four pattern with onCompleted() and onError() Observer Pattern
- 27. INSERT DESIGNATOR, IF NEEDED (EDIT ON MASTER SLIDE)27 Insert copy Operators (marbles)
- 28. 28
- 29. 29 all about the Observables • Observable • Operators • Marbles • Learning curve Summary: rxJava
- 30. One Rule: “Don’t mutate state outside of the function”
- 31. Reactive Streams
- 32. INSERT DESIGNATOR, IF NEEDED (EDIT ON MASTER SLIDE)32 a standard for asynchronous stream processing that isn’t for end users • Standard • Interoperability layer • no operators • java.util.concurrent.Flow • Github • JavaScript • Lightbend, Netflix, Pivotal, Red Hat Reactive Streams
- 33. INSERT DESIGNATOR, IF NEEDED (EDIT ON MASTER SLIDE)33 Actor Mailbox Actor MailboxActor Mailbox Actor Mailbox Actor Mailbox
- 34. INSERT DESIGNATOR, IF NEEDED (EDIT ON MASTER SLIDE)34 Actor Mailbox Actor Mailbox akka://default/user/$a#114635109 akka://default/user/$a#114635173
- 35. INSERT DESIGNATOR, IF NEEDED (EDIT ON MASTER SLIDE)35
- 36. 36 its all about the actor model • Actor Model • Messaging • Addressing • Steams, Web, others • Reactive end to end Summary: akka
- 37. INSERT DESIGNATOR, IF NEEDED (EDIT ON MASTER SLIDE)37 a toolkit for building reactive applications on the JVM Event Loop COLUMN HEADING ALL CAPS Vertices Event Bus
- 38. 38 single threaded event loop
- 39. Cardinal Rule: “Don’t Block the Event Loop”
- 40. 40 its all about verticles
- 41. 41 messages
- 42. 42 JsonObject
- 43. 43 its all about reactive • Reactive from end to end • Json • Event Loop • Messaging • rxJava built in • Polyglot Summary: Eclipse Vert.x
- 44. 44 Project Reactor and WebFlux
- 45. 45
- 46. 46 its hidden • Flux • Mono • WebFlux • Reactive Streams Summary: Spring Reactor
- 49. 49 RxJava Books: http://shop.oreilly.com/product/0636920042228.do Code: https://github.com/ReactiveX/RxJava https://github.com/jhusain/learnrxjava Presentations: GOTO 2013 • Functional Reactive Programming with RxJava • Ben Christensen Links
- 51. 51 Shootout! • Ken Finnigan - WildFly Swarm • Brian Ashburn - Spring Boot • Lance Ball - NodeJS • Deven Phillips - Eclipse Vert.x Next Up