Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

20170721 future of reactive architectures

3,297 views

Published on

Some knowledge will be difficult to scale across an entire team. How do we build applications that are reactive while still delivering business value quickly?

Published in: Technology
  • Be the first to comment

20170721 future of reactive architectures

  1. 1. Future of Reactive Architectures Scala Up North, July 21, 2017
  2. 2. Director of Engineering Unified Commerce Platform Jamie Allen
  3. 3. Microservices Engineers Senior Microservices Engineers Principal Microservices Engineers Technical Managers
  4. 4. It’s easy to lose sight of what companies are really trying to accomplish Vendor life
  5. 5. Nothing matters more to stakeholders Delivering business value quickly
  6. 6. Cannot be done unless you can rapidly develop teams Caveat
  7. 7. FP? Reactive? Yes, use both, where they add value
  8. 8. Only one team had FP help Our teams each learned differently
  9. 9. Painful making calls between services Hand-stitched interactions
  10. 10. We’ve avoided that so far Use Akka Cluster?
  11. 11. FP knowledge doesn’t scale Critical fact
  12. 12. Critical fact Neither does Akka knowledge
  13. 13. I need to deliver business value! It doesn’t matter
  14. 14. Make it easier to quickly deliver business value in a Reactive architecture So what do we do?
  15. 15. Let the toolchain handle the majority of resilience issues Use Reactive principles where they’re most needed
  16. 16. Simplify service interactions gRPC
  17. 17. Orchestration is as much about the ecosystem as the capabilities Kubernetes
  18. 18. Service mesh with additional telemetry and security support Istio
  19. 19. Absolutely not Is Starbucks abandoning Scala and Akka?
  20. 20. What about data? Turns out, we were wrong here too
  21. 21. CAP Theorem isn’t what we thought Next generation storage
  22. 22. CAP Theorem isn’t what we thought Next generation storage Google: Calvin Fauna
  23. 23. Do we need to be Reactive everywhere? Choose how to be reactive in delivering business value quickly
  24. 24. Thank you! Questions?

×