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
+84-59Lines changed: 84 additions & 59 deletions
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@
51
51
<divclass="w3-grayscale w3-large">
52
52
<!-- About Container -->
53
53
<divclass="w3-container" id="about">
54
-
<pclass="w3-content" style="max-width:800px">
54
+
<pclass="w3-content" style="max-width:700px">
55
55
<h5class="w3-center w3-padding-64"><spanclass="w3-tag w3-wide">ARCHITECTURE OF MACHINE LEARNING PIPELINE</span></h5>
56
56
<p>Writing a working machine learning code does not guarantee a production ready system. This blog is about designing a machine learning prototype through the engineering road map. What you need is a team of professional Software Engineers by your side to take your (disposable) proof of concept and turn it into a performant, reliable, loosely coupled and scalable system!</p>
57
57
<p>Given below is the roster of objectives that we need to build a production ready system:
@@ -66,82 +66,107 @@ <h5 class="w3-center w3-padding-64"><span class="w3-tag w3-wide">ARCHITECTURE OF
66
66
</ul>
67
67
</p>
68
68
<p>I will start-off by writing some of the most commonly used design architectures:
69
-
<ul>
69
+
<ol>
70
70
<li>
71
71
<b>Reactive Style:</b>
72
-
<p>Properties of a reactive system: <br>
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>
<p>SOA centres around the concept of decomposing business problems into services. The services share information via the network and they also share code (i.e. common components) to maintain consistency and reduce development effort. <br>
84
+
SOA centres around the concept of decomposing business problems into services. The services share information via the network and they also share code (i.e. common components) to maintain consistency and reduce development effort. <br>
84
85
</li>
86
+
<br>
85
87
<li>
86
-
<b>Streaming Architecture: </b>
88
+
<b>Streaming Architecture:</b>
89
+
<ul>A streaming architecture comprises of the following components:
90
+
<li><b>Producers:</b> Applications that generate and send messages</li>
91
+
<li><b>Consumers:</b> Applications that subscribe to and consume messages</li>
92
+
<li><b>Topics:</b> Streams of records belonging to a particular category and stored as a sequence of ordered and immutable records partitioned and replicated across a distributed cluster</li>
93
+
<li><b>Stream Processors:</b> Applications that process messages in a certain manner (e.g. data transformations, ML models, etc).</li>
94
+
</ul>
87
95
</li>
88
-
</ul>
89
-
</p>
90
-
<divclass="w3-panel w3-leftbar w3-light-grey">
91
-
<p><i>"Use products from nature for what it's worth - but never too early, nor too late." Fresh is the new sweet.</i></p>
<divid="Eat" class="w3-container menu w3-padding-48 w3-card">
112
-
<h5>Bread Basket</h5>
113
-
<pclass="w3-text-grey">Assortment of fresh baked fruit breads and muffins 5.50</p>
114
-
<br>
115
-
<h5>Honey Almond Granola with Fruits</h5>
116
-
<pclass="w3-text-grey">Natural cereal of honey toasted oats, raisins, almonds and dates 7.00</p>
117
-
<br>
118
-
<h5>Belgian Waffle</h5>
119
-
<pclass="w3-text-grey">Vanilla flavored batter with malted flour 7.50</p>
120
-
<br>
121
-
<h5>Scrambled eggs</h5>
122
-
<pclass="w3-text-grey">Scrambled eggs, roasted red pepper and garlic, with green onions 7.50</p>
123
96
<br>
124
-
<h5>Blueberry Pancakes</h5>
125
-
<pclass="w3-text-grey">With syrup, butter and lots of berries 8.50</p>
126
-
</div>
127
-
<divid="Drinks" class="w3-container menu w3-padding-48 w3-card">
128
-
<h5>Coffee</h5>
129
-
<pclass="w3-text-grey">Regular coffee 2.50</p>
130
-
<br>
131
-
<h5>Chocolato</h5>
132
-
<pclass="w3-text-grey">Chocolate espresso with milk 4.50</p>
133
-
<br>
134
-
<h5>Corretto</h5>
135
-
<pclass="w3-text-grey">Whiskey and coffee 5.00</p>
136
-
<br>
137
-
<h5>Iced tea</h5>
138
-
<pclass="w3-text-grey">Hot tea, except not hot 3.00</p>
97
+
<li>
98
+
<b>Lambda Architecture:</b>
99
+
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
<pclass="w3-text-grey">Coke, Sprite, Fanta, etc. 2.50</p>
142
-
</div>
104
+
<li>
105
+
<b>Microservice Architecture:</b>
106
+
Microservices, is an architectural style that structures an application as a collection of small, autonomous, loosely coupled and collaborating services, modelled around a business domain. The services communicate using either synchronous protocols such as HTTP/REST or asynchronous protocols such as AMQP. They can be developed and deployed independently of one another. Each service has its own database in order to be decoupled from other services.
107
+
</li>
108
+
<br>
109
+
<li>
110
+
<b>Representational State Transfer (REST) Architecture:</b>
111
+
REST is an architectural style for developing web services and it builds upon existing features of the internet’s HTTP. It allows transferring, accessing and manipulating textual data representations, in a stateless manner i.e. applications can communicate agnostically. A RESTful API service is exposed through a Uniform Resource Locator (URL), which provides the capability of data being created, requested, updated, or deleted (CRUD). It is best used to manage systems by decoupling the information that is produced and consumed from the technologies that produce and consume it!
0 commit comments