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