You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: blogs/machine_learning.html
+10-4Lines changed: 10 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -68,15 +68,18 @@ <h5 class="w3-center w3-padding-64"><span class="w3-tag w3-wide">ARCHITECTURE OF
68
68
<p>I will start-off by writing some of the most commonly used design architectures:
69
69
<ol>
70
70
<li>
71
-
<b>Reactive Style:</b>
71
+
<b>Reactive Architecture:</b>
72
72
Properties of a reactive system: <br>
73
73
<ul>
74
74
<li><i>Responsive:</i> A responsive system provides rapid and consistent response times, establishing reliable upper bounds so they deliver reliable quality product.</li>
75
75
<li><i>Resilient:</i> The system stays responsive in case of failure. Resilience is achieved by replication, containment, isolation and delegation. Failures are contained within each component, isolating components from each other and thereby ensuring that parts of the system can fail and recover without compromising the system as a whole. Recovery of each component is delegated to another (external) component and high-availability is ensured by replication where necessary. The client of a component is not burdened with handling its failures.</li>
76
76
<li><i>Elastic:</i> The system stays responsive under varying workload. </li>
77
77
<li><i>Message Driven:</i> Reactive Systems rely on asynchronous message-passing to establish a boundary between components that ensures loose coupling, isolation and location transparency. This boundary also provides the means to delegate failures as messages. Employing explicit message-passing enables load management, elasticity, and flow control by shaping and monitoring the message queues in the system and applying back-pressure when necessary. Location transparent messaging as a means of communication makes it possible for the management of failure to work with the same constructs and semantics across a cluster or within a single host. Non-blocking communication allows recipients to only consume resources while active, leading to less system overhead.</li>
@@ -97,8 +100,11 @@ <h5 class="w3-center w3-padding-64"><span class="w3-tag w3-wide">ARCHITECTURE OF
97
100
<li>
98
101
<b>Lambda Architecture:</b>
99
102
The Lambda (λ) Architecture is designed to handle both real-time and historically aggregated batched data in an integrated fashion. It separates the duties of real-time and batch processing while query layers present a unified view of all of the data. The concept is simple: When data is generated, it is processed before stored, so analysis can include data generated in the last second, the last minute, or the last hour by only processing the incoming data — not all the data.
100
-
This is by far the most commonly used architecture
This is by far the most commonly used architecture in machine learning where data is considered as the first class entity in the entire architecture. Shown below is the diagram reflective upon a superficial example of this setup.
0 commit comments