Skip to content

Commit 8efa450

Browse files
committed
Merge branch 'master' of github.com:ReactiveDesignPatterns/website
2 parents 9be4fcf + fb3784f commit 8efa450

33 files changed

Lines changed: 121 additions & 350 deletions

index.html

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
<!DOCTYPE html>
22
<html>
3+
<head>
4+
<meta charset="utf-8" />
5+
</head>
6+
<body>
37
<title>Reactive Design Patterns</title>
48
<xmp style="display:none" toc-disabled >
59

@@ -16,4 +20,5 @@
1620

1721
</xmp>
1822
<script src="./strapdown.js"></script>
23+
</body>
1924
</html>

jquery.strapdown.js

Lines changed: 0 additions & 289 deletions
This file was deleted.

jquery.strapdown.min.css

Lines changed: 0 additions & 1 deletion
This file was deleted.

jquery.strapdown.min.js

Lines changed: 0 additions & 2 deletions
This file was deleted.

patterns/active–active.html

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
<!DOCTYPE html>
22
<html>
3-
<title>Reactive Design Patterns — Active–active</title>
4-
<xmp style="display:none">
3+
<title>Reactive Design Patterns</title>
4+
<xmp style="display:none" toc-disabled >
5+
# Active–active replication
6+
57
_“Keep multiple copies of a service running in different locations, and perform all modifications at all of them.”_
68

79
With multiple-master replication patterns, you achieved resilience for the

patterns/active–passive.html

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
<!DOCTYPE html>
22
<html>
3-
<title>Reactive Design Patterns — Active–passive</title>
4-
<xmp style="display:none">
3+
<title>Reactive Design Patterns</title>
4+
<xmp style="display:none" toc-disabled >
5+
# Active–passive replication
6+
57
_“Keep multiple copies of the service running in different locations, but only accept modifications to the state in one location at any given time.”_
68

79
This pattern is also sometimes referred to as failover or master-slave

patterns/aggregator.html

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
<!DOCTYPE html>
22
<html>
3-
<title>Reactive Design Patterns — Aggregator</title>
4-
<xmp style="display:none">
3+
<title>Reactive Design Patterns</title>
4+
<xmp style="display:none" toc-disabled >
5+
# Aggregator
6+
57
_“Create an ephemeral component if multiple service responses are needed to compute a service call’s result.”_
68

79
We have introduced the [Ask pattern](ask-pattern.html) for the case of requiring a request-response

patterns/ask-pattern.html

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
<!DOCTYPE html>
22
<html>
3-
<title>Reactive Design Patterns — Ask pattern</title>
4-
<xmp style="display:none">
3+
<title>Reactive Design Patterns</title>
4+
<xmp style="display:none" toc-disabled >
5+
# Ask
6+
57
_“Delegate the handling of a response to a dedicated ephemeral component.”_
68

79

patterns/business-handshake.html

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
<!DOCTYPE html>
22
<html>
3-
<title>Reactive Design Patterns — Business handshake</title>
4-
<xmp style="display:none">
3+
<title>Reactive Design Patterns</title>
4+
<xmp style="display:none" toc-disabled >
5+
# Business handshake
6+
57
_“Include identifying and/or sequencing information in the message, and keep retrying until confirmation is received.”_
68

79
While discussing the [Saga pattern](saga.html), we made the implicit assumption that

patterns/circuit-breaker.html

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,9 @@
11
<!DOCTYPE html>
22
<html>
3-
<title>Reactive Design Patterns — Circuit Breaker</title>
4-
<xmp style="display:none">
3+
<title>Reactive Design Patterns</title>
4+
<xmp style="display:none" toc-disabled >
5+
# Circuit Breaker
6+
57
_“Protect services by breaking the connection to their users during prolonged failure conditions.”_
68

79
In previous patterns, we discussed how to segregate a system into a hierarchy

0 commit comments

Comments
 (0)