Reactive All the Way Down the Stack
•
0 likes•275 views
Reactive applications & reactive programming result in flexible, concise, performant code and are a superior alternative to the old thread-based programming model. The reactive approach has gained popularity for a simple reason: we need alternative designs and architectures to meet today’s demands. However, it can be difficult to shift one’s mind to think in reactive terms, particularly when one realizes that we must be Reactive up and down the entire programming stack. In this talk we’ll explore what it means to be ‘Reactive’. We’ll examine some of the more interesting tools available to us, some of which come from the Groovy community. Specifically we’ll cover Ratpack, RxGroovy, React, and RabbitMq - along with examples and a sample implementation. We’ll demonstrate how effectively they can work together at each level of the stack - from the front end, to the back end, to handling http requests and message queue events - and how easy it can be to go Reactive all the way down.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Reactive All the Way Down the Stack
Similar to Reactive All the Way Down the Stack (20)
More from Steve Pember
More from Steve Pember (20)
Recently uploaded
Recently uploaded (20)
Reactive All the Way Down the Stack
- 1. Reactive All the Way Down with Ratpack, RxGroovy, React, and RabbitMQ Steve Pember CTO, ThirdChannel Greach, 2018 @svpember
- 3. Reactive All the Way Down with Ratpack, RxGroovy, Groovy, rxJava, React, and RabbitMQ Steve Pember CTO, ThirdChannel Greach, 2018 @svpember
- 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
- 9. A Good Kind of Manifesto
- 10. –Johnny Appleseed “Type a quote here.”
- 11. @svpember Reactive Services… • Are Fast and Efficient
- 13. @svpember Reactive Services… • Are Fast and Efficient • Resist and are Resilient to Failure
- 15. @svpember Reactive Services… • Are Fast and Efficient • Resist and are Resilient to Failure • Scale Horizontally to Meet Current Demand
- 16. @svpember Reactive Services… • Are Fast and Efficient • Resist and are Resilient to Failure • Scale Horizontally to Meet Current Demand • Are Driven by Asynchronous Messages / Events
- 17. @svpember
- 18. @svpember
- 19. @svpember Advantages of Reactive • Highly optimized usage of resources -> optimal throughput
- 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. @svpember
- 26. @svpember
- 27. @svpember Advantages of Reactive • Highly optimized usage of resources -> optimal throughput • Fast • Reduces Synchronous Communications • Increased Error Protection • “Simpler” testing
- 28. @svpember
- 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 a Reactive Service
- 32. @svpember
- 34. Don’t Write Imperative JS
- 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 • Write Async Code!
- 39. @svpember Service Layer • Write Async Code! • java.util.concurrent
- 40. @svpember Service Layer • Write Async Code! • java.util.concurrent • GPars!
- 41. @svpember Service Layer • Write Async Code! • java.util.concurrent • GPars! • Project Reactor
- 42. @svpember Service Layer • Write Async Code! • java.util.concurrent • GPars! • Project Reactor • Reactive Streams
- 43. @svpember Service Layer • Write Async 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 Blocking I/O is vital! • Need an Asynchronous Message Broker • Need a dedicated Thread Pool (ExecutorService) • Message Flow:
- 46. @svpember
- 47. @svpember
- 48. @svpember Layers • Front-End • HTTP • Service Layer • Messaging / Intra-Service comms • Persistance
- 50. @svpember
- 51. Reactive JDBC Driver is Coming!
- 52. Tech Choices at Each Level
- 54. Front-End
- 55. @svpember React • View Library for JS • Define Components that receive props and maintain state
- 56. React favors pushing properties ‘down’ through layers of components
- 59. @svpember React • View Library for 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 Library for JS • Define Components that receive props and maintain state • + Encourages reusable components • + Shadow / Virtual DOM
- 66. @svpember React • View Library for JS • Define Components that receive props and maintain state • + Encourages reusable components • + Shadow / Virtual DOM • + Reacts to property changes
- 67. @svpember React • View Library for 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 additional functionality
- 69. @svpember Redux • Library for handling 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 Library for 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 Library for 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. HTTP
- 75. –Johnny Appleseed “Type a quote here.”
- 76. @svpember Ratpack • NIO HTTP Library • + 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 use Ratpack • 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. Service Layer
- 79. @svpember RxJava • Reactive Streams implementation 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. @svpember
- 81. @svpember
- 82. @svpember When to use RxJava • 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. Messaging
- 84. @svpember RabbitMQ • High Throughput Message 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 use RabbitMQ: • 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. Persistance
- 87. Come on, Async JDBC!
- 89. @svpember
- 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 for the demo: https://github.com/spember/reactive-ratpack-demo