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?

1. Future of Reactive Architectures
Scala Up North, July 21, 2017

2. Director of Engineering
Unified Commerce Platform
Jamie Allen

3. Microservices Engineers
Senior Microservices Engineers
Principal Microservices Engineers
Technical Managers

5. It’s easy to lose sight of what companies
are really trying to accomplish
Vendor life

7. Nothing matters more to
stakeholders
Delivering business value quickly

8. Cannot be done unless you can
rapidly develop teams
Caveat

9. FP? Reactive?
Yes, use both, where they add value

10. Only one team had FP help
Our teams each learned differently

11. Painful making calls between services
Hand-stitched interactions

12. We’ve avoided that so far
Use Akka Cluster?

13. FP knowledge doesn’t scale
Critical fact

14. Critical fact
Neither does Akka knowledge

15. I need to deliver business value!
It doesn’t matter

16. Make it easier to quickly deliver business
value in a Reactive architecture
So what do we do?

17. Let the toolchain handle the majority of
resilience issues
Use Reactive principles where they’re most needed

18. Simplify service interactions
gRPC

19. Orchestration is as much about the
ecosystem as the capabilities
Kubernetes

20. Service mesh with additional telemetry
and security support
Istio

21. Absolutely not
Is Starbucks abandoning Scala and Akka?

22. What about data?
Turns out, we were wrong here too

23. CAP Theorem isn’t what we thought
Next generation storage

24. CAP Theorem isn’t what we thought
Next generation storage
Google: Calvin Fauna

25. Do we need to be Reactive everywhere?
Choose how to be reactive in delivering business value quickly

26. Thank you!
Questions?