Reactive programming and Hystrix fault tolerance by Max Myslyvtsev

•

0 gefällt mir•838 views

Reactive programming is a new paradigm that provides asynchronous event-based flow control. Java implementation is called rxJava and is being developed by Netfix. They have also released Hystrix — a non-functional layer that provides fault tolerance and latency features which also exposes reactive API.

Technologie

Reactive programming
and Hystrix fault tolerance
Max Myslyvtsev

Agenda
• Reactive
• Observables
• Hystrix
• How we use it
2

Reactive
Initiate Call
Wait
Get Response
Continue
3

When call is complete
Reactive
Initiate Call
Get Response
Continue
Continue
4

When call is complete
Reactive
Initiate Call
Get Response
React
Continue
5
Observer pattern

Why Reactive?
• Event-driven applications
• Easy dependency composition
• Allows parallel execution 
 
6

Why Reactive?
• Event-driven applications
• Easy dependency composition
• Allows parallel execution
• No callback hell
7

rxJava
Observable<T>
Future<T> Iterable<T>
8

Observable
onNext onComplete onError
9
Terminal

Observable
Observer
onNext
onComplete
onError
Subscription
unsubscribe
Observable
subscribe
Work
start
stop
emit
X

Operations
• Create
• Modify (immutable)
• Terminate
10

Creation
Create
Observer
onNext
onComplete
onError
Subscription
unsubscribe
Observable
subscribe
onSubscribe
X

Item
Creation
Never
Just
Empty
ErrorThrowable
11

Creation
FromIterable
FromFuture
Factory Defer
Range 1 2 3Start, Count
12

Source
Observable
Lift
onNext
onComplete
onError
New Observable
onNext
onComplete
onError
Operator
23

Termination
BlockingObservable
Single[OrDefault]
First[OrDefault]
Last[OrDefault]
ToIterable
ToBlocking
Observable
24

Observable<List>
Termination
ToList
BlockingObservable<List>
Single[OrDefault]
ToBlocking
Observable
25

Temperature
Cold
• Lazy
• Does not emit until subscribed
• Whole sequence
Hot
• Eager
• Emits regardless of subscriptions
• Partial sequence
26

Scheduling
Observable
subscribeOn
observeOn
Schedulers
Immediate
Trampoline
New Thread
Computations
IO
From(Executor)
Test
27

Immediate
Unit of Work
schedule
Unit of Work
Thread
X

Trampoline
Unit of Work
schedule
Unit of Work
X
Thread

New Thread
Unit of Work
schedule
Unit of Work
Thread 1 Thread 2
X

Computations / IO
Unit of Work
schedule
Unit of Work
Thread 1 Pool
X

Test Scheduler
Unit of Work
schedule
Unit of Work
Thread 1 Virtual Thread
X

Dependency Composition
• Single Item Observables
• Fork Join
• If Then Else
X

Fork Join
Map Map
Observable
Observable Observable
Observable
Zip
X

If Then Else
Filter (If) Filter (Else)
Observable
Map Map
Observable
Merge
X

Why Hystrix?
• Latency
• Fault-tolerance
• Isolation
28

Command
Hystrix
Fragile Operation
API
Observable
Future
Sync Execute
Remote
Service
Metrics Dashboard
Conﬁguration
Fallback
29

How we use it
30
Server
REST Resources
Client
Maven Plugin
Generated Client Hystrix
generate during build
REST API
RX API
same API

References
• http://reactivex.io/intro.html
• https://github.com/ReactiveX/RxJava/wiki
• https://gist.github.com/staltz/
868e7e9bc2a7b8c1f754
• https://github.com/Netﬂix/Hystrix/wiki
• https://github.com/mmyslyvtsev/rx-workshop
31

Weitere ähnliche Inhalte

Was ist angesagt?

DSR Microservices (Day 1, Part 1)

Steve Upton

Resiliency through Failure @ OSCON 2013

Ariel Tseitlin

Apache Kafka - Patterns anti-patterns

Florent Ramiere

Devoxx university - Kafka de haut en bas

Florent Ramiere

"You need to monitor only a few machines and applications before fixing issues in your environment becomes very complicated. Throw in the type of dynamic infrastructure provided by Amazon EC2, and your static monitoring strategies will most likely not scale. Knowing which metrics to watch and how to troubleshoot based on those metrics will help you solve problems more quickly. In this session, we will look at a framework for your metrics and how to use it to find solutions to the issues that come up. We will cover the three types of monitoring data; what to collect; what should trigger an alert (avoiding an alert storm); and how to follow the resources to find the root causes of problems. Session sponsored by Datadog. "

(DVO204) Monitoring Strategies: Finding Signal in the Noise

Amazon Web Services

Just enough web ops for web developers

Datadog

Transactional Streaming: If you can compute it, you can probably stream it.

jhugg

Training – Going Async

Betclic Everest Group Tech Team

In a world where every “thing” is producing lots of data, ingesting and processing that large volume of data becomes a big problem. In today’s dynamic world, firms have to react to changing conditions very fast, or even better in real time. This presentation covers how two of the latest and greatest tools from Big Data community, Kafka and Spark Streaming, enables us to take on that challenge.

Real time analytics with Kafka and SparkStreaming

Ashish Singh

In your ever-changing Infrastructure, some changes are intentional while others are not. Drift is what happens whenever the real-world state of your infrastructure differs from the state defined in your configuration. This can happen for many reasons, sometimes it happens when adding or removing resources, other times when changing resource definitions upon resource termination or failure, and even when changes have been made manually or via other automation tools. While Terraform itself can detect drifts, in most cases, you will be informed about it too late: just before you are about to deploy new changes to your infrastructure. What’s interesting about Terraform though, is that you can apply changes in two separate and distinct steps of “Planning” and “Applying”. This means that you have full visibility of what Terraform is planning on doing beforehand, and if you are satisfied with the changes, you can choose to apply them. So how does this work? When something is changed intentionally, it will appear in the source code, and the Terraform plan will not do anything. However, if any part of the infrastructure has been changed manually, Terraform’s plan will identify this, and alert you to the change. In other words, if your IaC drifted from its expected state, then Terraform’s plan will, in fact, detect it. Applying this simple solution can empower DevOps and developer velocity, with the reassurance and context for unexpected changes in your IaC, in near real-time. This talk will showcase real-world examples, and practical ways to apply this in your production environments while doing so safely and at the pace of your engineering cycles.

DON'T PANIC: GETTING YOUR INFRASTRUCTURE DRIFT UNDER CONTROL, ERAN BIBI, Firefly

DevOpsDays Tel Aviv

Performance doesn’t have the same definition between system administrators, developpers and business teams. What is Performance ? High CPU usage, not scalable web site, low business transaction rate per sec, slow response time, … This presentation is about maths, code performance, load testing, web performance, best practices, … Working on performance optimizaton is a very broad topic. It’s important to really understand main concepts and to have a clean and strong methodology because it could be a very time consumming activity. Happy reading !

Training - What is Performance ?

Betclic Everest Group Tech Team

Online algorithms are an increasingly popular yet often misunderstood branch of machine learning, where model parameter estimates are updated for each new piece of information received. While mini-batch methods have often been mislabeled as 'streaming-machine learning', true online methods have different implementations and goals. This talk will explain key differences between online and offline machine learning, an introduction to many common online algorithms, and how online algorithms can be analyzed. An example using Apache Flink to detect trends on Twitter will be presented. Attendees will come away from this talk with a better understanding of the challenges and opportunities from working with online algorithms and how they can begin implementing their own algorithms in Apache Flink.

Flink Forward SF 2017: Trevor Grant - Introduction to Online Machine Learning...

Flink Forward

Abstract: The demands and expectations for applications have changed dramatically in recent years. Applications today are deployed on a wide range of infrastructure; from mobile devices up to thousands of nodes running in the cloud—all powered by multi-core processors. They need to be rich and collaborative, have a real-time feel with millisecond response time and should never stop running. Additionally, modern applications are a mashup of external services that need to be consumed and composed to provide the features at hand. We are seeing a new type of applications emerging to address these new challenges—these are being called Reactive Applications. In this talk we will discuss four key traits of Reactive; Responsive, Resilient, Elastic and Message-Driven—how they impact application design, how they interact, their supporting technologies and techniques, how to think when designing and building them—all to make it easier for you and your team to Go Reactive. Intended Audience: Programmers, architects, CIO/CTOs and everyone with a desire to challenge the status quo and expand their horizons on how to tackle the current and future challenges in the computing industry.

Go Reactive: Building Responsive, Resilient, Elastic & Message-Driven Systems

Jonas Bonér

FunctionalConf '16 Robert Virding Erlang Ecosystem

Robert Virding

From Zero to the Actor Model (With Akka.Net) - CodeMash2017 - Tamir Dresher

Tamir Dresher

netflix-real-time-data-strata-talk

Danny Yuan

OWASP DefectDojo - Open Source Security Sanity

Matt Tesauro

At many high-growth companies, staying at the bleeding edge of innovation and maintaining the highest level of service availability often sideline financial efficiency. This problem is exacerbated in a micro-service environment, where decentralized engineering teams can spin up thousands of instances at a moment’s notice, with no governing body tracking cost. By developing a cost-conscious culture and assigning the responsibility for efficiency to the appropriate business owners, you can deliver innovation efficiently and cost effectively . At Netflix, the Finance and Operations Engineering teams bear the responsibility for ensuring that the rate of innovation is fast and that development is cost effective. In this presentation, we’ll explore the building blocks of AWS cost management and discuss Netflix’s best practices.

(ISM309) Efficient Innovation:High-Velocity Cost Management at Netflix

Amazon Web Services

Resiliency through failure @ QConNY 2013

Ariel Tseitlin

CQRS (Command Query Responsibility Segregation) was all the hype in .NET architecture circles a few years back. But has it faded away? Is it old news? I argue that it hasn't, and the concepts of CQRS are alive and well and probably more widely accepted and considered today than a few years ago. From event-driven systems to the Reactive Manifesto, the principles of CQRS are with us and impacting many different tools. In this session, we'll explore those CQRS principles and how they have manifested themselves in the architectures of choice today. You'll come away with a greater appreciation of CQRS and ideas on how to incorporate those principles in your applications today.

CQRS Evolved - CQRS + Akka.NET

David Hoerster

Was ist angesagt? (20)

DSR Microservices (Day 1, Part 1)

Resiliency through Failure @ OSCON 2013

Apache Kafka - Patterns anti-patterns

Devoxx university - Kafka de haut en bas

(DVO204) Monitoring Strategies: Finding Signal in the Noise

Just enough web ops for web developers

Transactional Streaming: If you can compute it, you can probably stream it.

Training – Going Async

Real time analytics with Kafka and SparkStreaming

DON'T PANIC: GETTING YOUR INFRASTRUCTURE DRIFT UNDER CONTROL, ERAN BIBI, Firefly

Training - What is Performance ?

Flink Forward SF 2017: Trevor Grant - Introduction to Online Machine Learning...

Go Reactive: Building Responsive, Resilient, Elastic & Message-Driven Systems

FunctionalConf '16 Robert Virding Erlang Ecosystem

From Zero to the Actor Model (With Akka.Net) - CodeMash2017 - Tamir Dresher

netflix-real-time-data-strata-talk

OWASP DefectDojo - Open Source Security Sanity

(ISM309) Efficient Innovation:High-Velocity Cost Management at Netflix

Resiliency through failure @ QConNY 2013

CQRS Evolved - CQRS + Akka.NET

Ähnlich wie Reactive programming and Hystrix fault tolerance by Max Myslyvtsev

Reactive Programming in Java 8 with Rx-Java

Kasun Indrasiri

How to secure your web applications with NGINX

Wallarm

Reactive microservices with eclipse vert.x

Ram Maddali

Reactive Extensions .NET

George Taskos

DevOps and AWS

Shiva Narayanaswamy

Mini training - Reactive Extensions (Rx)

Betclic Everest Group Tech Team

You're building your startup and you know it will be big. You don't want to spend a lot of time on infrastructure, but you also don't want to be putting out fires after you get mentioned on Hacker News. In this session, we will give you real practical tips that you can take home with you on building an infrastructure that will scale quickly with minimal up front work on your part, using time tested techniques in infrastructure as code, SaaS, and Serverless, among other things.

Jeremy Edberg (MinOps ) - How to build a solid infrastructure for a startup t...

Startupfest

RxJava - introduction & design

allegro.tech

AWS Loft Talk: Behind the Scenes with SignalFx

SignalFx

App Mod 04: Reactive microservices with eclipse vert.x

Judy Breedlove

Reactive programming with examples

Peter Lawrey

Introduction to Resilience4j

Knoldus Inc.

Javantura v3 - Going Reactive with RxJava – Hrvoje Crnjak

HUJAK - Hrvatska udruga Java korisnika / Croatian Java User Association

APIdays Singapore 2019 - Building Applications in the Cloud: Best Practices F...

apidays

Deterministic behaviour and performance in trading systems

Peter Lawrey

Fault Tolerance in Distributed Environment

Orkhan Gasimov

Lattice yapc-slideshare

Gwenn Etourneau

Introduction of failsafe

Sunghyouk Bae

Async CTP 3 Presentation for MUGH 2012

Sri Kanth

Javaone 2016 - Operational Excellence with Hystrix

Billy Yuen

Ähnlich wie Reactive programming and Hystrix fault tolerance by Max Myslyvtsev (20)

Reactive Programming in Java 8 with Rx-Java

How to secure your web applications with NGINX

Reactive microservices with eclipse vert.x

Reactive Extensions .NET

DevOps and AWS

Mini training - Reactive Extensions (Rx)

Jeremy Edberg (MinOps ) - How to build a solid infrastructure for a startup t...

RxJava - introduction & design

AWS Loft Talk: Behind the Scenes with SignalFx

App Mod 04: Reactive microservices with eclipse vert.x

Reactive programming with examples

Introduction to Resilience4j

Javantura v3 - Going Reactive with RxJava – Hrvoje Crnjak

APIdays Singapore 2019 - Building Applications in the Cloud: Best Practices F...

Deterministic behaviour and performance in trading systems

Fault Tolerance in Distributed Environment

Lattice yapc-slideshare

Introduction of failsafe

Async CTP 3 Presentation for MUGH 2012

Javaone 2016 - Operational Excellence with Hystrix

Mehr von JavaDayUA

Science, Technology, Engineering and Mathematics, STEM, are vital to the future of our children. The parents and students in our educational systems need to understand and embrace the technology that affects them every day of their lives. Devoxx4Kids is on a global mission to complement the classical schooling system by offering workshops to kids in a fun way. and teaching them computing concepts using Scratch, Greenfoot, Minecraft, Raspberry Pi, Arduino, NAO, Tynker. We will share a path that can be followed by adults to keep kids in their vicinity engaged and build, instead of just play, games. You will learn best practices to organize similar workshops in your local setting and hear tips on opening a local chapter. This talk will be appreciated by anybody who has kids, nephews, nieces, and in general kids around them.

STEMing Kids: One workshop at a time

Reactive programming and Hystrix fault tolerance by Max Myslyvtsev

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie Reactive programming and Hystrix fault tolerance by Max Myslyvtsev

Ähnlich wie Reactive programming and Hystrix fault tolerance by Max Myslyvtsev (20)

Mehr von JavaDayUA

Mehr von JavaDayUA (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Reactive programming and Hystrix fault tolerance by Max Myslyvtsev