These days, a lot of people also prefer PM2, which handles the clustering for you and also provides some cool monitoring features.
Then, add Nginx or HAProxy in front of several machines running with clustering and you have multiple levels of failover and a much higher load capacity.
Using the same example above, page-2.html SHOULD NOT designate
page-1.html as the target (canonical) IRI because this may
cause a loss of data. When page-2.html designates page-1.html
as the canonical, only content from the target IRI, page-
1.html, will be processed. page-2.html may be marked as a
duplicate of page-1.html and its content disregarded.
The first page of a multi-page article or multi-page listing of
items (since the first page is not duplicative or a superset of
the context IRI). For example, page-2.html and page-3.html of
an article SHOULD NOT specify page-1.html as the canonical.
This may cause a loss of data from page-2.html and page-3.html
as they will be marked duplicative of page-1.html with only
content from page-1.html being processed.
<ul>
<li></li>
<li></li>
<li v-for="page in pages" :key="page" class="pagination-numbers"></li>
<li></li>
<li></li>
</ul>?page=1