Downloaded 10 times
Uploaded bySteve Pember
Reactive All the Way Down the Stack
The document discusses the benefits and anatomy of reactive services using technologies like Ratpack, RxGroovy, React, and RabbitMQ. It highlights the advantages of reactive programming, such as efficiency, resilience, error protection, and asynchronous communication, alongside specific recommendations for tech choices at different service layers. Additionally, it covers the use of React and RabbitMQ for frontend and messaging solutions, respectively, emphasizing performance and functional programming styles.
More Related Content
![[Annotated] QConSF 2018: Airbnb's Great Migration - From Monolith to Service-...](https://cdn.slidesharecdn.com/ss_thumbnails/qconsf18-airbnbsgreatmigration-frommonolithtoservice-orientedannotated-181110005137-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Reactive All the Way Down the Stack
Reactive All the Way Down the Stack
- 1. Reactive All theWay Down with Ratpack, RxGroovy, React, and RabbitMQ Steve Pember CTO, ThirdChannel Greach, 2018 @svpember
- 3. Reactive All theWay Down with Ratpack, RxGroovy, Groovy, rxJava, React, and RabbitMQ Steve Pember CTO, ThirdChannel Greach, 2018 @svpember
- 4.
- 5. @svpember Agenda • Reactive ? •Anatomy of a Reactive Service
- 6. @svpember Agenda • Reactive ? •Anatomy of a Reactive Service • Technology Choices for a Reactive Service
- 7. @svpember Agenda • Reactive ? •Anatomy of a Reactive Service • Technology Choices for a Reactive Service • Demo
- 8.
- 9. A Good Kindof Manifesto
- 10. –Johnny Appleseed “Type aquote here.”
- 11. @svpember Reactive Services… • AreFast and Efficient
- 13. @svpember Reactive Services… • AreFast and Efficient • Resist and are Resilient to Failure
- 15. @svpember Reactive Services… • AreFast and Efficient • Resist and are Resilient to Failure • Scale Horizontally to Meet Current Demand
- 16. @svpember Reactive Services… • AreFast and Efficient • Resist and are Resilient to Failure • Scale Horizontally to Meet Current Demand • Are Driven by Asynchronous Messages / Events
- 17.
- 18.
- 19. @svpember Advantages of Reactive •Highly optimized usage of resources -> optimal throughput
- 21.
- 22. @svpember Advantages of Reactive •Highly optimized usage of resources -> optimal throughput • Fast
- 23. @svpember Advantages of Reactive •Highly optimized usage of resources -> optimal throughput • Fast • Reduces Synchronous Communications
- 24. @svpember Advantages of Reactive •Highly optimized usage of resources -> optimal throughput • Fast • Reduces Synchronous Communications • Increased Error Protection
- 25.
- 26.
- 27. @svpember Advantages of Reactive •Highly optimized usage of resources -> optimal throughput • Fast • Reduces Synchronous Communications • Increased Error Protection • “Simpler” testing
- 28.
- 29. @svpember Advantages of Reactive •Highly optimized usage of resources -> optimal throughput • Fast • Reduces Synchronous Communications • Increased Error Protection • “Simpler” testing • Promotes a functional programming style
- 30. @svpember Advantages of Reactive •Highly optimized usage of resources -> optimal throughput • Fast • Reduces Synchronous Communications • Increased Error Protection • “Simpler” testing • Promotes a functional programming style • Ease of Development
- 31. Anatomy of aReactive Service
- 32.
- 33.
- 34.
- 35.
- 36. @svpember HTTP • C10k problem •Nonblocking I/O • Many popular web servers support async or reactive handlers • Ratpack’s been doing it for years now
- 37. @svpember Layers • Front-End • HTTP •Service Layer
- 38. @svpember Service Layer • WriteAsync Code!
- 39. @svpember Service Layer • WriteAsync Code! • java.util.concurrent
- 40. @svpember Service Layer • WriteAsync Code! • java.util.concurrent • GPars!
- 41. @svpember Service Layer • WriteAsync Code! • java.util.concurrent • GPars! • Project Reactor
- 42. @svpember Service Layer • WriteAsync Code! • java.util.concurrent • GPars! • Project Reactor • Reactive Streams
- 43. @svpember Service Layer • WriteAsync Code! • java.util.concurrent • GPars! • Project Reactor • Reactive Streams • Create an internal Message Bus
- 44. @svpember Layers • Front-End • HTTP •Service Layer • Messaging / Intra-Service comms
- 45. @svpember Messaging • Non BlockingI/O is vital! • Need an Asynchronous Message Broker • Need a dedicated Thread Pool (ExecutorService) • Message Flow:
- 46.
- 47.
- 48. @svpember Layers • Front-End • HTTP •Service Layer • Messaging / Intra-Service comms • Persistance
- 50.
- 51. Reactive JDBC Driveris Coming!
- 52. Tech Choices atEach Level
- 53.
- 54.
- 55. @svpember React • View Libraryfor JS • Define Components that receive props and maintain state
- 56. React favors pushing properties‘down’ through layers of components
- 59. @svpember React • View Libraryfor JS • Define Components that receive props and maintain state • + Encourages reusable components
- 60. @svpember Stateful Components (“Containers”) •Maintains internal state of Component • Written as a class, with a variety of internal functions (e.g. click Handlers) • Not intended for re-use • May receive external State as props • Passes Props to Child Components • Simple Render functions that may concern layout • Children can be both Containers and Presentational • Refrain from ‘raw’ HTML (JSX), CSS, render() should use Presentational Components • Little-To-No Business Logic
- 62. @svpember Stateless Components (“Presentational”) •No State. Only receives Props. • Written as a single function (representing the render()) • Ideal if Presentational components are reusable • Potentially complex render functions. note: calling render() only affects DOM if props have changed for a component • No Business Logic
- 64. @svpember React • View Libraryfor JS • Define Components that receive props and maintain state • + Encourages reusable components • + Shadow / Virtual DOM
- 66. @svpember React • View Libraryfor JS • Define Components that receive props and maintain state • + Encourages reusable components • + Shadow / Virtual DOM • + Reacts to property changes
- 67. @svpember React • View Libraryfor JS • Define Components that receive props and maintain state • + Encourages reusable components • + Shadow / Virtual DOM • + Reacts to property changes • + Has a massive ecosystem
- 68. React-Friendly Libraries for additionalfunctionality
- 69. @svpember Redux • Library forhandling global state, derived from Flux • One Immutable Store, but can allow for hierarchy (i.e. not flat shape) • Strict, Unidirectional Data Flow • Reducers, Actions, ActionCreators • Intended for Synchronous change operations • Hooks for Middleware / plugins
- 71. @svpember React • View Libraryfor JS • Define Components that receive props and maintain state • + Encourages reusable components • + Shadow / Virtual DOM • + Reacts to property changes • + Has a massive ecosystem • - APIs change frequently
- 72. @svpember React • View Libraryfor JS • Define Components that receive props and maintain state • + Encourages reusable components • + Shadow / Virtual DOM • + Reacts to property changes • + Has a massive ecosystem • - APIs change frequently • - Forces you to think in React
- 73. @svpember React: Use If… •You need a powerful View layer for your frontend • You appreciate the usefulness of composed, reusable View components • You have the mental agility to follow and keep up with the latest Javascript trends
- 74.
- 75. –Johnny Appleseed “Type aquote here.”
- 76. @svpember Ratpack • NIO HTTPLibrary • + Built on top of Netty • + Fast, lightweight • + Non-opinionated • + Excellent Testing support • + Excellent Gradle support • - Taking a while to adopt rxJava2 • - It’s I/O thread pool is Unbounded • - Non-obvious how to access registry / DI during a test
- 77. @svpember When to useRatpack • You need NIO http support, but don’t want a full framework • You need to handle high levels of concurrent users • You’re comfortable going to a conference with many folks from the Grails team and talking about an alternative solution
- 78.
- 79. @svpember RxJava • Reactive Streamsimplementation on the JVM, designed for communication across boundaries • + Makes Async / parallel programming ‘easy’ • + Promotes a highly functional, stream-oriented style • + Promotes stream-oriented programming • + Backpressure • + Composable & Cancelable • + Ideal for inputs of potentially infinite amounts of data • - Learning curve is steep / new programming paradigm • - can swallow exceptions if not careful
- 80.
- 81.
- 82. @svpember When to useRxJava • You need to write Async code • You have 1000s+ or potentially infinite events to process • You want to feel stupid • You comfortable going to a Groovy conference and telling people you don’t use GPars
- 83.
- 84. @svpember RabbitMQ • High ThroughputMessage Broker • + Complex and Powerful routing mechanisms • + High Availability, clustering, back pressure • + Durability / failure tolerance • + Easy to deploy / cluster • - not as fast as other message brokers • - Written in Erlang
- 85. @svpember When to useRabbitMQ: • You need Async message handling • You like having simple consumers and smart routing • You don’t mind being looked down upon by Kafka fans
- 86.
- 87. Come on, AsyncJDBC!
- 88.
- 89.
- 90. @svpember Images • I’m sorry(Rain): https://imgur.com/gallery/J27yj3k • Spartans: www.300themovie.com/ • Colbert: https://giphy.com/gifs/stephen-colbert-report- hopeful-4KxeicCUTvhrW • The Flash: https://www.bleedingcool.com/2016/12/27/cws-flash-today- tomorrow-beyond/ • React Virtual Dom: https://www.youtube.com/watch?v=UH6dz6IGbK4
- 91. @svpember Links • Repo forthe demo: https://github.com/spember/reactive-ratpack-demo