5 Reasons to use Reactive Programming if you are not eBay
This video is also available in the GOTO Play video app! Download it to enjoy offline access to our conference videos while on the move.
Reactive Systems address challenges of modern applications, the challenges related to a high number of users and high throughput. Not every application has high enough throughput to benefit from non-blocking reactive design. Imperative blocking applications can still be fast, resilient and responsive. But surprisingly there are other reasons to use reactive programming except for a really high throughput. At eBay daily requests reach billions. No surprise that reactive programming could bring a value to eBay. What about systems that do not reach such a high amount of traffic? As part of eBay Inc., eBay Classifieds Group includes 10 local brands including GumTree, Kijiji, eBay Kleinanzeigen and others. While ebay.com is a global platform with a huge load, each of Classifieds businesses is local, often being one of the most visited websites in the country at the same time. I've collected 5 use-cases why you might want to use reactive programming without having as much traffic as ebay.com with real-life examples from eBay companies
-
15 Years of Spring: Evolving a Java Application FrameworkJürgen HöllerThursday Nov 1 @ 10:50
-
Zen and the Art of Convincing Your Company to Use RustAshley WilliamsThursday Nov 1 @ 13:50
-
Functional Programming in 40 MinutesRuss OlsenWednesday Oct 31 @ 10:50
-
A Cartoon Quest: New Adventures for WebAssemblyLin ClarkWednesday Oct 31 @ 15:00
-
Keeping Up with JavaSander MakFriday Nov 2 @ 13:50
-
GraalVM: Run Programs Faster AnywhereOleg ŠelajevFriday Nov 2 @ 16:10
-
5 Reasons to use Reactive Programming if you are not eBayGrygoriy GoncharFriday Nov 2 @ 15:00
-
Boost your API Development with GraphQL & PrismaNikolas BurkFriday Nov 2 @ 16:10