regex101: JavaScript Match Workspace

Regular Expression

<(\/?[a-z][A-Z0-9]*)([^>]*?)>

New

<div dir="ltr" style="text-align: left;" trbidi="on"><div style="text-align: left;"><span style="font-family: Gafata;"> Asynchronous event-driven programming is at the heart of Node.js, however it is also the root cause of&nbsp;</span>Callback Hell<span style="font-family: Gafata;">. The purpose of asynchronous execution is to overlap computation with communication and I/O, which can be achieved in other ways.&nbsp;</span></div><div style="text-align: left;"><span style="font-family: Gafata;"><br /></span></div><div style="text-align: left;"></div><div style="text-align: justify;"><i><b><span style="font-family: Gafata; font-size: 27px; text-align: center;">We propose using more event loops instead of</span></b></i></div><i></i><br /><div style="text-align: justify;"><i><i><b><span style="font-family: Gafata; font-size: 27px; text-align: center;">asynchronous I/O to prevent blocking the event loop.</span></b></i></i></div><i></i><br /><div style="text-align: left;"><span style="font-family: Gafata;"><br /></span></div><div class="separator" style="clear: both; text-align: center;"><a href="http://synsem.com/SyncNotAsync/Figures/nodeParallelism.svg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://synsem.com/SyncNotAsync/Figures/nodeParallelism.svg" height="157" width="400" /></a></div><div class="separator" style="clear: both; text-align: center;"><br /></div><div class="separator" style="clear: both; text-align: center;"><br /></div><h6 style="border-bottom-style: solid; border-bottom-width: 2px; color: #404080; font-family: Gafata; font-size: 1.25em; line-height: 1em; margin: 20px 49.640625px 10px; padding-bottom: 2px; padding-top: 0px; text-shadow: rgba(0, 0, 0, 0.298039) 2px 2px 4px;"><i>Pros and Cons of Async and Cluster</i></h6><div class="pmulti" style="-webkit-column-count: 2; -webkit-column-gap: 40px; -webkit-column-rule-color: rgba(0, 0, 0, 0.0980392); -webkit-column-rule-style: outset; -webkit-column-rule-width: 3px; font-family: Gafata; font-size: 18px; margin: 8px 49.640625px; text-align: justify; text-indent: 1.5em;"><i>Unlike shared-nothing processes forked using Node's<a href="http://nodejs.org/api/child_process.html" style="color: #4040a0; text-decoration: none;">Child Process module</a>, Node's built-in&nbsp;<a href="http://nodejs.org/api/cluster.html" style="color: #4040a0; text-decoration: none;">Cluster module</a>enables forked processess to share sockets. This allows any number of processes to receive requests from the same interface and port, mimicking multithreaded execution.<br />No single programming or execution model is appropriate for all tasks - programming is making decisions about how to best complete a given task. Neither multithreading nor asynchronous execution magically makes work disappear, they merely move work to another thread where it is performed.</i></div>
<table id="decotable" style="border-collapse: collapse; font-family: Gafata; font-size: 1em; margin: auto; width: 889px;"><tbody>
<tr><th style="background-color: rgba(0, 50, 0, 0.498039); border: 4px solid rgba(0, 20, 0, 0.901961); color: white; font-size: 1.1em; padding: 5px 7px 4px; text-align: center; vertical-align: top;"></th><th style="background-color: rgba(0, 50, 0, 0.498039); border: 4px solid rgba(0, 20, 0, 0.901961); color: white; font-size: 1.1em; padding: 5px 7px 4px; text-align: center; vertical-align: top;"><i>Cons</i></th><th style="background-color: rgba(0, 50, 0, 0.498039); border: 4px solid rgba(0, 20, 0, 0.901961); color: white; font-size: 1.1em; padding: 5px 7px 4px; text-align: center; vertical-align: top;"><i>Pros</i></th></tr>
<tr class="alt2"><td style="background-color: rgba(0, 50, 50, 0.2); border: 4px solid rgba(0, 20, 0, 0.901961); font-size: 0.9em; line-height: 1.1em; padding: 10px 6px 0px 0px; vertical-align: middle;"><i>Async Execution</i></td><td style="background-color: rgba(0, 50, 50, 0.2); border: 4px solid rgba(0, 20, 0, 0.901961); font-size: 0.9em; line-height: 1.1em; padding: 10px 6px 0px 0px; vertical-align: middle;"><ul>
<li><i>Callback Hell</i></li>
<li><i>Limits parallelism to shared nothing tasks</i></li>
<li><i>Adds latency with parallel overhead</i></li>
<ul>
<li><i>Creating a closure</i></li>
<li><i>Copy-In/Out of all data shared between threads</i></li>
<li><i>Scheduling work task execution</i></li>
<li><i>Scheduling callback execution</i></li>
</ul>
</ul>
</td><td style="background-color: rgba(0, 50, 50, 0.2); border: 4px solid rgba(0, 20, 0, 0.901961); font-size: 0.9em; line-height: 1.1em; padding: 10px 6px 0px 0px; vertical-align: middle;"><ul>
<li><i>Callbacks help enforce error-prone synchronization</i></li>
<li><i>Node.js implements boilerplate infrastructure like event loops</i></li>
</ul>
</td></tr>
<tr class="alt"><td><i>Cluster Execution</i></td><td style="background-color: rgba(0, 50, 0, 0.2); border: 4px solid rgba(0, 20, 0, 0.901961); font-size: 0.9em; line-height: 1.1em; padding: 10px 6px 0px 0px; vertical-align: middle;"><ul>
<li><i>Larger memory footprint</i></li>
</ul>
</td><td style="background-color: rgba(0, 50, 0, 0.2); border: 4px solid rgba(0, 20, 0, 0.901961); font-size: 0.9em; line-height: 1.1em; padding: 10px 6px 0px 0px; vertical-align: middle;"><ul>
<li><i>Less&nbsp;Callback Hell</i></li>
<li><i>Utilizes multiple cores</i></li>
<li><i>Allows for over-subscription of cores and graceful performance roll-off</i></li>
<li><i>Improved resiliency against abnormal server exit</i></li>
</ul>
</td></tr>
</tbody></table>
<div class="figcaption" style="font-family: Gafata; font-size: 0.85em; font-style: italic; margin: 0.5em 49.640625px 8px;">
Tradeoffs between the callback programming model with asynchronous execution, and sequential programming with a cluster execution model.</div>
<div style="text-align: left;">
<span style="font-family: Gafata;"><br /></span></div>
</div>