<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Microservices - Page 5 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Microservices&amp;p=4">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Microservices&amp;p=6">3.Next</a>
</p>
<p>can be individually scaled. In the monolithic approach, an application supporting three functions would have to be scaled in its entirety even if only one of these functions had a resource constraint. With microservices, only the microservice supporting the function with resource constraints needs to be scaled out, thus providing resource and cost optimization benefits. Despite its benefits, microservices architecture introduces challenges such as increased operational complexity, network latency, and the need for robust monitoring and fault</p><p>
<a accesskey="1" href="page.php?w=Microservices&amp;p=4">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Microservices&amp;p=6">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
