Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

The Future of Reactive Architectures

138 Aufrufe

Veröffentlicht am

What's next for Reactive Systems ? Next is making apps communications reactive. This keynote presentation was given with Steve Gury from Facebook Engineering.

Veröffentlicht in: Software
  • Als Erste(r) kommentieren

The Future of Reactive Architectures

  1. 1. Future of _______ Architectures Reactive
  2. 2. 💡 1974 TCP VintCerfJI3.jpg by Joi Ito / Creative Commons Attribution 2.0 Generic
  3. 3. TCP VintCerfJI3.jpg by Joi Ito / Creative Commons Attribution 2.0 Generic
  4. 4. TCP VintCerfJI3.jpg by Joi Ito / Creative Commons Attribution 2.0 Generic
  5. 5. TCP VintCerfJI3.jpg by Joi Ito / Creative Commons Attribution 2.0 Generic
  6. 6. TCP is 
 Bidirectional TCP has 
 Flow Control VintCerfJI3.jpg by Joi Ito / Creative Commons Attribution 2.0 Generic
  7. 7. 💡 HTTP 1989 Tim Berners-Lee CP 2.jpg by Silvio Tanaka / Creative Commons Attribution 2.0 Generic
  8. 8. 🗞 🗞 HTTP Tim Berners-Lee CP 2.jpg by Silvio Tanaka / Creative Commons Attribution 2.0 Generic GET GET
  9. 9. 🗞 🗞 WAREZ Lycos HTTP Tim Berners-Lee CP 2.jpg by Silvio Tanaka / Creative Commons Attribution 2.0 Generic
  10. 10. HTTP Serve Documents Tim Berners-Lee CP 2.jpg by Silvio Tanaka / Creative Commons Attribution 2.0 Generic
  11. 11. 🗞 🗞 WAREZ HTTP Lycos Serve Documents 👍 Tim Berners-Lee CP 2.jpg by Silvio Tanaka / Creative Commons Attribution 2.0 Generic
  12. 12. Now Google's Lexus RX 450h Self-Driving Car.jpg by Steve Jurvetson / Creative Commons Attribution 2.0 Generic 
 Apple Watch by fancycrave1 / Creative Commons CC0 1.0 Universal Public Domain Dedication Amazon Echo.jpg by Frmorrison / Creative Commons Attribution-Share Alike 3.0 Unported facebook-internet-login-screen by Pixabay / CC0 License
  13. 13. 🗞 Now Connected Experience Google's Lexus RX 450h Self-Driving Car.jpg by Steve Jurvetson / Creative Commons Attribution 2.0 Generic 
 Apple Watch by fancycrave1 / Creative Commons CC0 1.0 Universal Public Domain Dedication Amazon Echo.jpg by Frmorrison / Creative Commons Attribution-Share Alike 3.0 Unported facebook-internet-login-screen by Pixabay / CC0 License
  14. 14. HTTP ?
  15. 15. HTTP ?
  16. 16. HTTP ?
  17. 17. HTTP ?
  18. 18. HTTP ?
  19. 19. HTTP ?
  20. 20. HTTP ?
  21. 21. HTTP ?
  22. 22. HTTP ?
  23. 23. HTTP ?
  24. 24. HTTP ?
  25. 25. HTTP ?
  26. 26. Thundering herds Cascading failure Circuit breaking Retry logic Timeouts Configuration HTTP ?
  27. 27. Reactive ?
  28. 28. Reactive ? +
  29. 29. Reactive ? Order(s) of Magnitude 
 more efficient 🤑
  30. 30. Reactive ? Designed for 
 connection volume scalability 📱
  31. 31. Reactive ? But reactive support stops at the application boundary 😕
  32. 32. Reactive ? 🔎 🏎 🔎 💩 🔎 Los Angeles Traffic by prvideotv / CC0 Creative Commons
  33. 33. Reactive ? If my reactive apps could use all interaction models from TCP with the simplicity of HTTP 😀
  34. 34. Reactive ? An hyper-efficient protocol designed for Application Communications 😃
  35. 35. Reactive ? Resilient without 
 more network hops
 or layers ? 😆
  36. 36. request/reply request/void (fire&forget) request/stream stream/stream (channel) 4 defined interaction models
  37. 37. request/replyrequest/reply
  38. 38. request/reply request/reply
  39. 39. request/reply request/replyrequest/reply
  40. 40. request/reply request/replyrequest/reply
  41. 41. request/reply request/replyrequest/reply 🔎multiplexed
  42. 42. 🔎transport agnostic 
 e.g. Websocket
  43. 43. request/streamrequest/stream
  44. 44. request/streamrequest/stream
  45. 45. request/stream 🔎 🔎 bidirectional
  46. 46. 2 per-message
 flow-control
  47. 47. 2 2 per-message
 flow-control
  48. 48. 2 per-message
 flow-control
  49. 49. 00 per-message
 flow-control
  50. 50. 0 per-message
 flow-control
  51. 51. language agnostic
  52. 52. compose with no semantics loss 🔎 🔎 🔎 ws tcp udp
  53. 53. RSocket Protocol TCP WebSocket Aeron/UDPHTTP/2 Protobuf JSON Custom Binary RPC-style Messaging Java JavaScript C++ Kotlin Flow
  54. 54. A growing community including: Facebook, Netifi, Pivotal 😍
  55. 55. at
  56. 56. LiveServer
  57. 57. live query (GraphQL subscription)
  58. 58. receive query response
 and update when the data change
  59. 59. Subscription resumption
  60. 60. ...continue streaming updates
  61. 61. Significant running costs savings Moving from polling to subscription model Subscription resumption
  62. 62. Imagine If a Cloud Platform supported that Reactive Protocol as a feature 🤓🤓 🤓
  63. 63. Imagine
  64. 64. Learn more 11:30 Maryland Ballroom C Point-to-Point Messaging Architecture - The Reactive Endgame Ryland Degnan, Netifi (CTO) - Stephane Maldini, Pivotal 2:00 Maryland Ballroom C Multi-Service Reactive Streams Using Spring, Reactor, and RSocket Rossen Stoyanchev, Pivotal - Ben Hale, Pivotal

×